This guide is for owners and leaders of small and mid-sized businesses without a full-time AI lead: nobody inside whose whole job is AI, and no time to waste. It covers the eight things we see separate companies where AI sticks from companies where it fades after a month.
Why most AI rollouts stall
Most companies are not early to AI. Their staff already use it, often on personal accounts. The gap is that very few people use it well. A 2026 survey of 5,026 US knowledge workers found only 5.5% were proficient with AI.
The typical pattern: leadership buys licences, sends a launch email, maybe runs one lunch-and-learn. Usage spikes, then fades. Six months later someone asks whether AI “worked”, and nobody can say, because nobody measured where they started.
The research points the same way. BCG's 2026 study of 11,749 workers found that redesigning workflows raised the odds of measurable gains by 24 points, and a clear AI strategy by 25 points. Better tools on their own added about 5. The tool is the easy part. The eight steps below are the rest, and Where AI rollouts go to die covers the seven places a rollout usually stalls.
Sources: Section, AI Proficiency Report 2026. BCG, AI at Work 2026 (press release, 3 June 2026).
1. Name one accountable owner
Every AI rollout needs one named person who answers for whether it worked. When AI is “everyone's job”, nobody books the training, nobody chases the stragglers, and nobody notices when the output quality slips.
The owner does not need to be technical. They need authority, time, and a seat in leadership conversations. In a 50-person company this is often the COO, an operations director, or the owner. A simple test: when an AI-drafted proposal goes out with a wrong number in it, who gets the call? That person should own adoption.
What the owner is accountable for:
- Which business goals AI is meant to move, and the before numbers
- Which tools are approved, and the basic rules for using them
- Who gets trained, in what order, and by when
- Who checks AI output for each kind of work
- A short monthly report to leadership: what changed, what did not, what is next
If nobody inside has the time or the experience, that is the most common reason companies bring in outside help. The owner can still be internal, with an outside partner doing the heavy lifting.
2. Start at the top: leaders and the people others follow
Adoption runs top down. Get your leaders proficient first, then spread AI to everyone else.
In Gallup's 2026 research at companies that have brought in AI, employees whose manager strongly supports AI use it frequently 78% of the time, against 44% for everyone else. Only 36% say they get that support. BCG found positive feelings about AI rise from 15% to 55% when leadership support is strong.
Three reasons leaders go first:
- Leaders are often the bottleneck. Proposals, approvals, client calls and planning wait on them. Freeing their time pays off across the whole company.
- Leaders set the rules. Someone has to decide where AI fits the strategy, where it should be avoided, and what “good enough” output looks like. People who have never used it well cannot make those calls.
- People copy what leaders do. A team will not take AI seriously while their boss still says “I'm not really a tech person.”
“Top” includes influence as well as title. Include the people others go to for judgment on how work gets done: the senior estimator, the office manager, the account lead everyone asks. If they are on board, the team follows.
Training front-line staff before leaders can use AI well tends to backfire. Staff come back with questions nobody above them can answer, and opinions compete instead of converging.
Sources: Gallup, AI in the workplace (2026). BCG, AI at Work 2025. More from us: How executives can become AI-proficient in 28 days.
3. Tie AI to strategy and record before numbers
Start from the business goals you already have, then ask where AI helps reach them. Starting from “what can AI do?” produces a pile of interesting experiments and no change in results.
If the goal this year is more revenue, look at sales and marketing work first: proposals, follow-ups, research on prospects, content. If the goal is margin, look at the back-office work that eats senior people's hours. Agree with leaders on two or three areas, and just as clearly on where AI should not be used yet.
Then write down the before numbers for each area before anyone changes how they work:
| Measure | Example |
|---|---|
| Time per task | Hours to produce a proposal |
| Volume | Proposals sent per month |
| Quality | Win rate, revisions requested, errors caught |
| Speed to client | Days from request to response |
Without a before number, you will never know whether AI helped, and the first sceptic in a leadership meeting wins the argument. Judge results on quality as well as time. A task that takes the same time but comes out much better is still a win.
4. Pick tools people actually want to use
A decent tool that gets used all the time always beats a perfect tool that never gets picked up.
Most companies pick their AI tool by default: whatever their IT provider sells, or whatever came bundled with their email. Then they wonder why usage stays flat. When staff dislike the approved tool, they quietly go back to personal ChatGPT or Claude accounts on their phones, with your client data and no oversight. That is the outcome you most want to avoid.
A better order for choosing:
- Rule out what security rules out. Your IT provider confirms what can connect to your email, files and CRM, and what your client agreements allow.
- Shortlist the main options. For most companies that is ChatGPT, Claude and Microsoft Copilot, on a business plan.
- Let a few of your best people try them on real work for two weeks. Ask which one they kept opening.
- Pick the one people preferred, as long as nothing in step 1 ruled it out.
Your IT provider will probably suggest Copilot. Most IT providers default to the Microsoft tools they know best. Familiarity is a fine starting point and a poor reason on its own. If your team dislikes the tool and quietly moves to personal ChatGPT accounts, the “safe” choice has made you less safe.
The big platforms are all enterprise-grade now. ChatGPT, Claude and Copilot are used across the world's largest companies, and Microsoft 365 Copilot itself now offers Anthropic's Claude models alongside OpenAI's. What the AI can see and do is mostly set by the permissions of the accounts you connect it to. If your Microsoft 365 permissions are set up properly, Claude and Copilot get the same access when connected. Get the permissions right, and the tool choice becomes a question of which one your people will use.
Our default is Claude, and we are open about that bias. In our testing, we asked the tools to do risky things on someone's behalf, like creating accounts, logging into sensitive systems or making payments. Claude more often stopped or declined, while other tools were more likely to go ahead. We also find its output stronger for the business writing and analysis most of our clients do. We still recommend whichever approved tool your team will actually use. A secure tool used badly is riskier than a reasonably secure tool used well, so training matters as much as the tool.
Connect the tool to the systems where the work happens: email, calendar, files and CRM. Copying and pasting into a chat window is where most people start and where most people give up.
Source: Microsoft, Expanding model choice in Microsoft 365 Copilot. More from us: Microsoft Copilot vs Claude vs ChatGPT and Is Copilot safer than Claude for business?
5. Start on real work, not practice tasks
People learn AI by using it on the work already on their desk this week. Generic prompt courses and “write a poem about our company” exercises feel productive and change nothing on Monday.
Ask each person to pick one task they do often, that takes real time, and that they know well enough to judge. Then do it with AI, together, start to finish. Good first candidates are proposals and quotes, meeting prep, client follow-ups, reports, and marketing material.
What this looks like with our clients:
- A home builder went from 40 hours per proposal to four.
- A fractional HR firm cut RFP responses from several days to several hours, and builds marketing materials in about 85% less time.
- Conference prep with all signage became a small afternoon task instead of a week-long project.
Results vary by task, company and person. Some tasks get much faster and better. Some get better in the same time. A few get worse with AI and should stay manual. Working on real tasks is how you find out which is which.
More from us: Where to start with AI and Should AI do this work?
6. Build a few champions, then spread
Once leaders are proficient, pick a small number of AI champions: people who do the team's everyday work and are one step ahead on AI. They show peers how to use it on actual tasks, answer the daily questions, and tell the owner what is getting in the way.
Docusign's engineering team is a useful example. A standard rollout of AI coding tools stalled at 49% adoption. A six-person champions team lifted it to 65%. Embedding champions inside each team took active use to 93% within about two months.
A good champion already uses AI without being told to, and peers already come to them with questions. They know the work well enough to judge the output, and their manager will give them real time for it. Poor picks: the busiest person on the team, a brand-new hire, or someone given the role as a reward.
As a starting point, plan on roughly one champion for every 15 to 20 staff, with two to three protected hours a week. That ratio is our working rule, not a research finding, so adjust it to your team.
Source: Docusign, How we drove AI adoption across Docusign engineering. More from us: How to train your employees on AI, the full champions guide.
7. Decide who checks the work
AI output is a first draft until someone qualified signs off on it. For every kind of work AI touches, name the person who checks it and write down what “good enough to send” means.
This matters more as AI gets connected to email, files and your CRM. More access makes AI far more useful, and it also means something wrong will eventually land in a draft. No plan survives first contact. You will hit edge cases, give feedback, and add rules about what the AI should never include.
Keep the checking simple:
- One reviewer per workflow. The person who would normally sign off on that work.
- A short written standard. Three to five things the output must get right, such as numbers, names, tone, and claims you can stand behind.
- Rules stored in the tool. Most AI tools let you save standing instructions. Put your rules there so every draft starts from them.
- A feedback habit. When the output misses, fix the instruction as well as the draft.
More from us: After AI training: how your company moves from using AI to running on it.
8. Decide what freed-up time is for
If leaders do not say what saved time should go toward, it disappears into email. BCG found 66% of regular front-line AI users get little or no guidance on what to do with the time AI saves.
We frame it as three levels:
- Catch up. Existing work gets done faster and better. The backlog shrinks.
- Get ahead. The proactive work you always wanted and never had capacity for: more follow-ups, better client reporting, new markets researched.
- Do new things. Work that was not possible before. Chase had never done web design, marketing design or deep market research before AI. He now does all three for Sidekick himself.
The third level is where the largest gains usually sit. Make the choice explicit, team by team, and check it in the monthly report.
Source: BCG, AI at Work 2026. More from us: AI is handing your team back hours. Who decides where they go?
Safety without stalling
You are not early here either. The companies that came before you have worked out established practices, and following them puts you well ahead of the many teams running personal accounts with no guardrails.
A sensible order:
- Basic security first. Your IT provider confirms two-step login, strong passwords and phishing protection on your sensitive systems. In our client work, the security gaps we have found were weak passwords and phishing. None came from the AI tool itself.
- Know what is sensitive. List the systems that hold client, financial or personal data, and what is in them.
- Then choose and connect the AI tool, on a business plan, with IT approving each account and connection.
- Layer the protections. Limit what data the AI can see, limit what each connection can do, and write simple rules into the tool and your procedures.
These protections reduce risk a great deal. They do not remove it, or the need for a person to review important output. Work from your own priorities: if getting into the work is the priority, do it quickly and safely; if security is the priority, take the time to be thorough.
More from us: AI safety, cost and staff: honest answers for Canadian owners and AI policy for Canadian businesses.
A 90-day plan
Put the eight steps in order and the first three months look like this. Each phase ends with a check; move on when it is met.
- // Days 1 to 30
Leaders first
- Name the accountable owner.
- Pick two or three goals and record the before numbers.
- Choose the tool with your IT provider.
- Leaders use it on tasks from their own week.
- Check: every leader has one AI workflow in weekly use.
- // Days 31 to 60
Champions
- Pick champions and protect their time.
- Write a check standard for each shared workflow.
- Save the rules in the tool.
- Check: each champion has one team workflow in use.
- // Days 61 to 90
Whole team
- Roll out team by team.
- Decide what saved time is for.
- Send leadership the first before-and-after report.
- Check: leadership has seen the before and after numbers.
This pace is realistic for most small companies. Larger teams usually stretch the third phase across another month or two.
Common questions
How long does AI adoption take?
Expect about 90 days to get leaders proficient, champions in place and the first workflows measured. Rebuilding how the company works around AI takes most of a year. Those timelines come from our practice; published research does not give stage-by-stage timing.
Do we need a full-time AI lead?
Usually not. Most small and mid-sized businesses need an accountable owner with a few hours a week, plus outside help if nobody inside has done this before. If your rollout needs someone full-time on AI, it is better to know early, and we will tell you.
Should we write an AI policy first?
Write a one-page version, then improve it as you learn. A long policy written before anyone has used the tools tends to block the work and miss the real risks.
What if some staff resist?
Start with the people who are keen and let results do the persuading. Mandating a tool people dislike pushes them toward personal accounts.
Which AI tool should we buy?
The one your people will use that your IT provider approves. Our default recommendation is Claude, for the reasons in step 4, but a tool your team actually opens beats a better one they avoid.
How do we know AI adoption is working?
Compare against your before numbers on time, volume and quality. Logins and licence counts tell you very little.
Where Sidekick fits
You are not early, and the people who came before have worked out the playbook. What takes experience is knowing which decisions to make, and in what order. Sidekick helps owners and leaders do that with ChatGPT, Claude and Copilot: we set the strategy with you, get leaders proficient first, build the workflows, coordinate with your IT provider, and stay accountable to the before and after numbers.
To see where AI could pay off in your business first, try the free AI Opportunity Map, about 5 minutes. If no one inside has time to own the rollout, Fractional AI operations leadership runs it with your team. For a single leader getting set up first, see Solo.
Client results are anonymized and come from Sidekick's own before and after measurements.


