The 7-Day Customer Discovery Sprint: How Solo Founders Run 20 AI Interviews Before Writing a Line of Code

The Bottom Line

A 7-day customer discovery sprint is a focused, time-boxed week where a solo founder ships 20+ customer interviews, extracts the strongest pattern, and decides whether the idea is worth building — all before writing the first line of production code. The discipline matters because the alternative (build first, ask later) is the most common reason early-stage startups fail. CB Insights tracks "no market need" as the #1 startup post-mortem reason, year after year. A weeklong sprint is the cheapest insurance policy against that failure mode.

This playbook walks through the day-by-day structure, the AI tooling that makes 20 interviews-in-a-week realistic for a solo founder (without compromising rigor), the specific question patterns that elicit decision-grade signal, and the four go/no-go criteria you should be checking against by Friday evening. With Koji handling the interview moderation, transcription, and analysis automatically, the founder's job collapses to three things: design the brief, recruit participants, and read the report.

Why 7 Days, Not 7 Weeks

The traditional customer discovery cycle takes 4–8 weeks: write a guide, schedule interviews one by one, sit through them, take notes, transcribe afterward, code the themes, write the report. By the time you have an answer, your initial assumption has drifted, your competitive landscape has shifted, and your motivation has cooled.

The 7-day sprint compresses this for two reasons:

1. AI interview moderation removes the scheduling bottleneck. With AI moderated interviews, participants take the interview when they are free — async, at any hour, from any timezone. You don't need 20 calendar invites; you need 20 link clicks. That alone collapses two weeks of scheduling into zero.
2. AI analysis removes the synthesis bottleneck. As interviews complete, the analysis engine scores quality, tags themes, and updates the synthesis in real time. By the time interview 20 finishes, the report is already drafted. You read it; you don't write it.

The sprint is built around these two automations. A solo founder running it manually in 2026 — booking calendar slots, taking notes, transcribing afterward — would still need 4–6 weeks. With Koji, the same volume of evidence is reachable in 5 working days plus a weekend.

The Sprint at a Glance

That's a full discovery cycle for one founder on roughly a 10-hour budget across a week. The math only works because the AI layer is doing the heavy lifting on moderation and analysis. With a traditional zoom-and-notetake approach, the same week buys you 8 interviews, not 20.

Day 1 (Monday): Draft the Brief

The entire sprint hinges on a tight research brief. The best briefs answer four questions:

1. What decision will this research inform? Not "I want to understand my users" — "I want to decide whether to build feature X."
2. What's your current hypothesis? Write it down explicitly so the analysis can be tested against it.
3. Who specifically should participate? Define a tight screener — role, company size, current tool stack, last action they took.
4. What's a no-go signal? If 0 of 20 participants exhibit the pain you're solving, that's evidence to walk away. Decide the threshold now, not after the data.

In Koji, open a new study and hand the brief to the AI Consultant. It will ask 2–4 clarifying questions and draft a full interview guide with structured questions (open_ended, scale, single_choice, multiple_choice, ranking, yes_no — see the structured questions guide). Review and edit. Total time: ~2 hours.

For founders new to discovery, see customer discovery interviews for the methodology principles and koji-for-founders for the founder-specific workflow.

Day 2 (Tuesday): Recruit + Publish

The recruitment day is the most labor-intensive. Spread your sourcing across four channels:

1. Your network — DM 15–20 people who fit the persona. Don't mass-blast; personalize.
2. Communities you're already in — relevant Slack, Discord, Reddit, indie hacker forums. One post per community, low-key, with the Koji study link.
3. LinkedIn cold outreach — 30–40 connections with a tight personal note, link to the async interview at the end.
4. Existing customer lists — if you have an email list, signup waitlist, or beta tester pool, this is the highest-converting channel.

The key advantage with Koji: each contact gets one link, not a calendar invite. They can complete the async interview at 11pm if that's when they have 15 minutes. Conversion rates roughly 3-5x what you'd get with calendar-based booking.

For B2B founders, see recruiting B2B participants for sourcing tactics and user research recruitment email templates for proven copy.

Total time: ~3 hours.

Day 3 (Wednesday): First Interviews Land

By Wednesday morning you should have your first 3–5 interviews completed. Open Koji's insights dashboard and read them with these questions in mind:

• Is the guide eliciting the kind of answers you hoped for?
• Are participants matching the target persona (the screener is doing its job)?
• Is anyone giving suspiciously short answers? (The quality gate flags these as score 1 or 2 — Koji excludes them from the final report and refunds the credits automatically.)

If the answers are sparse, edit the discussion guide now. Add a follow-up probe to the question that's under-eliciting. Tighten a screener field that's letting wrong-fit participants through. You have time to course-correct on Day 3 in a way you don't on Day 6.

Total time: ~1 hour monitoring.

Day 4 (Thursday): Mid-Sprint Check + Push

By now you should have 8–12 interviews completed. Two things happen:

