Post-merger IT integration that ships in the first hundred days.
We encode the flows between both companies’ systems — AP, cash, reporting — while both keep running. The acquired ERP stays until the flows outlive it.
Official services partner of the platforms defining AI
NVIDIA
Anthropic
Five acquisitions. Five ERPs. No map of what talks to what.
From integration work inside PE-backed portfolios: $20–500M companies in non-tech sectors, where every deal arrives with its own systems and there is no integration team.
Every deal is its own systems archaeology
Five acquisitions on five ERPs, each with its own vendors, coding, and workarounds. First, someone must map what talks to what — including the Excel in between.
“We don’t know what we owe”
No portco-wide view of AP or cash. The sponsor asks a simple question and gets five exports in five formats, then a week of reconciliation before answers.
Contract addendums rekeyed by hand
A portco team rekeys addendums from SharePoint PDFs into Sage, field by field — every renewal, price change, and termination clause typed in by hand.
Your own data, gated behind the vendor
Vendor portals with no API. Reports only through the ERP partner. Two-year retention caps on history you thought you owned. Getting data out becomes its own project.
The operating partner’s Excel liquidity tracker
Hand-built, parsing BAI bank feeds line by line — the feed is unambiguous; the ERPs have workarounds. The portfolio’s most reliable reporting lives in one person’s spreadsheet.
The integration debt compounds quietly.
What we have seen inside post-close portfolios. Your numbers will differ — the first two weeks put figures on yours before anything gets built.
From anonymized engagements — PE-backed portfolio companies, $20–500M, non-tech sectors
We encode your exceptions.
No rip-and-replace. Both systems keep running while the flows between them become encoded, checkable, and boring.
- 01
Map what actually talks to what
We inventory both companies’ systems and the spreadsheets between them: what feeds AP, where cash gets reported, which portals have no API. The map is yours to keep.
- 02
Encode the flows that pay first
Cash visibility goes live in week two, sequenced bank-feed-first. Then AP across both charts of accounts, then weekly reporting. Each flow runs on your rules, not templates.
- 03
Retire the shadow spreadsheets one by one
Every encoded flow replaces a manual workaround — the liquidity tracker, the rekeyed addendums, the Friday export. By day 100, the integration is running, not planned.
You don’t need a bigger stack. You need the exceptions encoded.
Enterprise playbooks assume a PMO, a systems integrator, and eighteen months. A PE-backed portco has an operating partner, a controller, and a hundred days.
Integration platforms sell plumbing without the rules — nobody encodes your exceptions. AI does the reading; we encode them into flows between the systems you already own, while both companies keep operating.
We stopped waiting on the ERP migration. The bank feeds gave us portco-wide cash in the second week.
Led by Peter Enestrom.
Asked by operating partners and portco CFOs.
The straight answers, before you book anything.
The first flows should be live in weeks, not quarters. We sequence bank-feed-first, so portco-wide cash visibility typically arrives in week two, and the flows that pay — AP, cash, weekly reporting — run inside the first hundred days. A full ERP migration, if it is ever needed, follows on its own timeline.
Usually not first. Migrating mid-integration stalls both companies and buries the exceptions that make the acquired business run. We encode the flows between the two systems while both keep operating; the acquired ERP gets retired only when the flows outlive it.
Cash, then accounts payable, then weekly reporting. Cash is unambiguous — bank feeds do not have workarounds — so it comes first. AP follows because it is where the money leaves, and reporting follows because it is what the sponsor reads.
The exceptions. Vendor portals with no API, reports gated behind an ERP partner, two-year retention caps on your own history, and the shadow spreadsheets holding it all together. Playbooks cover the standard case; the manual workarounds around it are where integrations stall.
Start with one workflow.
Tell us where your team loses hours. We will come back with a straight answer on whether AI can help, what it would take, and what it would pay.