Commercials, pricing & the business case

As a Field Engineer you are the technical truth-teller in a commercial conversation, not the person who quotes a number or signs a 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, and the removal of friction in security and procurement. When you blur that line you create chaos — an AE can't walk back a number you blurted out, and Legal can't unsay a compliance commitment you improvised.

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 the way you'd treat a sticker price on a car: it anchors the conversation, it is not what a 2,000-seat customer pays.

Enterprise adds the admin plane buyers actually need at scale: Organizations (GA, admin over teams), Groups for cohort-based spend and agent permissions, 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, audit logs, and AI-code tracking. That's why enterprise isn't 'list plus a markup' — it's a different product surface, and the price reflects governance, not just seats.

Seats are predictable; compute is where buyers get nervous. Agentic features — Cloud Agents in isolated VMs, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. runs, Autofix — consume model/compute, and a security or finance gatekeeper's first fear is an unbounded bill. Your job is to show that Cursor gives admins the dials 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.

Engineers measure in tokens, latency, and merged PRs. Buyers buy in dollars and throughput. Every technical metric you cite must be translated into the buyer's currency or it's just trivia.

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. Same product, three different opening lines.

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. The discipline is in being conservative on the inputs so the number survives scrutiny.

The frame an FE can defend in a procurement room
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 seat-math objection, done well

The objection: '$40 × 2,000 seats = $960K/yr — that's a lot.' The weak FE argues the price. The strong FE reframes the denominator and corrects the anchor.

1. 1Correct the anchor: list × headcount isn't the deal — enterprise is negotiated with volume discounts at 100+ seats.
2. 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.
3. 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.'
4. 4Land on payback: show the period in which value created exceeds total cost — then hand price negotiation to the AE.

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 — surface the right artifact, set the follow-up, and never improvise legal or compliance terms.

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.

1. 1Land a pilot with explicit, pre-agreed success criteria (cycle time, time-to-first-commit, adoption, review toil).
2. 2Drive adoption deliberately — Box got +75% usage in 6 weeks via mentorship, not by hoping.
3. 3Measure against the criteria; capture outcomes in the buyer's dialect (dollars/throughput).
4. 4Expand only when the evidence clears the bar — scale toward 500–5,000 seats with the AE carrying the commercial.

Map the buying committee