A failed side project — what should you list it for? Setting a starting price when you sell an MVP prototype
"How much could I actually get for this?" — that's the first question that stops people cold the moment they decide to sell the abandoned app. Revenue-multiple formulas only work for a SaaS with users and revenue. A prototype with zero users and zero revenue needs a different basis for setting an MVP prototype sale price.
1. What's actually going on — why "my hours × my hourly rate" doesn't work
- The late nights and weekends you personally put in are a sunk cost. The market doesn't buy "how hard I worked" — it buys "how much time this saves me going forward."
- The price tags attached to side project monetization success stories in the indie scene are heavily survivorship-biased. The sale price of a quietly abandoned project is almost never made public.
- That's why public bidding (an auction) with a discovery-oriented starting price, rather than a fixed price, often becomes the realistic path to indie hacker income.
· r/indiehackers
· Small-SaaS acquisition market discussion (general reference)
2. The insight — four axes that split prototype pricing
(1) Rebuild cost
How many days or weeks would it take a buyer to build the same functionality from scratch? A UI kit, auth, a payments slot, an admin panel — all of these push rebuild cost, and price, up.
(2) Evidence of validation
Landing-page conversions, a waitlist, interview notes, screenshots, a demo video — these are far more persuasive than "just a repo with an idea." Even small numbers are better than none.
(3) How easy it is to transfer
Value goes up when docs, sample env vars, a README, and deployment steps are organized. A local setup only you understand drags the price down.
(4) How sharp the niche is
"A general-purpose productivity app" is a harder sell than "a workflow tool for a specific role or job." The narrower the niche, the more concrete the conversation gets — and the more realistic side project monetization expectations become.
A practical tip: a starting price is a conversation-opener, not your pride
- Too high a fixed price → zero views, zero feedback
- Too low a starting price → gets discovered, but can make the write-up look weak
- Recommended: a low-pressure starting price + an honest description + public bidding
Aiming for "coffee money, server costs, seed for the next sprint" is often more favorable for actually closing a deal than chasing a giant exit fantasy. That's also the realistic range for quiet indie hacker income.
3. What WakeAgain does about it
WakeAgain is a time exchange where you list a sleeping project publicly and see how the market reacts. Rather than agonizing over a number alone and then deleting it, testing it once through selling the MVP prototype leaves you with information — and a lighter head.
Just set a starting price and list it
You don't need a perfect valuation. The first step of selling the abandoned app isn't "finding the right number" — it's "finding where the market reacts." List it for free.
The takeaway
A failed side project's price isn't set by past labor — it's set by future time saved. If you want side project monetization, don't just try to land on a number alone — test the market by selling the MVP prototype.
Disclaimer: this post is a general guide for marketing and educational purposes and doesn't guarantee any listing price or revenue. Check the terms and listing details for actual deal conditions.