I am planning to deploy at least $30 million to start a merchant-services roll-up. The point is not to assemble a collection of payment gateways. It is to buy excellent sales and business-development leadership, give those people a better operating system, and let them spend more time building the businesses they know how to build.
That distinction determines what gets integrated.
The conventional roll-up buys residuals, adds companies and leaves the machinery alone. I have heard of platforms with four or five gateways under one roof, each with its own onboarding process and reporting. The buyer can show a larger revenue base while its operators still move information between systems by hand. That is financial consolidation, not an operating company.
The opposite mistake is to centralize every decision. That strips the founder of the customer knowledge, vertical relationships and entrepreneurial judgment the buyer paid for in the first place. A local leader who knows how to win in restaurants, healthcare or a particular software channel should not need headquarters to design a referral offer or choose a target merchant segment.
The operating model I want has a clear line: centralize the repeatable work, keep market judgment close to the customer. I am buying distribution judgment, not a collection of software assets.
What belongs in the center
The back office is the first place to look. If an owner spends hours reconciling residual statements, checking merchant files, chasing underwriting exceptions or rebuilding the same management report every month, that is time taken from selling and serving merchants. Those workflows can share data definitions, controls and software without requiring every acquired business to use the same sales pitch.
I have seen the distinction in two kinds of work. A staffer was downloading multiple Salesforce pipelines each week, combining them by hand and calculating what changed. I connected Claude to Salesforce and built a skill around the report we used. After one or two rounds of human correction, it could pull the data and flag the changes. The manager still owned the pipeline; the weekly assembly job went away. That is the practical lesson behind putting AI in the hands of people doing the work.
At Finexio, by contrast, a four-person team spoke to suppliers full time and onboarded about 1,200 a month. Another person worked on retaining suppliers who wanted to opt out. Those conversations produced the relationships and the data that made the payment network work. Software could help route the work and record the objections; buying another gateway would not replace that team. The lesson carries into an ISO acquisition: remove the administrative work around a strong seller, but do not confuse the seller with the administration.
The front office needs shared infrastructure too. A seller should see which merchants are stalled in onboarding and which partners are producing revenue. AI tools and focused software development can remove the swivel-chair work between a lead, an application, an approval and a live merchant. The point is speed to revenue, not an AI label on a slide.
I would measure the change in units an operator can see: days from signed application to first transaction, hours spent resolving an exception, merchant activation, retained gross profit and revenue produced per salesperson. If a new tool does not move one of those measures, it is not integration. It is another system to maintain.
What stays with the founder
The ISO founders I want to work with have an unusually precise view of a market. They know which referral partners trust them, what merchants in their vertical need, and which service failure will cost a relationship. Centralizing that judgment in a distant committee would slow the business and make the acquisition less valuable. This is what an ISO buyer actually owns: durable relationships and rights, not merely a residual report.
Angela Antrim of Payroc made a related point in a recent Leaders in Payments conversation: acquisition-led growth requires useful systems and consistent follow-through, but it does not require standardizing employees’ thinking or specialist expertise. The ideas do not have to originate at the center.
That is the balance I am after. The center should own common data, fraud controls, underwriting standards and service commitments. The founder should keep authority over vertical strategy, referral relationships and how to win a merchant within those guardrails. If a proposed merchant crosses a common risk threshold, the risk team decides whether it can be boarded and explains why. If the merchant is inside the threshold, headquarters should not rewrite the founder’s sales strategy. The rule belongs in the deal documents and operating cadence, not just in a speech about culture.
There is a test for my thesis. If moving local sales decisions to headquarters produces better merchant activation, retained gross profit and founder retention than giving founders real authority inside common controls, my boundary is wrong. I expect the opposite. A founder who sells the business and then has to ask permission to run the market they built will eventually leave, and the buyer will have paid for relationships it can no longer reach.
This is why I am not looking to buy technology for its own sake. I will build or rent a few capabilities where they shorten the path from sale to revenue. I am primarily looking for people who have built defensible, recurring-revenue, high-cash-flow merchant businesses and can see how to build the next one.
An ISO owner considering a sale should ask a prospective buyer a practical question: which work will you take off my desk, and which decisions will remain mine? If the answer is only a larger logo and another reporting package, that is not an operating advantage.
The asset is the entrepreneur. Integration should give that entrepreneur room to move.