How Much Is a Pre-Revenue Project Worth? A 2026 Valuation Guide

You built something. A SaaS app, an AI tool, a Chrome extension, a Telegram bot. It works. Maybe you have users. Maybe you have a waitlist. But you have zero revenue — and now you want to know what it's worth, because you're thinking about selling.

Here's the problem with almost everything you'll find when you search this. Every top guide on "pre-revenue valuation" — the Berkus method, the Scorecard method, the VC Method — was built to answer a completely different question: how much equity should I sell to an investor? Berkus assigns up to $500,000 to each of five factors, which can value a no-revenue startup at $2.5M pre-money. That number is real, and it's useless to you.

Traditional business valuation relies on revenue multiples — 3× annual revenue, 4× SDE, and so on. When revenue is zero, those formulas produce a single unhelpful number: $0. But pre-revenue doesn't mean pre-value. This guide gives you a practical, buyer's-eye framework: real 2026 deal data, a price-band table you can locate yourself in, four valuation methods that actual micro-acquisition buyers use, an honest look at what kills your price versus what raises it, and why an auction — not a fixed asking price — is the structurally correct way to price an asset that has no obvious number.

What Pre-Revenue Projects Actually Sell For (Real 2026 Data)

Forget theory for a second. Here is what pre-revenue projects have actually changed hands for, from public sales you can verify.

• Recover — $4,500 (from a $4,000 asking). Richie McIlroy sold this SaaS with $0 revenue on MicroAcquire (now Acquire.com). He listed at $4,000; a buyer asked for extra pricing tiers and paid $500 more for the work. Time from listing to close: about two weeks, with 20+ interested buyers, paid via PayPal. (full breakdown on Indie Hackers)
• Microns marketplace — ~$4,300 average deal. Over three years the Microns marketplace sold 90 startups for $390K in GMV. In 2022 alone: 21 deals, $130K GMV, with individual sales ranging from $150 to $40,000. Roughly 20% of listings are pre-revenue. (Microns newsletter, founder AMA)
• Real pre-revenue floor prices. Actual Microns pre-revenue listings: a work-from-home content website for $500, an SMS idea-tracking tool for $1,000, a crypto donations tool for $1,500. The floor for a no-users product is hundreds of dollars, not thousands.

Synthesizing the public data into bands you can locate yourself in:

One honest caveat on that table: the documented, closed pre-revenue sales we can verify cluster in the bottom two bands, roughly $500–$4,500 (the Recover and Microns comps above). The upper two bands — anything into the low five figures — are asking prices and with-traction estimates, not proven closed sales. Real users and transferable assets can get you there, but treat those figures as a ceiling to bid toward, not a number the market has promised.

Notice what these ranges are not: the $500K–$2.5M numbers you get from Berkus or the Scorecard method. Those are pre-money valuations for raising equity. If you're selling the whole thing for cash, the buyer is doing a build-vs-buy calculation, not underwriting your future. The rest of this guide is about winning that calculation.

Why Pre-Revenue Projects Have Real Value

Before we get to the methods, let's establish why pre-revenue projects are worth anything at all. It comes down to three fundamental assets that buyers pay for:

Working Code

A functioning product — even without revenue — represents real engineering work. A buyer who acquires your SaaS MVP doesn't need to spend 3-6 months building from scratch. They get a working codebase, a deployable product, and a head start. For many acquirers, especially those with existing distribution channels, the build-vs-buy math strongly favors buying.

Consider the economics: hiring a competent developer for 3 months costs $15,000-$45,000 depending on location and skill level. If they can buy a working product for $5,000-$15,000 that does 80% of what they need, the math is obvious. This is why even simple, well-built tools with zero users can sell for $500-$3,000.

Existing Users

Users are the single most valuable asset in a pre-revenue project. A product with 2,000 active users has proven something critical: people want this thing. That's market validation that no amount of market research can replicate. Users can be monetized. Users provide feedback. Users tell their friends. For a buyer, acquiring a product with an existing user base is dramatically less risky than building something new and hoping people show up.

Market Potential

