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:

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 the market has established rough per-user values based on user type:

• Registered accounts (inactive): $0.10-$0.50 per user. They signed up but aren't active. Still valuable as a retargeting audience, but low-confidence.
• Monthly active users (MAU): $0.50-$1.50 per user. They're using the product regularly. This is the most common metric buyers evaluate.
• Weekly active users (WAU): $1.00-$2.00 per user. Higher engagement means higher retention, which means higher value.
• Daily active users (DAU): $2.00-$3.00+ per user. Daily usage signals strong product-market fit and high switching costs.

These ranges vary by project type and market. A DAU on a productivity SaaS is worth more than a DAU on a novelty Chrome extension. But these brackets give you a working baseline for estimation.

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.

The market applies growth premiums roughly as follows:

• Declining or flat growth: No premium (may apply a 10-20% discount)
• 5-10% monthly growth: 10-20% premium on user value
• 10-20% monthly growth: 20-40% premium on user value
• 20%+ monthly growth: 40-60% premium on user value

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 typically add a 10-30% premium to the base valuation, depending on strength and verifiability. A Product Hunt launch with 500+ upvotes is a stronger signal than 200 Twitter followers.

Factor 5: Project Type Premium

Not all project types are valued equally. The current market applies premiums based on project category, reflecting buyer demand and perceived monetization potential:

These multipliers are applied to the overall base valuation and reflect current market conditions as of early 2026. AI tools carry the highest premium because demand from buyers significantly outstrips supply — many acquirers are specifically hunting for AI-powered products they can integrate into existing businesses.

Valuation Formulas with Worked Examples

Now let's put these factors together into a practical formula. The general framework is:

Let's walk through four real-world scenarios to show how this works in practice.

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.

• Code base value: $500-$1,000 (prototype quality)
• User value: $0 (no users)
• Growth premium: 1.0x (no growth data)
• Type multiplier: 1.5x (SaaS)
• Demand signals: None

Estimated value: $750-$1,500

This is essentially a code sale. The buyer is paying for a head start on building something similar. At this price point, the buyer's calculation is simple: is it cheaper to buy this and fix it, or build from scratch? For most SaaS products, buying a working prototype for $1,000 beats hiring a developer for a month.

Example 2: SaaS Product, 2,000 MAU, 20% Monthly Growth, Clean Code

You've built a subscription management tool with a solid codebase, comprehensive documentation, and 2,000 monthly active users growing at 20% per month. No revenue — you never added a payment system.

• Code base value: $5,000-$8,000 (production-ready)
• User value: 2,000 MAU x $1.00 = $2,000
• Growth premium: 1.5x (20% monthly growth = 50% premium on user value, so user value becomes $3,000)
• Type multiplier: 1.5x (SaaS)
• Demand signals: +$1,000 (Product Hunt launch with 300 upvotes)

Estimated value: $13,000-$17,500

This is a strong pre-revenue listing. The combination of clean code, active users, and meaningful growth makes this attractive to buyers who already have monetization expertise. A buyer with experience in SaaS pricing could realistically start generating revenue within weeks of acquisition.

Example 3: AI Tool, 1,000 MAU, 25% Monthly Growth, Waitlist of 800

You built an AI-powered content repurposing tool. It takes long-form content and generates social media posts. You have 1,000 monthly active users, 25% growth, and 800 people on the waitlist for a "pro" version you never built.

• Code base value: $4,000-$7,000 (functional MVP with API integrations)
• User value: 1,000 MAU x $1.25 = $1,250
• Growth premium: 1.5x (25% growth = $1,875 adjusted user value)
• Type multiplier: 1.8x (AI tool)
• Demand signals: +$2,000 (800-person waitlist, active Twitter following)

Estimated value: $12,500-$18,000

The AI multiplier and strong waitlist push this project into a higher range despite having fewer users than Example 2. The waitlist is particularly valuable because it represents people who have already expressed willingness to pay — they signed up for a "pro" version, implying price tolerance.

Example 4: Chrome Extension, 5,000 WAU, Steady Growth

You built a Chrome extension that helps users manage browser tabs with keyboard shortcuts. It has 5,000 weekly active users in the Chrome Web Store, growing at 10% per month, with a 4.5-star rating and 200+ reviews.

• Code base value: $3,000-$5,000 (production-ready, well-documented)
• User value: 5,000 WAU x $1.50 = $7,500
• Growth premium: 1.25x (10% monthly growth = $9,375 adjusted user value)
• Type multiplier: 1.3x (Chrome extension)
• Demand signals: +$1,500 (200+ reviews, 4.5-star rating, Chrome Web Store presence)

Estimated value: $14,000-$21,000

Chrome extensions with established store presence and strong reviews carry hidden value: the Chrome Web Store listing itself is an asset. Reviews, ratings, and install counts take months to build and can't be transferred to a new listing. A buyer gets all of this instantly.

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.

Use the Free Valuation Calculator

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