The Anti-Interchange Playbook: Patterns from ISOs Adding Software Revenue

Quick answer: Across early-access conversations with ISOs adding software residual to their portfolios, five patterns recur. The two that work consistently: agent-led pilots and vertical pilots. The two mistakes that recur: bundling software into processing and underpricing below $39. The sleeper opportunity nobody's optimizing for: multi-location merchant pricing.

I get into a lot of conversations with ISO operators thinking about adding software to their portfolios. Most of these conversations have a structure — the operator describes their book, asks how to start, and I describe the math. Over a couple hundred of these conversations now, patterns have emerged. This article is a synthesis of what I'm seeing.

To be clear about what this is and isn't: this isn't a benchmark study with rigorous data. It's pattern observation across early-access conversations and partner pilots. I'm flagging it as such because the cohort is small (low double-digit partners in early access plus the pipeline of conversations behind them) and the data is qualitative more than quantitative. But the patterns are consistent enough across operators that they're worth naming.

Pattern 1 (working): Agent-channel pilots convert fastest

The clearest pattern across the cohort. Single agents or small offices — the relationship-led segment of the ISO channel — convert software at materially higher rates than larger institutional ISOs.

Indicative numbers from pilots:

Agent-led pilots: 60-80% end-of-trial conversion when the agent personally pitches and onboards
Larger direct-sales ISO programs: 30-50% end-of-trial conversion through a rep team
Email-only campaigns (no personal pitch): 5-15%

The reason is relationship strength. An agent who has known a merchant for five years, picked up the phone when the chargeback hit at 11 PM, and shown up to in-person trainings has earned credibility that translates directly into software conversion. The merchant doesn't evaluate the product on features — they trust the agent's recommendation and try it.

This has an implication for how ISO programs should sequence their rollout. If you're a multi-office ISO with both agent-led and rep-led sales channels, start the software pilot in the agent channel. The motion is faster, the conversion data is stronger, and the agents become the internal evangelists who convince the rep team it's worth the effort.

Pattern 2 (working): Vertical pilots compound

ISOs serving a specific vertical — legal, dental, trades, professional services, B2B wholesale — see software conversion compound through word-of-mouth in a way that horizontal ISOs don't.

Mechanic: when a dental ISO sells software to one practice, that practice talks to other practices in their study group. References generate 2-4 additional opportunities per win. The ISO doesn't have to do cold outreach for those — they come inbound through the network.

Horizontal ISOs (serving retail, restaurants, services, B2B, all in one book) don't get this effect because their merchants don't know each other. Every pitch is a standalone effort.

The implication for ISOs who have any vertical concentration: lean into it for the software program. Pilot in the vertical where you have the deepest concentration. Use the wins to generate referenceable case studies for the vertical. Then duplicate the playbook into the next vertical.

For ISOs who are genuinely horizontal: you can still succeed at software, but the early conversion curve is slower because each win is isolated rather than networked.

Pattern 3 (working): The QuickBooks-displacement pitch

The pitch framing that converts highest is the vendor-switch frame — "I can take over the QuickBooks line item on your bill" — not the new-product frame — "I'm offering a new service you might like."

I've covered this elsewhere (see How to Pitch Software to a Skeptical Merchant), but it shows up consistently enough to call out as its own pattern. The single biggest predictor of conversion is whether the pitch positions the offer as a switch from an existing software vendor the merchant is already paying. When it does, conversion runs 60%+. When it positions as a new product, conversion drops below 30%.

The implication: invest in knowing what software each merchant already uses. The first question of any software pitch should be "what are you using for invoicing now?" That answer determines both whether the merchant is a fit and what the pitch frame should be.

Pattern 4 (recurring mistake): Bundling software into processing rates

Some ISOs try to simplify pricing by quoting a higher processing rate that "includes" the software — for instance, adding 25 basis points to processing and providing the invoicing software at no separate charge.

This consistently underperforms separate-line pricing for three reasons:

The software residual disappears from the P&L. The ISO can't measure software economics independently of processing economics. Optimization becomes guesswork.
The bundled price often underprices the software. A merchant doing $50K/month in volume at 25bp markup is paying $125/month for the software — but most of that merchant population would have paid $59-$79 for software separately, and lower-volume merchants are getting it effectively free.
Renegotiation gets harder. Any future change to either pricing component opens the whole bundle. The ISO can't upsell software without re-opening processing.

The ISOs who report the strongest software-revenue programs in this cohort all keep the software on a separate line. Always.

Pattern 5 (recurring mistake): Launching below $39

A subset of ISOs new to software pricing try to launch aggressively low — $29, $19, sometimes $9 — with the thought that they'll capture broad adoption and raise prices later.

