McKinsey 2026: 52% of PE-backed companies have been held longer than four years — the highest share on record. The platform risk that survives a financial buyer's review will not survive a trade buyer's technical team.
Kern Advisory works with fund partners and portfolio company leadership across Nordic and DACH mid-market software businesses and industrial technology companies. We deliver the diagnosis. Remediation or modernisation follows only if it warrants it.
Engineering capacity that should be building competitive advantage is being consumed by maintenance. Feature velocity has stalled. The software business looks healthy from the outside — revenue is growing — but the gap between the roadmap and what actually ships is widening. You can see it in every release cycle conversation, in the cost of every new integration, in the distance between where the product is and where the value creation plan needs it to be.
The buy-and-build pipeline you built the thesis on is queued and ready. The platform underneath it was never designed for integration volume. Three add-on acquisitions and a fragmented architecture do not compound. They collide.
The audit defines the target state and the remediation sequence to reach it. The output is a technical document that specifies what the platform looks like at full operational capability, the sequence of changes required, how long each takes, and what each costs.
And if the platform is sound — the board has an independent view on a question that has remained open throughout the ownership period. Either outcome has the same value: you know. The audit costs less than a single day of M&A legal fees.
You need an external view with domain credibility — from people who have built the systems being assessed, not advised on them. Independent, partner-led, delivered in two weeks.
You know where the architecture is fragile. You need a partner who can help you remediate and document it with production-hardened output — working code, architecture documentation, and CI/CD pipelines that demonstrate the platform's operational state, not a presentation describing it.
The integration architecture was not designed for the acquisition rate the value creation plan requires. You need a partner who understands the industrial and software domain you operate in — not a generalist who has to learn it during the engagement.
Nordic and European PE hold periods now average 6.6 years — the highest on record (McKinsey 2026). When a technical acquirer's diligence team discovers undocumented architecture debt, fragile data pipelines, or a codebase no senior engineer will sign off on, that risk becomes their negotiating position. The value swing happens in the room, not in the P&L.
The question is never "is there technical risk?" There is always technical risk. The question is whether it was understood before the process started, or discovered during it.
We give you the diagnosis. If remediation is needed, we do the work — in weeks, not quarters, with production-hardened output your team inherits clean.
52% of all PE-backed companies globally have been held longer than four years — the highest share on record. When exits do clear, technical acquirers are conducting deeper diligence than at any point in the last decade. The platform risk that survives a financial buyer's review will not survive theirs.
Each acquisition adds a new data model, a new API surface, a new authentication layer. Without a designed integration architecture, the platform becomes a patchwork. Research shows more than 70% of post-merger integrations fail to capture planned synergies — in buy-and-build programmes the problem compounds with each deal because the previous integration is unresolved when the next one starts. The ceiling is invisible until a potential acquirer's technical team pulls the first thread.
Acquirers apply a technical risk discount — or walk — when diligence reveals brittle codebases, undocumented infrastructure, or no CI/CD discipline. The platform you didn't remediate becomes the justification for a lower offer or a broken deal. The platform you remediated and documented becomes a diligence-ready asset with a clean handover story. The multiple compression between the two is material — and it happens in negotiation, not in the P&L.
Feature velocity flatlines. The software business falls behind the competitive set without any single visible failure event — just compound erosion that surfaces in revenue trends, customer retention data, and eventually in a commercial diligence finding. The root cause is almost always architectural — a codebase that makes every new feature expensive, and every maintenance task risky. This is fixable. But not without a diagnostic that goes below the surface of sprint velocity metrics.
In PE-backed industrials and software businesses with operational data, the reporting layer is commonly the first infrastructure to be neglected. When financial and operational data lives in Excel exports, undocumented legacy pipelines, or BI tools nobody believes, utilisation reporting is a fiction and EBITDA quality is a risk. Acquirers find this immediately. We find it first — and we rebuild the pipeline. Not a recommendation to commission one. Production-grade data infrastructure, delivered clean.
An internal team — whether that is a dedicated value creation function or an investment partner at the fund sitting on the board — has an inherent incentive to validate decisions already made. An external team with no stake in the investment produces a finding the board can act on with confidence.
The audit's value is only partly technical. It is also evidentiary. When a technical acquirer asks "has this architecture been independently assessed by a firm with industrial domain credentials?" the answer changes the negotiation. That answer is now yes — and you own the report.
OPC UA, Modbus, IAPWS thermodynamics, plant data semantics — these are the protocols and standards that PE-backed energy, maritime, and manufacturing platforms actually run on. An architecture assessment that cannot read this layer cannot assess the platform.
The industrial domain expertise in this firm comes from building production systems in these environments at enterprise scale. Not from advising on them. For Nordic and DACH PE-backed industrials and technology companies with physical operations, that distinction determines what the assessment can actually find.
The delivery standard in this firm was shaped in environments where data pipeline integrity is an operational requirement, not a preference — industrial systems serving energy operators, ETL infrastructure where incorrect data drives incorrect decisions in physical operations. That standard applies here.
The two-week audit and three-month sprint timelines are a function of how senior engineers now build — not of cutting corners on scope. The deliverable your team inherits is production-hardened: CI/CD pipelines, documented architecture, security posture, clean handover. Not a proof of concept. Not a slide presentation of recommendations. A system built to the same standard as infrastructure that cannot afford to fail.
We do not run transformation programmes. We run defined engagements — scoped, priced, and delivered in weeks. Every engagement starts with the audit. You receive a full codebase and architecture assessment, a definition of what the platform looks like at full operational capability, and the complete remediation sequence — timeline and cost — to reach it. Priced to be approved without a board meeting. No obligation to continue with us.
If you proceed to the modernisation sprint, delivery is production-hardened — with CI/CD, security architecture, and documentation your CTO can present in technical diligence. Not a proof of concept. A production system with a clean handover.
For portfolio-wide mandates, we work with fund partners across multiple portfolio assets — combining technical assessment where the value creation plan requires it.
Two-week fixed engagement. Full codebase and architecture assessment. Definition of what the platform looks like at full operational capability. Complete remediation sequence — what changes, in what order, at what cost, on what timeline. A technical document your board can act on.
Eight to twelve weeks. Backend refactoring, data pipeline modernisation, reporting infrastructure, API redesign, or full-stack rebuild — scoped from audit output with a fixed deliverable your team inherits clean. Production-hardened with CI/CD, documented architecture, and security posture your CTO can stand behind in diligence.
Three months. Complete architectural decomposition and rebuild — integration architecture, reporting infrastructure, and full documentation. Scoped for platforms where architecture is the primary constraint on the buy-and-build thesis. Fixed deliverable your team owns on handover.
Ongoing advisory across multiple portfolio assets. Platform assessment prioritisation across the portfolio. Pre-exit diligence preparation on a defined timeline. Structured for fund partners managing three or more software or technology assets through the hold period — combining technical and commercial assessment.
This is not a team of junior developers managed from a distance. Every scoping call, every audit, every sprint is led by one of the two partners. The judgment you engage is the judgment you get — with full technical and commercial accountability, from initial conversation to final deliverable.
Structural engineer by training (UCL) — which is to say, someone whose foundational discipline is predicting how systems behave under extreme load and where they fail. That analytical framework maps directly to platform architecture assessment: what breaks first when acquisition volume triples, where the single points of failure are, what can't scale and why.
Data scientist by practice, solution architect by delivery — across SLB (global energy services at enterprise scale), Cognite (industrial data platform serving the world's largest energy operators), CGI, and Capgemini — in energy, industrial, maritime, and process sectors over more than a decade. He has built production systems at the scale and in the domains that PE-backed industrials aspire to reach.
His technical stack spans the industrial protocol layer (OPC UA, Modbus, IAPWS thermodynamics, plant data semantics), the modern cloud build layer (Python, TypeScript, Azure, Databricks, FastAPI, React), and the AI-native delivery layer (Claude Code, Cursor, production ML pipelines). This combination — industrial domain depth plus AI-native delivery capability — is not something a generalist tech advisor can replicate.
He builds new production systems continuously. The capability described here is not historical project experience. It is an active, current delivery bench.
Ten years in enterprise sales at Johnson & Johnson Medical Devices, followed by roles in product marketing at Arundo Analytics and Asolvi. She has been on the portfolio company side of a PE ownership cycle.
The Asolvi background covers Nordic software under PE ownership — from the inside.
Carola leads all fund partner relationships and scoping conversations. The call that starts every engagement is with someone who has operated in your portfolio company's market.
A two-week fixed engagement. Priced below a single day of M&A legal fees. You own the output unconditionally.