1 min lesson
The four objections you will get
Use "The four objections you will get" to tell the cases apart, then choose a response for each one.
Step 1 of 2
The four objections you will get
The one that kills deals if you fumble it.
Speak to 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. and enterprise controls plainly, do not over-claim and route specifics to the SE and the security review.
Honesty here is the deal; a confident wrong answer is worse than “let me get you the exact policy in writing.”
Position on depth, not slogans: codebase-wide context, agent workflows and the developer preference you already saw in their own org.
Use their reality: a Copilot license with low usage and devs choosing Cursor anyway.
Reframe free individual usage as the risk it is: shadow AI with no admin controls and no audit trail.
Enterprise buys governance, security and a managed rollout, not the editor.
Offer a defensible model tied to their numbers, with assumptions stated.
Propose a pilot with agreed success metrics rather than a slide of vendor-claimed percentages.
“On training: with our enterprise setup your code is not used to train models and 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. is built for exactly this concern. I will get you the precise data-handling terms in writing and I want our Sales Engineer to walk your security team through the controls so you are verifying it, not taking my word.”