Set a first-year revenue target: median, not top 1%

Plan a solo product from the verified median, not from the rare top outcome. The exception is a caution, and the middle is the workable baseline. You are building something you can own, maintain, and keep profitable without burning out.

A verified monthly recurring revenue benchmark helps because it separates the products that are actually earning from the ones that are only promising. A recent analysis of a public revenue platform counted 10,150 products on September 4, 2026. The population is useful for solo software: small, public, and mostly unglamorous.

The median is the planning number

The most useful number is the middle of the products that actually made money in the recent period. Keep the baseline in view when you are deciding whether to keep building, pivot, or stop.

• Never-earned rate: 2,654 products, or 26.1%, had all three revenue fields at zero.
• 30-day median take: 4,987 products earned in the previous 30 days, and their median was $169.
• Top-1% capture: the top 1% took 76.1% of all platform revenue in that period.
• Personal earning rate: your own revenue, divided evenly across months.

The external baseline comes from the list. The personal number comes from your ledger. If your product has never earned, you are not failing the median. You are still below the minimum.

For a solo operator, the median is a margin number. It tells you whether a small product can cover its costs without a team. It also tells you when a slow start is normal and when it is a signal to change the offer, the audience, or the price. A slow start is a data point, not a verdict. Use it to choose the next fix.

The top slice is a warning, not a target

The strongest objection is that the median feels too low. If you are building a product, why not aim for the big number? Because the big number is not a realistic solo product first-year revenue plan. The top performers are a rare result, not a template.

When a small slice takes most of the money, the average becomes misleading. If you build your budget around the exception, you will keep working past the point where the product should be fixed, pivoted, or stopped. The outlier is useful as a check, not as a schedule.

The same caution applies to the headline annual revenue number. 272 products reported monthly recurring revenue of at least $8,333.33, the monthly amount required for a $100,000 annual run rate. After removing 27 stale qualifying records, 245 products, or 2.41%, had sufficiently fresh monthly recurring revenue. The outcome is rare, not a default.

Stale numbers matter. Of 390 records with monthly recurring revenue of at least $5,000, 37 were expired or had not synced for more than 30 days, and those records represented 37.4% of the platform's reported monthly recurring revenue. If a product is not syncing, treat its number as old and check the source.

A monthly margin and a year-long rule do the work

Now turn the data into a decision. Set a monthly margin target: the amount of revenue you need in a normal month to cover your costs, your time, and a small profit. Do not set it from a dream. Set it from what a solo product can plausibly earn, then compare it with your own recent take.

If your product is new, give it a fair test. If it is still earning nothing after a full year, stop or pivot. If it is earning, but below your margin target, ask whether the gap is fixable with a durable change: a clearer buyer, a better onboarding path, or a price that matches the value. Pick a single fix.

Count the hours, not just the dollars. A product that earns a little but consumes your evenings is a bad trade. A small product can still be a real business. If the margin is thin, the fix is usually smaller scope, not more features.

Write the target down, set a review date, and make the next decision from the margin. Keep the scope small enough to own, and let the next month's take set the next step.