ZigaForm version 5.5.1

Here’s a story I hear more than I’d like: A founder has a genuinely great app idea. They’re excited — the kind of excited where you’re sketching screens on your phone at midnight. They find a developer. They spend weeks in planning calls. They spend $10,000 to $15,000 on a build. And then they launch. And nothing happens. Not because the app was built wrong. Not because the developer did a bad job. But because nobody was waiting for it. No warm audience. No early adopters. No one who’d been asking “when is this going to exist?” The app launched into silence — and it’s incredibly hard to recover from that.

The key takeaway is validate your app idea first, read on to learn more about the why and how.

The most expensive mistake in app development isn’t choosing the wrong platform or the wrong developer. It’s building before you know anyone will use it.

This post is about what to do instead. It’s not a sales pitch — it’s the actual framework I wish every founder I work with had read before our first call together. Stick with me through the whole thing, because the order matters.

First: What Validation Actually Is (And What It Isn’t)

Most founders think they’ve validated their idea because they did some research. They Googled it. They found competitors — which they took as proof that the market exists. They asked their friends, who said “that’s a great idea!” They maybe even posted in a Facebook group and got some likes.

That’s not validation. That’s optimism with extra steps.

Real validation is about reducing risk before you spend money. It means finding out — from strangers, not friends — whether the problem you’re solving is real, whether people will actually pay for your solution, and whether you’ve correctly identified who your buyer is.

Notice what’s not on that list: a working app. A finished design. A pitch deck. A PRD. None of those things validates anything on their own.

Validation is a conversation before it’s anything else.

The three questions you’re trying to answer

Before you write a single feature, open Figma, or talk to a developer, you need honest answers to these three things:

1. Is the problem real — and painful enough to pay to fix?
 People have lots of problems they tolerate. They only pay to fix the ones that are frequent, frustrating, and expensive to live with. Your job is to find out which category yours falls into. Not from your own experience — from theirs.

2. Will they pay — and how much?
 “I would totally use that” is one of the most dangerous sentences a founder can hear. People say it to be kind. What you actually need is someone who pulls out their wallet, joins a waitlist, or gives you their email in exchange for early access. Behaviour, not opinion, is the signal.

3. Who exactly is the buyer?
 “Everyone” is not a market. Neither is “small business owners” nor “people who love fitness.” The more specific you can get — “independent tattoo artists in cities with no walk-in booking system” — the easier every future decision becomes. Specificity is what turns a good idea into a buildable business.

If you can answer all three with real evidence from real conversations, you’re ready to build. If you can’t, that’s your next task — not the app.

The Validation Anxiety Problem

Here’s something nobody talks about: most founders don’t skip validation because they’re reckless. They skip it because they don’t know what “done” looks like.

How many people do you need to talk to? What do you ask them? How do you find strangers who fit your target user? What counts as a signal that you’re onto something versus polite encouragement?

Because those questions feel hard to answer, many founders default to the thing that feels like progress: building the app. At least that produces something tangible. At least you can see it. At least you can show it to people.

But a half-built app is not a validated idea. It’s a bet.

The good news: validation doesn’t have to be complicated. It just has to come before the build.

What Bad Validation Looks Like vs. Good Validation

Bad validation:

  • Asking your friends and family if it’s a good idea (they will say yes)
  • Surveying people online with yes/no questions (they’ll click yes to be helpful)
  • Spending three months building a “beta” to test with users
  • Assuming competitors exist means the market is there for you too
  • Collecting “interest” without any friction or commitment

Good validation:

  • Having 10–15 honest conversations with strangers who match your target user
  • Asking about their current behaviour, not their hypothetical future behaviour (“how do you handle this today?” not “would you use an app that…?”)
  • Spotting the same pain point, unprompted, across multiple conversations
  • Finding someone who says “I’d pay for this right now — how do I sign up?”
  • Getting email signups on a landing page before the app exists
  • Sharing a prototype and watching where people get confused without you explaining anything

The common thread in good validation: you’re looking for behaviour and commitment, not opinions and encouragement.

A Note on “Fake Door” Testing

One of the most useful validation tools almost no one talks about is the fake door test.

Here’s how it works: you describe your app as if it exists — a landing page, a social post, a waitlist — and you measure how many people try to sign up, click “get early access,” or share it before you’ve built a single screen.

If nobody clicks? That’s data. If people sign up and then message you asking when it launches? That’s better data than any focus group.

