The AI Strategy One-Pager

Core Concepts

AI Strategy One-Pager A single-page document that captures an organization's current AI position, the specific opportunities it is pursuing, the investments required, the guardrails in place, and the near-term milestones that define progress. It is a decision-alignment tool, not a planning artifact.

The one-pager works because it forces prioritization. You cannot fit everything on one page. Every word you include is a choice about what matters. That constraint is the point.

Strategic context The opening section answers: why is AI relevant to this organization right now? Not in general terms, but in specific terms tied to your market, your customers, and your competitive position. For X-company, that means naming the AI-native competitors entering the professional services project management space and acknowledging that the current product has no AI capabilities to differentiate on.

AI opportunity statement A short list of concrete use cases the organization is committing to explore or build. Each use case should be specific enough that a product manager could write a brief for it. "Use AI to improve our product" is not an opportunity statement. "Use AI to generate first-draft PRDs from structured inputs provided by product managers" is.

Capability investment The skills, infrastructure, or process changes required to execute the opportunities. This is where organizations underinvest. They identify the right use cases and then assume their existing team can execute them without any new capability. For X-company, the gap is not infrastructure: it is that the product team has never written a production-grade AI prompt, and the engineering team has never integrated an LLM into a shipped feature.

Governance commitments The boundaries and review processes that keep AI usage responsible. These do not need to be elaborate. At X-company's stage, two commitments are sufficient: a data use policy that defines what customer data can and cannot be sent to external AI models, and a quarterly review cadence to assess what is working.

90-day milestone plan A short list of observable outcomes, not activities, that define what success looks like in the near term. Milestones answer the question: "how will we know we made progress?" Activities ("run training", "ship a prototype") are not milestones. Outcomes ("product team can independently draft and evaluate prompts for PRD generation", "first AI feature in beta with 10 customers") are milestones.

Key Points

• A one-pager is a stakeholder alignment tool, not a planning document
• Opportunity statements must name specific use cases, not general ambitions
• Capability investment is as important as use case selection
• Governance does not require complexity: two clear commitments beat a 20-page policy
• 90-day milestones should describe outcomes, not activities

---

Tools, Prompts, or Templates

Most organizations that attempt an AI strategy document produce either a five-slide deck that says nothing concrete or a 12-page document nobody reads before the meeting. The template below solves both problems: it is long enough to force real decisions and short enough to be read in three minutes.

Fill every section before sharing it. A one-pager with blank sections signals that the strategy is not ready. Incomplete documents invite scope creep in the review meeting rather than alignment.

AI Strategy One-Pager Template

AI STRATEGY ONE-PAGER
Organization: [Name]
Date: [Month Year]
Owner: [Name, Title]

─────────────────────────────────────────────────
STRATEGIC CONTEXT
─────────────────────────────────────────────────
Where we are today:
[2–3 sentences on your current AI capability and why the status quo is a risk or a missed opportunity. Be specific about your market position.]

─────────────────────────────────────────────────
AI OPPORTUNITY STATEMENT
─────────────────────────────────────────────────
The three use cases we are committing to:

1. [Use case name]: [One sentence description of what AI will do and who benefits]
2. [Use case name]: [One sentence description of what AI will do and who benefits]
3. [Use case name]: [One sentence description of what AI will do and who benefits]

Selection criteria used: [e.g. time-to-value, feasibility, strategic fit]

─────────────────────────────────────────────────
CAPABILITY INVESTMENT
─────────────────────────────────────────────────
To execute these opportunities, we are investing in:

- [Skill or training investment]: [What it is and who it targets]
- [Infrastructure or tooling investment]: [What it enables]
- [Process change]: [What workflow or team practice is changing]

─────────────────────────────────────────────────
GOVERNANCE COMMITMENTS
─────────────────────────────────────────────────
1. [Policy or boundary]: [What is permitted, what is not, and who owns it]
2. [Review cadence]: [Frequency, attendees, and what gets reviewed]

