When momentum needs an architecture.
Growth that compounds rather than expands. M&A integration, operational scale-up, capital optimisation, and the systems beneath them.
Grow is the mode for the company whose business is working and whose next stage requires structure: an acquisition that needs to integrate, an expansion that needs an operating model, a capital base that needs to be redesigned for the size the business is now reaching.
The work is patient where Turn is fast. The mandate runs in defined phases rather than a continuous compression. The risk is not collapse — it is growth that expands faster than the architecture beneath it can carry.
Five types of architecture. One operating posture.
M&A and integration leadership
Buy-side and sell-side advisory through close. Post-merger integration designed and run from inside the integrated entity. Where the value of the deal depends on operational integration, our partners take seats inside the combined company rather than handing the work to others.
Operational scale-up
The structural work of growing past the founder-led phase: supply chain rebuilt for volume, procurement scaled to leverage size, distribution redesigned for new geographies. The operating system tuned to a larger company.
Capital optimisation
Capital structure designed for the growth phase, not the survival phase. Working capital, debt mix, equity discipline. The financial architecture that lets growth compound rather than dilute.
International expansion
New-geography entry, joint ventures, regional platforms. The strategy and the operating model and the seat that runs it — including the principal-level relationships the expansion actually requires.
Programme architecture
Stand-up of new ventures, new units, new lines of business. PMO design, gate-review architecture, governance cadence. The architecture that compounding growth needs underneath it.
Phased delivery. The architecture built and absorbed.
Grow mandates run in defined phases. Scope is set before design; design before execution; execution before handover. The partner is in the seat where the structural decisions are made.
Scope and structure
Two-to-three week scoping engagement. The growth thesis pressure-tested. Workstreams defined. Decision rights and authority designed. The mandate signed before any architecture work begins.
Design
The structural architecture designed — operating model, capital structure, governance, integration approach. Decisions taken at principal level. Outputs tested against the operating reality, not against the slideware.
Execute
The partner takes the seat — programme director, integration lead, regional MD — with decision authority inside scope. The architecture moves from designed to delivered. Client capability built in parallel to the partner's presence.
Integrate and hand over
The architecture absorbed into the permanent operating system. Permanent leadership identified and inducted. Documented exit with the client running what the partner built.
A sample of recent Grow work, by introduction only.
Specific mandates are discussed with prospective clients under NDA. The case file below indicates the kind of work without identifying the engagement.
View the mandate archive→If the architecture is the constraint, the conversation is now.
Make contact→