2 min lesson
The wedge: bottom-up usage you can find
Put yourself in this case: "You learn that several engineers at a target account already use Cursor individually. How should that shape your outreach to the VP of Engineering?" Give the clearest next step.
Step 1 of 2
The wedge: bottom-up usage you can find
Many teams already have engineers using Cursor individually before you ever call. That is the wedge, not a problem. The motion is to find that organic usage and pitch making it the team standard.
- 1Find the love. Look for individuals at the account already on Cursor, public mentions or champions who'll say it's spreading.
- 2Quantify it. "Several of your engineers already use this" is a far stronger opener than a cold feature pitch.
- 3Name the gap. Individual usage has no admin, no shared billing, no security review. That gap is the team-plan conversation.
- 4Hand the AE a reason. The meeting you book is "standardize what your team already chose," which an AE can run with.
“Noticed a handful of your engineers are already in Cursor day to day, so this isn't a cold intro. I'd love twenty minutes on making that the team standard, with the admin and central billing an individual seat can't give you.”
Engineers adopting Cursor on their own is the start, not the finish. Turning that into a company deal means clearing concerns the IC never thinks about: data privacy and security, admin controls, central billing and a budget owner. Knowing these gates exist and who owns each is what separates an SDR who books real meetings from one who books enthusiastic dead ends.