1 min lesson
Frame value as workflow, not magic
Name the key items in "Frame value as workflow, not magic", then explain why each one matters.
Step 1 of 3
Frame value as workflow, not magic
- Say what changes in their day: less boilerplate, faster onboarding, fewer context-switches out of the editor.
- Talk team standardization for managers - one tool, consistent practice, faster ramp.
- Keep claims testable: “codebase-aware edits,” not “10x your engineers.” Engineers will check.
“AI that writes your code for you” and “10x developer productivity” are credibility-killers with this audience. They're vague, unverifiable and slightly insulting to people who write code for a living. Describe the workflow change precisely and let them infer the value.
Learn more
Full explanation
Acknowledge competitors honestly
Acknowledge competitors honestly
If a team already runs Copilot or evaluated Windsurf, pretending those don't exist makes you look naive. Honesty about the landscape is more persuasive than spin - name the comparison and point to where Cursor is genuinely differentiated, like deep codebase context and the agent workflow.
HYPE (delete on sight): “Cursor's revolutionary AI will 10x your team and automate your entire codebase overnight.” CREDIBLE (an engineer keeps reading): “Cursor reads your whole repo for context, so edits and explanations are grounded in your actual code - most teams feel it first on onboarding and big refactors.”
“You're already on Copilot, so this isn't a first AI tool - the difference teams notice is how much Cursor pulls from the whole codebase, which is where most of the onboarding and refactor time goes. Happy to show the specific spots if it's useful.”
Learn more
Optional practice
Practice: Frame value as workflow, not magic
QA prospect's team already uses GitHub Copilot. What's the most credible way to position Cursor in your outreach?