A finding is not the same thing as a risk to the deal
A hundred technical observations are not useful to an investment committee. What they need is which findings would actually change the price or the plan.
Investor diligence
Independent AWS due diligence, before the money moved.
An investor needed to understand a target company’s AWS estate before a technology investment closed — not a hundred technical findings, but which of them were actually material to the growth thesis the deal was built on.
← Some of our past work · anonymised prior delivery, no client named
Stack
Read-only IAM roleAWS OrganizationsTerraformAWS CloudTrailAWS Cost Explorer
Rough timeline
| Phase | Typical duration |
|---|---|
| Scope and read-only access agreed | days |
| Independent assessment | 1–2 weeks |
| Findings translated into investment impact, delivered before close | concurrent with the deal timeline |
The challenge
A deal timeline does not wait for a platform review.
The assessment had to run to the investor’s clock, not an engineering team’s, and had to be understandable to people who are not platform engineers.
The target’s team, understandably, was not the audience
The report had to speak to what the investment thesis depended on, in language an investor’s technical advisor could act on.
Access had to be independent and read-only
The same scoped, revocable role model used on any InfraEdge engagement, with no production authority at any point.
What we found
Architecture that had scaled by accident, and technical debt that was routine, not alarming.
The findings were sorted, from the start, by what they meant for the deal rather than by how many there were.
Architecture that had scaled by accident, not design
A platform that had grown to meet demand without anyone stepping back to ask whether the current shape would hold for the growth the thesis assumed.
Security and resilience gaps that were routine, not alarming
Most findings were the ordinary technical debt of a company that had prioritised growth over platform investment — a normal, fundable position, not a red flag on its own.
Infrastructure as code coverage was partial
Enough to move quickly. Not enough to say with confidence what a post-investment platform team would be inheriting.
Cloud economics did not obviously track the growth model
Spend patterns that would need attention at the scale the thesis projected, even though they were unremarkable at current scale.
What we assessed
Six domains, each translated into what it would mean after the deal.
This is diligence, not remediation — InfraEdge changed nothing in the target’s AWS estate. The work was assessment and translation.
| Domain | What we assessed |
|---|---|
| Architecture and scalability | Whether the current design would hold at the scale the growth thesis assumed, and what would need to change if it did not. |
| Security and resilience | Identity, exposure, backup and recovery posture, assessed the same way an EdgeReady assessment covers them. |
| Infrastructure as code maturity | How much of the estate is reviewable and reproducible, versus how much exists only in the console. |
| Cloud economics | Spend patterns, and whether they would scale linearly, worse, or better with the growth the thesis projects. |
| Technical debt | Named specifically, and separated from the routine technical debt that is normal for a company at this stage. |
Outcome
Findings translated into investment impact, not a list of a hundred issues.
Rather than a finding register, the report gave the investor three things they could actually act on before close.
Which risks were material to the growth thesis. Which were routine technical debt every company this size carries. And what platform investment the deal would likely need to fund afterwards. The investor went into the close with a clear picture of what they were buying, not just what was wrong with it. Where a deal completed, portfolio companies have gone on to run EdgeReady and EdgeResolve in their own right — the same kind of assessment, and then the remediation, on the other side of the investment.
Book a 20-minute triage call
Twenty minutes, no charge. We work out what would actually help — which is sometimes us and sometimes not. Nothing is priced on the call; if there is work worth doing, a written scope and a price reach you within 24 hours.