Home / Guides / A 90-day AI rollout
What a 3-month AI rollout looks like, week by week
A realistic AI rollout for a small business takes about 12 weeks for its first department: two weeks measuring, two weeks connecting data, then about eight weeks running side by side with staff while the AI is tuned and widened. After that it carries nearly all of that job, and people handle the exceptions.
A plan that skips the side-by-side weeks is selling the demo, not the rollout.
The 12-week rollout, in six two-week blocks
Watch and measure
Sit in the business. Count missed calls, order errors, hours spent on admin and where money leaks. Write the baseline numbers down, because without them you cannot tell later whether anything worked.
Pick one job and connect the data
Choose the single job with the biggest leak, usually the phone or order taking. Connect the systems it needs: menu or price list, point of sale, calendar, payment. Write the answers to the 20 most common customer questions.
Run it side by side
Switch the AI on for part of the work only, such as after-hours calls or one phone line, while staff handle the rest. Review every conversation it handles. Fix wrong answers the same day.
Widen it and add the second job
Move more of the work to the AI as its error rate drops. Start the second job, such as table ordering or follow-up texts, using the same data you connected in weeks 3 and 4.
Train staff on the new roles
Staff stop doing the repetitive part and handle exceptions: upset customers, unusual orders, anything the AI hands off. Write a one-page sheet for what to do when the AI flags something.
Measure against the baseline and hand over
Compare to the week 1 numbers. Keep what moved the numbers, drop what did not. Set up the daily owner summary and the alerts so problems surface without anyone checking dashboards.
Why the AI runs side by side with people first
An AI answers from what it has been told. On day one it has not met your real customers: the caller who orders by nickname, the regular who wants "the usual", the question nobody thought to write down. Running side by side means those calls still get handled by a person while the AI learns them.
What goes wrong in month one
- Names and numbers misheard on noisy lines.
- Questions with no written answer yet.
- Callers who hang up during the greeting.
- Staff who do not trust it and work around it.
What fixes it by month three
- Every conversation reviewed, every miss written into the answers.
- Shorter greetings and faster paths for regulars.
- Clear hand-off rules, so staff know which calls are theirs.
- Numbers that show staff the time it saves them.
The numbers to write down in week 1
| If the first job is | Measure before | Measure after |
|---|---|---|
| Phone | Calls per week, missed calls, calls outside hours | Calls answered by AI, calls that became orders or bookings, hand-offs to staff |
| Order taking | Orders per day, errors, unpaid or abandoned orders | Share of orders placed without staff, orders paid before work starts |
| Admin and books | Owner hours per week on admin, days the books run behind | Hours saved, days behind |
| Marketing | Repeat customers per month, review count | Repeat rate, reviews per month |
Swipe the table sideways to see every column.
How this played out at our proof restaurant
AZ follows this plan at our proof restaurant in Houston, one department at a time. Ordering went first: guests order and pay on their phone at the table and online, and every order is paid before it cooks. The AI phone host followed and is in its side-by-side period now.
share of direct orders that place themselves, mid-August to mid-October 2026.
real calls answered by the AI host in its first three weeks.
of those calls came outside opening hours, every one answered.
October 2026. For the restaurant version of this plan, see what a forward-deployed engineer does week by week. For the cost side, see back office automation costs.
Where these facts come from
- Restaurant Dive on NRA State of the Restaurant Industry 2026 - 26% of operators use AI tools, read Oct 2026
- DataCamp: What is a forward deployed engineer - read Oct 2026
Questions owners ask
How long does it take to implement AI in a small business?
Plan on about 12 weeks for the first department. Two weeks to measure, two to connect data and write answers, then about eight weeks running side by side with staff while it is tuned. Simple self-serve tools can switch on in days, but getting them to handle real customers well takes longer.
What should a small business automate with AI first?
The job with the biggest measurable leak. For restaurants and service businesses that is usually the phone: missed calls are lost orders and bookings. Measure it for two weeks first so you can prove the change.
Why not switch AI on for everything at once?
Because you cannot tell what worked, and staff get overwhelmed. One department at a time gives clean before and after numbers, and the data you connect for the first job makes the second one faster.
What do staff do during an AI rollout?
In the first weeks they keep doing the work while the AI handles a slice of it. Later they handle the exceptions it hands off: upset customers, unusual requests, anything it flags. Give them a one-page sheet for hand-offs.
When does an AI system run without people?
After about three months of side by side running, an AI phone host carries nearly all calls. That is the pattern we follow at our proof restaurant. People stay for exceptions and hospitality. No honest rollout removes people on day one.
How do I know if the AI rollout worked?
Compare against numbers you wrote down in week 1: missed calls, orders placed without staff, owner hours on admin, errors. If a number did not move after 12 weeks, drop or rethink that tool.
Tell us which department to start with. We map your 12 weeks.
Same-day reply. No vendor commissions, so we recommend whatever fits, including a tool that is not ours.
Guides for owners
Comparisons