Some projects sit at the intersection of a hot market and a genuine need. An AI-powered writing tool built in 2026 carries a different kind of value than a generic to-do app — not because the code is necessarily better, but because the market demand is structurally higher. Buyers pay premiums for projects in growing markets because the upside potential is larger and the risk of zero-demand is lower.

The 4 Methods Buyers Actually Use to Price You

Micro-acquisition buyers don't run DCF models on a $2,000 side project. They use four fast, defensible methods — usually in combination. If you understand each one, you can set an asking price the buyer can't easily argue down, and you'll know exactly where your number comes from.

Method 1: Cost-to-Rebuild (Replacement Cost)

This is the buyer's primary anchor, and it's the one you should compute first. The cost-to-rebuild method asks a single question: what would it cost me to recreate this from scratch? Estimate the development hours, multiply by a realistic contractor rate, then apply the buyer's discount.

Worked example. Your SaaS MVP would take a competent contractor roughly 160 hours to rebuild at $60/hour → $9,600 full replacement cost. Apply a typical 55% buyer discount → a cost-to-rebuild anchor of about $4,300. That's your floor for the code alone, before you add users or other assets. Note how close that lands to the real Recover and Microns numbers — this isn't a coincidence.

One honest caveat: for a corporate buyer, rebuilding your product internally (meetings, procurement, QA) can cost 5–10× what it cost you — which is why some acquisitions go for far more. But micro-buyers aren't corporations. Price for the buyer you'll actually get: an indie operator or a small studio doing the math above.

Method 2: Asset Stacking

Your project isn't one thing — it's a stack of separable assets, each with its own market. Asset stacking means pricing each one individually and summing them to establish a floor the buyer can't dismiss.

• Domain — benchmark against aftermarket comps on GoDaddy Auctions or Namecheap Market. A generic two-word .io is worth its renewal fee; a short, brandable, keyword .com is a real line item.
• Code — the cost-to-rebuild figure from Method 1.
• Email list / waitlist — captured intent. A waitlist of people who signed up for a paid tier is worth more per head than cold signups.
• SEO & backlinks — indexed pages that rank, plus referring domains. This is distribution the buyer gets for free.
• Social accounts & GitHub stars — social proof of demand that takes months to build.
• Configured integrations & billing — Stripe, auth, webhooks, and third-party APIs already wired up. Setup time the buyer skips.

Sum the stack and you have a defensible floor: "the domain alone comps at $300, the code rebuilds for $4,000, and there's a 600-person waitlist — so $4,500 is the floor, not the ask."

Method 3: Comparable Sales (Sold Prices, Not Asking Prices)

The most persuasive number you can bring is a comparable sale: a similar project that actually sold, for a known price. But there's a trap. Asking prices are not sale prices. On free classifieds like SideProjectors, listings routinely sit for months, unsold, at aspirational numbers — those tell you nothing. You want sold comps.

• Browse sold listings on Microns, Tiny Acquisitions, and Acquire.com — filter for pre-revenue in your category.
• On Tiny Acquisitions (a sub-$100K marketplace), listings under $10K typically have under $500/month revenue — so pre-revenue naturally sits at the very bottom of that range.
• Read the deal write-ups founders post on Indie Hackers and r/microsaas; the useful ones state the final price and why the buyer paid it.

This is exactly why the classifieds-forever model is weak for pricing: a stack of unsold asking prices is a graveyard, not a market. An auction produces a real, dated comp every time it closes.

Method 4: Option Value (What the Buyer Is Really Buying)

The final method is the buyer's own logic. They're not buying your past — they're buying an option on a future they can create faster than starting cold. The internal pitch sounds like: "I'll buy six months of development and a validated hypothesis for $3,000, then plug it into my existing audience."

Option value is why a project with the right buyer can sell above its cost-to-rebuild floor: to someone who already has distribution, your product is worth the incremental revenue it unlocks, discounted for risk. You can't force this — but you can price toward it by identifying the buyer for whom your project is a shortcut, not a science project. (This is also the entire argument for an auction, which we'll get to: option value differs wildly by buyer, so let them bid it out.)