─────────────────────────────────────────────────
90-DAY MILESTONES
─────────────────────────────────────────────────
By the end of day 30:
- [Observable outcome]

By the end of day 60:
- [Observable outcome]
- [Observable outcome]

By the end of day 90:
- [Observable outcome]
- [Observable outcome]

─────────────────────────────────────────────────
WHAT THIS STRATEGY DOES NOT INCLUDE
─────────────────────────────────────────────────
[1–2 sentences naming the AI opportunities you are explicitly not pursuing in this period, and why. This prevents scope creep and shows you made deliberate trade-offs.]

When to use this template: Use it when you need to move a leadership group from "we should do something with AI" to "here is what we are doing and who is accountable." It works equally well for a 12-person startup and a 160-person Series B company. The difference is specificity, not structure.

Adaptation for early-stage organizations: If you have fewer than 20 people, collapse capability investment to a single line and limit governance to one commitment. Speed of iteration matters more than policy completeness at this stage.

Adaptation for enterprise contexts: Add a "Dependencies and approvals" row below governance. Large organizations need to know which legal, security, and procurement stakeholders must sign off before any use case reaches production.

---

Actionable Takeaways

• Draft your strategic context section today using one specific market or competitive signal, not a generic statement about AI trends.
• Limit your opportunity statement to three use cases. If you have more than three, apply an impact-versus-effort screen and cut the bottom half.
• Name a capability gap before you name a tool. The gap reveals the investment; the tool is just one way to close it.
• Write your governance commitments as policies your team can follow on Monday morning, not principles they agree with in a meeting.
• Set your 90-day milestones before you start execution. Milestones written after the work is underway are descriptions, not commitments.

---

Practical Examples

X-company: Worked AI Strategy One-Pager

AI STRATEGY ONE-PAGER
Organization: X-company
Date: January 2026
Owner: Sarah Chen, Chief Product Officer

─────────────────────────────────────────────────
STRATEGIC CONTEXT
─────────────────────────────────────────────────
Where we are today:
X-company has no AI capabilities in its core product. In the past 18 months,
two AI-native competitors have entered the professional services project
management market with features that automate status reporting and generate
client-facing deliverables from structured project data. Our renewal rate
with mid-market law and consulting firms has declined 4 points year-over-year.
We have a 22-person engineering team and a 9-person product team with no
production AI experience. We need to close that gap before the next annual
planning cycle.

─────────────────────────────────────────────────
AI OPPORTUNITY STATEMENT
─────────────────────────────────────────────────
The three use cases we are committing to:

1. PRD drafting: AI generates a structured first-draft PRD from a product
   manager's brief, saving 2–3 hours per initiative and improving consistency
   across the team.

2. Onboarding documentation: AI generates role-specific onboarding guides for
   new client contacts from project setup data, reducing time-to-first-value
   for new accounts.

3. Churn prediction: AI surfaces early warning signals in usage and support
   data, giving the customer success team a prioritized list of at-risk
   accounts to contact each week.

Selection criteria used: time-to-value within one quarter, no new data
infrastructure required, directly addressable by existing team with training.

─────────────────────────────────────────────────
CAPABILITY INVESTMENT
─────────────────────────────────────────────────
To execute these opportunities, we are investing in:

- Prompt engineering training for product team: All 9 product managers
  complete a structured prompt engineering curriculum in Q1. Outcome: each PM
  can independently draft, test, and iterate prompts for their use case
  without engineering support.

─────────────────────────────────────────────────
GOVERNANCE COMMITMENTS
─────────────────────────────────────────────────
1. Data use policy: No customer project data, client names, or billing
   information may be sent to external AI models without explicit customer
   consent and legal review. Internal documents and anonymized usage data
   are permitted. Policy owner: General Counsel. Effective: February 1, 2026.

2. Quarterly AI review: CPO, CTO, and Head of Customer Success review AI
   initiative progress, incident log, and updated opportunity list at the
   start of each quarter. First review: April 2026.

