In March 2019, a global IT services firm acquired a Dublin-founded, London-based fintech whose platform automated post-trade processing for taxes, fees, commissions, and cash flows across global financial institutions. At acquisition, the software was trusted by five of the world's eight largest investment banks. The PE investors had grown the team threefold since 2015 and exited at a 4.0x return with a 47% IRR. The company's accumulated profits had risen to €16.2M in the twelve months prior to sale. On paper, a clean exit. On the ground, a high-functioning, deeply expert startup that had never operated inside a Fortune 500.
Ninety days post-close, the team had no acquirer credentials, no standard tooling, no sprint cadence, and no communication from leadership about what integration would look like. The co-founder was the sole keeper of the legacy codebase. Requirements arrived from client contracts and were manually converted into a proprietary task system — no product owner, no strategic prioritization, no repeatable delivery framework. The engagement was deployed by the acquirer's accelerator group as the integration lead: build the operating model, close the gap, don't break what the banks depend on.
The co-founding CTO was the sole keeper of the legacy codebase. All production triage ran through one person at a platform embedded in global systemically important banks.
Work was driven entirely by client contracts. Requirements moved from SOW to technical task with no strategic prioritization in between. No product owner existed to hold the roadmap.
The team understood the philosophy but ran zero ceremonies. No sprint cadence, no grooming, no retrospectives. Development happened on-demand — whoever was loudest got prioritized.
Sales, BA, engineering, and implementation operated without a shared communication pattern across five distinct product lines. Changes didn't travel. Decisions didn't either.
The team ran on a proprietary task system. Jira, GitHub, Slack, and Confluence — the acquirer's standard delivery stack — had not been provisioned, configured, or even discussed by day 90.
Leadership was silent about the transition. A 30+ person team was running anxious and disengaged, with no credentials, no onboarding, and no visibility into what life inside the parent company would look like.
"The theology of Agile was in place. But the team was bootstrapping — ancient code, production issues taking hours to triage, requirements written in contracts and thrown over a wall. The gap between what they knew and what they could execute was the whole job."
Over an initial immersive week in London followed by an extended engagement through 2022, the engagement embedded directly with the team across all five product lines and both offices — building the operating infrastructure the acquirer required without disrupting the delivery their bank clients depended on.
Full Agile immersion training delivered to the entire organization — engineering, BA, product management, and implementation — covering Scrum framework, sprint ceremonies, user story standards, backlog management, and Definition of Done. Jira configured from scratch, with the proprietary task system mapped and migrated in parallel. Product backlog consolidated and groomed across all five product lines, with active client enhancement work reprioritized against strategic goals for the first time. A full delivery lifecycle framework designed and implemented, replacing ad hoc contract-driven development with a repeatable end-to-end process from intake through release. The full team roster of 30+ employees built and maintained, with Slack, GitHub, Confluence, and parent-company credentials provisioned to close the tooling gap. Served as integration liaison across the acquired company, the acquirer's accelerator group, and the Banking and Financial Services business unit throughout.
The following figures combine what's directly documented from the engagement with publicly available context about the deal. The stakes framing draws on published acquisition data and the platform's known footprint in global capital markets.
| Value Driver | Basis | Estimated Value |
|---|---|---|
|
Acquisition protected
Integration risk closed 90 days post-close
|
A failed integration at a platform embedded in 5 of 8 global top-tier investment banks carries regulatory, reputational, and contractual exposure. Synova's PE exit valued the business at an implied £80–100M+ range based on published fund return data (4.0x on a typical £20–100M portfolio company) | £80–100M+ asset stabilized |
|
30+ person team trained & onboarded
Full org across Dublin + London
|
Every employee across engineering, BA, product, implementation, and sales trained in Agile delivery and provisioned with parent-company tooling — from zero, in a team that had never run a sprint | 100% of org transformed |
|
5 product lines groomed + structured
Backlog consolidated for the first time
|
Fragmented, client-reactive backlog across 5 distinct product lines structured against strategic priority and migrated into Jira from a proprietary system | 5 backlogs → 1 model |
|
Single point of failure addressed
Co-founder as sole codebase custodian
|
Technical documentation and knowledge dissemination program initiated. At a platform supporting systemic financial infrastructure, a single-person dependency is a material business continuity risk — flagged and acted on in week one | Key-person risk reduced |
|
Delivery framework stood up from zero
Intake → SOW → dev → release
|
End-to-end delivery lifecycle designed and implemented — replacing ad hoc client-reactive development with a repeatable, enterprise-compatible operating model across all five product lines | Scalable model installed |
|
€16.2M profit base defended
FY2018 accumulated profits (Irish Times)
|
A disengaged, untooled team at a critical integration juncture risks client attrition. By stabilizing team operations and closing the communication vacuum, the conditions for client retention were preserved through the transition | Revenue base protected |
| Stakes of the engagement | £80–100M+ asset |
This was not a typical startup acquisition. The platform was embedded in the post-trade settlement operations of some of the most systemically important financial institutions in the world. A disrupted team or a failed integration at that layer doesn't just affect the vendor — it affects the banks, their counterparties, and in some cases, regulatory obligations that are time-critical by law.
The work here wasn't transformation as an end in itself. It was building the operational floor that let a high-performing, deeply specialized team survive their first years inside a Fortune 500 — without losing the speed, trust, and institutional knowledge that made the acquisition worth making in the first place.