Hire an automation agency and the first thing built should be nothing. The work runs in four phases, in a fixed order. This is what they looked like on a real ninety-day plan for a premium, multi-market service company: details blurred, structure intact.
- 01Diagnose
- 02Prioritize
- 03Build
- 04Run & improve
What does the diagnosis find?
A five-star product wrapped in systems that lose the customer before the sale. The plan does not touch the product; everything around it leaked.
Ask for a quote and it lands hours later, by email, long after the buyer stopped deciding.
A booking tool from another decade, connected to nothing. Follow-up and repeat business live in people’s heads.
Two-thirds of the locations don’t show up on Google. In one city, a rival holds six times the reviews.
A premium price point wearing a website that doesn’t look it. The product reads five-star; the site doesn’t.
None of that is about the product. The diagnosis maps the whole machine, five areas, against the company’s own numbers.
Make the phone ring: marketing, ads, search and AI answers, reputation.
Lose nothing that arrives: answered, priced, booked, followed up.
The product itself. Here it already earned five stars.
Get paid for all of it: invoices, payments, books that reconcile.
The symptom and the cause rarely live in the same area. Here, the empty calendar was a capture problem: a price that took hours.
- 01Diagnose
- 02Prioritize
- 03Build
- 04Run & improve
What gets prioritized, and why?
Two rules: start where the money leaks, and build into what already works. Demand generation waits on purpose, because making the phone ring harder only sends more people into the same leak.
View data
| Piece | What happens |
|---|---|
| Door | Search & AI answers |
| Door | Ads |
| Door | Referrals |
| Door | The phones |
| Hub | One record per lead — every source tagged, whatever door it came through |
| Stage | Answered in minutes — a price on the spot, never "we’ll get back to you" |
| Stage | Booked — follow-up on the system, not on memory |
| Return | They come back, and they review — every job creates the next one |
Build the funnel first and everything added later has somewhere to land. Build the doors first and they leak.
- 01Diagnose
- 02Prioritize
- 03Build
- 04Run & improve
What gets built in ninety days?
Four deliverables, wired together from day one: one CRM as the hub, modern booking rails, a website that quotes in the moment, and the marketing engine behind them.
- 01Month one, the foundationThe baseline photographed: the day-zero numbers every review is measured against. The CRM live. The invisible locations claimed on Google.
- 02Month two, the premium faceThe website ships, quoting in the moment on every page. Booking rails wire in, invoices sync to the books, an AI backstop covers the phones after hours.
- 03Month three, prove and scaleThe marketing engine on. The old tool replaced in a parallel run, never a big bang. The dashboard live, and the first proof against the baseline.
One bet the plan refuses to make at signing: which booking platform carries the operation. That is settled in week one at a live demo, with the old tool running until cutover.
- 01Diagnose
- 02Prioritize
- 03Build
- 04Run & improve
What does "run and improve" mean?
The agency operates what it built. A weekly review, every week, and a scoreboard with four numbers on it.
Time to quote
hoursseconds
A price in the moment, on the site and on the phone.
Response time
hoursminutes
Every inquiry answered, day or night.
Findable on Google
a thirdthe map
Every location claimed, reviews accumulating.
Repeat work
by handon rails
Reminders, review asks, next-visit nudges.
View data
| Metric | Day zero → target |
|---|---|
| Time to quote | hours → seconds |
| Response time | hours → minutes |
| Findable on Google | a third → the map |
| Repeat work | by hand → on rails |
These are KPIs, not promises. The baseline is photographed at kickoff, and every review reports the movement, in both directions.
Why phase it at all?
Because each phase has to earn the next, and nothing should depend on the agency staying.
The roadmap past ninety days is gated on numbers the last phase proved.
The old system keeps running until the new one has carried real work.
Opened on day one. If the relationship ever ends, nothing turns off.
Movement against the day-zero baseline, reported in both directions.
"We don’t sell one tool for one area. We map the whole business, and we start where the money leaks."
The method without the worked example is in how to automate part of your business without regretting it.
Questions owners ask
What are the four phases of a business automation engagement?
Diagnose: map the whole business against its own numbers. Prioritize: start where the money leaks and build into what already works. Build: the deliverables, wired together from day one. Run and improve: operate against a baseline photographed at kickoff, with a weekly review.
Why diagnose the whole business instead of just the broken process?
Because the symptom and the cause rarely live in the same area. An empty calendar can be a capture problem, not a marketing problem, if quotes take hours to arrive. Mapping all five areas first keeps you from automating the wrong thing well.
How long does the build phase take?
The plan in this article runs ninety days: foundation and CRM in month one, the customer-facing pieces and booking rails in month two, the marketing engine and a parallel-run replacement in month three. Scope moves the number; the proof review around day thirty does not.
What happens if you stop working with the agency?
In an engagement structured like this one, nothing turns off. Every account is opened in the client’s name from day one, so the CRM, the website, the booking rails, and the data stay theirs. Ask any agency that before signing.
The first meeting starts with findings, not promises.The free Business Health Report reads your business and shows you what it found, in days.
Get Your Free Business Health Report