1. Read the rolling synthesis. Koji generates a draft report continuously as interviews complete. Check what themes are emerging. Are they confirming your hypothesis, contradicting it, or revealing something you didn't anticipate?
2. Push for more recruitment. If you're behind the 20-interview target, send a second wave to your network. Founders often plateau at 10 interviews because they stop asking; the founders who hit 20 are the ones who do a Thursday push.

Total time: ~1 hour.

Day 5 (Friday): Wave 2 Lands + Synthesis Review

By end of day Friday you should have 18–22 interviews completed. Open the Insights Chat and run three disconfirming queries:

• "Find quotes that contradict our main hypothesis."
• "Which participants pushed back on the proposed solution?"
• "Have any participants suggested something we didn't anticipate?"

This is the highest-leverage 30 minutes of the entire sprint. The disconfirming evidence is what saves you from confirmation bias — it's the data that prevents you from building the wrong thing.

Total time: ~1.5 hours.

Day 6 (Saturday): Report Drafting

The report is mostly already written by Koji at this point — themes ranked, structured questions visualized as charts, verbatim quotes pulled, participant counts tallied. Your job is editorial:

• Read the research report end-to-end.
• Highlight the three strongest themes and the three strongest disconfirming signals.
• Add a one-page executive summary in your own voice for future-you (or future investors).

The report is publishable as a shareable link. If you need it as a PDF for an investor pitch, Koji exports it directly.

Total time: ~30 minutes.

Day 7 (Sunday): Go / No-Go Decision

You have your evidence. Run it against the four go/no-go criteria you set on Monday:

1. Pain validation: Did 70%+ of participants exhibit the pain you're solving? (If yes → green light on problem.)
2. Solution interest: Did 50%+ react positively to the proposed solution direction? (If yes → green light on direction.)
3. Willingness to pay: Did 30%+ express explicit willingness to pay something? (If yes → green light on commercial viability.)
4. Disconfirming signals: Are the disconfirming signals strong enough to require a pivot? (If yes → revise hypothesis before building.)

The combination tells you what to do next:

• All four green: Start building. You've validated demand, direction, and price with real evidence.
• Pain green, solution red: The problem is real but your solution doesn't fit. Run a follow-up JTBD switch interview on the dissenting participants.
• Pain red: Don't build. You've saved yourself 6 months of work for a 7-day investment. This is the highest ROI outcome of the entire sprint.

Total time: ~1 hour to read and decide.

Cost of the Sprint

For a solo founder using Koji:

• Free tier signup includes 10 credits — enough for ~10 text interviews end-to-end.
• For a full 20-interview text sprint: upgrade to the Interviews plan at €79/month (79 credits — covers 20 voice or 79 text interviews with margin).
• Bad interviews don't cost. The quality gate auto-refunds credits for sessions scoring 1 or 2, so participants who give one-word answers don't cost you anything.
• All-in cost for the sprint: ~€80. Cheaper than one hour of a hired moderator's time — and you get the recordings, transcripts, analysis, and report as artifacts.

Compare that to the alternative: 4 weeks of part-time effort for 8 interviews and a manually-written report. The 7-day sprint is faster, cheaper, and produces more evidence.

When the Sprint Isn't the Right Move

A few cases where 7 days is too compressed:

• Highly technical B2B (e.g., infosec leadership): May need a 3-week sprint to recruit enough VPs of Security willing to take a 30-min interview.
• Regulated industries (e.g., healthcare clinicians): IRB approval and compliance review can take longer than the sprint itself.
• Concept testing with prototypes: If you need to ship a Figma click-through prototype as part of the interview, plan for an extra week of prototyping before the sprint starts.

For everything else — early-stage SaaS, indie hacker MVPs, founder-led consumer apps, pre-product B2B — the 7-day sprint is the highest-leverage way to validate before building.

What Happens After the Sprint

The sprint produces three durable artifacts:

1. A validated research report that you can hand to a co-founder, advisor, or investor.
2. A queryable transcript corpus — open the Insights Chat any time post-sprint to re-query the same interviews with new questions.
3. A baseline for the next sprint. Run the same brief 3 months later with new participants; the longitudinal comparison shows whether the pain is intensifying, easing, or shifting.

Most founders find their second sprint is even faster — they've learned the recruiting channels and can hit 20 interviews by Day 4. By the third sprint, the cycle compresses to 5 days.

Related Resources

• Customer Discovery Interviews — The methodology principles behind discovery interview questions
• Koji for Founders — Founder-specific workflow and plan recommendations
• Structured Questions Guide — How to mix open-ended and quantitative questions in a discovery guide
• MVP Validation Guide — The validation framework the sprint is built on
• Recruiting B2B Participants — Sourcing tactics for B2B founders
• User Research Recruitment Email Templates — Proven copy for cold outreach
• Insights Chat Guide — Post-sprint querying of the transcript corpus