It is still one job. The job changed shape.
Find where revenue stops. Clean up what is in the way. Run it. I have done this inside very different companies and it has been the same three moves every time. What changed is what the cleaning up means.
What cleaning up used to mean, and what it means now
Scrubbing fields somebody forgot to fill.
Connecting the mail, the calendar and the calls so nothing has to be filled.
Chasing the team to log the call.
Going back for the calls that were logged as good call, follow up.
A stage picked on a Friday to make the forecast look right.
A forecast that can point at the conversation it came from.
A process document nobody opened.
How you work, written in plain words that the system follows.
Look, remember, write it down, run it
The order matters more than any single step. Most of what goes wrong is doing the fourth one first. Pick what is stuck and the same four moves are drawn on it.
Read what happened, not what the plan said.
Read the last thirty first calls and what happened after each. The drop is between the call and the second touch, and it is not discipline. Nobody could tell which calls had earned a second one.
Nothing gets built in week one. There is almost always one place things die, and it is almost never the place people assume.
Get the record to remember.
Connect the mail, the calendar and the call recorder, and read the last quarter in. The record now holds what was said on every one of those calls, not the word “good” in a notes field.
Merge the duplicates, close the deal from April. This part is boring and it is where the value is.
Write down how you work.
One page on what a second call has to have earned: who decides, what date they are held to, and what it costs them to do nothing.
Four years of philosophy taught me to say exactly what I meant and defend it, and most of a broken CRM is people using one word for four different things. That page is the business now.
Run it, and show what fell.
The follow up goes out on time, written from the call. Stalls get chased. The weekly read counts the second calls that happened and the ones that died.
A report that only ever shows wins gets ignored inside two months, so the number that went down is on the page.
What changes, and what never does
Changes every time
- The industry, and the vocabulary that comes with it
- Which tools are already in the building
- Whether the problem is demand or the machinery behind it
- How much has to be rebuilt before anything can run
- What the words say, because that is the client's voice and not mine
Never changes
- Look first. Nothing gets built in week one.
- The cleanup happens before the clever part
- One place where the truth about revenue lives
- Something runs at the end, not a document about running
- The number that went down is on the page
If a description of the work only makes sense for one industry, it is a case study wearing a service page. This is the part that travels.
What I take on, and what stays yours
Agree it in the first conversation, not in month two.
Mine
- The record, and everything wired to it
- The written page on how you work, kept current
- The cleanup, all of it
- Follow up, written and sent
- The weekly read on what moved
Yours
- Pricing, and what a piece of work is worth
- Who you will and will not take on
- Delivering the work itself
- Anything a lawyer should decide
- Saying no to a bad fit
The line is where it always was. I run the machine. You stay the person the customer is buying from. And the work here is built with AI tooling, to a production standard. Better you hear that now than find it later. It is why a small practice can carry it, and it does not replace the judgment, the part you are buying.
One problem, six vantage points
This is the part a timeline cannot show, and it is the part you are hiring. It is also why the work is not limited to whatever engagement happens to be running this quarter.
It used to mean the fields: pricing nobody can explain, a pipeline that is a guess, follow up that depends on one person remembering. Now it means going back for what the fields threw away, and building it so nothing is thrown away again. Somebody has to do that before anything clever is worth doing. It is not a glamorous title and it is the honest one.
Making payroll for five people out of revenue you personally brought in changes how you price, how you scope, and how fast you tell a client something is not worth doing.
Six plus years inside a product at that scale is the only way I know to calibrate what good looks like, and it is the one thing you cannot get from working on small systems for a long time.
The largest deal in the company's history, won on wireframes drawn in house with no deal team behind it, which is what you can do when you know the product well enough to invent the half that is missing.
Helping architect a CRM out of nothing teaches you that a field exists because somebody decided it should, usually for a reason nobody wrote down. That is still true of every system I inherit.
Every system I have built since answers to that, and most software is designed by people who have never once been that person. This is the seat that empties first when a business starts to remember on its own.
Pick a seat. The janitor is driving. That is the seat this practice is in now. There is a trailer.
Start with whatever is stuck.
Thirty minutes, no deck. If the answer is that you need someone in house, I will say that.
Two front doors, by the shape of the business: a services firm whose deals arrive through relationships, or a product that works and nobody knows about.