Where does your business keep the truth?

Six years ago I wrote a post arguing that having information about your customers is not the same as having it organized, and that businesses which know things about their own operation are several steps ahead of the ones that do not. I still believe every part of it. What I could not have written then is the part that makes it urgent now.

Back then, a disorganized record cost you a follow-up you forgot to make. Today it makes your agent tell a customer something that is not true.

The habit I picked up in a foundry

I spent eight years inside Tupy, the largest foundry in Latin America, building the systems the sale actually ran through, from the order to the tax book. I sat with logistics, with sales, with invoicing, with export. And the thing I learned there is the thing I keep finding in businesses a thousand times smaller.

A company almost never has one version of the truth. It has six, and they disagree politely.

Sales thinks the order shipped. Logistics knows it did not, because a document was missing. Invoicing has a number that is right for the tax authority and wrong for the customer. Somebody in the middle knows the real story and holds it in their head, and everything keeps working because that person is good and answers their phone. I have seen this in a foundry with thousands of employees and I have seen it in a bakery with four. Size changes nothing. Only the number of versions changes.

Later, when we started Sizebay, I wrote the first validation algorithm and built the first database myself, and I made the first sales with my own hands before I taught anyone else to make the next one. Doing both jobs teaches you something you cannot learn from either one alone: the record is not paperwork that happens after the sale. The record is the part of the sale that survives.

Since 2019, accredited by SEBRAE, I have run that same interview through hundreds of small and medium Brazilian companies: talk to every department, find out what the data already answers, build only what is genuinely missing. Nine times out of ten, what is missing is not a tool. It is a decision nobody made.

Why this suddenly matters more than it did

An agent does not remember your business. It reads.

Every time it answers, it reads what it was given: the request, whatever it can look up in your tools, and its instructions. If the status of a customer exists in a system it can check, it will check. If the status exists only in a WhatsApp thread on somebody's phone, the agent cannot check anything, and the thing it produces instead is the most plausible continuation of the sentence. That reads exactly like a fact. It is not one.

Janderson wrote about this from the model's side, about what happens when one long chat is asked to hold everything at once. I am writing about the same failure from the other side, the one I can actually do something about on day one of an engagement. The model is not the part of this you control. Your records are.

The test I use in the first meeting

I do not start by asking what CRM someone uses. I ask this:

Pick a customer. Without calling anyone, in under a minute, tell me what stage they are at, what was promised to them, and who is responsible for the next step.

If the answer takes ten minutes, or takes a phone call, or takes opening four things, the business is not ready to hand any customer-facing work to an agent. Not because the agent is not capable. Because there is nothing for it to be right about.

That test is free, it takes a minute, and it has never once given me a misleading result.

What "organized" actually means, minimally

People hear "structure your data" and picture a project. It is smaller than that. A customer record that an agent, or a new hire, can rely on needs five things:

That is the whole specification. It fits on an index card, and it is worth more than the feature comparison you were about to read.

The mistake I would save you from

The instinct is to fix this by buying something. I understand the instinct, and I have watched it fail often enough to name the sequence it fails in.

A business with no agreed record buys a CRM, imports the mess, and now has the same six versions of the truth plus a monthly bill and a login nobody uses. Three months later the real status is back in WhatsApp, because WhatsApp is where the customer actually is, and the CRM has become a place people update on Fridays if there is time.

The order that works is the opposite. Decide where the truth lives. Write down what a record must contain. Make filling it part of the work rather than a report about the work. Only then does the tool matter, and by then the choice is easy, because you know exactly what you need it to hold.

And here is the honest part: an agent will not save you from this step. It can help you do it, by drafting the record structure, by cleaning up duplicates, by reading old threads and proposing what a record should contain. That is genuinely useful and I use it. But an agent cannot decide which of your six versions is the true one. That decision is yours, and it stays yours.

What this has to do with Holybiz

At Holybiz, this is the second conversation we have with an owner, right after the one about what they actually sell. Not because we like paperwork. Because everything after it depends on it: which process is ready for an agent, what the agent is allowed to say, and whether anyone will be able to tell if it got something wrong.

It is the same craft I have practiced since Tupy and since Sizebay, and the same one I have taught through SEBRAE since 2019. Interview the operation, find out what the data already answers, build only what is missing. An agent is just the newest thing that method builds, and like everything else it builds, it is only as honest as what it is standing on.