Skip to lesson
Exit
Discovery, value mapping & the 90-day pilot1 / 3

1 min lesson

Value mapping: pain → capability → metric → money

Start at the first move in "Value mapping: pain → capability → metric → money" and carry it through to the proof.

Step 1 of 3

Discovery surfaces pain. Value mapping converts it into a number the economic buyer cares about. The chain is always the same:

  1. 1A persona's pain.
  2. 2The Cursor capability that addresses it.
  3. 3The metric that proves it.
  4. 4The economic translation into engineer-hours, cycle time or time-to-first-commit.
Learn more

Advanced table

Every row ends in a unit the economic buyer already budgets against

Persona
Staff/Senior Eng
Pain
Context-switching across repos to make one change
Capability
Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition.: guided environments, snapshots, /in-cloud subagents and local/cloud handoff
Metric
Cycle time per cross-repo change
Economic translation
Engineer-hours reclaimed per sprint
Persona
Reviewer / Tech Lead
Pain
Review queue backs up; bugs slip through
Capability
BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. (~90-second average review, ~10% more bugs found, ~22% lower run cost)
Metric
PR-to-merge time; escaped-defect rate
Economic translation
Faster merge cadence; fewer prod incidents
Persona
New hire
Pain
Weeks to first meaningful commit in an unfamiliar codebase
Capability
Codebase-aware chat + governed workflows
Metric
Time-to-first-commit
Economic translation
Onboarding cost per new engineer
Persona
Eng Director
Pain
Can't see or govern AI usage across teams
Capability
Organizations admin plane, Teams, Groups, usage analytics and audit logs
Metric
% governed AI usage; policy coverage
Economic translation
Risk reduction + spend visibility

Every row ends in a unit the economic buyer already budgets against.

Say it like this

"Your champions will tell you it 'feels faster.' The CFO doesn't buy feelings. I'll translate every win into engineer-hours per sprint, days off your cycle time and weeks off new-hire time-to-first-commit - the three lines your finance team already tracks."

The translation step is non-negotiable. A capability with a metric but no economic unit dies in the procurement review. 'BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. finds 10% more bugs' is a feature. 'Bugbot cuts escaped defects and at your incident rate that's N fewer Sev-2s a quarter at $X each' is a business case.

Learn more

Optional practice

Practice: Value mapping: pain → capability → metric → money

QA champion is thrilled that 'BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. finds about 10% more bugs.' Why isn't that a business case yet and how do you finish it?