How to Value a Pre-Revenue Project in 2026

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.

This is one of the most common questions in the micro-acquisition space, and it's also one of the most misunderstood. Traditional business valuation relies on revenue multiples — 3x annual revenue, 4x SDE, and so on. When revenue is zero, those formulas produce a single unhelpful number: $0.

But anyone who's been in the startup ecosystem knows that pre-revenue doesn't mean pre-value. Every SaaS unicorn was once a pre-revenue project. Every acquired product started with zero customers. The question isn't whether pre-revenue projects have value — it's how to quantify that value in a way that's honest, defensible, and useful for both buyers and sellers.

This guide gives you a practical framework. No hand-waving, no "it depends" without specifics. We'll walk through the five factors that actually determine what a pre-revenue project is worth, show you real formulas with worked examples, and explain the common mistakes that cause sellers to either massively overprice or massively undersell their work.

Why Pre-Revenue Projects Have Real Value

Before we get to the numbers, 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 5 Valuation Factors for Pre-Revenue Projects

After analyzing hundreds of pre-revenue project sales on platforms like ExitBid, Acquire.com, and SideProjectors, five factors consistently determine final sale price. Here's each one in detail.

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. According to TechCrunch's reporting on micro-acquisitions, growth rate is the single most cited factor in acquisition decisions for sub-$100K deals.

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.

Use the Free Valuation Calculator

If you want a quick, data-driven estimate of your pre-revenue project's value, we built a free valuation calculator that applies these factors automatically. Input your project type, user count, growth rate, and code quality — and get an instant range estimate.

The calculator is based on the same framework outlined in this article and is calibrated against real transaction data from the ExitBid marketplace. It's not a guarantee of what your project will sell for, 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.

Where to Sell a Pre-Revenue Project

Once you have a valuation, you need a buyer. Here are the most viable channels for selling pre-revenue digital projects in 2026:

• ExitBid: Auction format with verified buyers. The competitive bidding model works particularly well for pre-revenue projects because it lets the market determine the price — removing the guesswork from "what's it worth?" The auction creates urgency and often results in final prices above the seller's initial expectations. Zero commission means you keep every dollar. Learn how it works on our How It Works page.
• Acquire.com: Focused on startup acquisitions, including pre-revenue. Strong buyer pool of funded operators and serial acquirers. They charge a success fee but offer good deal support and buyer verification.
• SideProjectors: A free bulletin board specifically for side project sales. Lower price points on average, but zero barriers to listing. Good for sub-$5K projects where the overhead of a formal platform doesn't make sense.
• Direct outreach: If you know who your ideal buyer is — a competitor, a complementary product, a company in an adjacent space — reaching out directly can yield the best results. No platform fees, no middleman, and you can tailor the pitch to the buyer's specific situation.

For a complete breakdown of all the platforms available, read our guide on how to sell a pre-revenue project, which covers preparation, pricing, and the full sale process.

Frequently Asked Questions

Related Reading