They came to us for agents. We started with questions.
They came with a budget and a short list of tools. We did not talk about agents on the first call. We asked to see the work.
The email said they wanted agents. It usually does.
A project-based services company, back office drowning, came to us with a clear ask. Build AI agents to move work through operations faster. They had a budget for it and a short list of tools they were ready to buy.
We did not talk about agents on the first call. We asked to see the work instead.
The ask is always a tool. The problem is never a tool.
By the time a company reaches out, they have usually already decided what they need. More automation. A model wired into the CRM. Something that makes the backlog move.
That instinct is not wrong. It is early. The tool you ask for is a guess about a problem you have not mapped yet, and a guess, automated, is just a faster way to be wrong.
So we start where it is least glamorous. We ask you to walk us through your most painful workflow, step by step, out loud, the way it actually runs and not the way the org chart says it runs.
The three questions before any agent
Before we write a line of anything, we ask three things.
- Can you draw this process on a whiteboard in under five minutes?
- Does more than one person do it the same way?
- When the work is done, does a human still have to make a judgment call on the output?
If the answer to the first one is no, you are not ready for an agent. You are ready to write the process down. Most companies are not behind on AI. They are behind on knowing what their own people do all day.
This client could not draw it in five minutes. Nobody in the room could. That was the first finding, and it was worth more than anything on their short list.
What the map showed
We walked their most painful workflow end to end. Twenty-three steps. Eleven of them were manual handoffs, someone copying a number out of one system and typing it into another that should have been talking to the first one all along.
You cannot automate what you have not mapped. And most companies have not mapped it.
Buried in those handoffs was a disagreement nobody had named. Sales and operations did not agree on which work was real, which is the exact undocumented-standard problem from the last piece in this series. That disagreement had quietly buried roughly $388K in recoverable operations value. Not projected. Measured, in the first two weeks, by walking the process instead of pitching a fix.
The number was not hiding in one dramatic thing. It was fifty small things, each costing a few thousand a year, that nobody had time to question because that is how it had always been done.
Then, and only then, the agents
Once the process was on paper and the definitions were shared, the agents finally had somewhere to stand.
We put a reasoning layer on the tools they already ran. It held the documented standard and checked each live piece of work against it. It closed the eleven manual handoffs by moving numbers between systems that used to need a person in the middle. It surfaced the question a busy operator would have skipped.
Time from that first discovery call to deployed agents was seven days. Not seven weeks. The build was fast precisely because the thinking was done first.
The reporting work that used to eat 340 hours a quarter came back to the team. Same people. Same headcount. They spent the recovered time on judgment, the part they were actually hired for, instead of moving numbers between screens.
Why we start with questions
Here is the uncomfortable version, and it is the whole point of this series.
If we had built what they asked for on day one, we would have automated the mess. We would have shipped their unmapped, unagreed process at speed, with a confidence it never earned. It would have looked like progress for about a quarter. Then the same disagreement would have resurfaced, faster and harder to unwind.
Process before prompts. The agent is the payoff, not the starting point.
The questions are not a delay before the real work. The questions are the real work. The agent is what you get to build once the questions have answers.
They came for agents. They kept us for the map.
The thing that changed their operation was not the model. It was naming the twenty-three steps, cutting eleven handoffs to zero, and agreeing, on paper, what the work was supposed to be. The agents made that durable. They did not create it.
If a team comes to you asking for a tool, the most valuable thing you can do is ask to see the work first. That is not consulting theater. It is where the $388K was.
Ask to see the work first.
If your operation has a workflow with more manual handoffs than anyone wants to count, that is the conversation worth having. Thirty minutes, no deck, no pressure. We will start with questions.
Talk to us →This is for operators who came looking for agents and are willing to hear that the real fix is upstream of any tool. Fast-scaling operations teams, especially in SMB and mid-market ops, are exactly who this discovery-first approach is built for.