Skip to lesson
Exit
Positioning & Messaging for a Developer ICP1 / 2

1 min lesson

Validate with users, not the conference room

Take "Validate with users, not the conference room" step by step, then finish with the result that proves it worked.

Step 1 of 2

Validate with users, not the conference roomthe JD calls for regular user interviews

  1. 1Draft the house from positioning. Core narrative and pillars first, grounded in the segment work, not in internal taste.
  2. 2Test it on real developers. Run interviews and message tests; watch which line they repeat back unprompted and which they shrug at.
  3. 3Listen for their words. The phrasing a developer uses to describe the value is usually better than yours - steal it.
  4. 4Refine and re-ship. Update the house, then keep it living as the product and the market move; messaging is an asset you maintain, not a deck you finish.
Watch out

The strongest internal opinion in the room is not evidence. A message everyone at Cursor loves can still fall flat with the developer it's for. Resolve disagreements by testing on users and bring that instinct to the interview - at a truth-seeking company, “let's check it with users” beats “I think it's catchier.”