Most operators commit to "we should use AI more" and then nothing changes. The work doesn't get done because there's no plan. Here's the 90-day plan I'd run if I were the operator at a 30-50 person company committing to a real AI rollout.
This is sequential, opinionated, and assumes you have one person who will own the rollout (you, an ops lead, or a fractional). Without an owner, none of this works.
The 90-day shape
Days 1-21 (Weeks 1-3): Foundation. Audit, hygiene, single workflow live.
Days 22-60 (Weeks 4-9): Scale. 2-3 more workflows live, team adoption.
Days 61-90 (Weeks 10-13): Measure and optimize. Real numbers, retro, plan for next quarter.
The order matters. Operators who try to deploy 5 workflows in week 1 burn out the team. Operators who deploy too slowly never see compounding returns.
Days 1-7: Audit + first principles
Day 1: 90-minute workflow audit (the playbook from the adjacent post, or hire someone for the $1,495 Audit Pro). Output: ranked list of 3-5 workflow candidates with ROI math.
Day 2: Pick the FIRST workflow. Best first pick is usually the highest-frequency one with the lowest customer-facing risk. CRM hygiene, meeting notes, or inbox triage are the typical winners.
Day 3-4: Confirm the data is ready. If you're starting with meeting notes → CRM, is your CRM clean? If not, do CRM Hygiene Sprint first (week 1 only, 7 days fixed).
Day 5: Designate the owner. Someone whose name is on the rollout. Not the founder unless founder-led is genuinely the right move at this size.
Day 6: Communicate to the team. The team needs to know: a workflow is changing, AI is involved, here's what's expected to change about their day. Without this, you get cultural friction.
Day 7: Kickoff with whoever's building (us, an internal team, or a contractor).
Days 8-21: First workflow live
This is the productized agent build window. If you're using a $2,995-$4,995 productized SKU:
Days 8-14: Build phase. Sample data, prompt tuning, integration setup. Day 12 = soft demo on real data. Day 14 = v1 live.
Days 15-21: Soft adoption. The agent is running. The team is using it. The owner is checking accuracy daily and flagging edge cases.
Day 21 milestone: Agent has handled 20+ real instances of the workflow. Accuracy is at 85%+. Team has stopped checking it manually.
If you don't hit Day 21 milestone, slow down. Don't deploy a second workflow yet. Get the first one working.
Days 22-45: Second workflow
The second workflow should be in a different category from the first. If you started with meeting notes → CRM, second is something on the inbox or proposal side. Don't double up on the same category — you want to test breadth, not depth, in the first 90 days.
Days 22-28: Plan the second workflow. Confirm pre-reqs, pick the SKU, kickoff.
Days 29-35: Build phase.
Days 36-45: Soft adoption + first workflow continues to compound.
By Day 45 you should have two workflows live, both at 85%+ accuracy, team using them daily.
Days 46-60: Third workflow + first measurement
Days 46-52: Plan + kickoff third workflow.
Days 53-60: Build + soft adoption.
By Day 60: three workflows live. Now you need data.
Day 60 measurement:
- Hours recovered per week per workflow (track explicitly — ask the team)
- Accuracy rate per workflow (sample-check 20 instances per workflow, score correct/incorrect)
- Customer-facing impact: any complaints, any positive feedback
- Team morale: did anyone push back on the AI? Why?
This is when real data starts replacing your before-rollout assumptions.
Days 61-90: Optimize + plan next quarter
The third month is about making what you've built actually compound.
Days 61-75: Tune. Each agent has edge cases that show up in real production. Now's when you fix them. Schedule one weekly hour with whoever built the workflows to walk through what isn't working.
Days 76-83: Document for the team. Each workflow needs a 1-page "how this works, what to do if it breaks, who owns it" doc. Without this, the next person who joins doesn't know what AI is doing in the background.
Days 84-90: Retro + plan next quarter. What worked? What didn't? What's the next workflow? What's the actual ROI you measured (not estimated)?
End-of-quarter milestone: 3 workflows live, measured ROI documented, team adopts the workflows as default behavior, plan for the next 3 workflows ready.
The 5 mistakes operators make in this 90-day period
1. Deploying too many workflows simultaneously. 3 in 90 days is the right pace. 5+ leads to none of them working well.
2. Skipping the data hygiene step. Building meeting notes → CRM on a CRM with 50% dirty data fails predictably. Hygiene first.
3. No designated owner. "We'll all check on it" means nobody checks on it. Every workflow needs one name.
4. Not measuring before deploying. If you don't know how long the manual workflow took, you can't claim the AI saved time. Measure week 1, before the first build.
5. Treating Day 14 as "done" instead of "v1 live." The first 30 days are when edge cases surface. Plan for tuning time, not for "set and forget."
What you should NOT do in days 1-90
Three temptations to avoid:
1. Don't try to build a custom AI tool from scratch in this window. Use productized SKUs for first 90 days. Custom builds come in quarter 2 once you have data on what's working.
2. Don't roll AI into customer-facing workflows in this window. Internal first. Customer-facing comes in quarter 2 with proper review gates.
3. Don't subscribe to 5 new AI SaaS tools. Pick one underlying chat AI (ChatGPT or Claude) and one productized agent vendor. Resist tool sprawl.
The realistic expectations at Day 90
A 30-50 person company that runs this 90-day playbook honestly should see:
- 12-25 hours per week recovered across the team
- 1 measurable workflow improvement (forecast accuracy, response time, recall rate, etc.)
- Foundation in place to build 3-5 more workflows in quarter 2
- Team comfortable with the AI changes, not threatened by them
That's the ground floor. Companies that compound from here typically 3-5x their AI footprint over the next 12 months without doing anything dramatic.
Where to start
If you want help running this playbook: the Audit Pro at $1,495 maps your specific situation, ranks the workflows, and outputs a 90-day plan with priced quotes for each build. Most operators leave with a fully sequenced quarter ready to execute.
If you want to run it yourself, the audit playbook in the previous post is the starting point. Block 90 minutes this week.
Get started
Want a real number for your specific situation?
30-minute audit call walks through your workflows and outputs a fixed price for the 2-3 things worth automating first.