Framework · AI strategy operating plan
SCALE
SCALE is a five-step AI strategy operating plan: Strategic Outcomes, Chart Friction, Align Capabilities, Launch with Control, Evolve and Expand. Each step ends in a deliverable a leader can show a board. The rule that separates it from other adoption models is that it starts with the business number, not the tool.
Share this framework
Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.
What it is
AI without business outcomes is expensive experimentation. Most models start with the technology. SCALE starts with the number the business already committed to.
Each of the five steps produces one artifact. By the end you have a running pilot with a measured result and a scale or kill decision, not a deck.
The five steps
S
Strategic Outcomes
Pick one or two measurable business targets before touching a tool. Revenue up, win rate up, cycle time down, margin up. Output: an outcome charter with a specific delta and a gap analysis.
C
Chart Friction
Map the workflow and find where work gets stuck. Separate people friction from process, technology, and data friction, then quantify what each bottleneck costs. Output: a prioritized friction map.
A
Align Capabilities
Match the right AI capability to each real problem and assess whether data, process, and people are ready. Output: a capability match map and a vendor shortlist scored on features, fit, security, and scale.
L
Launch with Control
Run one high-value pilot with a small team, clear success metrics, guardrails, and a feedback loop. Time boxed and small scope. Output: a running pilot with controls.
E
Evolve and Expand
Measure impact against the pre-AI baseline. Scale what worked, kill what did not, and stand up a center of excellence for governance. Output: a scaling blueprint and a governance structure.
The visuals
Figure
Why most AI programs stall
Companies usually start at the wrong end of the transformation. The tool arrives before the number it is supposed to move.
Common approach
Technology first
- Let us try a model with the sales team
- No business outcome written down
- Experimentation with no measurement plan
- Pilot cannot be scaled because nothing was baselined
Result: the pilot ends when the champion leaves.
SCALE approach
Outcome first
- Name the delta: revenue per rep, cycle time, cost to serve
- Strategic outcome defined before the tool shortlist
- Friction mapped, then capability matched to the friction
- Pilot has controls, a baseline, and a kill date
Result: a scale or kill decision backed by a number.
Figure
Start with the end in mind
SCALE runs backward before it runs forward. Set the strategic outcome, work back through the behaviors and KPIs that produce it, then let gap analysis tell you where AI belongs.
Gap analysis, process audit, friction points
The feedback loop that connects the outcome back to the program. Skip it and you automate a broken process.
AI program strategy
The initiative, the budget, and the named owner.
Key behaviors, process, tasks
The work that actually produces the number, mapped step by step.
- Leading: qualified meetings held
- Leading: multithreaded accounts
- Lagging: win rate by segment
- Lagging: revenue per rep
Strategic outcome
The business result the board already committed to this year.
Read right to left to plan. Read left to right to execute.
Figure
The SCALE five-step plan
Five weeks, five deliverables, one scale or kill decision.
Figure
Where revenue teams actually sit
Lagging means manual with no meaningful AI use. Fragmented means tools without orchestration. Advancing means orchestrated and operational.
- Lagging 60%
- Fragmented 29%
- Advancing 11%
Momentum field analysis of 1,000+ calls across 150+ industries, January to July 2025, cited by Jonathan Kvarfordt on The AI Gap. Reported adoption in the same period was 78 percent, against 7.6 percent operational.
Figure
The SCALE deliverables checklist
A phase is complete when a named person signs off on the artifact, not when the meeting ends.
- SOutcome charterIs there a specific delta with a date on it?
- CFriction mapIs each bottleneck costed in time or money?
- ACapability mapIs the data ready for the capability we picked?
- LPilot controlsAre success metrics and guardrails written down?
- EScaling blueprintIs there a named governance owner?
Score: ___ / 5
Figure
Common gaps inventory
Chart Friction produces a list, not a feeling. Most gaps in a revenue team fall into four categories, and the category decides whether AI is even the right instrument.
Map the gap to diagnose the root cause before you select an AI capability. A skills gap does not get fixed by a systems purchase.
What you get out of it
Run SCALE and you get a five-week operating plan a board will approve. Each step ends in a deliverable, not a slide. By week five you have a pilot with measured business impact and a clear scale or kill decision.
- A direct line between AI spend and a business result the CFO can trace.
- A pilot that survives finance review, because the outcome was defined before the tool was picked.
- Governance that prevents every team from buying its own version of the same capability.
The mistakes it prevents
- Starting with the tool
- Buying licenses before defining the business initiative. The problem is step two. The business number is step one.
- Automating a broken process
- You cannot automate a broken process. Teams that skip friction mapping get faster broken work.
- The pilot with no controls
- A pilot without success metrics is a demo, and a demo cannot scale because there is nothing to measure against.
- Adoption theater
- Reported adoption and operational adoption are different numbers. Most of the gap is projects that skipped the outcome step.
- No governance
- Successful pilots without governance fragment into sprawl within a year.
How it is used here
SCALE is the five-week plan for any reader who asks where to start. Each phase can be run on its own, and each phase's deliverable is the entry ticket to the next.
So many people come out and say focus on your problem first. That's step B. That's not step A. Step A should be what are the business initiatives you're focusing on this year.
Jonathan Kvarfordt, RevOps Champions podcast
It requires a lot of what people call unsexy work, because no one gets on LinkedIn and says, hey, I just mapped out 30 workflows.
Jonathan Kvarfordt, RevOps Champions podcast
Terms used here are defined in the glossary and explained in plain language in the AI and Revenue Dictionary.
Apply it with a skill
Each skill turns this framework into a job you can finish. Copy the quick prompt for one task, or download the SKILL.md file, a reusable set of instructions for an AI assistant, for repeatable work.
All skills and prompts →Common questions
- What does SCALE stand for?
- Strategic Outcomes, Chart Friction, Align Capabilities, Launch with Control, Evolve and Expand. Five steps, five deliverables, in that order.
- How is SCALE different from other AI adoption models?
- Most models start with the technology or the use case. SCALE starts with a business number the company already committed to, then works backward to the capability. AI without a business outcome is expensive experimentation.
- How long does SCALE take to run?
- One week per step is the working default, so five weeks to a controlled pilot with a measured result. Larger organizations stretch Chart Friction, because workflow mapping is the slowest step.
Cite this framework
Kvarfordt, Jonathan. "SCALE." The Revenue AI Report. https://www.therevenueaireport.com/frameworks/scale
All frameworks →