Start below replacement cost
The cost to recreate the product is useful context, but a buyer will not reimburse every hour. They inherit your decisions, dependencies, and technical debt along with the useful work.
Score transferable utility
A working deployment, coherent codebase, clear documentation, owned brand, active integrations, and tested workflows are more valuable than an impressive feature list that cannot be operated.
Look for demand evidence
Waitlists, retained users, credible interviews, search traffic, signed pilots, or repeated manual use can support value. The closer the evidence is to a buying decision, the more weight it deserves.
Subtract the buyer’s immediate burden
Estimate the focused work needed to make the product stable, compliant, supported, and sellable. Unclear ownership and undocumented infrastructure deserve especially large discounts.
Price for the realistic buyer pool
A narrow strategic fit can create strong value for one buyer but weak marketability overall. The range should reflect how many credible operators exist and how easily you can reach them.
Use a range, then let the market answer
For small pre-revenue products, a defensible range is more honest than a precise valuation. State the assumptions, show the evidence, and adjust based on qualified interest rather than vanity.
Ready to make the project legible?
Start with a private submission. There is no obligation to list.
Submit a project