1 min lesson
Conservative math makes adoption the risk
Use "Numbers make the method concrete and credible" to say what you would do next.
Step 1 of 3
A worked example
Numbers make the method concrete and credible. This is a mid-market team, modeled conservatively on purpose.
Learn more
Advanced table
Adoption risk becomes the real question
- Input
- Developers on the team
- Value
- 40
- Source
- Discovery
- Input
- Loaded cost per dev
- Value
- $200,000/yr
- Source
- Their finance figure
- Input
- Hours saved / dev / week (measured)
- Value
- 3.0
- Source
- POC self-report + usage
- Input
- Realization haircut
- Value
- 40%
- Source
- Conservative assumption
- Input
- Realized hours / dev / week
- Value
- 1.8
- Source
- 3.0 × 60%
- Input
- Annual value
- Value
- ≈ $830,000
- Source
- 1.8 × 48wk × ~$96/hr × 40
- Input
- Cursor annual cost (40 seats)
- Value
- ≈ $19,000
- Source
- List, per-seat
- Input
- Payback period
- Value
- ≈ 9 days
- Source
- Cost ÷ monthly value
| Input | Value | Source |
|---|---|---|
| Developers on the team | 40 | Discovery |
| Loaded cost per dev | $200,000/yr | Their finance figure |
| Hours saved / dev / week (measured) | 3.0 | POC self-report + usage |
| Realization haircut | 40% | Conservative assumption |
| Realized hours / dev / week | 1.8 | 3.0 × 60% |
| Annual value | ≈ $830,000 | 1.8 × 48wk × ~$96/hr × 40 |
| Cursor annual cost (40 seats) | ≈ $19,000 | List, per-seat |
| Payback period | ≈ 9 days | Cost ÷ monthly value |
Even after a heavy haircut, the payback is so fast it stops being the argument - adoption risk becomes the real question.
Cursor's own field-engineering team built an internal usage calculator in Cursor: feed it an account name or a direct team ID (e.g. from Stripe) and it returns a granular breakdown of how that account uses Cursor by token and by model, so GTM can predict usage scope and trends. They keep hardening it on feature requests, and they wired it straight into Salesforce. The bridge went no-code-to-code too: an Airtable prototype rebuilt as a real app, hosted on Vercel with webhooks and a proxy feeding live data. Ask your SE counterpart whether that per-account view exists for your deal - it sharpens scoping and the business case.
"in Salesforce we have actually a tab that pulls up this usage calculator that's prefiltered to that account or that opportunity."
Before you send it, attack your own model the way a CFO will. Are the hours sourced or invented? Is the loaded cost theirs or yours? Did you haircut? Is every assumption visible and labeled? If you can't defend a line, cut it. A model that survives your own audit survives theirs.
In a mock demo or panel, when asked to justify value, don't recite features - walk them through a model out loud: "Forty devs, their loaded cost, measured hours from a POC, a 40% haircut and you still clear payback in under two weeks. The real question isn't ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition., it's whether adoption sticks - here's how we'd de-risk that." Showing the math and naming the real risk reads as a closer, not a pitch-deck reader.