How to Write a One-Page AI Strategy

Most small businesses don't have an AI strategy. They have a tool list.

Claude for writing. Midjourney for social images. An AI scheduler someone found in a newsletter. Maybe a Zapier automation that half the team doesn't know exists. Each tool arrived as its own decision, disconnected from the others, with no defined owner, no quality standard, no cap on spend, and no articulation of what problem it was supposed to solve.

When I ask a team what their AI strategy is, they usually describe the tools. When I ask who owns each workflow, there's a pause. When I ask what they won't do with AI, there's a longer pause.

The fix is a single document — one page, seven sections, filled in during a 90-minute working session. Here's the format.

The seven sections

Section 1: What we're trying to accomplish (2–3 sentences)

The strategic outcome AI is supposed to drive. Not "use AI more" — that's a direction, not a goal. The actual business result AI serves.

Examples:

• "Reduce time-to-first-response on customer support inquiries from 8 hours to under 2 hours, without adding headcount."
• "Increase the volume of marketing content we ship per week from two pieces to six, while keeping editorial quality at or above current levels."
• "Free up the operations lead's calendar by 10 hours a week so she can focus on the new product launch in Q3."

Specific, measurable, time-bound. If you can't write a goal you'd be embarrassed to miss, the strategy isn't real yet.

Section 2: Where AI fits — three workflows, named (a short list)

Pick three workflows where AI will be deployed in the next 90 days. Three is the limit. Four is too many for an SMB in a single quarter.

Each workflow gets:

• Name: "Customer support first-draft responses"
• Owner: "Maria"
• Tool: "Claude project, custom prompt, integrated via Zapier"
• Output volume target: "All inbound support tickets get an AI-drafted response within 30 minutes; Maria reviews and sends."

No paragraph of context. The detail lives in the workflow's own documentation. The strategy doc just lists the three.

Section 3: Tools selected (a short list)

The specific tools committed to for the next 90 days. Named, with a defined purpose for each.

Example:

• Claude Sonnet — drafting and analysis
• Cursor — internal tooling and prompt iteration
• Otter.ai — meeting transcription
• Zapier — workflow integration

Resist listing every tool under evaluation. If you haven't committed, it doesn't belong on the strategy doc. The evaluation candidates live in a separate document.

Section 4: Quality standards (3–5 bullets)

The minimum bar AI output has to clear before it ships. This is the most under-written section in most strategy docs — and the one that protects your brand.

Examples:

• "All customer-facing AI output is reviewed by a human before sending."
• "All published content passes a voice match score of 80 or higher."
• "AI-generated images are reviewed against the brand color palette before posting."
• "Internal-only output — summaries, drafts, internal notes — doesn't require review."
• "Anything tied to legal, compliance, or financial accuracy is reviewed by the relevant subject matter owner."

The point is to answer "is this AI output okay to ship?" without convening a meeting every time.

Section 5: Budget cap (2 numbers)

The total spend on AI tools and AI-driven workflows for the next 90 days. A hard cap.

Two numbers:

• Monthly tool subscriptions: $X
• Per-call API spend: $Y

With the cap defined, the team can experiment freely up to the limit without checking in. Without it, spend creeps and nobody notices until the quarterly review.

For most SMBs starting out, the right caps are smaller than they expect — $200–500/month in subscriptions, $50/month in API usage. You'll know within a quarter whether to raise them.

Section 6: Review cadence (1 sentence)

Quarterly. Not monthly — the workflows haven't matured. Not annually — the tooling and your business both move too fast for that.

One hour on the calendar every 90 days. Pull up the strategy doc, check the workflows, update the tool list, decide what's next.

The sentence: "Reviewed quarterly. Next review: [specific date]."

Section 7: Red lines — what we won't do (3–5 bullets)

The most important section in the document. Most teams skip it entirely.

This is where you write down what AI is not going to be used for, regardless of how compelling the pitch. The red lines.

Examples:

• "We won't use AI for direct outreach to our top 20 clients."
• "We won't use AI to generate our brand voice from scratch — we anchor against our existing corpus."
• "We won't ship AI-generated content without an editor reviewing it."
• "We won't deploy autonomous AI agents that take customer-facing actions without human approval."
• "We won't subscribe to any AI tool without a defined 30-day success criterion."

The red lines protect you from the next ten vendor pitches that will arrive sideways. When someone proposes "fully autonomous customer outreach," you don't debate it on the merits. You point at the document. The answer is already written.

Operators who write red lines well end up with cleaner, more focused AI strategies than operators who don't. The constraint does the work.

The rules that keep it on one page

Rule 1: One page is the constraint. If it doesn't fit on a single sheet at readable font size, you're not done editing. Cut, combine, or move detail into supporting documents.

Rule 2: No section longer than five bullets or three sentences. This forces precision. If you can't say it in five bullets, you don't actually know what you mean yet.

Rule 3: Every workflow has an owner. Every tool has a purpose. Every red line is concrete. "We will be thoughtful about AI" is not a red line. "We won't use AI for top-20 client outreach" is.

The format

Use this as your template.

[BUSINESS NAME] — AI STRATEGY · Q[X] 20[XX]

GOAL
[2–3 sentences. The business outcome AI serves.]

WORKFLOWS (3)
1. [Workflow name] — owner: [name], tool: [tool], target: [output volume]
2. [Workflow name] — owner: [name], tool: [tool], target: [output volume]
3. [Workflow name] — owner: [name], tool: [tool], target: [output volume]

TOOLS
- [Tool] — [purpose]
- [Tool] — [purpose]
- [Tool] — [purpose]
- [Tool] — [purpose]

QUALITY STANDARDS
- [Standard]
- [Standard]
- [Standard]

BUDGET CAP
- Subscriptions: $[X]/mo
- API/per-call: $[Y]/mo

REVIEW
Quarterly. Next review: [date].

RED LINES
- We will not [specific action].
- We will not [specific action].
- We will not [specific action].

Most SMBs can fill this in during a single 90-minute session. Once it's written, every tool decision has a context, every workflow has an owner, and every team member can answer the same question the same way: what are we doing with AI, who owns it, and what won't we do?

That's the install. Keep it to one page and review it every quarter. The discipline of the format is the point.

Try it yourself

The widget below is the template, but live. Every field is editable — replace the Daring Strategy values with your own, then copy the result as plain text. (We seeded it with our actual one-pager so you can see what a real, filled-in version looks like.)