Diagnose before you build: the habit that saves the year.

A guess with a price on it

A build quoted before the numbers are understood is a guess with a price on it. It may be a good guess. The company asking for a new CRM may need a new CRM. But the thing a company asks for and the thing holding it back are often different, and the only way to know is to look.

Looking first is the cheapest step in the whole engagement, and the one most often skipped, because it does not feel like progress.

What the symptom hides

Leaders describe the symptom they can see. Sales says the leads are cold. Finance says month-end takes a week. The website does not work. Each of those is true, and each sits one layer above its cause.

• Cold leads are often good leads, answered two days late
• A slow month-end is often three systems that disagree
• A website that does not work is often a message nobody can repeat

Build for the symptom and you get a faster version of the same problem.

What Diagnose produces

A short, written plan. Where revenue leaks, in order of size. The one or two things to fix first. What each would take, before you decide. What to leave alone, and why. It is written to be handed to anyone: your own team, another firm, or us.

The most useful page in the plan is usually the one that says what not to do.

Why it saves the year

Because the expensive mistakes are made in the first month. A platform chosen before the process is understood. A campaign scaled before anyone knows what a customer is worth. A hire made to run a system nobody will use. None of them look like mistakes at the time. They look like momentum.

Looking costs less than any one of them. And if the answer turns out to be smaller than you expected, you have saved the year and kept the plan.