1 min lesson
Do not open with a productivity multiplier or a generic claim
Tell someone how to act on this idea. "Show you understand the motion, not just the product."
Step 1 of 2
Your message may be the brand's first impression with an engineer, so open with a verified account signal, connect it to one concrete team problem, state the boundary on what the evidence supports and ask for one small next step. That is the test: specific evidence, relevant problem, honest boundary and clear ask.
Do not open with a productivity multiplier or a generic claim: open with a verified account signal, connect it to one concrete team problem, state the boundary on what the evidence supports and ask for one small next step. A technical reader can test what you say, so refuse a broader promise the evidence cannot support.
“I found verified Cursor usage on your team. If shared rules, security review or team administration is now the blocker, I can show your engineering lead the relevant controls in 20 minutes. If that is not the problem, I will leave it there.”
Show you understand the motion, not just the product. Explain the two lanes: verified existing usage calls for a team-level conversation, while a net-new account needs researched outreach. In both lanes, say which signal you would use, which problem you would test and which claim you would refuse to make without evidence.