1 min lesson
Lock your kit
Walk through each part of "Lock your kit", then explain what each one does.
Step 1 of 2
Lock your kitStop tinkering
- Story bank
- One first-person story per value, each result-first and under 90 seconds, with the failure story rehearsed for follow-ups.
- Theses
- Your sequenced roadmap and your individual-vs-enterprise position, both defensible under pushback without losing the thread.
- Prototype stack
- The tools you'll build the small project in, fast enough that setup never eats your clock. Decide it now, not on the day.
Locking the kit a week out frees the final days for reps instead of fiddling.
The go/no-go bar
Don't book the loop until three things clear on the recordings: build (a demoable prototype from a vague gap, AI-driven and overridden with judgment), product sense (a sequenced roadmap defended under pushback) and authenticity (your Cursor usage and why-Cursor sound true, not prepped). If any of the three is faking a yes, that's exactly where this week's reps go.
Learn more
Full explanation
Final checklist
Final checklistBefore you book
- 1Demo-ready. You can spec, prototype and demo a real Cursor gap end to end inside 90 minutes and name the metric you'd watch.
- 2Opinion-ready. Your sequenced roadmap and individual-vs-enterprise thesis survive pushback, anchored to latency, trust, cost and daily usage.
- 3Story-ready. One first-person story per value, a real failure and a why-Cursor only you could give.
- 4Logistics set. In-person SF or NY confirmed, calendar blocked for a multi-day onsite and an honest yes on the flat, fast, no-process pace.
Learn more
Optional practice
Practice: Lock your kit
QYour mock scores are: product sense 5, build/technical 2, GTM/enterprise 4, values 4. How should you spend your prep week?