Commercials, pricing & the business case
Support the deal in the buyer's dialect - without being the AE.
Your lane: support the motion, don't run it
After this you can name what the FE owns versus the AE and deflect a direct pricing question without quoting a number.
You are the technical truth-teller in a commercial conversation.
You don't quote a number and you don't sign the deal. Knowing exactly where your lane ends is what makes an AE trust you in the room.
The Account Executive owns price, terms and the close. You own proof:
- The technical evaluation.
- The success criteria.
- The value translation.
- Friction removal in security and procurement.
Blur that line and you create a mess the AE can't clean up. They can't walk back a number you blurted out and Legal can't unsay a compliance commitment you improvised in the room.
The FE makes the business case credible and the buying process frictionless. The AE makes the deal. You translate engineering reality into the buyer's dialect (dollars, throughput, ramp) so the AE negotiates from evidence instead of vibes.
- Owns
- Pricing & discount
- FE
- Never quotes
- AE
- Owns
- Owns
- Contract terms / legal
- FE
- Never improvises
- AE
- Owns w/ Legal
- Owns
- Technical eval & POV
- FE
- Owns
- AE
- Sets the goal
- Owns
- Value model / ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in.
- FE
- Builds the math
- AE
- Carries it to the buyer
- Owns
- Security/procurement friction
- FE
- Removes & routes
- AE
- Quarterbacks
| Owns | FE | AE |
|---|---|---|
| Pricing & discount | Never quotes | Owns |
| Contract terms / legal | Never improvises | Owns w/ Legal |
| Technical eval & POV | Owns | Sets the goal |
| Value model / ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. | Builds the math | Carries it to the buyer |
| Security/procurement friction | Removes & routes | Quarterbacks |
When in doubt, route price and terms to the AE and follow up.
"I'm not the right person to talk price - my job is to make sure the technical case is airtight so that conversation is easy. Let me get your AE the exact number and bring back the value model."
Takeaway. You own the proof; the AE owns the price. Route every number and term to the AE and follow up.
Self-check
How Cursor is priced: list vs negotiated
After this you can explain why enterprise pricing isn't list × headcount and what the negotiated tier buys beyond seats.
The two worlds: self-serve list and enterprise negotiated
Cursor has a published, self-serve tier and a negotiated enterprise motion. The published number is a starting point, not the deal. Treat list price like the sticker price on a car: it anchors the conversation, but it is not what a 2,000-seat customer pays.
Never let a buyer multiply list × headcount and call that 'the price.' That math ignores volume discounts (which kick in at 100+ seats), enterprise features and negotiated terms. If you let that number stand unchallenged, you've handed the buyer a fake-high anchor that makes your deal look expensive.
Enterprise adds the admin plane buyers actually need at scale.
So enterprise isn't 'list plus a markup.' It's a different product surface and the price reflects governance rather than seat count.
Self-serve, card-on-file
~$40/user/mo list
Team admin, privacy controls
Right for pilots and small teams
Negotiated annual contract
Volume discounts at 100+ seats
Org admin plane, SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool./SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave./RBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually.
Allowlists, audit, AI-code tracking
Takeaway. List ~$40/user/mo is a sticker-price anchor. Enterprise is a different product surface (governance), priced on that, not on seats alone.
Self-check
Usage, compute & avoiding bill-shock
After this you can turn a buyer's runaway-bill fear into a governance pitch using the three admin spend controls.
Seats are predictable. Compute is where buyers get nervous. Agent workflows consume model compute and a finance or security gatekeeper's first fear is an unbounded bill. The features that drive the spend are:
- 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. in isolated VMs.
- BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. runs.
- Autofix.
Show them the dials Cursor gives admins to make spend governed and predictable.
The three dials that kill bill-shock
- Model allowlists. Admins control which models can run, so spend can't leak to an expensive model nobody approved.
- Spend limits via Groups - set budgets at the cohort level, not per individual, matching how orgs actually fund teams.
- Per-team budgets. Fund a pilot squad differently from a 2,000-seat rollout; expansion doesn't silently inflate everyone's compute.
Don't apologize for usage-based compute. Reframe: 'You get to set model allowlists, Group-level spend limits and per-team budgets - so finance gets a ceiling, not a surprise.' Governance over compute is a selling point to the economic buyer, not a liability.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Runaway bill → spend limits via Groups; pricey models → model allowlists; unpredictable quarter → per-team budgets. Compute spend is governed, so bill-shock becomes a governance pitch.
Privacy ModeCursor's setting that routes requests under zero-data-retention terms so providers don't store or train on your code. + ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. are available, but NOT when the customer uses their own API keys. If a security gatekeeper assumes they can BYO-key and keep ZDR, correct it precisely or route to the right doc - do not hand-wave.
Takeaway. Compute spend is governed, not open-ended: model allowlists, Group-level spend limits and per-team budgets give finance a ceiling.
Self-check
The business case in the buyer's dialect
After this you can translate any technical metric into the dollars-or-throughput currency the specific buyer in the room cares about.
Engineers measure in tokens, latency and merged PRs. Buyers buy in dollars and throughput. Every technical metric you cite has to land in the buyer's currency or it's just trivia.
- Technical metric
- Time-to-first-commit for new hires
- Buyer's dialect
- Onboarding ramp → weeks of salary recovered per hire
- Technical metric
- Cycle time / PR lead time
- Buyer's dialect
- Throughput → more features per quarter, same headcount
- Technical metric
- Review & CI toil reduced (BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. averages ~90 seconds, finds ~10% more bugs, costs ~22% less per run)
- Buyer's dialect
- Senior-engineer hours returned → $ at fully-loaded cost
- Technical metric
- Cloud-agent fix proposals
- Buyer's dialect
- Bounded fixes prepared remotely → reviewer hours saved when accepted
- Technical metric
- Migration effort (Box: 80–90% less)
- Buyer's dialect
- Project cost avoided → headcount freed for roadmap
| Technical metric | Buyer's dialect |
|---|---|
| Time-to-first-commit for new hires | Onboarding ramp → weeks of salary recovered per hire |
| Cycle time / PR lead time | Throughput → more features per quarter, same headcount |
| Review & CI toil reduced (BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. averages ~90 seconds, finds ~10% more bugs, costs ~22% less per run) | Senior-engineer hours returned → $ at fully-loaded cost |
| Cloud-agent fix proposals | Bounded fixes prepared remotely → reviewer hours saved when accepted |
| Migration effort (Box: 80–90% less) | Project cost avoided → headcount freed for roadmap |
If you can't name the dollar or throughput equivalent, you haven't made the case.
Box: 85%+ daily active, 30–50% throughput increase, 80–90% less migration effort, +75% usage in 6 weeks driven by mentorship. Cursor is trusted by 64% of the Fortune 500. Use these as social proof, not as guaranteed outcomes for the prospect.
Lead with the metric the specific buyer loses sleep over:
- A platform VP buys cycle-time and review toil.
- A CTO scaling a team buys onboarding ramp and time-to-first-commit.
- A CFO buys throughput-per-dollar and migration cost avoided.
One product, a different opening line for each chair at the table.
"Your new hires take six weeks to their first meaningful commit. If Cursor takes two off that, across 40 hires a year that's 80 engineer-weeks back - call it your fully-loaded cost times eighty. That's the line your CFO will care about, not the seat price."
Takeaway. A technical metric with no dollar or throughput equivalent attached is trivia. Lead with the number that buyer loses sleep over.
Self-check
ROI / TCO framing and the seat-math objection
After this you can build a value frame a CFO can't tear apart and reframe the '$40 × seats' objection in four moves.
A simple, defensible value frame
Keep the model so simple a CFO can poke at it without a spreadsheet. The whole frame is value created minus cost to own. Stay conservative on the inputs and the number survives scrutiny.
ROI value = fully-loaded engineer cost/hr × hours saved per engineer per period × realistic adoption rate <-- discount this HARD × number of seats Net value = ROI value - (seat cost + enablement/mentorship cost) # Then: payback = net cost / monthly value created
The most common way these models lie is assuming 100% of engineers save 100% of the claimed hours on day one. Apply a realistic adoption rate (Box hit 85%+ daily - but over time, with mentorship). Model a ramp, not a step function. A conservative model that lands beats an aggressive one that gets torn apart in procurement.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
The value chain collapses to one number a CFO can check: the payback period. Adoption is the honesty dial - discount it hard so the number survives procurement.
Tab-accepts, suggestions shown, lines of AI code - these feel good and prove nothing about value. Tie the case to outcome metrics: cycle time, time-to-first-commit, review hours, escaped defects, migration cost. If a metric can go up while nothing ships faster, it's vanity.
The seat-math objection, done well
The objection sounds like this: '$40 × 2,000 seats = $960K/yr, that's a lot.' A weak FE argues the price down. A strong FE corrects the anchor and reframes the denominator.
- 1Correct the anchor: list × headcount isn't the deal - enterprise is negotiated with volume discounts at 100+ seats.
- 2Reframe vs. one input cost: compare the seat cost to a single fully-loaded engineer or to the eng-hours saved across those same seats.
- 3Convert to throughput: 'If each engineer gets back even an hour a day at adoption, that's the equivalent of N extra engineers you didn't hire.'
- 4Land on payback: show the period in which value created exceeds total cost - then hand price negotiation to the AE.
"Compare that seat cost to one fully-loaded senior engineer. If the tool gives your 2,000 engineers back an hour a day at realistic adoption, the math isn't 'a lot' - it's the cheapest capacity you'll add all year. Your AE will sharpen the actual number."
Takeaway. Value created minus cost to own. Discount adoption hard so the number survives procurement, then hand price to the AE.
Self-check
QWhich is the single most important variable to discount when building a Cursor ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. model and why?
Procurement, security review & land-and-expand
After this you can clear a security review by surfacing the right artifact and routing the rest and gate a pilot-to-rollout expansion on evidence.
Procurement and security as a path you clear, not a wall you climb
Enterprise deals die in procurement and security review more often than in the demo. Your job is to remove friction and route precisely.
- Buyer asks for
- Master agreement
- You provide / route
- MSAMaster Service Agreement. The overarching contract between a customer and a vendor. → AE/Legal
- Owner
- Legal
- Buyer asks for
- Data processing terms
- You provide / route
- DPAData Processing Agreement. A contract spelling out how a vendor is allowed to handle your data. → AE/Legal
- Owner
- Legal
- Buyer asks for
- Security attestation
- You provide / route
- SOC 2 Type II report
- Owner
- Security/FE routes
- Buyer asks for
- Who touches our data
- You provide / route
- Sub-processors list
- Owner
- Trust Center
- Buyer asks for
- Self-service due diligence
- You provide / route
- Trust Center
- Owner
- Trust Center
| Buyer asks for | You provide / route | Owner |
|---|---|---|
| Master agreement | MSAMaster Service Agreement. The overarching contract between a customer and a vendor. → AE/Legal | Legal |
| Data processing terms | DPAData Processing Agreement. A contract spelling out how a vendor is allowed to handle your data. → AE/Legal | Legal |
| Security attestation | SOC 2 Type II report | Security/FE routes |
| Who touches our data | Sub-processors list | Trust Center |
| Self-service due diligence | Trust Center | Trust Center |
Surface the artifact, set the follow-up. Never invent a term.
SOC 2 Type II, AES-256 at rest, TLS 1.2+ in transit, annual penetration test, Privacy ModeCursor's setting that routes requests under zero-data-retention terms so providers don't store or train on your code. + ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. (not with your own API keys), PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. + Cloudflare Tunnel, SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool./SAMLAn enterprise standard that powers single sign-on./OIDCOpenID Connect. A modern standard that powers single sign-on, built on OAuth., SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave., RBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually., model/MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs./repo allowlists, hooks, terminal sandboxing, audit logs, AI-code tracking. State what's verified; route anything you're unsure of.
If asked 'do you support [specific regulation]?' or 'can you commit to X in the contract?' and you don't have a verified answer, say 'let me get you the precise answer from our security/legal team' and set the follow-up. An invented compliance commitment can sink the deal or worse. Confidence in your lane; routing outside it.
Land-and-expand: expansion gated on evidence
The motion is land-and-expand: a focused pilot proves value, then you expand to the broader org, typically scaling from a pilot into the 500–5,000 seat range. Expansion is gated on evidence, not optimism. You don't ask for 3,000 seats. You let the pilot's measured outcomes ask for them.
- 1Land a pilot with explicit, pre-agreed success criteria (cycle time, time-to-first-commit, adoption, review toil).
- 2Drive adoption deliberately - Box got +75% usage in 6 weeks via mentorship, not by hoping.
- 3Measure against the criteria; capture outcomes in the buyer's dialect (dollars/throughput).
- 4Expand only when the evidence clears the bar - scale toward 500–5,000 seats with the AE carrying the commercial.
Map the buying committee
Usually an eng lead/IC who loves the product
Sells internally when you're not in the room
Arm them with the value model and proof
VP Eng / CTO / sometimes CFO
Buys throughput-per-dollar and ramp
Wants payback and predictable spend
CISOChief Information Security Officer. The executive who owns security; usually the hardest and most important person to win over. / security review team
Can veto; rarely champions
Win with SOC 2, allowlists, Trust Center
Owns MSAMaster Service Agreement. The overarching contract between a customer and a vendor./DPAData Processing Agreement. A contract spelling out how a vendor is allowed to handle your data., vendor process
Optimizes for terms and risk
Clear the path; route to AE/Legal
Expect: 'Walk me through how you'd handle a security review and a seat-math objection in the same call.' Strong answer: route price/terms to the AE, state verified security posture (SOC 2 Type II, allowlists, Trust Center) and set follow-ups for anything unverified, then reframe seat math via fully-loaded cost and throughput. Show you know your lane and the buying committee.
Takeaway. Surface the artifact, set the follow-up, never invent a term. Expansion is gated on measured pilot outcomes, not optimism.