The 5 Factors That Move Your Number Up or Down

The four methods above tell you how to compute a number. These five factors are the inputs that push that number up or down. After analyzing hundreds of pre-revenue project sales on platforms like ExitBid, Acquire.com, and SideProjectors and its alternatives, these five consistently determine the final sale price — and, not coincidentally, they're exactly the inputs our free calculator asks for.

Factor 1: Code Quality and Documentation

This is the foundation. The quality, completeness, and documentation of your codebase sets the floor for your project's value.

Think of it as a spectrum:

• Prototype / Proof of concept: Messy code, no tests, no documentation, works-on-my-machine only. Base value: $500-$1,500. Buyers are essentially paying for the idea validation and a starting point. They expect to rewrite most of it.
• Functional MVP: Clean-ish code, basic documentation, deployable by someone other than the creator. Base value: $1,500-$5,000. Buyers can actually use this as a foundation without a full rewrite.
• Production-ready: Well-structured codebase, comprehensive README, tests, CI/CD pipeline, environment documentation, deployment guide. Base value: $5,000-$15,000+. Buyers can take over same-day with minimal ramp-up time.

The gap between a prototype and a production-ready codebase is massive — often a 5-10x difference in base value. If you're planning to sell, investing a week in cleaning up your code and writing documentation can literally add thousands of dollars to your sale price. See our guide on how to value an online business for more on how code quality affects overall business valuation.

Factor 2: Active Users and Signups

Users are where pre-revenue valuation gets interesting. Each user represents proven demand, and engagement depth is what buyers actually scrutinize — not a headline signup count:

• Registered accounts (inactive): they signed up but aren't active. Still worth something as a retargeting audience, but low-confidence.
• Monthly active users (MAU): people using the product regularly. This is the most common engagement metric buyers evaluate.
• Weekly active users (WAU): higher engagement means higher retention, which means higher value.
• Daily active users (DAU): daily usage signals strong product-market fit and high switching costs.

How much any of this adds depends entirely on the buyer and the niche — a DAU on a productivity SaaS matters more than a DAU on a novelty Chrome extension — which is exactly why a competitive auction, not a per-user rule of thumb, is the honest way to price it.

Here's why users matter so much: a SaaS MVP with zero users is a code purchase. A SaaS MVP with 2,000 active users is a business purchase. The buyer isn't just getting code — they're getting validated demand and a group of people who already trust the product enough to use it.

Factor 3: User Growth Rate

Static user counts tell part of the story. Growth rate tells the rest. A project with 1,000 users and 25% month-over-month growth is fundamentally more valuable than a project with 1,000 users and flat or declining usage. Declining or flat usage is a discount; steady month-over-month growth is a premium — and the steeper and more sustained the trend, the more a buyer will pay above your cost-to-rebuild floor.

Growth rate is powerful because it's forward-looking. A buyer who acquires a project growing at 20% per month is buying a trajectory, not just a snapshot. It's also the fastest way to beat the Microns founder's warning that "buyers don't tend to pay well for pre-revenue" — a rising trend line is the closest thing to revenue you can show without having any.

Factor 4: Market Demand Signals

Beyond current users, several external signals indicate whether a project has latent demand that a buyer can unlock:

• Waitlist size: People who signed up but haven't been given access yet. A waitlist of 500+ indicates genuine interest and provides a built-in launch audience for the buyer.
• Beta signups: Similar to waitlist, but specifically for upcoming features or versions. Shows forward demand.
• Social proof: Product Hunt upvotes, Reddit threads, Twitter mentions, Hacker News appearances. These are non-trivial to manufacture and indicate organic market interest.
• Inbound interest: Have people asked to buy your product? Have competitors reached out? Have potential partners approached you? Document this.
• SEO position: If your project ranks for relevant keywords, that organic traffic is an asset. A project ranking on page 1 for "free invoice generator" has distribution value independent of its code.

Market demand signals meaningfully lift the base valuation, depending on their strength and verifiability. A Product Hunt launch with 500+ upvotes is a stronger signal than 200 Twitter followers.

Factor 5: Project Type