─────────────────────────────────────────────────
90-DAY MILESTONES
─────────────────────────────────────────────────
By the end of day 30:
- All 9 product managers have completed prompt engineering training and each
  has produced a tested prompt for their assigned use case.

By the end of day 60:
- PRD drafting tool is in internal use by the product team on at least 5
  active initiatives.
- Data use policy is signed, distributed, and confirmed received by all
  engineering and product staff.

By the end of day 90:
- Onboarding documentation feature is in closed beta with 10 customer
  accounts.
- Churn prediction model has surfaced its first weekly at-risk account list
  to the customer success team, with a feedback loop in place to assess
  accuracy.

─────────────────────────────────────────────────
WHAT THIS STRATEGY DOES NOT INCLUDE
─────────────────────────────────────────────────
We are not pursuing AI-generated status reports or meeting summaries in this
period. Both are technically feasible but require deeper integration with
client communication workflows that we have not scoped. They are candidates
for Q3.

How the one-pager changed X-company's leadership conversation

Before the one-pager existed, X-company's leadership meetings on AI had two recurring problems. First, every attendee arrived with a different mental model of what "doing AI" meant. The CEO was thinking about product differentiation. The CTO was thinking about infrastructure. The Head of Sales was thinking about a demo that could impress enterprise buyers. Second, because there was no written position, every meeting restarted the same debate.

The one-pager resolved both problems in a single working session. The CPO drafted it, shared it 48 hours before the next leadership review, and asked each attendee to mark the sections they disagreed with before the meeting. The meeting ran 40 minutes instead of 90. By the end, leadership had agreed on three use cases, one capability investment, and two governance commitments. The "what this strategy does not include" section prevented a 20-minute detour into meeting summaries.

Discussion Prompt Which section of the one-pager would be hardest to fill in for your organization right now, and what does that tell you about where your strategy work needs to start?

---

Implementation Workflow

Complete this workflow to produce a ready-to-share AI strategy one-pager for your organization.

1. Block 45 minutes. Do not try to write this document in a meeting. Write it alone first, then socialize it. Open a blank document using the template from the Tools section.

2. Write your strategic context. Name one specific competitive or market signal that makes AI adoption urgent for your organization right now. If you cannot name a specific signal, write down the question you would need to answer to find one, and set a date to answer it before you continue.

3. List every AI opportunity your team has discussed in the last 90 days. Do not filter yet. Write them all down. A typical list has 6 to 15 items.

4. Apply a two-axis screen. For each item on your list, score it on time-to-value (how quickly could this be in front of users?) and feasibility (does your team have the skills and data to build it without new infrastructure?). Drop anything that scores low on both axes. Keep the top three items.

5. Write your opportunity statement. For each of the three use cases you kept, write one sentence in this format: "[AI capability] does [specific action] for [specific user], resulting in [specific outcome]." If you cannot complete that sentence for a use case, it is not specific enough yet.

6. Identify your largest capability gap. Ask: if you started building use case one tomorrow, what would stop you within two weeks? Name that blocker as your first capability investment. Add any infrastructure or process changes required for use cases two and three.

7. Write your governance commitments. Write one data policy sentence: what customer or user data is permitted to leave your systems and go to an external AI model, and what is not. Write one review commitment: how often will you assess what is working, and who will be in the room?

8. Set your 90-day milestones. Working backward from day 90, write one observable outcome per milestone checkpoint (day 30, day 60, day 90). Read each milestone aloud and ask: "would I know with certainty whether we hit this or not?" If the answer is no, rewrite it until it is.

9. Write the "what this does not include" section. Name at least one AI opportunity you are explicitly not pursuing in this period. Write one sentence explaining why. This section is not optional: it demonstrates that your strategy is a set of deliberate choices, not a wish list.

10. Share a draft with one critical reader before the stakeholder meeting. Choose someone who will challenge the specificity of your opportunity statements or the realism of your milestones. Revise based on their feedback. Then schedule the alignment session.