The pattern that follows is consistent and bad:

Per-merchant economics are negative on labor. At $9-$19 merchant-facing with $25 wholesale, the ISO is paying to sell the software. Time spent pitching is uncompensated.
The price anchors permanently. Raising from $29 to $59 a year later is a 100% increase that merchants resist. Most operators who try this end up holding the original price and never capturing the upside.
Low pricing signals low value. The merchant interprets $29/month as "this isn't important software" and treats it accordingly — low adoption, easy churn.

The pattern I've covered in detail in Setting Markup: What ISOs Actually Charge for Software. The short version: $39 is the floor. Below that, you're worth less than your wholesale supplier.

Pattern 6 (sleeper opportunity nobody's optimizing for): Multi-location pricing

This one is interesting because it's not yet showing up as a pattern in practice — but the math suggests it's a major missed opportunity for ISOs with any multi-location merchant exposure.

The setup: most ISO software pricing today is per-merchant-account, where "merchant" is the legal entity. A franchise operator with 12 locations is one merchant on the wholesale side ($25/month) and one merchant-facing price (whatever the ISO charges, typically $49-$129).

But that operator runs 12 locations, each of which uses invoicing as a workflow tool. A more accurate pricing model is per-location-with-discount — $59/location for the first few, scaling down toward $39 at 10+ locations. That converts a single merchant relationship from $79/month to $700+/month while still respecting the volume discount the operator expects.

Few ISOs in the cohort are pricing this way yet. The first ones to figure it out will own the multi-location segment for that vertical, because the franchise operator who's converted at $700+/month with operational dependence on the branded portal is essentially impossible for a competitor ISO to displace.

If you have any multi-location merchants in your book — franchises, restaurant groups, multi-office service businesses, chains of any kind — this is the segment to think about first.

How to use these patterns

If you're an ISO designing a software program from scratch, the implication is sequencing:

If you have an agent channel, start there. Pilot with 5-10 agents and their top merchants each. Faster conversion data, cleaner refinement loop.
If you have a vertical concentration, lean into it. Pilot inside the vertical where you have the most reference power. Use the wins to compound.
Use the vendor-switch pitch frame, not the new-product frame. Know what each pilot merchant is paying for invoicing software today.
Keep software as a separate line on the merchant's bill. Never bundle into processing rates.
Floor your pricing at $39. $49 is the recommended starting price for the pilot cohort. Refine into tiered pricing after 60 days of data.
If you have multi-location merchants, price per-location. Most of your competitors won't be doing this. It's the sleeper revenue lever in 2026.

How to start

If you want to run the math on what software residual looks like on your portfolio with the segmentation patterns above, the revenue calculator lets you model different scenarios in 30 seconds.

For the pricing pattern specifically, Setting Markup: What ISOs Actually Charge for Software goes deeper.

For the pitch motion that pairs with these patterns, How to Pitch Software to a Skeptical Merchant is the operator-level companion piece.

If you want to talk through how these patterns map to your specific portfolio, book 20 minutes with me. I'll be specific about what's likely to work for your book — and what isn't.

FAQ

What patterns are emerging in ISO software adoption in 2026?

Five patterns recur: the agent-channel-first pattern (agent-led portfolios convert faster), the vertical-pilot pattern (concentrated verticals compound through references), the QuickBooks-displacement pitch (vendor-switch framing outperforms new-product framing), the bundling mistake (don't fold software into processing rates), and the underpricing trap (below $39 destroys unit economics).

Which ISO segment converts software fastest?

The agent channel — single agents or small offices with strong personal relationships. Conversion rates in agent-led pilots run 60-80% at end-of-trial vs. 30-50% for larger direct-sales ISOs.

What's the biggest mistake new software programs make?

Trying to roll out software portfolio-wide in the first quarter. Success comes from piloting with the top 10-20 merchants, refining the motion, then expanding. Mass rollout from week one usually produces the conclusion that software doesn't work.

Are vertical ISOs an advantage or disadvantage for software programs?

Significant advantage. Vertical ISOs see word-of-mouth compounding. A win in one merchant generates 3-5 reference opportunities in the same vertical. Horizontal ISOs don't get this network effect.

Is there a sleeper opportunity ISOs aren't yet optimizing for?

Multi-location merchants. Most ISOs price software per-merchant without accounting for chains and franchises. Per-location pricing on multi-location operators converts a single relationship from $79/month to $700+/month and creates dependency that makes the merchant hard to displace.

Ryan Meo is the founder of Invoisure, a white-label invoicing and payments platform for ISOs, acquirers, gateways, and independent agents. He writes about ISO economics and merchant software. To talk to him directly, book 20 minutes here.