Go or No-Go for an App Idea: Build, Narrow or Stop

What "go or no-go" means for an app idea

A go or no-go decision is a yes or no on spending money to build, based on evidence you set rules for in advance. "Narrow" is the answer most founders skip. It's also the one that saves the most money. For an app, there are really three answers, not two:

• Build: the evidence supports the idea as it stands.
• Narrow: the evidence supports part of the idea. Build that part only.
• Stop: the evidence doesn't support spending yet. Change something and test again.

The five signals and their pass bars

Use these bars to score your results. We suggest them as decision rules, not industry benchmarks. Raise them if your app needs lots of users to work, like a social app or a marketplace.

• 1. Problem. Pass: 5 of 10 target users describe the problem without prompting and already use a workaround. Fail: most say "nice idea" but do nothing about it. What a fail tells you: the pain is too weak, or you're talking to the wrong people.
• 2. Demand. Pass: 20 strangers sign up, 5 reply to a follow up email. Fail: signups mostly come from people you know. What a fail tells you: your promise isn't landing with strangers.
• 3. Commitment. Pass: 3 people pay a deposit, sign a pilot letter or book a setup call. Fail: everyone says "let me know when it's live". What a fail tells you: interest is polite, not urgent.
• 4. Usable flow. Pass: 4 of 5 testers finish the main task in a prototype without help. Fail: you have to explain the screens. What a fail tells you: a design problem, cheap to fix.
• 5. Repeat use. Pass: at least 2 users ask for the result a second time. Fail: nobody comes back after the first try. What a fail tells you: the outcome isn't worth enough yet.

How to score your results honestly

The score only works if you're strict with yourself. Follow these four rules, then add up the passes. Your total gives the verdict.

• 1. Bars are set before the data. If you moved a bar after seeing the results, count that signal as a fail.
• 2. Only strangers count. Friends, family and former colleagues don't count toward signals 1 to 3.
• 3. Almost is a fail. 4 of 10 on the problem signal is not a pass. Round down.
• 4. One strong B2B pilot can count as a pass. For a business tool, a signed pilot from a company that fits your target can be worth more than three consumer deposits.

From score to verdict

For each score, here is the verdict and the next step.

• 5 of 5. Verdict: build. Next step: get a fixed quote for the full first version.
• 4 of 5. Verdict: narrow. Next step: cut the scope to what passed, then get a quote.
• 3 or fewer. Verdict: stop. Next step: change the user or the problem and test again.

Build: when all five signals pass

A 5 of 5 means you have users waiting, their words for the problem, a flow they understand and proof they come back. That's what a studio needs to price your app without guessing. At this point, waiting costs you more than building. The people who committed in signal 3 won't wait forever, and their interest is your launch list. Our MVP Development package is built for this moment: your app on web, iOS and Android, fixed at $3,460, delivered in around 20 days.

Narrow: when four signals pass

A 4 of 5 is a go, but not for the app you first imagined. Which signal failed tells you what to cut.

If the flow failed (signal 4)

This is the best signal to fail. It's a design problem, not a demand problem. Simplify the main screens, test with five new people, and build once it passes.

If repeat use failed (signal 5)

People want the result once but not again. Shrink the promise to the moment they valued. A gym waitlist app might drop schedules and payments and only send the "a spot opened up" alert.

If demand or commitment failed (signal 2 or 3)

The problem is real but your offer isn't pulling strangers in. Narrow the target user. "Small business owners" becomes "physiotherapy clinics with two to five staff". Then rerun only the failed test.

If the problem signal failed (signal 1)

If this is your only fail, your sample was probably too broad. Check which interviewees did pass. Their segment is your real target. Once you know what stays, our guide You Got a Build Result. Here's What Goes in Your v1 walks you through what to keep, cut and postpone. Not sure which part to keep? Book a call and we'll go through your scores with you.

Stop: when three or fewer signals pass

Stop doesn't mean the idea is dead. It means hiring anyone now would turn a demand problem into an expensive build problem.

What to change before you test again

Change one thing at a time, then run the failed tests again with new people:

• The user: same problem, different group. A tool rejected by freelancers might pass with agencies.
• The problem: same users, a sharper pain. Go back to your interview notes and look for what people complained about without being asked.
• The promise: same user and problem, a different outcome. "Save time" rarely passes. "Send a quote in under a minute from your phone" is easier to test.

When to drop the idea for real

If you've changed the user or the problem twice and signals 1 and 3 still fail, let it go. No app fixes a problem nobody is trying to fix.

Three example verdicts

Here is how the score plays out on three ideas:

• Gym waitlist app, 5 of 5: owners manage waitlists by text, three sign up for a paid pilot, testers finish the flow, two owners ask for the alert again. Verdict: build.
• Expense app for freelancers, 4 of 5: strong problem and signups, but nobody logs a second expense in the manual version. Verdict: narrow to the one moment they valued, the end of month export.
• Social app for book clubs, 2 of 5: friendly interviews, signups mostly from friends, no commitments. Verdict: stop and change the user.

What to bring to your quote call

Scored a 4 or a 5? Book a call. In a free 30-minute call, we give you a fixed quote before we start. If you're still comparing studios, our guides on how to hire an MVP agency can help. Bring these four things:

• 1. Your score for each signal, with the bar you set.
• 2. Interview notes with the users' exact words.
• 3. The prototype link and where testers got stuck.
• 4. The one task the first version must do well.

What is a go or no-go decision for an app idea?

It's the choice to spend money on building, or not, based on evidence you set rules for in advance. For apps, there's a useful third option: narrow the idea and build only the part your results support.

Is 4 out of 5 good enough to build an app?

Yes, if you cut the first version to what passed. Which signal failed tells you what to remove. A failed prototype test only means fixing the design before you build.

Which validation signal matters most?

Commitment. A deposit, a signed pilot or a booked call costs the user something. Signups and kind words don't. If commitment fails, treat it as a stop even when other signals look good.

Should I hire a studio if my idea failed validation?

Not yet. Change the target user, the problem or the promise, then test again. A studio can build what you ask for, but it can't create demand that isn't there.