[{"data":1,"prerenderedAt":32},["ShallowReactive",2],{"article-technical-due-diligence-for-software":3},{"id":4,"slug":5,"title":6,"description":7,"authorId":8,"categoryIds":9,"status":11,"publishedAt":12,"updatedAt":12,"heroImage":13,"heroImageAlt":14,"content":15,"author":16,"categories":26,"readingTimeMinutes":31},"article-1794736224680","technical-due-diligence-for-software","Technical due diligence for software: what we check before we take a system over","What a technical due diligence review of software covers, how we run one before taking a system over, and what you receive.","author-andy-slack",[10],"category-ai-development","published","2026-11-15","\u002Fassets\u002Farticles\u002Ftechnical-due-diligence-for-software\u002Fhero.png","A clipboard marked software, not property, listing access, the product, the code, the infrastructure and the team","\u003Cp>Search for technical due diligence in the UK and most of what comes back is about buildings. The Royal Institution of Chartered Surveyors publishes a professional standard for the technical due diligence of commercial property, where the term means a survey of a building before it changes hands (\u003Ca href=\"https:\u002F\u002Fwww.rics.org\u002Fprofession-standards\u002Frics-standards-and-guidance\u002Fsector-standards\u002Freal-estate-standards\u002Ftechnical-due-diligence-of-commercial-property\" target=\"_blank\" rel=\"noopener noreferrer\">RICS, Technical due diligence of commercial property, 1st edition\u003C\u002Fa>). This page is the other meaning: a review of a software product. It is written for a nontechnical founder who already depends on a system and wants to know what such a review covers before anyone commits to it.\u003C\u002Fp>\u003Cp>We should be plain about what we sell. We don't sell a standalone due diligence report to buyers or investors. The technical assessment of the product, its code, its infrastructure and how the team works is part of onboarding on our fractional CTO service. We run it on an existing system before we commit to take it over (Andy Slack, confirmed 15 November 2026). If you are buying a company and want a report written for the deal, this is not that service.\u003C\u002Fp>\u003Ch2>Access comes before the assessment\u003C\u002Fh2>\u003Cp>The order is fixed, and it starts with access. Before anything else we check that the repository and the hosting are held in the company's name, not one person's. Access comes first so the company can see what it has (Andy Slack, confirmed 15 November 2026). If an agency or a freelancer still holds the keys, the questions to ask them are in \u003Ca href=\"\u002Farticles\u002Fwho-owns-my-app-code\">who owns my app code\u003C\u002Fa>. If the person who built the product has already gone, the first weeks are covered in \u003Ca href=\"\u002Farticles\u002Ftechnical-cofounder-left\">when your technical cofounder or only developer has just left\u003C\u002Fa>. This page starts once the company can see the system.\u003C\u002Fp>\u003Cp>Then we assess four things: the product, its code, its infrastructure and how the team works. From that we write a prioritised roadmap and agree a first milestone, which can be taking over the existing system (Andy Slack, confirmed 15 November 2026). The assessment is what the commitment waits on. Nothing is agreed before it is done.\u003C\u002Fp>\u003Cfigure>\u003Cimg src=\"\u002Fassets\u002Farticles\u002Ftechnical-due-diligence-for-software\u002Ffig-1.png\" alt=\"Three stages in order: access to the repository and hosting in the company name, then an assessment of the product, code, infrastructure and team, then a roadmap and an agreed first milestone\">\u003Cfigcaption>Access in the company's name, then the four-part assessment, then a roadmap and a first milestone.\u003C\u002Ffigcaption>\u003C\u002Ffigure>\u003Ch2>How we judge the way the team works\u003C\u002Fh2>\u003Cp>We judge another team's delivery practice against how we work ourselves (Andy Slack, confirmed 15 November 2026). Four questions:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cp>Does each change start as a written issue with acceptance criteria?\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Do tests run on every change?\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Is every change reviewed before it is released?\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Are the decisions and their reasons kept in the repository, where the founder can read them?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>How a spec is written, and how agents build and review from it, are already explained in \u003Ca href=\"\u002Farticles\u002Fspec-driven-development-ai-coding-agents\">spec-driven development with AI coding agents\u003C\u002Fa> and \u003Ca href=\"\u002Farticles\u002Fagentic-loop-development\">the agentic development loop\u003C\u002Fa>. We point there rather than repeat them.\u003C\u002Fp>\u003Cp>Whether the code was written with AI does not change what we look for. We would be more concerned if a development team were not using AI tooling to improve its performance (Andy Slack, confirmed 15 November 2026).\u003C\u002Fp>\u003Ch2>What to look at before you depend on the system\u003C\u002Fh2>\u003Cp>Three you can check without reading code, before you commit to depend on a system (Andy Slack, confirmed 15 November 2026):\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cp>Whose company account holds the repository and the hosting?\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Are the decisions and their reasons written down where you can read them, or are they in one person's head?\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Do changes reach users in small, frequent releases, or in large, rare batches?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>If a technical lead is still in place, the conversation is a different one. \u003Ca href=\"\u002Farticles\u002Fmy-ctos-playbook-predates-ai-native-engineering\">A fractional CTO's view when the playbook predates AI-native engineering\u003C\u002Fa> covers how to spot a way of working that is holding delivery back and how to raise it. The three above are the ones that matter before you commit.\u003C\u002Fp>\u003Cfigure>\u003Cimg src=\"\u002Fassets\u002Farticles\u002Ftechnical-due-diligence-for-software\u002Ffig-2.png\" alt=\"Three checks a founder can make without reading code: which company account holds the repository and hosting, whether decisions are written down, and whether releases are small and frequent or large and rare\">\u003Cfigcaption>Three checks before you depend on a system, none of which needs you to read the code.\u003C\u002Ffigcaption>\u003C\u002Ffigure>\u003Ch2>A product that only one person understands\u003C\u002Fh2>\u003Cp>In an assessment, a product that only one person understands is a risk in itself, so we look for whether the decisions are written down where the company can read them (Andy Slack, confirmed 15 November 2026). We are often called when that person has already gone, or when someone else holds the codebase. \u003Ca href=\"\u002Farticles\u002Ftechnical-cofounder-left\">When your technical cofounder or only developer has just left\u003C\u002Fa> covers those first weeks, and this page does not repeat them. Telling a people problem from a process problem is a separate judgement, and \u003Ca href=\"\u002Farticles\u002Funderperforming-development-team\">is your development team underperforming\u003C\u002Fa> covers how we make it.\u003C\u002Fp>\u003Ch2>What you receive, and when we decline\u003C\u002Fh2>\u003Cp>It isn't a separate report. Onboarding gives you the assessment, your environment and AI engineering team set up, a prioritised roadmap and an agreed first milestone. Onboarding targets two to four weeks from when we receive the access and inputs we need from you. It is covered by the published fractional CTO price on our \u003Ca href=\"\u002F\">homepage\u003C\u002Fa>, not priced on its own (Andy Slack, confirmed 15 November 2026).\u003C\u002Fp>\u003Cp>If the assessment shows the fractional CTO service isn't a fit, we say so and decline, or we offer a tailored scope of the same service. We don't sell a different service (Andy Slack, confirmed 15 November 2026).\u003C\u002Fp>\u003Cp>No vendor lock-in: every solution comes with full training to self-administer. Your code, your accounts and the written record stay in your name, and the homepage states those ownership terms.\u003C\u002Fp>\u003Cp>If you want to talk through a system you already depend on, \u003Ca href=\"\u002F#lead\">Book a founder fit call\u003C\u002Fa>. The price and the onboarding terms are on the \u003Ca href=\"\u002F\">homepage\u003C\u002Fa>, and the other pieces are on the \u003Ca href=\"\u002Farticles\">articles index\u003C\u002Fa>.\u003C\u002Fp>",{"id":8,"name":17,"slug":18,"title":19,"bio":20,"avatar":21,"featured":22,"social":23},"Andy Slack","andy-slack","Founder","Experienced Entrepreneur, Fractional CTO and Business Bootstrapper.","\u002Fassets\u002Fimages\u002Favatars\u002FAndy.jpeg",true,{"x":24,"linkedin":25,"website":24},"","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fandrewslack\u002F",[27],{"id":10,"name":28,"slug":29,"description":30},"AI Development","ai-development","Unlock the power of intelligent software. Our AI development category breaks down complex concepts into actionable insights. Discover how automation, predictive analytics, and custom AI solutions are transforming industries. Read case studies and guides on implementing enterprise AI effectively.",5,1795013445701]