NOTES

Notes on technical risk and due diligence

Practical notes for founders, CTOs and investors facing an expensive software decision: stabilise, rewrite, invest or pause.

  1. Stabilise, rewrite or pause: how to decide what to do with a codebase that is slowing you down

    The three options, the six questions that separate them and a simple rule to choose, with what the first 30 days of stabilisation look like.

  2. Technical due diligence in three days: what investors should actually check

    What to ask for before day one, the eight areas to check, how the three days run and which findings change the price or the term sheet.

  3. Your MVP was vibe-coded. Here is what to check before you scale it

    Seven checks for an AI-built MVP: access control, secrets, failed payments, business rules, tests, dependencies and ownership.