Anthropic’s revenue-organization guide frames rolling out Claude as climbing a maturity ladder rather than a one-off deployment: seats and training are the first step, and returns grow as the organization extends more access and trust.1 The source is vendor material; see the source summary.
The ladder
- Individual gains: chat assistant for drafting and research.
- Team workflows: connected systems and shared skills.
- Department workflows: plugins and managed agents.
- KPI and OKR gains: processes run end to end.
Three enablers grow alongside: fluency (from one task to parallel workflows), access and autonomy (from pasted notes to live CRM data), and governance (who publishes skills, what data each workflow reaches, who owns the results). The guide treats governance as continuous, not a phase.1
Decisions before a pilot
| Decision | Recommendation |
|---|---|
| Owner | RevOps, who own the CRM and the pipeline reporting |
| Connectors | Connect the tools people already use; manual uploads signal a missing connector |
| IT and security | Name an IT owner and agree provisioning dates before the pilot date; start the security review early |
| Metrics | One activity metric and one revenue metric, both baselined before deployment |
| Spend | Limits by org, group, and user, and usage analytics from day one |
| Cohort | Two or three teams with motivated leads |
As recommended in the guide.1
Rollout and the gate to scale
Set up (IT, connectors, champions), pilot (two or three teams, two or three use cases each), then scale in waves of about 25, then 150, then everyone, moving champion-built skills into a shared bundle.1 Scaling requires all three: people still producing after the novelty wears off, quality checks holding, and pilot teams ahead on the outcome metric. The guide’s best early predictor is how many champion-created skills pilot teams use regularly.1
Pitfalls
| Pitfall | Fix at setup |
|---|---|
| Pilot with no end date or decider | Put the scale decision, its owner, and its criteria on the sponsor’s calendar |
| Seats scaled, champions not | Keep one champion per 25–50 users through every wave |
| Spend ignored until the invoice | Set limits before the pilot; read usage weekly |
As described in the guide; the note’s author reads all three as a decision never given an owner and a date.1
Related
- Measuring an AI rollout
- Agent skill: the shared-skill mechanics behind stage 2.
- Source: Building an AI-Native Revenue Organization