1 min lesson
Speak the customer's stack and constraints
Rebuild the parts of "Speak the customer's stack and constraints", then say why each one matters.
Step 1 of 2
Speak the customer's stack and constraints
Enterprise developers live inside constraints you have to speak fluently: security, compliance, scale and how a tool fits their existing pipeline. Generic enthusiasm bounces off them; specificity earns the room.
Enterprise concerns to speak natively
- Security & data handling
- 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., what's sent to models, what's retained, where code lives
- Identity
- 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., admin and team management, provisioning
- Deployment & rollout
- How it lands across hundreds of devs, network/proxy, version control
- Scale
- Large monorepos, indexing behavior, performance at their repo size
- Fit
- How Cursor sits next to their CI, review tooling and existing IDE setup
Naming the concern in their vocabulary signals you understand their world before you've pitched a thing.