The Small Business AI Playbook: 4 Practices That Compound
Most articles about small business AI adoption tell you what to think about. This one tells you what to actually run. There is a difference, and the difference is the difference between a business where AI compounds and a business where AI produces scattered gains for six months and then quietly fades.
The playbook is four practices — an AI Person, a Living Policy, a Shared Workflow Library, and a Weekly Capability Scan. Each one solves a specific failure that breaks AI adoption at small-business scale, none of them requires real budget (roughly an hour a week of attention each), and the compounding only starts when all four run together. Most small businesses I work with have one or two.
If you have not yet read the cornerstone piece that introduces the framework, start with Do You Have an AI Person on the Team?. If you are not sure where your business currently stands and want to figure that out first, the companion piece on how to tell where you actually stand on AI covers that ground. This article assumes you already understand the four practices and want the playbook — the operational version of what each practice looks like once a real business builds it.
One thing worth saying up front. None of these practices is technological. There is no software to buy, no platform to adopt, no vendor to engage. They are operational habits that take roughly an hour a week of dedicated attention from a real person. The reason small businesses fail to build them is not capability. It is that no one has been told these habits matter, what they look like, or how to know they are working.
What are the four practices of the playbook?
The four practices that turn AI adoption from scattered gains into compounding capability are an AI Person, a Living Policy, a Shared Workflow Library, and a Weekly Capability Scan — in one line each:
- The AI Person. One named individual whose explicit job description includes responsibility for the company’s AI usage, decisions, and standards.
- The Living Policy. A short, written document that defines what AI is used for, what it is not used for, and who decides when something new is added or removed.
- The Shared Workflow Library. A central, accessible place where the team’s working prompts, processes, and outputs are documented so AI knowledge survives turnover.
- The Weekly Capability Scan. A short, recurring review of what is changing in AI capabilities and whether any of those changes apply to the business.
The rest of this article walks each one in detail, including what it looks like in operation, what most businesses get wrong, and how to know whether you are doing it well.
Practice 1: The AI Person
One named person, accountable for AI
A single named individual at your company whose job description explicitly includes responsibility for AI usage, governance, and standards. Not their only job. Not necessarily a senior role. But the person who, when someone on the team asks “can we use Claude for this?”, has the authority and the obligation to answer.
At a 12-person agency, this might be the operations manager. At a 5-person nonprofit, it could be the executive director themselves, with explicit weekly time blocked for the role. The AI Person reviews new tool requests, maintains the Living Policy, runs the Weekly Capability Scan, and is the named contact when a team member is unsure whether to use AI for a specific task. They spend roughly two to four hours per week on the role.
Three common failure modes. First, assuming “the most enthusiastic person” is the right pick. Enthusiasm is not the same as judgment. Second, making the role implicit rather than explicit. Without a written job-description line, the role evaporates the moment someone is busy. Third, picking someone too senior. The CEO is not the AI Person at a 20-person company. The CEO sets the mandate. Someone else owns the operating reality.
A new hire on their second day can answer the question “Who at this company decides how we use AI?” without having to ask anyone.
Practice 2: The Living Policy
A short written document people actually follow
A document, usually one to three pages, that defines three things. What AI is used for at this company. What AI is not used for. Who makes the decision when something new comes up. It is called a Living Policy because it is expected to change as the business and the technology change. The version that worked six months ago is probably wrong today.
A short document linked from the team handbook or the company wiki. Updated quarterly at minimum, sometimes monthly during active adoption phases. It names specific tools (Claude is fine for drafting client emails, ChatGPT is fine for brainstorming, neither tool gets used for legal documents), specific use cases (proposal first drafts: yes; final client deliverables: requires human review), and specific decision-makers (the AI Person, with the operations director, decides on new tool additions). It includes a date stamp and a changelog so the team can see what changed and when.
The biggest failure is treating the policy as a one-time deliverable instead of a living document. Sullivan and Cromwell had a policy that said “trust nothing and verify everything.” The policy existed. The policy was not followed. A policy that nobody references is worse than no policy at all because it creates the illusion of governance. The second common failure is over-engineering. A 12-page AI policy at a 10-person company gets read once and ignored. Short, specific, regularly updated beats comprehensive and inert.
Someone on the team mentions the policy in conversation, by name, within their first month, when discussing whether AI should be used for a specific task.
Practice 3: The Shared Workflow Library
A central place where AI knowledge lives
A central, accessible repository where the team’s working prompts, processes, and outputs are documented. This is the practice that turns individual AI usage into organizational capability. Without it, AI knowledge lives in one or two people’s heads, and your AI capability evaporates the day they leave.
The format varies based on the team. For some, it is a Notion database with one card per workflow. For others, it is a folder of templates in Google Drive with naming conventions. For very small teams, it can be a single shared document. What matters is not the tool but the discipline. Each entry includes the task name, the prompt or process used, the inputs required, the expected output, and any notes on edge cases. When someone discovers an improvement, they update the library entry. When a new hire arrives, the library is part of onboarding.
The most common failure is starting with too much ambition. A team decides to document every AI workflow at once, creates 40 placeholder entries, fills in three, and abandons the rest. The library becomes a graveyard. The better path is to start with the three workflows that matter most and grow only when the team actually uses what is already there. The second common failure is treating the library as the AI Person’s project rather than the team’s. If only one person updates it, it stops reflecting what the team is actually doing.
A team member who was on vacation can return on Monday, open the library, and know what changed in their absence without asking anyone.
Practice 4: The Weekly Capability Scan
A short recurring review of what’s changed
A short, recurring review by the AI Person of what is changing in AI capabilities and whether any of those changes apply to the business. Twenty minutes a week, not two hours. The point is not to be exhaustive. The point is to make sure the company is not still using AI the way it did four months ago when something materially better exists now.
Friday afternoon, twenty minutes. The AI Person reviews one or two industry newsletters, scans for new model releases or feature changes from the tools the company already uses, and notes anything that might apply to the business’s current workflows. Once a month, they bring one or two items to the operations review and recommend a small experiment. Most weeks produce nothing actionable. The rare week that does is what compounds over a year.
The first failure is making it too long and abandoning it. A weekly two-hour deep dive lasts three weeks. A weekly twenty-minute scan lasts a year. The second failure is treating every capability change as urgent. Most new model releases do not change anything material for a 15-person agency. The scan is not a directive to react. It is a discipline of not falling asleep.
Roughly once a quarter, the AI Person walks into a leadership meeting and says “there is a new capability that applies to how we do X. We should test it.” The other three quarters, the scan happens quietly and produces nothing visible. That ratio is correct.
A four-question diagnostic
Run your business through these four. The answers tell you which practice to build first.
Where does your business actually stand?
- The AI Person. If a new hire asked “who decides how we use AI here?” on day two, could they get an answer without anyone having to guess?
- The Living Policy. Does your AI policy fit on three pages, get updated at least quarterly, and get referenced in actual team conversations?
- The Shared Workflow Library. If your most senior AI user left tomorrow, would the next person be able to pick up the work without rebuilding from scratch?
- The Weekly Capability Scan. Can the person responsible for AI at your company tell you, off the top of their head, one or two specific changes in AI capability from the last month?
Most small businesses I work with answer yes to one. Occasionally two. Almost never three or four. That is not a problem. It is just the honest starting point, and it tells you exactly where the next ninety days of work belongs.
What does the 90-day playbook look like in practice?
The four practices build sequentially over about ninety days, each one reinforcing the next — they are not a single sprint. Here is a typical timeline for a small business or nonprofit starting from zero or one of the four.
Name the AI Person and write the first Living Policy
Pick the person. Add the line to their job description. Get owner or board sign-off on the role. The AI Person drafts the first version of the Living Policy. Three pages or fewer. Names tools, names use cases, names decision-makers. It will be imperfect. Ship it anyway.
Start the Workflow Library with three real workflows
Pick three tasks the team already does with AI. Document the prompts, inputs, and outputs in whatever shared system fits the team. Set the standard that any new AI workflow added to the team’s regular work gets documented before it counts as a workflow. The library starts small and grows by use.
Run the first Weekly Capability Scans
The AI Person establishes the Friday afternoon rhythm. Twenty minutes a week. After four scans, the discipline starts to settle. After eight, the AI Person has enough context to bring meaningful items to the monthly operations review.
First policy update, first workflow library audit
The Living Policy gets its first real revision based on three months of actual use. Workflows that turned out not to work get removed from the library. The team’s AI usage starts to feel like a system rather than a collection of individual habits. This is the first month where compounding becomes visible.
None of this requires new technology. Every practice can be built with the tools the company already uses — a shared document, a calendar reminder, a Notion database or Google Drive folder. The work is operational, not technical. Which is why the businesses that fail to build it usually do not fail for budget reasons. They fail because no one has been told it matters.
The playbook only works when all four practices run together
An AI Person without a Living Policy ends up making case-by-case decisions that nobody else can follow. A Living Policy without an AI Person is a document no one updates. A Workflow Library without a Weekly Capability Scan slowly drifts out of date. A Weekly Capability Scan without a Workflow Library produces insights that have nowhere to land.
The four practices are a system, not a checklist. They reinforce each other. The reason most small businesses are still using AI in fragments six months in is that they tried to start with one, hit a wall, and concluded AI adoption was harder than they thought. It is not harder. It just requires the four to operate together, with one person paying attention to the whole. That is the playbook.
It is not glamorous. It is not what gets posted on LinkedIn. But it is what separates the small businesses where AI actually compounds from the ones where it produces scattered gains that quietly fade.
Want to map where your business sits on the playbook?
A 30-minute discovery call is usually enough to surface which practice to build first, what the next ninety days should look like, and whether external help would speed it up.
Book a discovery callIf you’d rather not run the playbook alone, here’s how to work with an AI consultant.

