Three employees, three answers for one customer: how does that happen?
Three employees, three answers for one customer: it happens more often than you think in a company of 30 people. A customer calls and asks how his project is going. Within fifteen minutes he has heard three different stories, and nobody in the office has done anything wrong.
Picture the conversation for a moment. Your salesperson says: the quote has been signed, so it's under way. Someone from operations says: we're still waiting for materials. Your accounts department says: the deposit hasn't come in yet. Three people, three answers. And the annoying thing is that all three are right, seen from their own list. The customer hangs up knowing less than before he called. He now wonders whether you have things under control, while internally there is actually nothing wrong with the work itself.
So the problem isn't the people. It's where they look. The salesperson looks in his own Excel list. Operations has a mailbox full of supplier messages. Accounts works from the accounting package, and someone else has the most important detail on a notepad. Each source is correct on its own. Together they don't answer the one question the customer has.
With ten people you hardly notice it. Everyone sits on the same floor and you just call over to the colleague at the next desk. At around 30 people that stops working. That's where it really starts to pinch, and the cause is a simple sum. Once you know that sum, you also understand why the solution looks different from what most business owners think.
One place for each piece of information
In English it is called a single source of truth. We prefer to call it one version of the truth. It sounds like a term from an IT report, but the idea is very practical. There is one place where a particular piece of information is kept. Everyone looks at that same place. And that place is updated at the moment the work happens, not afterwards on a Friday afternoon. If that customer calls again, everyone he speaks to gives the same answer.
That doesn't mean everything has to go into one big system and that you throw away all your software. Many business owners are alarmed by that idea, and rightly so, because a project like that takes months. Your bookkeeping simply stays in your accounting package. Your email stays in Outlook. What changes: each piece of information gets one fixed place. The payment status sits in the accounts, the planning in one place, the agreements with the customer in one place.
How do you decide which place is leading? Ask two questions for each piece of information. Who creates this information first? And who suffers most if it is wrong? Usually the answer points to one system by itself. The payment status originates in the accounts, so that's where it belongs. The delivery date of materials comes from the supplier and lands with operations, so that's where you record it. Write those choices down on a single sheet of A4 and pin it up. It sounds old-fashioned, but it prevents someone from starting their own list again three months from now.
On top of that, you connect those systems to each other, so nobody has to retype anything. As soon as the deposit has come in, operations sees it too. As soon as the materials have been delivered, the salesperson sees it. Retyping is exactly the moment a second version of the truth is created, because sooner or later someone forgets it or types it in slightly differently.
Why it starts to pinch at 30 people
Between 30 colleagues there are 435 lines. That is the number of possible connections between two people in your team. With 10 people there are 45, and you can keep up with those easily over a cup of coffee and the odd phone call. With 435, nobody can. You no longer automatically know what your colleague has agreed, ordered or invoiced. That is why a company of around 30 people is the point at which you really have to sort this out.
What happens if you don't sort it out shows up in the diary. You start piling up meetings to close the gaps in your information. A monday kick-off, a status meeting with operations, a weekly slot with accounts about outstanding invoices. Each meeting is meant to bring the lists back into line. Lots of status meetings are not a sign of good communication, but of information that sits in too many places.
Three places where the second version is created
In practice we see the same three leaks again and again. The first is the personal list: the Excel sheet of the salesperson or planner that only he keeps up to date. The second is the mailbox: agreements with a customer or supplier that don't land anywhere else. The third is retyping: information that is moved by hand from one package to another. Go through your own business with these three in mind, and you will usually find within an afternoon where your customer is getting his three answers from.
When you close those leaks, you notice it in several places at once. There is less discussion about which version is correct. You make fewer mistakes, because nobody is working from an outdated list any more. The status meeting can be shorter or disappear altogether. And perhaps most importantly: decisions are made on the basis of facts, not on the basis of who shouts loudest in the meeting.
There is another reason to tackle this now. Many business owners want to get started with automation or AI. That only works if those tools can build on good, complete data. An automation that sends a customer a status update based on the salesperson's Excel sheet simply sends the wrong answer, just faster. One version of the truth is therefore the foundation for everything that comes after.
One version of the truth is not an IT project. It is making sure everyone in your business looks at the same thing. Start small: pick one question customers often ask, such as how their project is going, and find out how many sources the answer currently comes from. If there are three, you know where to start. Lead Innovation helps business owners with teams of around 30 people give each piece of information one fixed place and connect the systems they already have.