What does a mapped business actually look like?
Meridian Technical Services, thirty-two people in Miami, six to twelve week client projects. Three engines, forty-five steps, fifty-three handoffs.
We map how a business actually gets customers, delivers, and keeps them, then say where AI belongs and where it does not. This is one of ours, open to anyone.
Three engines. Every step, every handoff.
How you get customers, how you deliver, how you keep them. Everything a company does sits in one of those three.
- Every step. Who owns it, what tool it runs in, how many hours a month it takes, and whether AI can cut any of it.
- Every decision. The rule that decides it, or a note recording that there is no rule and it lives in one person's head.
- Every data source. Where information lives. It holds things. It does not do anything.
- Every handoff. Whether work moves on its own, waits for a person on purpose, or waits because nobody built the connection.
Fifteen steps in Meridian's Deliver engine. Two are marked as AI opportunities. Thirteen are not.
The same step, described by three people.
The owner describes the business the way it ran when he built it. The manager describes it by the result the owner expects, because producing that result is his job. The person doing the work describes what actually happens, which is usually a faster way he found himself, while the written procedure sits in a drawer.
All three are telling the truth. None of them can see the whole thing. So we interview each one separately, and we keep all three answers.
One step, out of forty-five. A deliverable going to a client.
"The significant ones. Anything going to a client that matters."
How long it waits"Not long. A day maybe."
"He reviews everything. Every deliverable, yes."
How long it waits"Same day if he's around. Two, three days if he's traveling."
"Everything. I've never sent something out that he didn't look at. Not once in four years."
How long it waits"Two days. Sometimes longer." Nine at the longest.
Later in the same interview, Marcus counted what was on his desk. One review since yesterday, one since Friday. "It's been a week."
That is one step. The map has forty-five.
The map follows the information, and marks where it stops.
Between every two steps, one of four things happens. The map records which, and why. That is what decides where AI goes.
Two steps in Meridian's Deliver engine, next to each other, with one handoff between them.
Package the deliverable
Tomás packages the deliverable, runs it against his own pre-send list, and messages Marcus that it is ready. The list is nine or ten things in his private notes, built from four years of what came back. Since he started using it, send-backs fell from one in four to one in eight.
Nobody has seen it. Asked whether Marcus knows: "I don't think so. He probably thinks we just got better."
The standard already exists, half written, by the person nobody asked. The map's first move is to finish it and have AI apply it before anything reaches Marcus. Measured by the send-back rate and the wait, not the hours.
Marcus reviews: approve or send back
"That's looking at something and knowing whether it's right. You can't write that down."
A person is here on purpose, and the map only calls it a gate when someone can say why. Danny, asked if the review should exist: "Yes. Absolutely yes. He catches things. Maybe one in eight, and it's always something that would have embarrassed us."
The judgment stays. What changes is that what arrives has already been checked.
The wait is the cost, not the hours.
The other opportunity in this engine is the Thursday client update, which Tomás assembles by hand from three systems and the crews' voice notes.
What usually arrives, and what this is.
| The usual assessment compared with a Blueprint | The usual assessment | A Blueprint |
|---|---|---|
| Who gets interviewed | The owner, sometimes one manager | The owner, the manager of each engine, and the person doing the work |
| What arrives | A report and a one hour readout | A map you open, click and correct |
| Where the numbers come from | Estimates | Hours asked per step, and the wait between steps |
| Where AI should not go | Rarely stated | Marked per step, with the percent |
| When it is wrong | It stays wrong | You correct it and regenerate |
| Handing it to a builder | Another discovery phase | Nine files per opportunity |
| Who can open it | Whoever gets the PDF | Up to ten people on your team |
| The format | A PDF | Plain markdown files, yours to keep |
| Your time | About an hour | Four to six hours across the month |
| Time to deliver | Two to three weeks | Thirty days |
Plain files, one per workflow.
Every file carries structured headers and links back to its node in the app, so the map and the files stay the same object. It is Google Cloud's Open Knowledge Format, published in June 2026: markdown, cross-linked into a graph an AI agent can follow, with a reserved index and a change log.
acme-plumbing/ ├── index.md START HERE. What this is, the two scores, how to read it ├── log.md version history and what's been marked done ├── diagnostic.md the written diagnosis ├── ask-your-business.md a ready prompt so any AI can answer questions about your map │ ├── get-customers/ │ ├── index.md this engine on one page: steps in order, every handoff │ ├── lead-intake.md │ ├── qualify-lead.md (Decision) │ ├── crm-hubspot.md (Data source) │ ├── lead-scoring/ an AI opportunity becomes a folder │ │ ├── index.md the step itself │ │ └── kit/ │ │ ├── index.md the reading order, and why │ │ ├── 01-spec.md 04-integration.md 07-guardrails.md │ │ ├── 02-blueprint.md 05-agent.md 08-harness.md │ │ └── 03-data.md 06-skills.md 09-build-plan.md │ └── handoffs/ │ ├── crm-to-sales-rep.md (Gap. Nobody built the notification) │ └── owner-approves-proposal.md (Gate. Intentional, and here is why) │ ├── deliver/ same shape └── keep-customers/ same shape
If you can read a text file, you can read your business.
Every quote on this page sits in one of those files, next to the step it belongs to. The export is part of a paid Blueprint. Here you can read the map. In the demo you can open it.
Watch it, then open it.
A short walkthrough of the finished map. The three engines, a handoff that is stuck, an AI opportunity, and the build kit that comes with it.
It works on a phone.
Go find where it's stuck.
No login, nothing to install. Click a workflow, open the drawer, follow a handoff.
Yours looks like this in thirty days.
Meridian is not a real company. It is a composite, assembled from thirty businesses we mapped in free sessions. The people, the sheet, the WhatsApp groups and the numbers come from those. It is built so an HVAC contractor, an agency, an engineering firm and an IT services company all recognise their own operation in it. Nothing here exposes anyone, and nothing here is invented.
More on how we work and what else we build: everything we do.