The same scaling problem can surface from two sides of the cap table. Before investment, investors need evidence that the company underneath the traction can support the thesis. After investment, investors and boards may see a critical scaling or leadership gap that the company needs to cross quickly.
CompoundWorks supports both situations without turning them into a funnel: independent transaction evidence when the decision is whether to invest, and separately commissioned portfolio-company support when the decision is how to scale.
The underlying company may be the same. What changes is the decision the investor or board needs to make.
Use independent Scale-Readiness Diligence when growth, deployment, acquisition or integration assumptions need to be tested before capital or transaction commitments are made.
Use a separate portfolio-company mandate when a known scaling constraint, leadership gap or operating transition requires focused intervention, ongoing senior counsel or temporary operating ownership.
These are separate decision contexts, not stages. An investor or board can engage CompoundWorks directly in either one.
Traction is not the same as scalability.
A deep-tech company can have strong technology, real customers and impressive growth signals — and still be structurally unready for the next stage. Scale-Readiness Diligence tests whether product, architecture, organisation, trust and deployment logic can support the investment, acquisition or integration thesis.
Independent assessment · transaction-specific scope · no automatic downstream mandate.
See the diligence model ↓Traditional diligence can establish whether the market exists, the numbers reconcile and the technology is credible. Scale-Readiness Diligence asks a different question: whether the company underneath those signals can absorb the next stage of customers, integrations, deployment contexts, organisational complexity and institutional expectations without redesigning itself under pressure.
The risk is not only whether the company can grow. It is whether growth exposes a structural limit currently hidden by founder effort, bespoke delivery or early-customer tolerance.
Scale-Readiness Diligence assesses the operating system behind the growth story. It tests whether product, architecture, organisation, trust and deployment logic mature together strongly enough to support the transaction thesis.
The company being assessed is the object of the diligence, not the commissioning client. The investor or acquirer commissions the work and receives the output. The company provides access to relevant people and evidence, while conclusions are built through triangulation rather than management self-reporting.
The objective is not another generic due-diligence report. It is to identify the structural risks most likely to change the investment thesis, acquisition logic, integration assumptions or post-transaction priorities.
The Scaling System Maturity Framework provides the three-dimensional maturity backbone: Technology, Organisation and Trust. The six CompoundWorks capabilities provide the investigative lenses used to test where scale-readiness is actually being created or constrained.
What is actually limiting repeatable scale, and what is likely to break under the next growth event?
Does the product boundary and roadmap support the market position and growth thesis being underwritten?
Can the architecture absorb more customers, integrations, deployment contexts and product complexity without disproportionate redesign?
Can execution continue beyond founder routing, key-person dependency and heroic coordination?
Can customers, procurement, regulators and partners rely on evidence rather than personal confidence or exceptional effort?
Can adoption be reproduced across customers, partners and deployment paths, or does each new win effectively restart the business?
Depth follows the transaction thesis and the evidence. The diligence does not force equal investigation across all six lenses.
The company appears to have a product, but growth still depends on bespoke engineering, customer-specific branches or architecture that does not replicate.
Critical decisions, customer commitments or technical trade-offs still depend on founders or a small number of individuals.
Pilots succeed, but procurement, assurance, integration or operational evidence is not yet strong enough to support repeatable deployment.
Revenue is growing, but every new customer, region or partner requires a materially different route to value.
The strategic plan assumes a rate or type of growth the underlying system is not yet structurally designed to absorb.
The most useful risk is often not the problem already visible. It is the structural failure mode that becomes material only after the next customer cohort, product expansion, partner layer, regulated deployment, acquisition integration or organisational growth step.
The diligence therefore tests the next scale event, not only the current state.
Align on the investment, acquisition or integration assumptions that matter enough to test.
Review the relevant product, architecture, organisational, delivery, trust, customer and deployment evidence. Interview the people closest to the critical decisions and hand-offs.
Use the SSMF and six capabilities to test competing hypotheses and identify where the growth, deployment or integration thesis is structurally exposed.
Deliver the scorecard, likely binding or coupled constraints, what breaks next and the implications for the investment, valuation assumptions or acquisition thesis.
Fixed fee · scoped per assignment.
When traction is real but the investor needs to understand whether the company can move from early repeatability to scalable delivery.
When the target may be attractive independently, but the acquisition thesis depends on integration, platform fit or the ability to scale inside a larger organisation. Add Integration Readiness DD when the deal thesis depends materially on what happens as target and acquirer become one operating context.
When the value thesis depends not only on technology quality but on whether the company can deploy into complex industrial, regulated or institutional environments.
When product or platform architecture is the material transaction uncertainty, the diligence can go deeper into system boundaries, coupling, integration model, extensibility, deployment topology and architectural runway.
Architecture Deep Dive can be used as a module inside Scale-Readiness Diligence or as a standalone review when the transaction question is primarily architectural.
When the acquisition thesis depends on combining the target with the acquirer, target scale-readiness is only half the question. Integration Readiness DD extends the core diligence to test whether the two systems can operate together without destroying the architectural, organisational, deployment or trust assumptions behind the deal.
Integration readiness runs both ways. The target must be ready to scale into the acquirer's system, but the acquirer must also be ready to absorb the target without destroying the speed, product coherence, decision model or operating conditions that made it valuable. In defence and dual-use transactions, this is the symmetry between asking whether the venture is prime-ready and whether the prime is venture-ready.
Different from Architecture Deep Dive. Architecture Deep Dive asks whether the target's own architecture is a material transaction risk. Integration Readiness DD asks what changes when target and acquirer become one operating context — across product and platform boundaries, organisation and decision rights, trust and deployment conditions, and the integration work required for the assumed synergies to exist.
Integration Readiness DD is an M&A extension module to Scale-Readiness Diligence. It is not a full PMI programme and is not positioned here as a standalone offer. It is a transaction-stage read on integration assumptions that could materially change the deal thesis.
Does the technology work, and is the code or architecture technically credible?
Can the company repeatedly turn that technology into product, deployment and growth without structural failure?
The two are complementary. Scale-Readiness Diligence does not replace specialist code review, cyber review, financial DD, legal DD or commercial DD.
Scale-Readiness Diligence does not depend on winning a later Sprint, advisory or embedded mandate. The investor or acquirer commissions the diligence, the target provides access and evidence, and the conclusion must remain independent of any future commercial opportunity.
Any work after investment is separately commissioned around a new decision. It is never presented as automatic remediation of findings from the diligence.
An investor or board may also bring CompoundWorks directly into an existing portfolio company without any prior diligence relationship.
Capital can accelerate the company faster than its product, architecture, operating model or leadership system can mature. Investors and boards often see the resulting gap from a different vantage point than the founders — but the underlying company problem is the same.
CompoundWorks can support a portfolio company through a separately commissioned mandate when the constraint is already visible and senior intervention can materially change the outcome.
The company remains the operating context. The investor or board may sponsor, mandate or introduce the work; the exact contracting model is defined case by case.
The investor or board may see the gap first, but the intervention is defined around what the portfolio company actually needs. These are separate ways to engage, not stages.
Use a bounded sprint when the problem is already known and a specific product, architecture, organisation, trust or market constraint needs to be resolved.
See Focused Domain Sprints →Use ongoing senior counsel when the leadership team can own execution but needs continuity of judgement across a sequence of coupled decisions.
Explore Strategic Advisory →Use temporary senior operating leadership when the transition needs someone inside the system to own decisions and execution before the permanent organisation is ready.
Explore Embedded Scaling Leadership →No prior diligence is required. The smallest intervention that can responsibly cross the transition is the right one.
Leadership gaps, post-round scaling pressure, productisation or platform constraints, pilot-to-program transitions, founder dependency or board-visible execution risk can all create the mandate.
Explore Strategic Advisory & Embedded Scaling Leadership →If you are testing an investment or acquisition thesis, we can frame the diligence question. If a portfolio company is already facing a critical scaling or leadership transition, we can start directly from that situation.