Not all project categories attract the same buyer demand. In late 2026, AI tools draw the deepest pool of active acquirers — many buyers are specifically hunting for AI-powered products they can integrate into an existing business — followed by SaaS products with a clear recurring-revenue path. Categories with built-in distribution (Chrome extensions via the Web Store, Telegram/Discord bots, newsletters with a direct audience) command interest for the same reason: the buyer inherits a channel they'd otherwise have to build. Content sites and mobile apps are more situational — their value hinges on SEO durability or platform risk rather than the category itself.

There is no reliable fixed "multiplier" per category — the premium a category earns is simply how many motivated buyers it puts in the room, which is precisely what a competitive auction converts into price. A hot category with two eager bidders clears higher than a hot category with one, regardless of any rule of thumb.

Worked Examples: Cost-to-Rebuild and Comps in Practice

The two methods that produce defensible, sourced numbers are cost-to-rebuild (your floor) and comparable sales (your market check). Here's how they combine on real pre-revenue cases.

Example 1: SaaS MVP, 0 Users, Prototype Code

You built a basic project management tool. It works, but the code is messy, there's no documentation, and you have zero users. You've essentially validated that the concept can be built, but nothing more.

Cost-to-rebuild: roughly 60 hours for a contractor to recreate the working parts at $60/hour is about $3,600 full replacement cost; apply a 60-70% buyer discount (messy code, buyer expects to rewrite much of it) and the anchor lands near $1,000–$1,500. Comps agree: real Microns pre-revenue listings with no users have sold for $500 (content site) and $1,000 (SMS tool). No users means no traction premium.

Realistic range: $500–$1,500. This is essentially a code sale. The buyer's calculation is simple: is it cheaper to buy this and fix it, or build from scratch? For most simple tools, buying a working prototype for $1,000 beats hiring a developer for a month.

Example 2: SaaS Product with Clean Code and Early Traction

You've built a subscription-management tool with a solid, documented codebase and a few hundred active users. No revenue — you never added a payment system.

Cost-to-rebuild: about 160 hours at $60/hour is $9,600 full replacement cost; a 55% discount for production-ready, handover-friendly code puts the code floor near $4,300. That is almost exactly what the SaaS Recover sold for ($4,500, $0 revenue, ~two weeks to close, 20+ interested buyers). Early users and clean documentation are what let a seller like that clear the top of the documented band rather than the floor.

Realistic range: $3,000–$4,500 as a documented closed sale. Meaningful, provable traction (a growing user trend, a waitlist for a paid tier) is what can push an ask into the low five figures — but that upper number is an aspiration until a buyer actually pays it, which is exactly the gap an auction closes.

What NOT to Include in Your Valuation

Just as important as knowing what to count is knowing what to leave out. These are the most common valuation mistakes sellers make with pre-revenue projects:

Don't Value Hours Spent

This is the number-one mistake. "I spent 400 hours building this at $100/hour, so it's worth $40,000." No. Your time is a sunk cost. Buyers don't care how long it took you to build something — they care about what they're getting. A project that took 400 hours to build but has messy code and zero users might be worth $1,000. A project that took 40 hours but has clean code and 5,000 users might be worth $20,000.

Your development time has zero correlation with market value. Pricing based on hours spent will either massively overprice your project (killing the sale) or occasionally underprice it (when you built something valuable in minimal time).

Don't Value Based on Revenue Projections

Pre-revenue means pre-revenue. You can't value a project at "3x projected annual revenue" when that revenue doesn't exist yet. Buyers will (correctly) view revenue projections from a seller as fantasy. Every seller thinks their product could generate $10K MRR "if someone just added Stripe." Buyers have heard this pitch a thousand times.

Value what exists today. If your product has strong signals that it could monetize well, those signals (users, growth, market demand) are already captured by the valuation framework above. You don't need to layer projections on top.

Don't Count Domain Registration Costs

Unless you own a genuinely valuable domain (short, brandable, keyword-rich .com), your domain registration cost is not an asset. A random two-word .io domain is worth approximately what you paid for it: $30-$50/year. Domain valuation is a separate discipline — don't conflate it with project valuation unless the domain has independent value.

