How We Think About Valuation: The Honest Version

Posted by Solen Teamon July 13, 2026
Pre-AcquisitionIndustry Insights
How We Think About Valuation: The Honest Opinion

Ask ten people how a software company is valued and you will get ten different numbers. Some of that is honest disagreement. A lot of it is people telling founders what they want to hear. We would rather be useful than flattering. We have valued hundreds of software businesses over the years, and the same patterns appear every time. Here is how we actually think about software company valuation, in plain terms, including the parts that founders do not always enjoy hearing.

What Software Company Valuation Really Measures

A valuation is an estimate of the future cash the business can produce, adjusted for how confident anyone can be in that future. That can feel cold to a founder who has spent twenty years building, but it is the lens every serious partner uses.

That single idea explains almost everything else. The more predictable your revenue, the more of it a partner can count on, and the higher the number climbs. The more the future depends on things that could break, the lower it lands. Valuation rewards durability above everything else.

It helps to make this concrete. Imagine two decades of future invoices stacked on a desk. A valuation asks two questions about that stack. How tall is it likely to be? And how much of it can be trusted? Everything a partner examines, from retention curves to customer contracts to how often you personally rescue a renewal, is a way of answering one of those two questions. Nothing in the process is mysterious once you see it that way.

The Two Anchors: ARR Multiples and EBITDA Multiples

Nearly every software company valuation begins with one of two anchors: a multiple of annual recurring revenue, or a multiple of profit.

Revenue multiples fit growing businesses. If a company has four million dollars in ARR and is valued at eight million, the ARR multiple is two. Quoted ranges vary widely and deserve caution, but as a broad indication, lower-middle-market software transactions often land somewhere between one and three times ARR. These are indicative ranges, not promises, and every business is specific.

Profit multiples fit businesses that are stable and cash generative. A company with steady earnings and modest growth is often valued on a multiple of adjusted EBITDA instead, commonly in the range of four to eight times depending on size and quality. A business producing one and a half million dollars of adjusted EBITDA at a six multiple lands at nine million, and the same logic of quality and risk then moves that anchor up or down.

Which anchor applies is not a choice the founder makes. It follows from the shape of the business. High growth with thin margins points to revenue. Steady cash with modest growth points to profit. Businesses in between often get valued both ways, with the conversation settling wherever the two views overlap. Neither number is the answer on its own. They are starting points that a set of real metrics then pushes up or down.

How Adjusted EBITDA Is Actually Calculated

Adjusted EBITDA causes more confusion than any other number in the process, so it is worth being precise. It starts with operating profit, then adds back interest, taxes, depreciation, and amortization. The adjustments come next, and this is where founders and partners can genuinely see different numbers.

Legitimate adjustments normalize the business to how it would run under any owner. If you pay yourself well below a market salary, a fair calculation adds the difference back as a cost. If the business carried true one-time expenses, a lawsuit, a relocation, a rebuild that will not recur, those can reasonably be added back. Personal expenses running through the company come out as well.

The honest caution is that add-backs have a credibility budget. A schedule with three well-documented adjustments strengthens trust in every other number you present. A schedule with fifteen creative ones weakens all of them. Present the version you can defend line by line, because you will be asked to.

What Actually Moves the Number

Four things move a software company valuation more than anything else.

Net revenue retention comes first. A business that keeps and grows its existing customers, showing retention above one hundred percent, is compounding without spending a dollar to replace lost revenue. That is the single most powerful signal in the model, because it makes the future stack of invoices both taller and more trustworthy at the same time.

Growth rate comes second. Faster, durable growth expands the multiple, as long as it is not won at a reckless cost. Growth that depends on unsustainable spending, or that churns out as fast as it arrives, gets discounted quickly by anyone who looks closely.

Gross margin comes third. Higher margins mean more of every dollar is available to reinvest, which is why software above seventy percent gross margin is viewed favorably. Heavy services revenue, expensive hosting, or third-party costs baked into delivery all compress this number and, with it, the multiple.

Customer concentration comes fourth, and it works in reverse. When one or two customers make up a large share of revenue, the risk goes up and the multiple comes down. It does not matter how loyal those customers feel. A future that a single renewal decision can break is a future no careful partner will pay full price for.

Why Two Companies With the Same Revenue Get Different Numbers

Founders are often surprised that a peer with similar revenue received a meaningfully different valuation. The difference almost always lives in the structure beneath the revenue.

Founder dependency is the quiet one. If key relationships and critical product decisions all route through you, then the business a partner is valuing partly walks out the door when you do. Reducing that dependency, genuinely and visibly, raises the number.

Contract quality matters more than founders expect. Multi-year agreements with auto-renewal and clean assignment clauses support the future in writing. Revenue that renews on goodwill and a handshake may be real, but it cannot be underwritten the same way.

Criticality does heavy lifting too. Software that sits inside a customer's daily operations, holding their data and their workflow, is painful to replace, and that pain is worth real money. A tool that is merely liked is worth less than a system that is relied upon. And finally, timing plays its part. Market conditions shift, and the same business can anchor differently in different years, which is one more reason to build durability rather than chase a moment.

Where Founders Over- and Under-Estimate

Founders tend to over-value the story and under-value the structure.

