The first 90 days of AI in your business

Week 1: Stack audit. List every tool in your business. CRM, email, invoicing, project management, communication. Where does data live? Which tools talk to which? Most teams discover three tools nobody knew about and two integrations that are broken. 2-3 hours. One owner from ops.

Week 2: Process mapping. Walk through your top workflows. Lead from inbound to deal. Customer from onboard to off. Spot the manual steps where humans are copy-pasting, typing repetitive info, or doing work that a system should own. Get your ops team in a room and map it on a whiteboard. Then write it down. 3-4 hours.

Week 3: Identify the 3 biggest leaks. Across the workflows, which three manual steps steal the most calendar time? Total them up. If lead follow-up is five hours a week, client onboarding is six, and reporting is four, those are your targets. Ask your team: if we automated one thing, what would it be? The answer often surprises you. 2 hours conversation, 3 hours documentation.

Week 4: Write the 30-day roadmap. You pick one of the three leaks. That is your day 31-60 build. The other two become day 61-90 and month four. Write down the specific deliverable: "We will automate lead follow-up with a three-email sequence in Zapier and Gmail." Not "We will explore AI tools." That is the roadmap.

Day 30 deliverables: One owner assigned to day 31-60 build. One tech lead or fractional who can scope the work. Written list of the stack. Written list of the three highest-impact moves. Green light from leadership. Budget allocated.

Days 31-35: Design the workflow. Do not code yet. Write out the exact steps. If you are automating lead follow-up: email lands, trigger fires, check if lead has booked or replied, send day three follow-up if no reply, send day five closer, log everything to CRM. Draw a diagram. Find the edge cases. Three hours with your owner and a tech person. This prevents rewrites.

Days 36-50: Build and test. Use Zapier, Integromat, or a native automation inside your CRM. Test with real data. Load 50 leads, run it end-to-end, catch bugs. Iterate. This is not sexy but it saves months of production problems. One person, 10-15 hours total, done by day 50.

Days 51-55: Team testing. Run it with three to five real team members. Is the email getting sent right? Is the CRM logging correct? Are people confused about what to do when the automation triggers? Get feedback and fix it fast. One person, 5 hours. One week of live testing with real workflows.

Days 56-60: Go live and document. Flip the switch for your whole team. On day 60, send an email to the company: here is what we just shipped, here is what it does, here is how to use it, here is what we saved. Attach one-page docs explaining the workflow. One person, 3 hours. Print it on the wall if you want people to remember it.

Day 60 deliverables: One automation in production, live with your whole team. Time tracking: what hours was this automation saving? Write it down. Internal documentation. Go/no-go on the second build for days 61-90.

Days 61-68: Design and build the second automation. You have done this once. You are faster now. Same rhythm: design, build, test with data. This one should take 8-10 hours instead of 15. Pick the second leak from your week four roadmap. Ship it by day 68.

Days 69-75: Team test, feedback, refinement. Real team testing. A week of live runs. Catch bugs. Fix edge cases. Go live by day 75. Same playbook, faster execution.

Days 76-85: Measurement framework. Now you prove what you built matters. First automation saved how many hours a week? Second automation saving how many? Calculate the cash value. USD $400 per week USD $20k per year. That is your baseline. Set up a simple spreadsheet you are updating monthly. Hours saved, cash value, confidence in the system.

Days 86-90: 90-day retrospective. Team meeting. Here is what we shipped. Here is what we learned. Here is what we are doing next. Show the hours saved. Show the cash. Do not keep it internal. Share it at an all-hands if you have one. Momentum is real and your team needs to feel it. This is where they believe in the next phase.

Day 90 deliverables: Two automations in production. Measurement framework documented. Team confidence on AI as a capability, not a buzzword. Roadmap for months four through twelve drafted. Budget and ownership for the next phase.

Days 1-30: Tool rabbit hole. You spend three weeks comparing Zapier, Integromat, and native automations instead of scoping the actual work. You end up paralyzed. Kill this fast. Pick one tool on day two and move on. You can migrate later if you need to. The audit is about workflow, not tool. The tool just executes the workflow.

Days 1-30: No sponsor. You run the audit but leadership did not sign off on the goal. By day 25 you are stuck because the build plan needs budget or headcount you do not have. Get the sponsor on day one. Have them sit in on the week two process mapping. They own day 31 forward.

Days 31-60: Scope creep. You design the lead follow-up automation and now someone wants to add SMS, add Slack alerts, add a custom CRM field. Stop. One thing. Ship it. Add the rest in month four. Your job is velocity, not perfection. Done is better than perfect on the first one.

Days 31-60: No team involvement. Your tech person builds it in isolation. Day 56 they show the team and people say it does not work for them. Now you have rewrites and delays. Get the team testing on day 51. Let them break it while you still have time to fix it.

Days 61-90: Losing momentum. You shipped the first win and people are exhausted. Days 61-90 you want to keep moving, not coast. If you need to, hire some fractional help to own the second build so your team is not burned out. Or compress it to days 61-75 and give them two weeks off before month four.