The system for an IT company that we rolled out to ourselves first

There is a practical reason, not a philosophical one. When you roll a system out at a client for the first time, every flaw in the flow is paid for by their team — in time, in frustration and in trust in the project. When you roll it out at your own company, you pay for it.

Second reason: only after going through a rollout do you know how long one really takes and what changes first in people's habits. That is not in any documentation.

Third: anything that gets in the way of daily work we fix immediately, because we are both the user and the team building it. Features a client sees with us have already survived daily use.

The enquiry and the client record — every contact ends up in one place, no matter where it came from.

A call with a note and a next step. This changed the way we work more than anything else: a conversation without a recorded next step counts as unfinished. No more “I'll get back to you one of these days” that nobody remembers.

A task with a deadline and an owner. Not a task in a group chat, but a task with a name on it.

The quote and its approval — with clear permission levels, so it is obvious who may send what and who confirms.

A commission calculated from the same job, instead of being assembled from memory in a spreadsheet at month end.

Email and the conversation archive next to the client, including transcripts of recorded calls — so what was agreed does not depend on who happened to be on the line.

Habit, not technology. For the first few weeks people work both the old way and the new one, because the old way is faster until the new one settles. That is normal and it passes — but only if it is not punished. Make an issue of every unrecorded call and the team will record the calls and stop telling you the important things.

Second: the temptation to switch everything on in the first round. We made the same mistake we see at clients — we wanted the whole system right away. What actually worked was the order: first enquiries and calls, then tasks, then quotes and approvals, then commissions.

Third: a report nobody looks at is work thrown away. We kept only the overview that actually gets used in the morning.

No enquiry gets lost between the inbox and the phone any more — and measured in missed work, that is the most expensive item of all.

The overview is accurate every day, not only on the day somebody sat down to tidy it.

Commissions are no longer agreed from memory, which removed an entire category of uncomfortable conversations.

And last, the least measurable and the most important: the feeling that you have forgotten something goes away. We write about that separately, because it is the part that never appears in a business case and is felt the most.

The first question is not which tool, but where your data disappears. At most service businesses that is between the conversation and the task: the agreement exists, but nowhere except in someone's head.

The second question is who may see what. With us, quotes, approvals and commissions have been separate permission levels from day one, because that is easier to set up at the start than to separate afterwards.

And third — do not roll out a system in your busiest week. You roll it out when there is air, because the first two or three days are slower. After that there is no going back.