Classifying AI Ambition With OAR

• Source: Report framework library

Encodes a Revenue AI Report framework so the agent applies the published method instead of improvising one.

1. 1.Copy the SKILL.md text below, or download the raw file.
2. 2.Create a folder named exactly classifying-ai-ambition-with-oar in your agent's skills directory.
3. 3.Save the file inside that folder as SKILL.md.
4. 4.Ask the agent one of the trigger requests below.
5. 5.Check the output against what you already know before it leaves your desk.

• Run the outcomes-first OAR audit across our nine live AI initiatives.
• Which sales-velocity driver should this AI investment change?
• Is our AI SDR rollout actually transformation or are we just going faster?
• Our board deck says we are reinventing GTM. Check whether the work supports that word.

• Build us a five-week plan to get started with AI.
• What order should we make these changes in without breaking the CRM?
• Summarize this vendor's pricing page.

---
name: classifying-ai-ambition-with-oar
description: Start with the strategic outcome and operating constraint, then classify AI ambition as Optimize, Amplify, or Reinvent.
---

# Classifying AI Ambition With OAR

Use OAR after the business diagnosis, not before it. The sequence is strategic outcome, metric and baseline, driver, operating constraint, AI fit and readiness, OAR level, measured result.

## When to use this skill

- A budget defense needs an outcome and an honest ambition level.
- A portfolio is described as transformation but reports activity or time saved.
- A team must decide whether to improve a task, change a workflow, or build a different operating model.

## Inputs to collect

- Strategic outcome, owner, period, and pre-AI baseline.
- Driver tree. For sales velocity: opportunity count x average deal size x win rate / sales-cycle length.
- Selected driver and evidence that it has credible room to move.
- Tasks, process, workflow, data, integrations, people, skills, ownership, incentives, and controls beneath the driver.
- AI fit, readiness gaps, full cost, and the expansion or exit decision.

## Process

1. **Name the outcome.** State the result, owner, period, baseline, and decision it will change.
2. **Decompose the metric.** Build the driver tree and select one component from the evidence.
3. **Diagnose the constraint.** Map tasks, process, workflow, data, integrations, people, skills, ownership, incentives, and controls.
4. **Test fit and readiness.** Decide separately whether AI can change the constraint and whether the organization can support, supervise, and measure it.
5. **Assign one OAR level.** Optimize improves a task in the current process. Amplify changes workflow, ownership, or decision quality inside the current operating model. Reinvent builds a different operating model from first principles.
6. **Attach the proof point.** Write the original metric, baseline, comparison, full cost, review date, and expansion or exit threshold.
7. **Measure the original result.** Activity, adoption, and hours saved can explain the mechanism but cannot replace the business outcome.

## Decision rules

- Do not classify an initiative until the outcome, driver, constraint, and readiness are known.
- If AI cannot credibly change the selected constraint, choose another intervention.
- Optimize, Amplify, and Reinvent are distinct. Never report task efficiency as workflow or operating-model change.
- Hours saved are capacity. Count them as financial return only when a cost stops or deliberate redeployment produces a measured result.
- A level without an outcome baseline and review decision is unproven.
- Reinvent is not automatically better. Readiness and the required outcome determine the appropriate level.

## Output requirements

| Initiative | Strategic outcome | Baseline | Selected driver | Operating constraint | AI fit | Readiness gaps | OAR level | Full cost | Measured result | Decision | Caveat |
|---|---|---|---|---|---|---|---|---|---|---|---|

Also deliver the driver tree, the reason the driver was selected, and the evidence that distinguishes the level from the other two.

## Verification loop

- Every row starts with a strategic outcome and baseline.
- Every selected driver is supported by the organization's own evidence.
- Every constraint includes process, data, integrations, people, and skills.
- AI fit and organizational readiness are separate decisions.
- The OAR level matches the operating change, not the ambition or budget.
- The measured result returns to the original metric.
- Vendor case studies are labelled directional and never used as expected return.

## Limitations

- OAR is a decision framework, not a causal model or universal benchmark.
- The correct level can change as readiness and the operating constraint change.
- Attribution requires a defensible comparison and an explicit note about concurrent changes.

## Rules of conduct

- Write for a Director, VP, or operator. Short sentences. Explain uncommon terms.
- Separate facts from assumptions. Never hide uncertainty.
- Do not invent numbers, benchmarks, quotes, or customer names.
- Do not send messages, change records, or publish unless the user explicitly asks.

## Evidence

- https://www.therevenueaireport.com/research/ai-roi-outcomes-first
- https://www.therevenueaireport.com/frameworks/oar
- https://www.therevenueaireport.com/blog/oar-matrix-ai-value-gap
- https://www.therevenueaireport.com/topics/measuring-ai-roi

## Cite this framework

Kvarfordt, Jonathan. "OAR." The Revenue AI Report. https://www.therevenueaireport.com/frameworks/oar

What does the Classifying AI Ambition With OAR skill do?

Connect a strategic outcome to its metric driver and operating constraint, then classify the AI ambition as Optimize, Amplify, or Reinvent.

Where does the Classifying AI Ambition With OAR skill come from?

Report framework library. The source and included files are shown on this page and in the package download.

Why was the Classifying AI Ambition With OAR skill chosen for this library?

Encodes a Revenue AI Report framework so the agent applies the published method instead of improvising one.

When should the Classifying AI Ambition With OAR skill not be used?

Do not use it for: Build us a five-week plan to get started with AI. Or: What order should we make these changes in without breaking the CRM? Or: Summarize this vendor's pricing page.

How do I install the Classifying AI Ambition With OAR SKILL.md file?

Download the file, create a folder named exactly classifying-ai-ambition-with-oar inside your agent's skills directory, and save the file inside it as SKILL.md. The agent loads it when a request matches the description.