2 min lesson
When an enterprise need should - and shouldn't - bend the roadmap
Use two rows in "When an enterprise need should - and shouldn't - bend the roadmap" to state the practical decision rules.
Step 1 of 2
When an enterprise need should - and shouldn't - bend the roadmapsequencing under pressure
A large prospect will ask for things. Some of those requests are real signals about the next 50 customers; some are one logo's idiosyncrasy dressed up as a trend. Reading the difference is most of the judgment in this part of the job.
- The enterprise ask
- A security control every large org will need
- Bend the roadmap?
- Yes
- The reasoning
- It's table stakes that unblocks a whole segment, not one deal
- The enterprise ask
- A workflow many enterprises independently asked for
- Bend the roadmap?
- Probably
- The reasoning
- Repeated, independent demand is a real signal worth sequencing in
- The enterprise ask
- A bespoke integration only this customer uses
- Bend the roadmap?
- Rarely
- The reasoning
- High cost, narrow value; offer a workaround or a paid services path
- The enterprise ask
- Something that degrades the individual experience
- Bend the roadmap?
- No
- The reasoning
- Protect the wedge; the individual product is why enterprises want you
| The enterprise ask | Bend the roadmap? | The reasoning |
|---|---|---|
| A security control every large org will need | Yes | It's table stakes that unblocks a whole segment, not one deal |
| A workflow many enterprises independently asked for | Probably | Repeated, independent demand is a real signal worth sequencing in |
| A bespoke integration only this customer uses | Rarely | High cost, narrow value; offer a workaround or a paid services path |
| Something that degrades the individual experience | No | Protect the wedge; the individual product is why enterprises want you |
Distinguish a segment-opening requirement from a single account's special request.
Cursor lands in enterprises because individual developers already love it and bring it to work. If you degrade the individual experience to chase enterprise revenue, you kill the exact thing that makes the enterprise want you. The order matters: keep the developer experience exceptional, then build the controls that let an org adopt it safely.
“Individuals and enterprises want opposite things: the developer wants flow - fast, low-friction, out of the way - and the org wants control - security, governance, predictability. So I keep every flow-state feature ungated in the core product and never tax the developer to force an upgrade. Governance lives in the admin layer, where the individual never sees it. And I'd bend the roadmap only for a segment-wide need - a control every large org will require - not one logo's bespoke ask. The order matters: keep the developer experience exceptional first, because that's the wedge that makes an org want us at all.”
Learn more
Full explanation
Full explanation
When the onsite asks "what would you build for individual vs enterprise," don't list features for each. Name the tension first - flow vs. control, user-as-buyer vs. CISOChief Information Security Officer. The executive who owns security; usually the hardest and most important person to win over. Press Enter for the full definition.-as-buyer - then show your sequencing rule: keep the developer experience ungated, build governance in the admin layer and bend the roadmap only for segment-wide needs. If you've shipped an enterprise developer product before, this is where you ground it in a real example.
QAn enterprise prospect says they'll sign for 5,000 seats if you build a custom integration only they use. Sales is pushing hard. How do you reason about it?