// FOR_PORTFOLIO_INVESTORS
The embedded CTO function for your portfolio.
Your portcos are running 2024 engineering cost structures into 2026 acquirers. Every quarter you don't restructure is a multiple-point haircut at exit. We are the operator layer that fixes it — one senior CTO + AI per portco, fixed price, programme economics from £500k / yr.
// THREE_TRACKS
Three ways we engage. One operating system.
Whether you spawn portcos, acquire them, or hold them — the embedded-CTO model bolts onto your investment cycle.
Diligence
Pre- or post-investment technical assessment.
Codebase health, team capability, AI readiness, restructuring cost. We tell you which portcos to fix first — and what intervention will cost before you commit capital.
Turnaround
Per-portco rebuild and engineering org restructure.
Codebase rebuild, AI-native delivery, lean org. Pass DD in the next round, open enterprise sales, remove the engineering line that was killing margin.
Portfolio Programme
Embedded CTO function across the cohort.
One operating system applied to every portco. Standardised diligence, shared rebuild playbook, single supply of senior operators. Annual programme covering 8-25 portcos.
// WHAT_WE_FIND
What we find inside portfolios
Three patterns we see consistently in software-heavy portcos.
The Coordination Tax
Standups, sprint planning, cross-team sync, code reviews, architecture committees — 30-50% of an eng budget consumed by managing complexity rather than creating value.
Most of that headcount is overhead, not output. AI-native delivery removes the layer.
The AI Readiness Gap
Teams with Copilot licences but no AI-native systems. A "head of AI" who burns 9 months hiring a team to ship a demo that never reaches production.
“We bought Copilot” is not an AI strategy. It’s a line item.
The Prototype-Code Debt
Vibe-coded MVPs that scaled without architecture. No security posture. Fragile systems that fail tech DD, can't onboard a real team, and can't pass enterprise procurement.
Technical debt compounds faster than financial debt — and harder to see on a balance sheet.
// THE_MATH
The portfolio P&L your operating partner needs to see
A small team of senior CTOs with AI-augmented delivery ships more shipped features per £ — fewer handoffs, faster decisions, no management layer to feed.
// USE_CASES
How the programme deploys
Venture Builder: Embedded CTO across the cohort
You spawn 6-25 portcos a year. We supply the senior CTO function for each — V1 builds, post-launch turnarounds, AI integrations — without you hiring 30 engineers per company.
One operator per portco. One playbook across the cohort.
PE / Buy-and-build: Diligence and turnaround
Pre-acquisition assessment, post-close eng-org restructure, cross-portfolio AI rollout. Same team, same playbook, predictable budget.
Restructured eng org operational within 90 days
Family office / hold-co: AI line in mature portcos
Add a defensible AI revenue line or productivity uplift to a mature operating company. 6-12 weeks to a shipped product, not a year-long PoC parade.
Production AI inside the perimeter, not a pilot
Single-portco intervention
A specific portco needs a rebuild, an AI build, or pre-exit restructuring. Fixed fee, fixed weeks. Reusable across the rest of the portfolio if the model fits.
Pass next-round DD; lift exit multiple
// OPERATING_MODEL
How a portfolio engagement actually works
The questions every operating partner asks before signing — answered up front.
Allocation
Each portco gets a named senior operator as its embedded CTO, plus on-call architecture/AI specialists from the collective. Time-boxed sprints, not open retainers.
IP & ownership
Code, architecture, models and operating playbooks transfer to the portco at handover. We do not retain IP. We do not white-label other firms' work.
Conflicts
No portfolio-vs-portfolio overlap inside the same vertical without explicit operating-partner sign-off. Conflict register reviewed at each quarterly programme review.
Hand-off
Every engagement ends with a 90-day knowledge-transfer plan and documented systems. The portco team owns it on day one of post-engagement; we stay on call only if the operating partner asks.
Reference calls with two existing portfolio clients available on request after first briefing.
// PROCESS
From briefing to first sprint
Three steps from a 30-minute call to operators on the work.
Portfolio Briefing
30-minute call with the operating partner. We map the engineering surface area across your portcos and identify where embedded CTO leverage compounds first. NDA-ready, no deck.
Triage
Priority-rank portcos by technical risk, AI readiness, and exit timeline. We deliver a sequenced intervention roadmap and budget envelope inside two weeks.
Deploy
Senior operators on the work. Fixed-price, fixed-timeline engagements. Weekly business demo in your KPIs (revenue, throughput, time-to-feature) — not burn-down charts.
Bring us your portfolio.
A 30-minute briefing with the operating partner. We map the engineering surface area across your portcos and show where embedded CTO leverage compounds first. NDA-ready, no sales pitch.