Why Software Penetration — Not Processing Volume — Is the Portfolio Metric Investors Now Track

What Is Software Penetration — and Why Does It Matter

For most of the ISO industry’s history, the primary performance metric was processing volume — total transaction dollars, monthly dollar volume (MDV), or annualized volume. It was the number in every sales deck, every broker’s valuation model, and every acquirer’s first-pass screening. It was also deeply misleading as a measure of business quality, but it was easy to count and easy to compare, so it became the default. That is changing, and the change is fast.

Investors and acquirers — both strategic and financial — have shifted their primary lens from volume to software penetration. Software penetration measures what share of an ISO’s merchant base runs on owned or embedded software platforms rather than simply processing payments through a terminal. High penetration means merchants are locked in by operational dependency, not price sensitivity. It means the ISO owns the data, controls the relationship, and has a recurring-revenue engine that compounds with adoption. Volume is a flow metric; software penetration is a quality-of-business metric.

The practical difference in valuation is not small. An ISO with 5,000 merchants on its own software platform — high penetration — is valued on software-enabled metrics at 8-15x EBITDA. An ISO with 20,000 merchants it merely processes for — low penetration — is valued on processing metrics at 3-5x. The revenue can be identical. The enterprise value is not. The rest of this article explains the mechanism, the metric framework, and the specific actions that raise software penetration before an exit.

1. Why Volume Stopped Being the Right Metric

Volume is a flow metric, not a quality metric: Processing volume tells you what merchants spent last month. It tells you nothing about whether those merchants will be there next year, whether they are dependent on your service, or whether a competitor can poach them with a lower rate. Two ISOs with identical volume can have 15% annual churn or 90%+ retention — and the volume number is identical. The metric was never a quality signal; it was a scale signal, and scale without quality is not worth what it used to be.

Software penetration captures the quality that volume misses: A merchant on your software platform is locked in by operational dependency — switching means changing the system they run their business on. A merchant who only processes with you is locked in by price perception, which changes the moment a competitor makes a better offer. Software penetration is the metric that separates these two types of merchants, and it is what investors now use to price the difference.

Acquirers price the moat, not the volume: Strategic acquirers and private equity are not buying a number on a page — they are buying a business that will still be there in five years with the same or higher EBITDA. A software-penetrated portfolio has a defensible moat (switch costs, owned data, embedded distribution) that makes the five-year projection credible. A processing-only portfolio is priced as a declining asset: the same merchants who can be poached today can be poached tomorrow, and the acquirer knows it.

2. The Three Dimensions of Software Penetration Investors Measure

SaaS attachment rate: What share of merchants pays a recurring SaaS or software fee, not just a per-transaction rate? SaaS attachment converts variable processing revenue into predictable recurring revenue — the kind that justifies higher multiples. An ISO with 70% SaaS attachment has a fundamentally different revenue quality profile than one at 10%.

Operational embedding: What share of merchants uses your software for inventory, ordering, loyalty, or analytics — not just payments? Deep embedding means the software touches multiple parts of the merchant’s operations, making it structurally costly to switch. A merchant who only runs payments through your terminal has one reason to stay; one who also runs ordering and inventory has three.

Data ownership: What operational data does the ISO own that no competitor can replicate? Proprietary data — multi-location performance, vertical-specific patterns, real-time usage — is the third dimension that converts a merchant book into a platform asset. Data owned is data that compounds in value over time, and it is what acquirers building AI and embedded-finance products will pay for.

3. How to Raise Software Penetration Before the Exit

Move processing-only merchants onto the platform: The highest-leverage conversion is existing merchants who currently only process — not yet on any software. Onboarding them onto your POS or software platform raises penetration immediately and visibly. Every merchant converted improves the portfolio’s penetration rate and, therefore, its exit multiple.

Layer SaaS products onto every new merchant from day one: Stop selling processing and offering software as an add-on. Start selling the software platform and including processing as a feature. The shift in framing — software-first versus processing-first — changes the penetration rate of every new merchant from the moment of signing.

Target high-embedding verticals: Restaurants, multi-location operators, and service businesses have natural points of operational dependency that make deep embedding easier to achieve. Start new merchant acquisition in verticals where you can achieve 3+ software touch points per merchant, not just payments.

Measure and report the right number internally: Stop running the business on volume. Run it on software penetration rate, SaaS attachment rate, and data-ownership score. These are the numbers that tell you where the business actually stands, and they are the numbers acquirers will ask for in diligence. If you are not tracking them, start now — the data compounds in your favor every month.