Centralize project information without multiplying tools: SME guide (2026)
AI and productivity in business
17.04.26
•
10 min
Centralizing project information means bringing decisions, documents, tasks, and conversations together in one place so every team member can find what they need without digging through five different tools. According to the McKinsey Global Institute, knowledge workers spend 1.8 hours a day searching for information. For a 20-person SMB, that adds up to 36 team hours lost per day, the equivalent of 4.5 full-time positions. The reality on the ground is even starker. Meeting notes in Drive, tasks in a spreadsheet, client conversations in emails, decisions in the head of whoever was there. A design office manager sums it up: "I get called and told: what’s the latest thermography? So I rely on my memory. I’ve been looking for 15 minutes."
What scattered information costs
According to BetterCloud and Statista (2024), SMEs with fewer than 200 employees use an average of 42 to 44 SaaS applications. Each tool creates its own silo. The Asana Anatomy of Work study (2023, 9,615 respondents) shows that 58% of knowledge workers' time is spent on coordination and information search, compared with 27% for skilled work.
Using McKinsey's low-end assumption (1.8 h/day), the hidden cost exceeds 150,000 euros per year for 20 people, at the average fully loaded cost. And this figure covers only search time, not duplicate work or rework decisions due to lack of records. As another prospect says: "We recreate the same output data every time even though we don't need to do so"
Which centralization strategy should you choose?
Faced with fragmentation, SMEs have three real options. None is universal. The right choice depends on what is already in place and what the team will accept changing.
Criterion | Replace everything with an all-in-one | Keep your tools and connect them | Add a knowledge management layer |
|---|---|---|---|
In practice | Migrate projects, docs, tasks, and communication into a single tool | Connect existing tools via Zapier, Make, or native APIs | Keep your tools and add a tool that connects them, indexes them, and makes them searchable |
Examples | Notion, Monday, ClickUp | Teams + Drive + Trello + automations | 5Days (SharePoint, OneDrive, Salesforce, Jira, Confluence connectors) |
What you gain | One interface, fewer switches between apps | Each tool remains best in its role | No migration, cross-functional visibility across the whole project, AI search |
What you lose | Migration time, resistance to change, features that are often mediocre across the board | Fragile maintenance, breaks as soon as a connector changes, no overall view | Depends on the quality and coverage of the connectors |
When it's the right choice | Team that's just starting out or doesn't yet have an established ecosystem | Technical team with someone to maintain the automations | SME that already has Teams/Drive/CRM in place and refuses to change everything |
Main risk | The team doesn't adopt it and quietly goes back to its old tools | Connections break and no one fixes them | Partial adoption if the tool doesn't deliver visible value quickly |
The common reflex is to look for the single tool. But a team that has been using Teams and SharePoint for three years is not going to migrate everything overnight. A prospect puts it this way: "What I'm afraid of is splitting the information into two parts. I'm even sure it will be done badly" The third approach, project knowledge management, consists of keeping the existing tools and adding a layer that connects, indexes, and makes all the project data searchable. For a comparison of tools that fit this approach, see our analysis of Copilot for meetings (D3).
How to centralize in practice
Audit before choosing. Map where information lives: decisions, minutes, documents, tasks. Identify the 2-3 most painful flows. Simple test: ask three colleagues to find a decision made two months ago. More than 5 minutes? You have a problem.
Define a source of truth by category. Tasks in the project tracking tool. Decisions and their context in knowledge management. Approved documents in Drive. The important thing: everyone knows where to look for what.
Start with a pilot project. Don't roll it out everywhere at once. Migrate only the useful data from the chosen project: minutes from the last 3 months, active reference documents. A prospect confirms it: "To avoid transferring all our documents, every X weeks we should ask ourselves what the new files are" (NCA Environnement, prospect interview 5Days).
Invest in adoption. You need at least one internal champion who uses the tool first and leads by example. A client sums up the success criterion: "If it's a simplification approach, yes. If it's just one more tool, not sure". Adoption depends more on fitting into habits than on feature richness.
Measure after one month. Three indicators: the time it takes to find information, the number of requests "do you know where the latest minutes are?", and the completeness of the knowledge base.
What AI changes about centralization
The difference between a well-organized Drive and an AI-augmented knowledge management tool: querying. Semantic search understands meaning, not exact words. If the meeting minutes say "approval of the budget envelope" and you search for "budget decision," the AI finds it. On a 12-month project with 50 meeting minutes, that's the difference between 15 minutes of digging and 30 seconds.
AI also makes cross-cutting summaries possible ("What decisions have been made with the client since January?") and the automatic extraction of tasks from meeting minutes. According to Fellow.ai, 44% of the action items decided in meetings are never carried out. Automation removes the re-entry step, where tasks get lost. This is the realm of AI applied to turning exchanges into actions.
FAQ: centralize project information
Pourquoi centraliser les informations d'un projet ?
Quel outil pour centraliser les données d'un projet en PME ?
Quelle différence entre centralisation et knowledge management projet ?
Comment centraliser sans créer un silo de plus ?
Combien de temps pour centraliser l'information d'un projet ?
La centralisation est-elle utile pour une petite équipe ?
The cost of inaction is measurable: hundreds of hours per year spent searching, asking again, recreating. The solution does not come from a magic tool, but from an assessment of your workflows and human support for change. 5Days makes it possible to centralize a project’s meetings, documents, and tasks and query them via AI, without replacing your existing stack. To structure daily operational tracking: how to follow your projects when you don’t have a PMO.
