An hour-by-hour timeline. What to do, when to stop, and the only validation signal that actually means anything.
Methodology. This is a tested 48-hour protocol, not theory. The hourly breakdown maps to what actually fits in two days of focused effort — about 12–16 working hours over the weekend. How we research.
The validation question that breaks most ideas is not “is this a good idea?” It’s “will anyone actually pay for it?” Surveys, conversations, likes, and even free signups all answer the wrong question. They tell you whether people like the idea. Liking an idea costs nothing. Paying for one costs money. The signals are not the same.
This protocol is designed to get you to a paid signal — or a clear “no” — in 48 hours. You will spend roughly $0–$50 in tools and you will know, by the end, whether to build the thing or kill it.
Your idea has to fit one sentence in the format: I’m building [product] for [specific audience] that [specific outcome] for [specific price].
If you can’t fit your idea in this sentence, the idea isn’t ready to validate. The most common reason people skip this step is that “specific audience” is the hardest part. “Small business owners” is not specific. “Owners of Shopify stores selling $10K–100K/month who fulfill orders themselves” is specific.
The price is part of the sentence because validation isn’t about whether people want the product — it’s about whether they want it at the price you need to charge. A free idea everyone loves has not been validated. A $49/month idea that 5 strangers pre-paid has been.
You need 50 names, with their handle or email, who match your specific audience and whom you can actually reach. Not 50 leads from a database — 50 humans you could DM by tonight if you decided to.
Where to find them, in order of yield:
Put all 50 in a spreadsheet with columns: name, contact handle, source, why they fit your audience.
The page does four things and nothing else: states the problem in your audience’s words, describes the solution in 2–3 sentences, shows the price prominently, and offers a way to commit (deposit, pre-order, or paid waitlist).
The tools that work for this in 4 hours flat:
The critical element: do not make this a free email signup form. Make it a paid waitlist or a founding-member deposit. $5–$25 is enough. Use Stripe’s payment links or a Lemon Squeezy product page if you want to avoid setting up a full Stripe account. The deposit can be refundable. What matters is that the prospect typed their card number.
Take your list of 50 and pick the 30 who you have the most context on — people whose recent posts you can reference, or who you have any connection to.
Each message should be 3–5 sentences long, reference something specific about that person, and end with a clear, low-pressure ask. Either “would you take a quick look?” or “does this resonate?” Not “want to schedule a call?” Calls take days to schedule and you don’t have days.
Send 5–10 messages per hour over 3–6 hours. Don’t batch all 30 in one sitting — the messages get worse as you fatigue. Spread them. Drink water.
Over the next 24 hours, replies will trickle in. Reply to all of them within 30 minutes. Send a polite, helpful message regardless of whether they’re going to convert. The replies fall into three buckets:
The first two buckets feel great. They’re mostly noise. Only the third bucket counts.
At the 48-hour mark, count the deposits. The interpretation:
5+ deposits means you have a real signal. Five strangers, contacted cold, pulled out their credit cards for a thing that doesn’t exist. That’s the strongest validation signal you can get without a finished product. Build it. Read the $0–$1K MRR playbook for what comes next.
1–5 deposits means there’s something here, but you don’t have enough signal to bet your time on it. The right next move is more discovery, not more building. Talk to the people who paid. Find out why they paid. Find 50 more people in the same audience and run a second 48-hour cycle with the messaging refined.
0 deposits means the idea, the audience, or the price is wrong. Don’t panic and don’t pivot wildly. Look at the replies you got. Did people seem to understand the offer? If yes — the audience or price is wrong. If no — the offer description is wrong. Either way, drop or reframe. Don’t spend three months building the thing.
The hierarchy of validation signals, from weakest to strongest:
The 48-hour protocol is designed to get you to the second-to-last signal — paid deposits — without building anything. That’s the highest-confidence signal achievable before you commit weeks or months of build time.
Your friends will tell you the idea is great. Your friends are not your audience. Validation from people who already like you is not validation. Specifically exclude friends and family from the 50-person list unless they happen to fit the exact audience profile.
“Take this 5-minute survey and I’ll send you the results” gets responses, but the responses are not validation. People answer surveys idly. Surveys filter for “people who fill out surveys,” which is not the same population as “people who pay for SaaS.”
The temptation is “I’ll spend 4 weekends building it, then pitch it once it’s real.” This inverts the order of operations. The point of validation is to find out whether building is worth your time. If you build first, you’ll be invested in the answer being yes.
If you ask for $1, you’ll get more deposits, but they don’t mean anything. The deposit needs to hurt enough that the person stops to think. $25–$50 is a sweet spot for B2B SaaS validation. $5–$15 for B2C.
When someone deposits, message them. Ask why. The reasons people pay are usually different from the reasons you assumed they’d pay. The real reason is the foundation of your messaging when you launch. Skip this and you’ll launch with the wrong pitch.
This is the template, with annotation. Adjust the bracketed parts to your specific context.
Hey [first name], saw your post about [specific thing they posted about] last week. Felt familiar — I’ve been talking to a few [audience] about exactly that.
I’m putting together a tool that [one-sentence value prop tied to their problem]. Charging $[price]/month. There’s a $[deposit amount] founding-member deposit that locks in the price for life.
Quick page here if you want a look: [link]
No pressure either way — would just love your gut reaction if you’ve got 30 seconds.
— [Your name]
Why this works:
This is itself a validation signal. If you cannot identify 50 specific humans in your target audience whom you could plausibly reach in 48 hours, your audience is either too narrow (not enough people exist) or too broad (you don’t actually know who they are). Both are problems with the idea, not the protocol.
Spend a few hours getting more specific. Browse our micro-SaaS idea catalog and AI SaaS ideas for examples of well-defined audiences. Look at the kinds of products in our micro-SaaS examples list — each one targets a clearly identifiable audience.
Some founders prefer to build a no-code MVP and validate by routing people to it. This works but it’s slower than the 48-hour deposit protocol. The MVP route takes a week or two. The deposit protocol takes a weekend. Use the deposit protocol first; if it greenlights the idea, then build the MVP.
If you’re going to build a quick MVP for validation, see how to build SaaS without coding for tools that compress the timeline.
Hours 0–2: write the one-sentence idea. Hours 2–6: list 50 reachable humans. Hours 6–10: build a one-page site with a real paid waitlist or deposit ask. Hours 10–24: send 30 personalized messages. Hours 24–48: count deposits.
5+ deposits means build. 1–5 means iterate the audience or messaging. 0 means drop or reframe. The protocol is rigorous because most ideas die at 0–1 deposits, and that’s the protocol working — you’ve saved yourself 3 months of building the wrong thing.
The founders who consistently ship working SaaS products are not the ones with the best ideas. They’re the ones who kill the wrong ideas in 48 hours instead of 18 months. Validation is, fundamentally, the discipline of being willing to hear “no” from strangers before you’ve fallen in love with the idea.
If you’re using a newsletter to build an audience around your future SaaS, see our take on Beehiiv vs Substack for the platform side of that question.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.