The software reads the repository. Andrew reads the deal.
A survey answers what the code can. A person answers the rest: the running system, the team, the contracts, and what it will take to combine two companies. Every engagement is led by Andrew Edmond, close to the code, remote and onsite as the deal requires.
Book a call Send the details instead or write to andrew@andrewedmond.com
Three engagements
- Buy-side diligence
- Typically two to four weeks, adapted to your timeline. Andrew runs it end to end, or works alongside your own engineers when you want them leading it. The deliverable is a risk register your whole investment committee can read: every dimension rated, the issues that must be fixed before close called out, and a clear read on what integration will take. Behind it sits the full write-up, with the evidence.
- Sell-side readiness
- The same assessment, before you go to market, so you fix what a buyer would find on your own terms instead of in the price.
- Post-close and integration
- For a company after the deal, where the engineering risk is actually managed: the integration plan and strategy that turn two engineering organisations into one.
Not sure you need a person yet? Start with a free survey of the repository, then book a call if the deal needs more.
Seven dimensions, one framework
The engagement assesses the same seven dimensions a Borehole survey reads. The survey covers what the repository can show. A person covers what it cannot.
| Dimension | What the survey reads | What a person adds |
|---|---|---|
| 01 Architecture & Codebase — including AI provenance | 12 checks | Design walkthrough · submodule access · design review with your architects · build-vs-buy calls |
| 02 Engineering Process & SDLC Maturity | 16 checks | Review depth · planning and estimation · incident-response review |
| 03 Organization & Key-Person Risk | 10 checks | Key people in the deal · gaps in the history · untouched subsystems · who actually mentors · hiring and bench · levelling · working pattern · retention risk · culture |
| 04 Product & Engineering Maturity | 19 checks | Delivery trend · roadmap review · experiment tracking · model card · whether the debt is funded · commercial consistency |
| 05 Security & Reliability Posture | 34 checks | Credential rotation · threat model · infrastructure drift · app permissions · incident history · penetration-test review · compliance evidence |
| 06 Observability & Operations | 16 checks | Restore rehearsal · alert routing · whether anyone watches the telemetry · postmortem walkthrough · SLO attainment · on-call rotation · cost and capacity |
| 07 Fit with the Acquirer | No checks: this one needs a person | Systems overlap · integration plan · team fit · deal dependencies · contract constraints |
Who does the work
Andrew Edmond. From 2016 to 2026 he worked at Amazon and its companies. In his last role there, from 2024 to 2026, he helped evaluate dozens of deals and led the technical diligence on five that closed.
- Principal, M&A Technology and Engineering Integration, Amazon (2024 to 2026)
- CTO, Woot.com, an Amazon company (2020 to 2023)
- Founding leader of Twitch's Seattle site engineering organisation (2016 to 2020)
Nearly thirty years in engineering leadership, and he still builds production software himself, Borehole included. More about Andrew.
Price and contract
€12,000+ (total price is determined per engagement; travel billed at cost). The total depends on scope: how many repositories and systems, how long, and whether the work is on site. You agree a written scope and price before any work starts, in a separate contract with AELaboratories.
Send the details
A short form, then a reply within two working days. Nothing is charged here and nothing is committed by either side.