Three months of building, a polished demo and a launch date on the calendar. Then the first ten prospects politely decline. Most founders have lived some version of that week. A focused customer discovery sprint prevents it, because it tests the riskiest assumptions before a single feature ships.
A two-week customer discovery sprint has three phases. First, write testable hypotheses about the customer, the problem and the buying process. Next, run 15 to 20 structured interviews. Finally, synthesize patterns and decide what to build, change or drop. Founders in the STAK Founder Residency use this rhythm with mentor support.
Key takeaways
- Customer discovery starts with written hypotheses, not a product demo.
- Interviews should ask about past behavior, never hypothetical future purchases.
- Synthesis turns raw notes into a clear decision about what to build next.
- A founder community supplies warm introductions that speed recruiting.
Days 1 to 3: write testable hypotheses
Good customer discovery begins by writing down what you believe and how you could be wrong. List three to five assumptions about your customer. For example, name who feels the problem, how often it happens and what they use today. Then rank them by risk. The assumption that would sink the company if false goes first.
Next, turn each assumption into a statement you can prove or disprove. “Property managers lose hours each week to manual access requests” is testable. “People want better software” is not. As a result, every interview has a clear purpose. Investors reviewing your pitch deck submission will look for exactly this kind of evidence later.
Finally, define your interview target. Choose one customer segment for the sprint, ideally one that matches the STAK Ventures focus areas if you plan to raise from us. Otherwise, mixed signals from different buyers will blur the results.
Days 4 to 10: run customer discovery interviews
Customer discovery interviews work when they focus on what people have already done. Recruit 15 to 20 people from your target segment. Warm introductions convert far better than cold outreach. Therefore, start with your own network, then ask each interviewee for one more referral. Founder events listed on the STAK Ventures events page are a strong place to meet operators and early adopters.
Keep each conversation to about 30 minutes. Ask about the last time the problem happened. Ask what they tried, what it cost and who else was involved. However, avoid pitching. The moment you describe your product, the interview turns into polite feedback instead of honest data.
In addition, take structured notes. Record direct quotes, current workarounds and any signs of budget. Meanwhile, a teammate or mentor can listen in and capture details you miss. Two sets of notes reduce the risk of hearing only what you hoped to hear.
Days 11 to 12: synthesize the patterns
Synthesis converts a pile of notes into a short list of facts you can act on. Start by tagging every note against your original hypotheses. Then mark each hypothesis as supported, contradicted or unclear. For example, if most interviewees describe the problem but none pay to solve it, urgency is the weak point.
Next, look for repeated language, a step mentors in the Founder Residency often review with founders. The exact words customers use become your positioning and your landing page copy. As a result, your messaging sounds like the buyer instead of the builder.
Finally, quantify loosely but honestly. Note how many interviewees raised a pain point without prompting. That count is not a market study. Still, it is more defensible than a guess. Wider market context, such as the PitchBook-NVCA Venture Monitor, cannot replace this firsthand evidence.
Want a mentor to review your interview plan and synthesis? The residency pairs early-stage founders with operators who have built before.
Days 13 and 14: decide what to build
A sprint is only useful if it ends with a decision. Choose one of three outcomes: proceed, adjust or stop. Proceed means the core problem and buyer held up. Adjust means the problem is real but the segment or solution needs to change. Stop means the evidence points elsewhere, which saves months of misdirected work.
Then translate the decision into a short build plan. Founders who later join the STAK Accelerator often bring these plans straight into their first pilot. Name the smallest product that tests the strongest finding. In addition, schedule follow-up calls with the most engaged interviewees, because they often become your first pilot users.
Share the summary with a mentor before you commit. A 1:1 mentor who has built before can spot blind spots that the team is too close to see.
Use your campus community to recruit faster
Founders who work inside an active community finish customer discovery sprints faster. Recruiting is the slowest part of any sprint. However, a shared campus shortens it. Peers introduce peers, and operators are often a short walk away. At STAK Space coworking, founders work alongside other companies that may be customers, partners or sources of introductions.
Moreover, the STAK campus connects living, working and mobility in one ecosystem. That ecosystem is part of what STAK Ventures offers founders. Founders building proptech or community products can speak with the people who run and use those spaces. That proximity turns a two-week plan into a realistic schedule.
Next step: run your sprint with support
A customer discovery sprint is simple to describe and hard to do alone. The STAK Founder Residency gives early-stage founders in downtown Oakland a 1:1 mentor, legal and accounting office hours, pitch coaching and investor access through the STAK Ventures network.
Applications are rolling, so you can start when your hypotheses are ready. In the meantime, write down your three riskiest assumptions and book your first five interviews. That small step turns customer discovery from an idea into a schedule, and it gives your mentor something concrete to review on day one.
Frequently asked questions
How many interviews does customer discovery need?
For a focused two-week sprint, 15 to 20 interviews within one segment usually reveal clear patterns. If the answers still conflict, narrow the segment and run another round.
Should I show my product during interviews?
Not during discovery. Ask about past behavior first. Once you have validated the problem, a separate round of demos can test the solution.
Is the Founder Residency worth the commitment during a sprint?
The residency is built for early-stage founders who are still testing assumptions. A mentor and peer community make the sprint faster, so it adds support rather than workload.
What if the sprint disproves my idea?
That is a valuable result. Two weeks of evidence that redirects the company costs far less than months of building the wrong product.