The fake door test works because it removes social pressure. People aren’t telling you it’s a good idea to be polite — they’re voting with their attention and their email address. Those are much harder to fake.

You don’t need a working app to run a fake door test. You need a clear description of the problem you solve and a way for people to raise their hand.

How to Actually Talk to Potential Users

Finding strangers to talk to feels awkward. Here’s how to make it less so.

Where to find them:

  • Reddit communities where your target user already hangs out (search for the problem, not the solution)
  • Facebook Groups for your niche
  • LinkedIn if your target user is a professional
  • Local communities, meetups, or industry events
  • Reaching out directly to people whose job title or life situation matches your target user

How to open the conversation:
 Don’t pitch. Ask. Something like:
 “I’m researching [the problem space] and I’d love to hear how you currently handle [the thing]. Would you be open to a 15-minute conversation? No selling, I promise — I’m just trying to learn.”

Most people say yes. People like being asked for their expertise.

What to ask:

  • “Walk me through how you currently handle [the problem].”
  • “What’s the most frustrating part of that?”
  • “How often does this come up?”
  • “What have you already tried to solve it?”
  • “What would it be worth to you if this were solved?”

Notice what’s not on that list: “Would you use an app that…?” That question is leading and almost always produces useless answers.

How many conversations do you need?
 Aim for 10–15 with people who closely match your target user. After that many, you’ll start hearing the same things — the same frustrations, the same workarounds, the same language. That pattern is your signal. If you’re still hearing wildly different things after 15 conversations, your target user might be too broad.

How Do You Know When You’re Ready to Build?

This is the question nobody answers, so here’s a framework.

You’re ready to move forward when:

✅ You can describe your target user so specifically that you could find ten of them in an hour
 ✅ You’ve had at least 10 conversations with people who match that description — strangers, not friends
 ✅ At least 3–5 of them described the same problem in their own words, without you suggesting it
 ✅ At least one person has taken a low-friction action that signals real intent (signed up, paid a deposit, joined a waitlist, shared it with someone)
 ✅ You can say clearly: here’s the problem, here’s who has it, here’s why they’d choose my solution over whatever they’re doing today

You’re not ready to build yet when:

  • Everyone you’ve talked to is someone who already likes you
  • The most common reaction is “I might use that” or “it depends”
  • You haven’t found anyone who actively wants to give you money or be first
  • You can’t name your target user more specifically than a broad demographic

The Four Steps to Validate Your Idea Properly

Once you’ve had those early conversations and you’re seeing a real signal, here’s how to sharpen and scale your validation before committing to a full build.

Step 1: Nail Your One-Line Elevator Pitch

If your early conversations have gone well, you’ve probably heard your target users describe their problem in their own words. Use those words — not yours.

Your elevator pitch should pass a simple test: can a stranger understand it immediately, without you explaining anything?

Here’s a formula that works:

[App name] helps [specific type of person] [do the thing they’re struggling with] so they can [the outcome they actually want].

Examples:

  • “ReCrafted helps independent makers sell handmade goods to conscious buyers who care where their products come from.”
  • “BookMyShot helps sports photographers book sessions with athletes who need professional headshots.”

If you find yourself adding “but also” or “and then” — the pitch needs more focus. One sentence. One person. One outcome.

Why this matters: Your elevator pitch becomes the filter for every decision that follows. Every feature, every screen, every dollar you spend should connect back to it. If it doesn’t, it probably doesn’t belong in the first version.

Step 2: Write a Simple PRD

A PRD — Product Requirements Document — sounds like something that belongs in a corporate planning meeting. It doesn’t have to be. Think of it as a written answer to three questions:

1. Who exactly is this app for?
 Name the person. Not a demographic — a person. “A freelance graphic designer who takes on 3–5 clients at a time and loses track of revisions in email threads” is infinitely more useful than “creative professionals.”

2. What does the app do — just the essentials?
 List only the features the app cannot function without. Not your wishlist. Not “phase 2.” The core. If you removed this feature and the app still worked, it doesn’t belong here.

3. Why will people use it — specifically?
 What does life look like before the app? After? What are they doing today that your app replaces, and why is your version better?

One page is plenty. The goal is to think through the fundamentals before you sit down with a developer — so the conversation is about priorities and trade-offs, not basics.

The goal isn’t to build everything you imagined. It’s to build the smallest version that proves the idea works.

Step 3: Test It With a Clickable Prototype

Here’s where most founders want to jump straight to building. Don’t.

