2 min lesson
Lead with a researched reason
Recall the main items in "Lead with a researched reason", then connect each one to the work.
Step 1 of 2
Lead with a researched reason
The line after the permission ask is your hook and it has to be specific to this person. Generic value props die here. A real observed detail - hiring, a migration, a conference talk or the fact that their devs already use Cursor - proves you did homework and earns the conversation.
- Team growth: "You've opened a bunch of eng roles" implies onboarding pain Cursor can speak to.
- Observed tooling or stack: a public job post, GitHub activity or a tech-stack signal you can reference honestly.
- Existing bottom-up usage: "A few of your engineers are already on Cursor" - a strong, true, Cursor-specific hook.
- A trigger event: a funding round, a new VP Eng or a stated push on AI tooling.
"Revolutionary," "transformative," "state-of-the-art," "synergy" - to a technical buyer these are noise and they flag you as someone who doesn't understand the product. Cursor sells to skeptical engineers who can smell marketing language in one syllable. Describe what the tool does in plain, concrete terms and let the specifics carry the weight.
Have your first ten seconds memorized to the point of muscle memory, so nerves don't leak through in the mock. When the interviewer picks up as a cold, slightly annoyed buyer, your automatic, calm opener is itself a graded signal. Practice it out loud until you can deliver it while distracted - that's the bar for sounding natural under pressure.