A day-by-day plan to test whether a real problem exists, whether people will act on it, and whether your idea deserves more of your time, before you write a line of code.
Most ideas fail because nobody wants them badly enough, not because the product was built badly. Validation is about collecting evidence quickly and cheaply. This plan assumes you can give the idea a few focused hours each day for two weeks.
Write down three sentences and keep them visible for the whole sprint:
If you cannot fill in the current workaround, that is your first warning sign. Problems people care about usually have a messy workaround already.
| Day | Focus | Output |
|---|---|---|
| 1 | Define your target segment narrowly (industry, role, city, company size) | One-paragraph customer profile |
| 2 | Build a list of 30–50 people who match it (LinkedIn, communities, your network, Foundly) | Outreach list in a spreadsheet |
| 3 | Send short, personal outreach messages asking for a 20-minute conversation | 8–12 interviews booked |
| 4–6 | Run interviews using the script below | Notes for every interview, same format |
| 7 | Review notes: look for repeated pains, workarounds and spending | Top 3 problems ranked by frequency and intensity |
Ask about past behaviour, not future opinions. "Would you use an app that..." produces polite yeses that mean very little.
| Day | Focus | Output |
|---|---|---|
| 8 | Write a one-sentence value proposition based on what you heard | Clear promise in the customer's own words |
| 9 | Build a simple landing page or a one-page offer document | Page with one clear call to action |
| 10–12 | Drive targeted traffic: go back to interviewees, post in relevant communities, message your list | Sign-ups, replies, booked demos |
| 13 | Ask for a real commitment: a pre-order, a deposit, a letter of intent, or a scheduled pilot | Number of commitments |
| 14 | Decide: continue, change direction, or stop | Written decision with evidence |
A "commitment" costs the customer something: money, time, reputation, or access to their data. Compliments and likes are not commitments.
Agree your thresholds on Day 1 so you cannot move the goalposts later. Example criteria many founders use:
Adjust the numbers to your market. For B2B products with high prices, a few strong commitments can be enough; for low-priced consumer products you usually need much larger numbers.
Share your results with a mentor on Foundly and ask them to challenge your conclusions before you commit to building.
A ready-to-use script for customer discovery conversations, with the questions to ask, the traps to avoid, and a note-taking template so every interview produces comparable insights.
OpenHow to think about splitting equity between co-founders and early team members, including the factors that matter, vesting and cliffs, fixed versus dynamic splits, and a simple worked example.
OpenHow to write an opportunity post that attracts the right co-founders, professionals and mentors, with a clear title, defined scope, honest commitment and compensation details, and a before-and-after example.
Open