User Discovery Cadence
Definition
User Discovery Cadence is the team’s operating rule that direction-search quality depends on dense, repeated market contact: many user interviews in a short window, across the most plausible verticals, with paid recruiting used to fill gaps when warm networks are too slow.
Key points
- The search is a numbers game. Saar’s framing: meeting 20-50 people dramatically raises the chance of finding a painful, repeated problem. One or two meetings per week leaves the team trapped in theory.
- Density changes cognition. Guy’s personal operating point: when the calendar is full of user conversations, the mind switches from day-job problem solving to startup problem discovery. Sparse meetings leave everyone “half in.”
- Ten interviews per week became the near-term target. The meeting set an informal target that each participant should source roughly three interviews, producing around ten weekly user conversations.
- AM and construction can run in parallel. The team agreed it can keep account-management-vertical live while also testing construction/real-estate, as long as the total interview volume is high enough.
- Paid recruiting fills empty calendar slots. user-interviews became the recommended external channel, with pay-as-you-go pricing favored before committing to a larger package.
- Trend scans supplement user friction. Nizan proposed a session over recent YC / VC investments to create “aha moments,” but the meeting treated that as an input to ideation, not a replacement for talking to users.
Evidence
- 2026-06-20-directions-planning-the-week-18-30 — planning session where the team set a high-cadence user-interview plan, chose to source construction and AM/real-estate conversations in parallel, and decided to use user-interviews for paid participant recruiting.
Open questions
- What is the minimum weekly interview count that creates useful pattern recognition?
- How should the team balance warm intros, paid panels, and VC-sourced founder/market intelligence?
- What interview template avoids leading operators toward “Brain” as the answer?
- When should the sprint stop and force a vertical/product decision?