A clickable prototype is a realistic, interactive mockup of your app. It looks and feels like the real thing. Users can tap through screens, follow flows, and run into the same moments of confusion they’d hit in the live product. But it’s not a working app — which means it takes weeks, not months, and costs a fraction of a full build.

More importantly, a prototype gives you something to test with real people before you’ve committed to anything permanent.

Here’s what to watch for when you put a prototype in front of someone:

  • Where do they pause or hesitate?
  • What do they tap that you didn’t expect?
  • What do they say out loud vs. what they actually do?
  • Where do they get lost without you explaining anything?

If you have to explain how something works during the test, that’s a design problem — and it’s a much cheaper problem to fix in a prototype than in a live app.

A polished prototype also gives you something concrete to show investors. Not a napkin sketch or a slide deck — an actual product experience. Many founders have used prototypes to raise their first round of funding before a single line of code was written.

Step 4: Build Your Launch Audience Before You Launch

This one surprises a lot of first-time founders: you need users before you launch, not after.

Here’s why. When you submit an app to the Apple App Store or Google Play, the algorithm judges your app by its early momentum — downloads, engagement, and ratings in the first few days. If you launch to an empty room, the algorithm buries you. Recovery from a cold launch is slow and painful.

The solution isn’t to get lucky on launch day. It’s to build an audience while you’re still building the product.

How to build a pre-launch audience without paid ads:

  • A simple landing page with a clear description of what your app does and an email capture. Not a full website — one page. The goal is 100 emails from people who are genuinely interested, not your contacts list.
  • Show up where your users are. If your target user hangs out in a specific Reddit community, Facebook group, or Slack workspace — be there. Answer questions. Be helpful. Don’t pitch. Build familiarity.
  • Document the build. Post behind-the-scenes content about what you’re building and why. Founders who share their process publicly build audiences who are invested in their success before the product is even live.
  • Direct outreach. Identify 20–30 people who are your ideal first users and reach out personally. Not a mass email — a real message that shows you know who they are. Offer beta access. Ask for feedback. Make them feel like insiders.

One hundred emails might not sound like a lot. But 100 people who opted in because they genuinely want what you’re building? That’s a warm audience. That’s your launch day. That’s the difference between silence and momentum.

What Happens After All This?

If you’ve done the work — had the conversations, built the pitch, written the PRD, tested the prototype, and grown the waitlist — you’re in a completely different position than most founders who walk into a developer meeting.

You’ll know:

  • Which features your users actually care about (in their own words)
  • What’s confusing or missing from your current thinking
  • Whether the market is real — not assumed
  • What your app store listing should say, because users have already told you
  • How much (money) people are willing to pay, because some of them already said yes

And if the feedback told you something needs to change? That’s the best possible outcome. You found out before spending $10,000 to $15,000 on the wrong thing.

Validation isn’t a delay. It’s the work.

How Tiny Oak Studio Can Help

If you’ve read this far and you’re thinking “okay, I need to do this — but I don’t want to figure it out alone,” that’s exactly where we come in.

At Tiny Oak Studio, we work with early-stage founders to validate, design, and build no-code apps. We’ll help you go from idea to testable product — without building the wrong thing at the wrong budget.

Here’s what that looks like in practice:

Clickable MVP Prototype — $3,500 USD
 A fully designed, tappable prototype of your app’s core user flows. Includes a consistent design system and a shareable link you can put in front of real users or investors right away. This is the thing you test with. It’s not the thing you launch — it’s the thing that tells you what to launch.

Launch Landing Page — $2,000 USD
 A clean, well-designed one-page site with email capture, basic SEO setup, and copywriting guidance built around your target user. Goal: 100 real subscribers before your app goes live.

The Validation Bundle — $5,000 USD (save ~$500)
 Both together. This is the full pre-build validation stack — prototype to test the product, landing page to build the audience. Everything you need before you commit to a full build.

PackagePrice
Clickable MVP Prototype$3,500
Launch Landing Page$2,000
Validation Bundle (both)$5,000 (save ~$500)

We also offer a free Discovery Call — 60 minutes to look at your idea together, pressure-test the concept, and figure out what the right next step is. No commitment. No pitch. Just clarity.

→  Book a free Discovery Call
 →  Start with the $5,000 Validation Bundle

—————————————————————

Christina Cheng is the founder of Tiny Oak Studio, a Venture Lab that assists early-stage founders in creating no-code apps to test/validate their ideas before committing to building an app.