The 90-day AI implementation roadmap I run inside client firms
This is the exact 90-day AI implementation roadmap I run inside client firms, published in full: two weeks of diagnosis, agreed workflow improvements by Day 90, counsel throughout – and how to run the same plan yourself if you have the engineering capacity in-house.
When a founder asks me what actually happens across the ninety days, I send them this page. There is no abridged version and no gated version; this is the whole method. Keeping it secret has never won me an engagement, because the plan was never the hard part. The hard part is shipping against it, week after week, inside a firm where everyone already has a full-time job. The buyer pays for the execution, not the secret. If you are still weighing whether the role itself makes sense, start with what a Business Automation & AI Specialist does; this piece assumes you are past that and want the plan.
Why ninety days
The ninety-day window includes diagnosis, implementation, testing, and adoption. The diagnostic selects a useful scope that fits that window and the fixed fee. Delivery milestones depend on the agreed work, access, and review requirements; a larger transformation is not implied.
The roadmap at a glance
Three phases. The first two run in sequence; the third runs alongside both.
Stakeholder interviews, a full workflow audit, and an ROI-ranked opportunity matrix, ending in a signed-off ninety-day plan the firm keeps either way.
Agreed workflow improvements, with delivery milestones set during the diagnostic. Each ships instrumented, documented, and owned by the client team.
A weekly leadership call, async access between calls, and guidance on AI vendors and data policy as those decisions come up.
Days 1–14: diagnosis, not building
Nothing gets built in the first two weeks, on purpose. Most firms carry ten candidate problems and have the budget and attention for three; the expensive mistake is not building badly, it is building the wrong thing well. So the first fortnight is spent interviewing everyone who touches the work, auditing how it actually flows – not how the org chart says it flows – and ranking every opportunity by return: hours consumed, revenue at stake, and how often the founder is the bottleneck in the middle of it.
The phase ends with a signed-off ninety-day plan. The firm keeps that plan whether or not we continue; it is a complete piece of work on its own. This is also why I offer the diagnostic standalone: $5,000 for the two weeks, credited in full toward the engagement if the firm goes ahead.
Days 15–90: build sprints
Then implementation begins against the scope authorized by the client. I configure existing software where it fits, connect tools, and build only what is needed. Each improvement is tested against agreed acceptance criteria and introduced with the people who will use it. The result is working operations, not a presentation deck.
Every system ships with the same six things, without exception:
- Monitoring – every call traced, every error logged, visible on a dashboard.
- An evaluation suite – so a prompt change can never silently degrade quality.
- A founder-controlled kill switch – one toggle, no tickets, no waiting on me.
- A one-page runbook – what it does, who owns it, what to do if.
- Full IP transfer – the code, the prompts, the credentials are the firm’s.
- A trained team – the people who will run it once I step back.
This list is the difference between AI that demos well and Automations that keep working after handover. It is also why each system carries a thirty-day stability commitment after handover: the ownership transfer is real, not theoretical.
A 90-day AI plan nobody ships against is a strategy deck with dates on it.”
Days 1–90: embedded counsel
The third phase runs underneath the other two for the full ninety days. A weekly leadership call keeps strategy and delivery in the same head instead of handed between a strategist and a builder. Async access covers the questions that cannot wait for Tuesday – “should we sign with this AI vendor?”, “is this safe with client data?” – and the vendor and data-policy guidance means those decisions stop being made in isolation on a Saturday night.
Running the roadmap yourself
If you have real engineering capacity in-house, you can run this AI implementation roadmap without me, and I would rather you did that than hire the wrong outside help. Three rules carry most of the value. First, pick one workflow – the one consuming the most senior hours – and resist the committee’s urge to start four. Second, get it running on real work and let it hold for a few weeks before starting the second; a system handling real work teaches you more than three in development ever will. Third, instrument everything from day one: monitoring, evaluations, a kill switch, a runbook. The honest caveat is that the constraint is rarely knowledge. It is senior engineering time, and the discipline to keep shipping when client work pulls everyone back.
What Day 90 looks like
For illustration, recovering fifteen usable hours a week at an assumed loaded labor cost of $80 an hour over fifty weeks represents $60,000 a year in recovered capacity before running costs. This is not an observed average, guaranteed result, or reduction in payroll. The diagnostic establishes a firm-specific forecast; the review measures what was actually achieved.
The commercial terms are equally public: $20,000 fixed for the Founders’ Edition – the first three firms, with continuation month-to-month afterwards, $1,500 for me to carry the maintenance instead of your team or $4,000 to keep new systems shipping – or $30,000 at Standard rates, paid 50/50 across the engagement. The full breakdown, alternatives included, is in what a Business Automation & AI Specialist costs.
Common questions
How long does AI implementation take for a small firm?
For a firm of eight to thirty people, plan on about ninety days: two weeks of diagnosis, then implementation, testing, training, and handover against an agreed scope. Milestones and client dependencies are established during the diagnostic.
What happens in the first two weeks?
Diagnosis, not building: stakeholder interviews with everyone who touches the work, a full workflow audit, and an ROI-ranked opportunity matrix, ending in a signed-off ninety-day plan the firm keeps whether or not the engagement continues.
Can I run the roadmap without outside help?
Yes, if you have engineering capacity in-house. Pick one workflow, get it running on real work before starting the second, and instrument everything: monitoring, an evaluation suite, and a kill switch. The method is public; the usual constraint is senior engineering time and the discipline to finish.