Don't Add "Sweat Equity" or Opportunity Cost

Related to hours spent, some sellers try to add value for "what I could have earned at my day job instead." This isn't relevant to a buyer. The opportunity cost of your time is real to you, but it has zero impact on what the project is worth to someone else. The market pays for assets, not for the seller's alternative career paths.

What Kills Your Price — and What Raises It

Two projects with identical user counts can sell for wildly different prices. The difference is usually in the due-diligence details buyers scrutinize before they commit. Here's what appears on real SaaS DD checklists (from consultefc, madewithlove, and FE International), translated for a pre-revenue sale.

Almost every item on the right-hand list is a direct input to a valuation calculation — tech stack, code quality, documentation, weekly maintenance hours, traffic source, business age. Spend a week converting red flags into green ones before you list; it's the highest-ROI work you can do on a pre-revenue sale.

The Honest Truth: Any Asking Price Is a Guess — Why Auctions Fix It

Here's the structural problem with everything above. A pre-revenue project has no revenue multiple, no obvious anchor. Cost-to-rebuild gives you a floor, comparable sales give you a range, option value gives you a ceiling — but the actual number depends entirely on which buyer shows up and how badly they want it. When you set a fixed asking price, you're guessing where in that range the right buyer sits. Guess too high and you scare everyone off. Guess too low and you leave money on the table. Guess anywhere and your listing can sit unsold for months — the classic SideProjectors problem.

An auction removes the guess by handing the pricing question to the market. And this isn't just intuition — it's one of the most robust results in auction theory.

The effect is strongest precisely for assets like yours. Research on how firms are sold (Vasu, University of Houston) finds that companies with high valuation uncertainty — unique products, R&D-heavy, no clear comps — maximize their sale price through auctions, specifically because of price discovery. A pre-revenue side project is the textbook case of high valuation uncertainty.

This is why ExitBid runs a 5-day auction format. The deadline forces interested buyers to reveal what they'll actually pay, instead of anchoring off a number you invented. And here's the honest flip side: an auction won't make junk expensive. If the bidding doesn't clear your floor, you've learned the market's real verdict in five days for a flat $199 listing fee — not after six months of a dead classified listing. Listings are moderated before they go live, and if yours is rejected you get a full refund; there's no commission on the sale, so the price the market sets is the price you keep.

Want a Number to Start From?

Reading is one thing; a number is another. We packaged the four methods above into a free valuation calculator that scores exactly the inputs that move your price — tech stack, code quality, documentation, weekly maintenance hours, traffic source, and business age — and returns an instant range. It's the same framework as this article, applied automatically.

The calculator is calibrated against real transaction data from the ExitBid marketplace. It's not a guarantee of what your project will sell for — only a live auction produces that — but it gives you a defensible starting point for pricing and negotiation.

No signup required. No email gate. Just a tool that helps you price your project honestly.

Once You Have a Number, Where Do You List It?

Pricing is only half the job — then you need the buyer. We keep the full platform breakdown in a separate guide so this one stays focused, but the short version:

• ExitBid: A 5-day auction with a pool of registered buyers. As the section above argues, competitive bidding is the structurally correct way to price an asset with no obvious number — it lets the market decide, not your guess. Flat $199 listing fee, 0% commission, and pre-revenue projects are explicitly accepted. See how it works.
• Acquire.com, Microns, Tiny Acquisitions: Curated marketplaces with real buyer pools; success fees vary. Best for browsing sold comps as much as for listing.
• SideProjectors and free classifieds: Zero barrier to listing, but listings can sit for months at aspirational prices. If you go this route, see our SideProjectors alternatives comparison first.
• Direct outreach: If you already know the buyer for whom your project has the highest option value — a competitor or an adjacent product — a direct pitch can beat any platform.

For the full comparison, read where to sell a pre-revenue project and our step-by-step how to sell a micro-SaaS or side project guide. If your project was built fast with AI tools, the selling a vibe-coded app guide covers the extra due-diligence buyers will run on generated code.

Frequently Asked Questions

Related Reading