I have spent my career finding the platform that already sits between a vendor and thousands of end merchants, and building the channel there. That instinct started in merchant acquiring, ran through franchise technology, and now runs through payment operations.
An ISV already owns the merchant relationship, the onboarding flow, and the daily workflow. A payments provider that integrates there does not win a deal — it wins a channel, and every merchant the platform onboards afterward arrives without a sales cycle.
That is why integrated payments competition is really competition for the integration slot. It is also why the technical and security conversation is commercial: the platform has to be able to say yes without inheriting risk it cannot carry.
This is not a recent interest. Across three roles I have repeatedly stopped selling account by account and gone looking for the organization already sitting in front of all of them.
Identified regional franchise operator organizations and secured group presentations to 15–30 owner-operators at a time, replacing one-to-one prospecting with a room.
Pursued corporate approved-vendor and integration status as a distribution strategy, competing against a venture-backed rival bidding at zero margin for the same standard.
Built partner prioritization and ecosystem plans across software platforms, banks, and payment providers, converting public signals into direct stakeholder conversations.
Our product ran on new-hire and payroll data. So I went looking for whoever already held that data at scale, and found the leading national payroll and accounting provider to McDonald's owner/operators — a firm serving hundreds of owner groups across thousands of restaurants.
I opened the relationship and drove it to executive review. One partnership would have represented a multiple of everything I closed directly in eighteen months of account-by-account selling, with the data integration problem already solved.
Leadership declined it on relationship ownership — the partner would have held the operator relationship and we would have become a back-end provider. That is a legitimate objection in channel deals, and I had brought the opportunity up before I had brought the answer to it. It is the single most useful thing I have learned about how partnership deals actually die.
This describes a channel opportunity I identified, opened, and escalated — not a signed partnership, executed agreement, or revenue-producing integration. The decision not to proceed was made above me.
I produced ecosystem plans and partner prioritization frameworks across vertical software platforms, banks, and payment providers — mapping where each sat relative to payment acceptance, posting, exceptions, and reconciliation, and where a partnership would create commercial leverage rather than channel conflict.
These were commercial analyses and prioritization frameworks produced for leadership, plus direct stakeholder outreach — not signed platform partnerships.
Not every software company is a partner worth signing. I would rank prospects on four dimensions and prospect against observable events rather than generic embedded-payments messaging.
Does the platform's vertical, merchant base, and business model actually benefit from this integration, or is payments incidental to what they sell?
Merchant count, transaction volume, average ticket, growth rate, and whether payments becomes a monetized line or stays a pass-through.
How embedded the relationship would be, how much engineering both sides must commit, and how durable the partnership is once live.
Whether the platform sets the standard in its vertical — a reference that makes the next several partners easier, or an isolated win.
These signals do not prove a platform has a problem. They create commercially relevant hypotheses that can be tested through discovery.
Illustrative discovery questions — not claims about Bluefin customers or partners.
Verified results from full-cycle selling — stated precisely, so the numbers can be trusted.
ISV cycles are long and technical. The first quarter should produce product command, a prioritized ecosystem, and real discovery — not premature revenue assumptions.
I understand payments from the merchant side, the platform side, and the operational side that has to reconcile afterward. I have opened channel relationships that would have changed a company's distribution, and I have learned the hard way what has to be answered internally before one survives executive review.
I bring a hunter's activity level, self-sourced pipeline discipline, and the ability to hold a commercial conversation with an executive and a technical one with the team that has to build it.