The deal closed. The value-creation plan names payments as a monetization lever. Now the honest question is what you actually do about it in the first 100 days, because the wrong sequence burns most of a hold period before it earns anything. This is the operator's version of that sequence: baseline first, take the fast wins, and only then reach for the model change and the migration.
The temptation post-close is to open with the big move (become a payfac, rip out the processor, re-platform) because that is the move with the biggest number attached. Resist it. The big move is real, but it pays back last and carries the most execution risk. The revenue you can bank inside a hold period lives mostly in work you can start in week two.
Days 1 to 30: baseline the current state against real numbers
You cannot improve what you have not measured, and the data room summary almost never has the granularity you need. Diligence told you the gap probably exists. The first month is where you confirm its size and shape against live data.
Pull four numbers and trend them:
- Attach (activation) rate. What share of eligible merchants are actually processing through the platform. This is the single most diagnostic number. A platform activating 25% of eligible volume has most of its payments revenue still in front of it.
- Net take rate in basis points. Total payments revenue divided by total processed volume, by month. The trend matters as much as the level. A declining take rate is a different problem than a low one.
- Leakage. Failed and declined payments never recovered, reserves held higher than the risk justifies, interchange running above where routing and card-type mix could put it. This is margin you are already entitled to and not collecting.
- The contract. The actual signed processor or PayFac agreement. Term, exclusivity, change-of-control and migration provisions. This decides which moves are even available to you later, so read it before you plan anything.
Frame this as discovery, not delivery. You are testing where the value is trapped, not committing to a build. The output of month one is a sized, prioritized gap list, not a roadmap.
Days 30 to 60: fix the fast wins before you touch the model
The fast wins share three traits: they convert volume you already have, they need no migration, and they carry almost no execution risk. Take them first. They fund the credibility you will spend later on the harder moves, and they show up on the board deck inside a single quarter.
Activation. Usually the largest near-term lever and the shortest payback, because the merchants and the volume already exist. The work is unglamorous (onboarding friction, a sales motion that never pitched payments, merchants who defaulted to their old processor) and it is where the money is. Start by understanding why eligible merchants are not turning payments on, then run the activation playbook against the back book.
Failed-payment recovery. Every declined or failed transaction that is never retried or dunned is revenue you earned and did not collect. Smart retries, updated card credentials and a real dunning sequence recover a meaningful share of it with no new pricing conversation and no partner sign-off.
Rate and reserve right-sizing. Deals signed at lower volume rarely reflect what the platform can command now. A credible competing quote anchored to current volume moves the number far more than a polite ask. On the risk side, reserves set conservatively at launch are often working capital sitting idle. Both of these are optimization inside the model you already run, which is exactly why they come before any migration.
The revenue you can bank inside a hold period lives mostly in work you can start in week two, not in the migration everyone reaches for first.
Days 60 to 100: confirm the model, then sequence the big moves
By now you have banked the quick revenue and you understand the platform's real economics. This is the window to confirm the monetization model and stage the moves that change it.
There are four models, in ascending order of economics and ownership: ISV Referral, ISV + Enhanced Residuals, PayFac-as-a-Service and Full PayFac. Most platforms enter a hold period on one of the first two and have real headroom to move up. The right target is rarely the top of the ladder. Full PayFac is a 12-to-18-month build that pays off only above roughly 200 million dollars in annual volume, and it can consume most of a hold period before it earns. For most portfolio companies the answer is a managed PayFac-as-a-service path that captures facilitation-level economics in weeks to months rather than quarters.
Two disciplines matter in this window:
- Decide the model against the four risks, not the biggest number. Value (will merchants accept the pricing and experience), usability (can they onboard without friction), feasibility (can your team stand up the operation) and business viability (does the economics clear the build and operating cost at your actual volume). A model that fails one of these looks great on a slide and stalls in execution. Work whether to change the model at all before you assume the answer is yes.
- Sequence migration last, and stage it. A model change or provider migration is where deals get disrupted, merchants churn and revenue dips before it climbs. Run it after the fast wins are banked, in cohorts, with a rollback path. Never migrate on the same clock you are still baselining on.
Staff it: someone owns payments as an operation
The most common post-close failure is leaving payments in the engineering backlog as a feature instead of running it as a business line. Payments cuts across product, pricing, risk, compliance and go-to-market. Owned by a single function it gets optimized as a feature and underperforms as a business.
Name an owner with a number attached, accountable at the GM or sponsor level. In an empowered-team model this is a durable payments team pursuing an outcome (payments revenue and attach), not a project team shipping a migration and disbanding. Whether that owner is a hire, a fractional operator or an internal leader given the mandate, the point is that someone wakes up responsible for the payments P&L and reports on it like one.
Set the board-facing metrics before the first board meeting
Decide what you report before you are asked, so the narrative is yours. A tight board dashboard for payments:
- Attach rate, trended, with the back-book runway sized in dollars.
- Net take rate in basis points, with the model target called out.
- Payments revenue and payments gross margin, separated from software.
- Leakage recovered, failed-payment recovery and reserve release, as a running total.
- The model roadmap, with the next move, its timeline and the revenue it unlocks.
These are the same numbers a next buyer will diligence, so managing to them now compounds twice: once in the earnings line during the hold, and again in the quality of revenue that sets the exit multiple.
The 100-day goal is not to finish the payments plan. It is to have banked the fast wins, confirmed the model against real numbers and stood up the ownership and metrics that let the bigger moves run on the rest of the hold period with confidence.
Frequently asked questions
What should a PE-backed SaaS platform do about payments in the first 100 days?
Baseline the current state first (attach rate, take rate, leakage, the processor contract), then take the fast wins that need no migration (activation, failed-payment recovery, rate and reserve right-sizing), then confirm the monetization model and stage any model change or migration for later. Big moves pay back last and carry the most risk, so they come after the quick revenue is banked, not before.
Should you migrate payments providers right after acquisition?
No. Migration is where merchants churn and revenue dips before it climbs. Run it after the fast wins are banked, in cohorts, with a rollback path, and never on the same clock you are still using to baseline the business. Most of the near-term upside is in optimizing the model you already run.
Which monetization model should a portfolio company target?
Rarely the top of the ladder. Full PayFac is a 12-to-18-month build that pays off only above roughly 200 million dollars in annual volume. For most platforms on a hold-period clock, a managed PayFac-as-a-service path captures facilitation-level economics in weeks to months, which is why it is usually the right target from ISV Referral or Enhanced Residuals.
Who should own payments after a PE acquisition?
A single accountable owner with a payments revenue number attached, empowered at the GM or sponsor level, running a durable team against an outcome rather than a project team shipping one migration. Left in the engineering backlog as a feature, payments underperforms as a business line.
What is the fastest payments win post-close?
Activation and failed-payment recovery. Both convert volume the platform has already earned into revenue, need no new pricing negotiation and no partner sign-off, and show up on the board deck inside a quarter.