Imagine two businesses. One has an excellent application and no customers. The other has thousands of established merchant relationships and limited capacity to build new products. If useful software becomes cheaper to deliver, which business improves its position?
The answer is not automatically the one with the code. Product development still matters, but a lower cost to build shifts attention to the work that remains expensive: earning access to a merchant, understanding the operating problem, installing a solution, and answering the phone when it breaks.
The cost of building a product can fall much faster than the time it takes to earn a customer’s trust.
A residual report is not a distribution strategy
Merchant services investors often start with a portfolio count and a residual stream. Those are real assets. Neither tells you whether the processor or ISO has a relationship it can use to introduce something new. The residual is the entry fee, not the ceiling on what the relationship is worth.
There are three different merchants hiding inside that count. One appears on a residual report. Another will take a call from the person who services the account. A third will act on that person’s recommendation, change a workflow, and pay for an additional service. Each step requires a different level of trust. Underwriting them as the same customer is how a cross-sell thesis becomes a spreadsheet exercise.
Consider a merchant whose processor has handled card acceptance for years. A new application promises to reconcile deposits against invoices. Before the merchant adopts it, someone has to show how the data enters the accounting system, who resolves exceptions, what happens when settlement does not match, and whom the controller calls on a Friday afternoon. A product demo answers none of those questions by itself.
That is why cheaper code does not eliminate the value of distribution. It changes what distribution has to prove. Ramp’s AR launch is a live example: the processing and banking infrastructure already exists, and the buyer network is the expensive part.
The wholesale ISO opportunity
Wholesale ISOs can be an attractive route to established merchant access. They know the partner who originated the account, the processor behind it, the service problems that recur, and the merchants who actually answer the phone. A buyer can acquire that network, improve the operating system behind it, and give partners products they could not economically build alone.
The mechanism is straightforward. Build shared infrastructure once, select a small number of products that fit a specific merchant base, then support implementation and service across the network. The merchant gets a solution to a real operating problem. The partner keeps the relationship and earns more from serving it well. The platform spreads product and support costs across many relationships.
But a wholesale ISO does not necessarily own the end merchant’s trust. Sometimes the agent does. Sometimes the processor does. Sometimes nobody has earned enough of it to sell a second product. If the acquisition case assumes every merchant in the portfolio is available for a new application, the buyer is paying for access that may not exist.
What I would underwrite
I would start with behavior, not the merchant count. Who speaks to the merchant when something goes wrong? How often does that conversation happen? Can the partner introduce a product without damaging the relationship? When a merchant says yes, who handles installation, training, exceptions, and ongoing support?
Then test a narrow product against a real segment of the portfolio. Count the merchants approached, the calls taken, the implementations completed, the accounts still active after the first service problem, and the cost of supporting each one. Those measures tell you whether the relationship can carry an additional product. Residual revenue alone cannot.
The company with the best application can still win if it finds a cheaper, more credible way to reach customers. The company with the merchant relationships can still lose if those relationships are passive, fragmented, or held by someone else.
Cheaper software makes that distinction more valuable, not less.