The story is the vision, the roadmap, the potential. It matters, but it is the part a partner discounts most heavily, because potential is exactly what has not happened yet. An honest process gives you little credit for the product you are about to build or the market you are about to enter.

The structure is the boring, verifiable foundation: contracted revenue, clean financials, documented retention, a broad customer base, low dependence on any single person. Founders often treat these as hygiene. In a valuation, they are the value. A business with a modest story and excellent structure is frequently worth more than a dazzling narrative built on a fragile base.

There is a second, kinder miscalibration worth naming. Founders of quiet, profitable, deeply embedded niche businesses often underestimate what they have built. Twenty years of retention in an unglamorous market is exactly the durability the whole model is trying to find.

The Difference Between the Headline Number and What You Receive

Two offers with the same headline value can produce very different outcomes, and founders deserve to understand this before the first conversation, not during the last one.

Structure shapes the outcome. How much is paid at closing, how much is deferred, and what conditions attach to the deferred portion all deserve attention. Earnouts are a common and often sensible part of software transactions; they can bridge a genuine gap between what a founder believes and what the numbers yet show, and they keep both sides aligned around the same future. The useful questions are practical ones. What do the targets depend on, how much influence will you have over those outcomes after closing, and how will progress be measured along the way? A well-designed earnout is one both sides would be comfortable explaining to the other.

Working capital adjustments, escrow terms, and diligence findings all move real money as well. All of it is a reason to weigh offers on their full shape, and to work with a partner whose first offer and final wire tend to look the same. That consistency is itself a signal worth paying attention to.

Why We Value Durability Over Speed

We invest as permanent capital. We hold and operate businesses for the long term, with no predefined endpoint. That model changes what we are willing to pay for.

A firm that plans to move on in a few years can afford to chase a quick jump in growth. We cannot, and would not want to. We are underwriting the next decade, so we pay for what will still be true in ten years: retention, embeddedness, a product customers cannot easily live without, and a team that will still be proud of the work.

This is also why our diligence looks the way it does. We spend less time on hypothetical upside and more on the machinery of the business: how renewals actually happen, where knowledge lives, what would survive a hard year. Growth is welcome. Durability is what we underwrite. When the two point in the same direction, that is where the strongest valuations live.

How to Raise Your Own Number Before Any Conversation

You do not need a process underway to improve your valuation. The work is the same work that makes the business better to run, and a year of it compounds.

Start with the numbers. Reconcile your metrics so ARR, retention, and churn all tie back to your financial statements, because the fastest way to lose credibility is a dashboard that disagrees with the accounts. Move to accrual accounting if you have not already, and build a clean adjusted EBITDA schedule you can defend line by line.

Then strengthen the structure. Put contracts behind revenue that currently renews on goodwill. Broaden a concentrated customer base, even slightly; moving your largest customer from thirty percent of revenue to twenty changes the risk conversation. Document the knowledge that lives in your head, and reduce the number of decisions only you can make. Delegation reads as durability.

None of this requires an advisor or a timeline. Each step lifts the predictability of future cash, and predictability is what the number is really measuring. If a conversation ever does begin, you will walk into it with a stronger business and a shorter diligence.

Frequently Asked Questions

How are software companies valued?

Software companies are valued as an estimate of the future cash they can produce, adjusted for how predictable that future is. The two most common starting points are a multiple of annual recurring revenue for growing businesses, and a multiple of adjusted EBITDA for stable, profitable ones. Net revenue retention, growth rate, gross margin, and customer concentration then move the multiple up or down.

What is a typical ARR multiple for a software company?

In the lower middle market, software transactions often land in the range of roughly one to three times ARR, depending on retention, growth, margin, and market conditions at the time. These are indicative ranges only, and every business is specific.

How is adjusted EBITDA calculated for a software company?

Adjusted EBITDA starts with operating profit, adds back interest, taxes, depreciation, and amortization, then normalizes for costs that would differ under any owner: below-market founder salary, true one-time expenses, and personal costs running through the business. Well-documented adjustments strengthen credibility; long lists of creative ones weaken it.

What lowers a software company's valuation the most?

Weak or negative net revenue retention, heavy reliance on one or two large customers, revenue that renews on goodwill rather than contracts, and a business that depends heavily on the founder. Each raises the risk attached to future cash flows, which compresses the multiple.

Does fast growth guarantee a high valuation?

No. Durable growth helps, but growth won at a high cost or built on a fragile customer base is discounted. A slower-growing business with strong retention and clean structure is often valued more highly than a fast grower on a shaky foundation.

If you want an honest read on how your business would be valued, and what would move that number over the next year, reach out to the Solen team, even if the timing is not right today. We are glad to tell you what we see, with no pressure attached.

The ranges in this article are indicative only and reflect the lower-middle-market software segment as of mid-2026. They are for general information and do not constitute financial or legal advice.

Share this article:

MONTHLY NEWSLETTER

Get insights that matter

Enterprise software trends
Operator perspectives
Portfolio company updates

Get our take on what drives lasting business success, where markets are heading, and the companies we're backing for years to come.

Join our community of investors and operators committed to building enduring value.

By subscribing to Code & Capital, you agree to our
Privacy Policy and Terms of Service