01
What you hold
The list of your sources, from the management system to the shared workbook, with what each one really contains and in what condition.
We list your data, work out what it lets you decide and rank the work by how useful it is. You leave with a written plan, before you buy a tool or start a project.
The number of customers, a project’s margin or the hours billed change with the report you open. Everyone defends their own, and the decision waits.
An Excel workbook, an Access database, a management system, emails: each holds part of the information. Nobody has the full list.
A dashboard, a new ERP or an AI project is on the table. Before investing, it is worth knowing whether the data will hold up.
They know the files, the exceptions and the fixes done by hand. A departure, a retirement or an acquisition makes writing that knowledge down urgent.
You hold data about your customers and employees. You do not always know where it sits, who can see it or how long it is kept.
A reporting tool or a data warehouse was installed, but few people use it. Nobody remembers which decision it was meant to serve.
A data strategy does not necessarily lead to a large project. Sometimes it shows that your data is in better shape than you thought.
The plan then says so plainly: two things to fix, the rest to keep as it is. Nothing to buy for now.
01
The list of your sources, from the management system to the shared workbook, with what each one really contains and in what condition.
02
The questions leadership asks every month, tied to the data that answers them. The missing ones are named.
03
For customers, projects or invoices: the system of record, the copies that depend on it and the ones to retire.
04
For each domain, the owner, the roles that can view or change the data and how long it is kept.
05
The possible uses, ranked by their effect on your decisions and the effort they take. The first project is chosen to show a visible result quickly.
06
The indicators kept, their exact definition and how to present them to the people who decide.
Short write-ups, reviewed with leadership and with each domain owner.
01 Discovery
Know which projects are profitable, every month
EssentialOne sales figure, whoever runs it
EssentialCompare regions with each other
LaterFollow up on late invoices without checking everything by hand
EssentialReconcile hours with billing
ImportantFind a customer’s history without opening three files
EssentialSee team workload before accepting a project
Important02 Inventory
| Data | Where it lives | Owner | Quality | Personal information |
|---|---|---|---|---|
| Customers | Management system, CRM, sales workbook | Léa M. | Duplicates | Yes |
| Projects | Project software | Marc P. | Reliable | No |
| Hours | Excel timesheets | To assign | Incomplete | No |
| Invoices | Accounting software | Julie T. | Reliable | Yes |
| Employees | Payroll software, shared folder | Sophie D. | To validate | Yes |
Customers live in three places and hours have no owner. These two points come first in the sources of truth.
03 Priorities
04 Sources of truth
05 Roadmap
When systems need to be built or connected, the plan becomes the starting point of our development method. A good part of the discovery is then already done.
The register gathers what you need to know about the personal information you hold. It prepares the conversation with your legal advisor about Québec’s Law 25, without replacing it.
Once the task is chosen and the data checked, AI integration takes over, with a measured trial on your own examples.
01
Bringing customers into one source, cleaning a history, building the first dashboard: our data and development teams handle it if you wish, starting from the plan already validated.
02
Fixing one source exposes another: a duplicate that comes back, data entry that drifts, a file nobody maintains any more. At the planned reviews, we go over the register with you and adjust the order of the work.
03
Are the chosen indicators moving? Do your teams rely on the figures, or go back to their own files? We check it with you before starting the next phase.
04
New automation and AI tools keep coming out. We tell you which ones your data already lets you use, and what would need fixing to make the most of the others.
Each of these projects started from the client’s files, as they arrived. The Observatoire des tout-petits receives 97 sources from ten providers, mostly in Excel. HEC Montréal’s MID platform receives 21 files every week, loaded into a database of more than 1.9 billion dated measures.
Witify has understood our needs from day 1, educating us, guiding us and accompanying us through the evolution of our system for over 7 years now. They are the cornerstone of our technological development.
What leadership teams ask us before handing over the inventory of their data.
Another question? Write to us at info@witify.io or call 1 800 334 9031.
A data strategy helps guide and structure your company’s efforts to collect, analyze, store and use data. It ensures that your data is used optimally to support your business objectives, improve decision-making, drive innovation and maintain a competitive edge.
Without a clear data strategy, your data management efforts could be inconsistent and inefficient. They could also fail to comply with privacy and data protection laws.
An effective data strategy includes several key elements: clear objectives aligned with your business goals, an understanding of the availability and quality of existing data, and guidelines on data collection and management. It also plans the technological infrastructure needed to store and analyze data, measures to keep it secure and confidential, and a plan to develop your team’s skills.
With us, these elements take the form of short documents: the data register, the map of sources of truth, the priorities, the rules and the roadmap.
Data strategy must be closely integrated with your overall business strategy. Its objectives should directly support your business goals. For example, if your business objective is to improve customer service, your data strategy could include collecting and analyzing data on customer behavior and preferences to improve the customer experience.
It is crucial to integrate legal and ethical considerations from the outset of creating your data strategy. This can include seeking legal advice to understand applicable laws and regulations, such as Law 25 in Québec. It also takes policies and procedures to ensure data consent, confidentiality and security, along with monitoring and auditing mechanisms to ensure ongoing compliance with these policies.
Our data register shows where personal information sits, who can access it and how long it is kept. It prepares the conversation with your legal advisor without replacing it.
The time needed to develop a data strategy can vary considerably, depending on the size of your company, the complexity of your operations and your specific objectives. It can range from a few weeks to several months.
It is important to note that developing a data strategy is an evolving process. It needs to be reviewed and updated regularly to remain relevant and effective.
With the domain that holds up the most decisions, often customers or hours. We first list the sources that touch that domain, in a single register. The others join in later phases, without stopping everything.
Excel is not the problem in itself. It becomes one when a workbook serves as a shared database: our article on Excel shows where that line is.
The strategy sets what to do with your data and in what order. Governance says who answers for each piece of data and under which rules: it is part of the strategy. A BI (business intelligence) project installs a tool to present the figures. It comes after.
Sometimes the plan ends with a cleaned-up workbook and a single dashboard. When more is needed, data management structures the sources and data visualization designs the dashboards.
Not a thick document. What you need is a short check: the data the task uses, its quality, the person who answers for it and what an outside service is allowed to read. Incomplete data gives incomplete answers, whatever the model.
Choose the task first for the time it frees or the errors it prevents. A trial on a data set that is already ready can move ahead in parallel. What follows is the work of our AI integration service.
It depends mostly on the number of sources to list, the teams to meet and the level of detail expected. Three tools and one precise question do not call for the same engagement as dozens of sources spread across several departments.
After a first meeting, we propose an engagement with its scope and its price. If development follows, our article on the cost of custom software details what drives the price of a project.
A person who sponsors the project in leadership, one contact per department involved and someone who knows your systems from the inside, in-house or at a supplier. For most participants, involvement comes down to a few targeted meetings.
If you wish, we sign a confidentiality agreement before opening your files.
In 30 minutes, an expert listens to how information moves through your company and points you to the first project worth a look.
Free. No commitment. Reply within 24 hours.
Names and figures shown in the interfaces are examples.