What actually happens in the ninety days.
Most agencies won't show you this. Not because it's secret — because writing it down means you can be held to it.
This is the whole install, day by day. What gets built. In what order. What I need from you and when. What you're holding at the end. If you hire me, this is what you bought. If you don't, take it and run it yourself — the order matters more than who executes it.
Book the audit call — we'll walk your version of this in thirty minutes.
Baseline frozen. Then infrastructure. Then ads. Never the other way round.
This is the only non-negotiable in the entire engagement, and it's the reason most of what you've paid for before didn't work.
Every agency you've hired started at step three. Ads live in week one, because ads live in week one is what the invoice implies. But a lead landing in a system that can't catch it is a lead you paid for and lost — and you can't even prove you lost it, because nobody froze the number it should have been.
So: I do not touch your ad account until the system underneath it can hold what it catches. Usually that's day fourteen.
If that sounds slow, it's because you've been sold speed before. Speed into a leaking bucket is just a faster way to spend money.
Diagnose, baseline, position. No ad account touched.
Kickoff and access
Scripted kickoff — scope, cadence, the ninety-day plan. I request access to everything: ad accounts, website, whatever CRM or spreadsheet you're running, WhatsApp, analytics. You get the intake form.
The data pull
Growth Score run properly, with real numbers instead of impressions. Lead data, sales data, ad account history, WhatsApp threads. Everything that exists gets pulled.
The baseline is frozen
The most important day of the ninety, and the one nobody else does. I lock your Day-0 numbers: lead volume, response time, lead-to-qualified rate, qualified-to-close rate, cycle length, revenue by source, and your hours. Then the file is closed and never edited again — not by me, not at day 90, not when the numbers are inconvenient. This is the day I make it impossible to lie to you later. Same day: the costed leak map, in your currency, with the method shown.
Positioning lock
ICP, offer, message, value proposition. This is the brief that drives every ad and every page after it. Skip it and you spend three months optimising the wrong promise.
Campaign and tracking plan
Campaign structure designed for lead quality, not lead volume — those are different builds, and most agencies quietly ship the second while invoicing for the first. Creative brief written. Tracking scheme planned.
Full admin access. Completed intake form. Brand and creative assets. If these are late, the ninety days start late — I'd rather say that now than manage the resentment in week six.
MILESTONE · DAY 5 — Baseline frozen. Positioning locked. Campaign designed.
Build everything the leads will land in — before any lead lands.
The CRM core
Your CRM is deployed from a pre-built install, then mapped to your actual sales process — the pipeline stages your team really uses, not the ones a template thinks they should. Custom fields configured to how you actually sell.
The landing page
Written to filter for quality rather than harvest clicks. A landing page that converts everyone is a landing page that's about to waste your closer's week.
Capture and WhatsApp
Every entry point wired into one place — web forms, WhatsApp inbound, lead forms, search. WhatsApp Business connected with a proper PDPL-compliant opt-in, because in this region that isn't optional and getting it wrong is expensive.
Tracking and attribution
Pixels, conversion tracking, source attribution — installed and verified end to end. Verified means I send data through and watch it arrive, not that I pasted a tag and hoped.
Conversion logic
Speed-to-lead automation — the instant first response that decides whether the lead is yours or your competitor's. Then qualification and scoring, so your team stops spending Tuesday on people who were never going to buy.
Sequences and dashboard
Follow-up sequences built — the ones that fire whether or not anyone remembers, because L.02 is where most of your money is currently going. Booking automation. Pipeline automation. The revenue dashboard.
Follow-up copy approved in your voice. Ad account admin confirmed.
MILESTONE · DAY 12 — Infrastructure live. Tracking verified. Dashboard rendering.
Test it with a real lead. Then launch.
The QA gate
A live test lead goes through the entire path — ad, landing page, CRM, speed-to-lead, follow-up, dashboard — and I watch every step. Anything that leaks gets fixed before a dirham of spend. A full day spent finding my own mistakes on my own time, because the alternative is finding them with your money in week four. Same day: your team gets onboarded. A system nobody uses is a system nobody bought.
Launch
Ads go live, tuned for qualified leads. I run and monitor them personally.
Monitor and reactivate
Daily monitoring. Confirming leads flow and follow-up fires. And the dead-lead reactivation campaign — the leads you already paid for and lost, worked properly. It usually produces the first visible win, and it costs nothing new, because you already bought those people once.
First optimisation
Weak ad sets killed. Targeting and copy pushed toward quality. First weekly review — we walk the dashboard together. Not a status update. The actual numbers, in the actual system, in front of you.
Stabilise
Qualified-lead flow confirmed as measurable. Early wins documented against the frozen baseline. Weekly rhythm locked for the rest of the ninety.
MILESTONE · DAY 20 — Campaign live. Leads flowing into an engine that holds them. Dashboard real. Founder using it.
Prove it moved. Separately from the ads.
Daily optimisation on quality, not volume. Follow-up timing and structure A/B tested. Qualification and speed-to-lead tuned. Weekly reviews on a fixed agenda.
And one thing that matters more than all of it: infrastructure metrics are tracked separately from ad metrics. Response time, lead-to-qualified, qualified-to-close — kept apart from spend and cost-per-lead.
I do this because it's the only way to prove the system lifted your conversion rather than the traffic. It also makes it substantially harder for me to take credit for something I didn't do. Any agency can point at a revenue chart and stand next to it. Separating the two is how you find out whether you bought infrastructure or just bought attention.
GATE · DAY 45 — Live dashboard. Measurable qualified-lead flow. Before-versus-current, documented against the frozen file.
Scale what works. Cut what doesn't.
Winning ad sets scaled, the rest killed without sentiment. Follow-up and nurture deepened. Lead scoring refined against real closes rather than assumptions. Proof artifacts captured at each checkpoint, so the case study assembles itself rather than getting reconstructed from memory in month four.
Trend lines against baseline. Pipeline velocity. Source-level return.
GATE · DAY 75 — Metrics clearly past baseline.
Prove it, hand it over, leave.
The full before-and-after
Against the file frozen on Day 3. Every metric. Including any that didn't move — those go in the same document, because a report that only contains wins isn't a report.
Team training and SOP handover
The system is documented and taught to the people who'll run it. This is where "you own the infrastructure" stops being a line on a website and becomes a folder your ops person actually opens.
Exit growth review
And a twelve-month roadmap. Then I leave. If a retainer makes sense I'll say so, and it's a separate decision made with ninety days of evidence — not a renewal that quietly happens because nobody cancelled it.
GATE · DAY 90 — Documented result. System handed over. You holding it.
On day 91, when I'm gone.
Your CRM, configured to how you actually sell — not to how a template assumed you would.
Follow-up sequences that fire without anyone remembering to fire them.
Speed-to-lead automation that answers before your competitor does.
Attribution that tells you which spend produced paying clients, not which produced leads.
A revenue dashboard your team already uses, because they were trained on it in week three.
Documented SOPs.
The frozen Day-0 baseline, and the Day-90 numbers next to it, in the same file.
None of it is rented. None of it stops working because I stopped invoicing. If you fire me on day 91, you fire me holding all of it.
That's the whole product. It's also why this is by application and why I take five at a time — I deliver these myself, and there are only so many ninety-day blocks in a year.
The honest caveats.
This is the shape, not a contract
Your business will move days around. A firm with no CRM at all runs differently from one with a CRM nobody uses. The order is fixed — baseline, infrastructure, ads. The calendar bends.
It only works if you turn up
The days you owe things are marked. When they slip, the ninety days slip. I've never seen an install fail because of the system; I've seen them stall because access took three weeks.
It doesn't fix an operations, pricing, or hiring problem
If your real constraint is one of those, this install will produce a beautifully instrumented view of a problem I can't solve — and I'd rather tell you that on a thirty-minute call than in month two.
Want to see what your version of this looks like?
Thirty minutes on your actual pipeline. I'll map where your leads enter and where they die, and you'll leave with the sequence — whether or not you hire me.
If I'm not the right fit I'll say so on the call.