1 min lesson
Enterprise table stakes
For each case in "Enterprise table stakes", name the signal and the response you would use.
Step 1 of 2
Enterprise table stakesthe checklist that gates the deal
A lot of enterprise work isn't glamorous product - it's the controls that let a security team say yes. These rarely show up for the individual user, but their absence ends an enterprise conversation before it starts. Know what's actually table stakes versus what's differentiating.
Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. defines what is sent, retained and used for training.
Zero-data-retention options and SOC 2-style attestations.
The first question a 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. asks: does our code leave our boundary?
SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. / SAMLSecurity Assertion Markup Language. The XML-era enterprise standard that powers single sign-on: your identity provider vouches for you to each app. Older than OIDC but still what many enterprise tools speak. Press Enter for the full definition., team and seat management, role-based access.
Org-level policy: which models, which features, which data settings.
Audit and usage visibility for the admin who has to answer for it.
Options that fit the customer's risk posture and data-residency needs.
Procurement, legal and vendor-review readiness.
Predictable behavior across a large, heterogeneous org.
A plan that maps to how the org buys, not just per-seat self-serve.
Centralized billing and provisioning.
Room for the enterprise motion without repricing the individual.