1 min lesson
Show your data instincts explicitly
Walk through each part of "Show your data instincts explicitly", then explain what each one does.
Step 1 of 2
Show your data instincts explicitly
- Activation gap
- Seats provisioned vs. seats actually used - the first churn tell.
- Weekly active devs
- Trend, not snapshot; a falling line triggers a check-in.
- Agent / Tab acceptance
- Depth of adoption, not just login frequency.
- Champion engagement
- A quiet champion is a leading risk before any usage drop.
For each signal, state the action it triggers - that's what separates an operator from a dashboard reader.
Don't overclaim AI productivity. If you cite cycle time or PR throughput, frame it as a directional signal you'd validate with the customer, not proof of a 10x. Cursor's truth-seeking culture punishes inflated ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. claims harder than modest ones.
Bring a clean one-pager or short deck even if not strictly required. Structure and clarity are part of what's graded for this role family. Make the artifact skimmable in thirty seconds: goals at top, phases in the middle, the three numbers at the bottom.
A compact narrated version: "This account needs to hit 70% weekly-active by day 90 without spooking their security team. Day 0 to 30 is onboarding and security config, plus one instrumented pilot squad. By day 90, expansion to two more teams is gated on that pilot's own cycle-time numbers, and the renewal conversation is already teed up with a real activation curve behind it."