What acquirers are actually buying in a pre-revenue SaaS sale, and how to frame and negotiate it.

Pre-revenue SaaS businesses are acquired every week. The acquirer is not paying for what the business has produced — they are paying for what it represents: a validated technical solution to a specific problem in a specific market, built by a team that has demonstrated the capability to build it, in a form that can be integrated into the acquirer's existing product or distribution. Understanding what pre-revenue acquirers are actually buying is the first step to structuring a pre-revenue business that can be sold — and to negotiating a price that reflects the real value of what you have built. For $1, this article explains the mechanics of early-stage strategic exits and gives you the negotiating framework for selling a pre-revenue SaaS product.

The phrase 'pre-revenue' understates what a developed SaaS product with no paying customers actually represents. It represents validated technology, real users (if not yet paying ones), and a team's time investment at real market cost. Each of these has a value to a strategic acquirer — and that value is the basis of the negotiation.

Acquirers of pre-revenue SaaS businesses are typically motivated by one of four strategic drivers. First: technology acqui-hire — buying the team more than the product. If your team has built something technically sophisticated, a larger company may pay to acquire the team and fold the technology into their existing product. Second: feature gap fill — your product solves a specific problem that the acquirer's product does not currently solve, and building it would take longer than buying it. Third: market entry — your product has traction in a market the acquirer wants to enter, and acquisition is faster than organic entry. Fourth: competitive pre-emption — the acquirer wants to prevent a competitor from acquiring you.

Understanding which driver applies to a specific potential acquirer changes the negotiating strategy entirely. An acqui-hire acquirer is primarily valuing your team. A feature gap acquirer is primarily valuing your technology. A market entry acquirer is primarily valuing your user base. Each valuation basis implies a different negotiating leverage.

The starting point for pricing a pre-revenue SaaS exit is the replacement cost of the technology: how much would it cost the acquirer to build the equivalent functionality from scratch, using external development resources at market rates? Get a credible estimate from a development firm — not your own assessment. A credible third-party cost estimate is a negotiating document.

The second input is the team cost: if the acquirer intends to retain the founding team in an earn-out arrangement, the cost of recruiting comparable talent in the market is the floor of the team component of the valuation. Senior SaaS developers and product managers command premium salaries — use current market salary data to build this calculation.

The third input is the strategic premium: the additional value the acquisition creates for the specific acquirer beyond the technology and team replacement cost. This is the hardest element to quantify but often the largest. If your technology helps the acquirer enter a market they have been pursuing for two years, the strategic value of shortcutting that timeline is real and significant — but the acquirer is unlikely to volunteer it. Your negotiating job is to research the acquirer's stated strategic priorities and make the connection explicit.

In a pre-revenue acquisition, the seller's negotiating leverage comes from one source: competition. A single interested acquirer can set whatever terms they choose. Two or three interested acquirers produce genuine competition and meaningful negotiating leverage.

Create competition by approaching three to five potential strategic acquirers simultaneously. A brief, professionally prepared teaser — two pages describing the technology, the team, and the strategic opportunity, without naming a price — is the standard format for initiating multiple simultaneous conversations. Conduct the conversations in parallel and be transparent that other parties are involved, without disclosing the identity of those parties.

Even for a pre-revenue acquisition, a buyer will require documentation before any serious conversation. Prepare a data room with: the product specification and technical architecture, any user data or waitlist registrations, the intellectual property ownership documentation, the team's CVs and employment agreements, and the financial history (even if it is limited to costs rather than revenue).

A data room that is prepared and accessible before the buyer requests it signals organisational maturity and accelerates the acquisition timeline. Acquisitions that stall in data room preparation lose momentum — and lost momentum in M&A frequently results in a failed transaction.

Pre-revenue SaaS valuations are determined by three factors: the cost to replicate the technology independently (the build cost the buyer avoids), the strategic value of the capability or market position the product provides, and the quality and replaceability of the founding team.

Prepare a documented estimate of the replacement cost: how many engineering months would it take to build this product from scratch, at what hourly rate, with what probability of achieving the same technical outcome? A product that would take 18 months and $800,000 to replicate has a floor valuation of $800,000 regardless of its current revenue — because that is what the buyer saves by acquiring rather than building.

Pre-revenue SaaS exits are possible when the technology, the team, and the strategic fit are compelling enough to a specific acquirer. The preparation is the same as any acquisition — clean documentation, clear IP ownership, and a clear articulation of what the acquirer gains that they cannot build more cheaply themselves.

—