What Makes an App Idea Score Well: How Our Rubric Reads an Idea

Every idea that reaches Goodspeed gets a score out of 100. The score is not a verdict on whether you should build it. It is a reading of the evidence: is someone already asking for this, is there room next to what exists, and will anyone pay for it.

This post explains how that reading is put together, so you can look at a score and know what it is telling you.

---

The three weighted parts

Most of the score comes from three parts, weighted so that together they add up to 100.

Market opportunity. Demand signals, the size of the market, whether people already pay for something close, and whether they would keep coming back. This is the part that asks "does anyone want this right now?"

Competitive landscape. How strong the existing options are, and how much room is left to do something different. A crowded market is not automatically a bad one. A market full of weak, generic tools can be an opening. One dominant product that people love is a wall.

Monetization. Whether a subscription makes sense for this product, and whether the revenue model is one that already works for similar apps.

---

The four adjustments

On top of the three parts, the rubric applies adjustments that move the score up or down.

Build difficulty. Points come off when an idea is hard to build or hard to keep running: deep technical work, reliance on third parties whose terms can change, or a real chance a platform rejects it. Being easy to build earns nothing, because an app that does nothing is the easiest app of all.

Solo viability. A small bonus when one person can realistically build, launch and market the app, which depends on how well it fits a phone and how reachable its first users are without a team.

Moat. A small bonus when the idea has an advantage a fast follower cannot copy in a weekend, such as its own data, a network that grows with use, or real switching costs.

Cold start. Points come off when the product is worth little until it already has content, supply or other users. Those first weeks after launch are the hardest part, and the score says so up front.

After deeper research. An idea that goes through deeper research can move a few points more: up for strong early retention, healthy unit economics or word-of-mouth growth, and down for serious risks.

---

Patterns that tend to score well

Specific tools for specific people. Not another to-do app, but a time tracker for freelance illustrators or a client portal for dog trainers. A narrow audience that already pays for tools scores well on market opportunity and monetization, and a narrow scope keeps build difficulty low.

Tracking for a specific condition or hobby. General fitness apps face strong incumbents. A tool for one condition, one sport or one collection has a passionate audience that general apps serve poorly.

Replacing a manual process people already pay for. When people spend money on spreadsheets, paper forms or a patchwork of tools to get something done, the demand is proven and the bar for a better version is clear.

---

Patterns that tend to score poorly

Social networks for a niche. "Like Twitter, but for X" runs straight into the cold start adjustment. The product is empty until other people are on it, and a solo builder has no budget to fill it.

Thin wrappers around a general chat tool. They score poorly on competition, because many already exist, and on monetization, because users can go to the underlying tool directly.

Ideas that depend on hardware or special access. These can have strong demand, but build difficulty and platform risk pull them down.

---

The monetization question

The single most useful test is whether people already pay for something close to what you want to build. "Users might pay for this" and "users already pay for a worse version of this" are very different starting points, and the rubric treats them differently.

Try it yourself: can you find people paying monthly for a tool that does part of the job badly? If yes, you are in good shape. If you would have to convince people the problem exists before you could sell the solution, the idea probably needs more work.

---

Reading a score in practice

A middling score usually means one part held the idea back. That is a diagnosis, not a rejection. Look at the breakdown: if monetization is strong but the competitive landscape is weak, the next step is research into how you would stand apart, not a new idea.

A low score usually means one part is close to zero, or an adjustment took a large bite. Ideas that depend on a crowd tend to lose points to cold start. Ideas that depend on hardware tend to lose points to build difficulty. Rewording the idea does not fix these, because they describe the shape of the product.

A high score is the rubric saying that people in this space pay for solutions, the existing tools are weak or narrow, and a focused product can ship and compete. That combination is rare.

---

Ideas that sit just below the top

The middle of the range deserves more attention than it gets. These ideas have real signal. Something specific is holding them back:

A real market, but too much scope. The market is there and pays, but the idea tries to solve everything at once. "A CRM for independent consultants" is a bigger, harder product than "a follow-up reminder tool for independent consultants."

Clear demand, no obvious way to reach buyers. If you can name the community, conference or newsletter where your first users already gather, the idea is easier to launch.

The right category, a vague angle. "A general health journal" competes with everything. "A migraine pattern tracker" competes with far less.

If your idea lands in the middle, read which part held it back and ask whether a tighter version of the same idea removes that constraint.

---

Try it yourself

The ideas library shows scores and the breakdown behind each one. Scoring your own idea is the free first step on Goodspeed.

Browse the ideas library or score your own idea.