The Rollout Plan
The First 90 Days of AI in Your Business.
What a real implementation looks like — not the keynote version. Week one corrections, month two expansion, and the honest month-three evaluation that tells you whether to keep building.
Quick Answer
What should the first 90 days of AI implementation look like in a small business?
Start with a small adjustment, not a company-wide change. Week 1: put the system into limited real-world use and sharpen it based on how employees actually interact with it. Weeks 2–4: expand its use, connect it to the next step, and begin measuring time saved, errors prevented, and opportunities recovered. Month 2: build the next piece, reusing most of the technology from the first. Month 3: evaluate honestly — if it worked, build the next piece; if not, understand why before investing more.
- →Successful implementations begin with a small adjustment, not a transformation
- →Week 1 is about sharpening the system — progress over perfection
- →Small corrections are normal, not failures — employees use systems differently than developers expect
- →Month 2: reuse useful parts of the first solution for the next piece
- →Month 3: measure hours, errors, opportunities — then decide whether to keep building
Before Day One
Start smaller than you think you should.
The implementations that fail usually fail before launch day. The scope was too broad, the process wasn't understood, and the plan required everything to go right. By the time the system meets a real employee, the project is already too big to fix.
The companies that get AI right do something less exciting: they pick one repeated process that costs time, money, or opportunities, and they build one small piece that improves it. Not the whole department. Not the end-to-end workflow. One piece that works.
Think big about where the company could go. Scope small enough to get something working. The 90 days below assume you've made that choice — one process, one system, one measurable result.
Most successful implementations do not begin by changing everyone's job. They begin with a small adjustment.
— Steffen deGraaf, BotLogix
Week 1
Limited real-world use. Watch, correct, document.
Put the system into limited operation with real work — not a demo, not a test account. Then watch. Real employees use systems differently than developers expect, and the first week is where you find out how.
These corrections are normal. They are not failures. A system that survives week one is not the one that was designed perfectly — it's the one that was corrected quickly. Here's the week-one checklist:
Watch employees use it
Sit with them. Where do they hesitate? What do they click that you didn't expect?
Identify unexpected inputs
The customer who emails instead of using the form. The file in the wrong format. Real inputs beat test data.
Correct confusing steps
If two people misread the same screen, the screen is wrong — not the people.
Adjust notifications, routing, permissions
The right alert to the wrong person is still the wrong alert.
Confirm output accuracy
A person reviews the output before it goes anywhere. Verify it's actually right.
Check for bypassing
If employees are working around the system, find out why. The workaround tells you what's broken.
Document every change
What changed, why, and what it fixed. This becomes the playbook for month two.
Keep the scope contained
Week one is not the time to add features. Fix what's in front of you.
The first week is about sharpening the system. It is progress over perfection.
— Steffen deGraaf, BotLogix
Weeks 2–4
Expand and stabilize. Then start measuring.
Once the first piece works in the real environment, expand its use. More volume, more employees, more of the process. Connect it to the next step — the system that prepares the quote now also drafts the follow-up email, or the intake automation now creates the task list.
Address the exceptions discovered during week one. Every business has them — the unusual customer, the edge case, the “we've always done it this way” situation. Decide which exceptions the system handles and which stay with a person. That boundary is a design decision, not an afterthought.
And begin measuring the result, in three categories: time saved, errors prevented, opportunities recovered.You don't need a dashboard. A simple weekly count is enough to know whether the system is earning its keep.
Month 2
Build the next piece — on the same foundation.
Take what you learned from the first project and apply it to the next opportunity. Here's the part many owners don't expect: the second project can be faster and less expensive than the first, because you may be able to reuse useful parts of the first solution for another part of the business.
The intake system you built for quotes becomes the intake system for service requests. The document-processing pipeline that reads contracts now reads invoices. The notification layer, the review step, the CRM connection — already built, already tested, already trusted by your team. This is how a company develops a practical, connected technology foundation instead of a pile of disconnected experiments.
Why the Second Project Can Be Easier
Reuse
Patterns, integrations, and lessons from project one
Faster
The team already trusts the pattern
Connected
Systems share data instead of duplicating it
Start smaller. Finish the project. Confirm that it produces the result you expected. Then connect the next small project to the first one.
— Steffen deGraaf, BotLogix
Month 3
Evaluate honestly. Then decide.
Ninety days in, look at the numbers — not the potential, the numbers. This is the evaluation that separates a working system from an expensive experiment.
Has the system reduced hours?
Compare the weekly time spent on the process before and after. Use your week-two measurements, not your memory.
Has it prevented errors?
Missed follow-ups, wrong data entry, lost documents — count what stopped happening.
Has it recovered opportunities?
Quotes that would have sat, calls that would have been missed, leads that would have gone cold.
Is the owner happier?
Less chasing, fewer surprises, better visibility. This counts — you're the one carrying the company.
Are employees actually using it?
Not grudgingly, not only when watched. If adoption is low, find out why before building anything else.
If the answers are yes, build the next piece. If they're not, understand why before investing more. A failed first project is usually a scoping problem or a process-understanding problem — both fixable, neither fixed by spending more money on the same plan.
The People Side
Getting employees to actually use the system.
Don't begin by telling employees everything is changing. That framing makes the system a threat before it does a single useful thing. Begin by removing the parts of their work that are repetitive, frustrating, inconsistent, or easy to forget.
Preserve the process people already understand. If the team quotes from a spreadsheet today, the new system can feed that same spreadsheet — while quietly removing the six hours of manual preparation behind it. The visible workflow changes less than the invisible workload.
Adoption follows relief. When the system genuinely removes work people didn't want to do, you won't have to mandate its use. When it adds steps without removing any, no amount of training will save it.
The system should feel like help, not disruption. Preserve the process people already understand while quietly removing unnecessary steps.
— Steffen deGraaf, BotLogix
Go deeper
Using AI in Your Business: The Owner's Guide
The full pillar — costs, failures, frameworks.
Build, Buy, or Hire: The Decision Guide
Choose the right path before the 90 days start.
How to Hire AI Help Without Getting Burned
Red flags and the questions to ask before signing.
Is Your Business Ready for AI?
The readiness check before you build anything.
AI Strategy Day
$1,000 on-site. Leave with a 90-day roadmap.
AI Readiness Quiz
Two minutes. Find out where you stand.
30-minute strategy session
For real businesses with real problems.
Not for tire kickers. Not for tech tourists looking for a demo. For business owners who already know something in their operation is broken — and want to know if AI can fix it.
This isn't about replacing people.It's about killing the bad business processes your team hates as much as you do — the manual work, the missed calls, the after-hours admin.
Strategy sessions are free. Strategy Days are $1,000, capped at 4 people per session. Larger teams or multi-location workshops by special arrangement — ask when you book.
Your session is with
Steffen deGraaf
Founder, BotLogix · Burlington, ON