Revenue Proxy Scoring: How To Tell If An App Idea Might Become Paid

The best early question is not “how much money can this make?”

It is:

What nearby behavior proves someone might pay?

That is revenue-proxy scoring. It is the lens behind every score on the App Opportunity Lab scorecard and every public opportunity brief.

What counts as a revenue proxy

A revenue proxy is not proof. It is a signal that the workflow touches money, deadlines, risk, status, or recurring effort.

Strong signals:

• the user already pays for a worse tool
• the user pays an expert to clean up the mess
• the user loses money when the workflow goes wrong
• the workflow repeats weekly, monthly, seasonally, or at deadline time
• the output is close to revenue, compliance, tax, or customer response

Weak signals:

• people say the idea is “cool”
• the demo gets likes but no one asks how to buy
• the user would only use it once
• the product depends on one fragile data source
• the buyer cannot name what happens if they do nothing

Example: thrift profit scanner

The revenue proxy is obvious. Resellers already make buy/skip decisions with money on the line. One avoided bad buy or one discovered high-margin item can pay for the month.

That does not mean the product is easy. Sold-comps data is fragile. But the willingness-to-pay signal is real. The Thrift Profit Scanner brief walks through this trade-off in full.

Example: rental receipt binder

The revenue proxy is tax-season pain and accountant back-and-forth. Small landlords already pay accountants. The app does not need to promise tax savings. It can promise better evidence and less reconstruction from memory. (Full write-up: Rental Receipt Binder brief.)

Example: boring compliance work

Compliance-adjacent workflows are an under-rated proxy goldmine. The buyer already needs proof that a task happened, and the cost of being wrong is real. See boring compliance app ideas for why this pattern shows up across so many niches.

A quick scoring scale

• 0-30: interest but no money signal
• 31-55: pain exists, willingness to pay unclear
• 56-75: plausible paid use if the MVP is narrow
• 76-100: strong paid-use signal, start validation now

Use the number to decide the next action, not to make yourself feel certain.

If the score is under 55, interview users. If it is 56-75, build a fake-door or concierge test. If it is over 75, run the 48-hour validation and ask for pre-payment or an annual founding spot.

Frequently asked

What is a revenue proxy?

A revenue proxy is a nearby behavior that suggests someone might pay for the workflow you are about to build. They already pay for a worse tool, they already pay an expert to clean up the mess, they lose money when the workflow fails, or the work repeats at deadline time. It is not proof of revenue. It is evidence that money already moves around this job.

How is revenue proxy scoring different from market sizing?

Market sizing asks 'how big could this be.' Revenue proxy asks 'is there any money near this job at all.' For a solo founder choosing between weekend builds, the second question is more useful — a huge market with no nearby money is worse than a small market with obvious money flowing through it.

What if there is no obvious revenue proxy yet?

Look one layer up. If users do not pay directly today, who else pays for the same outcome — an accountant, a consultant, a SaaS, a contractor? If nobody at any layer pays for the outcome, the app is selling delight, and delight is the hardest thing to charge for as a solo founder.

Does revenue proxy scoring replace user interviews?

No. It is the filter you use before interviews — to decide which ideas are worth interviewing about. The interviews then confirm or kill the proxy. Read more in validate an app idea in 48 hours.

Is a high revenue-proxy score enough to start building?

No. A high score means start validating, not start building. The next step is a 48-hour test that turns the proxy into a real conversation with a real buyer.