Skip to content

Software Assurance

Accountable for your software in production, whoever wrote it

We assess, assure, run and improve business-critical software, whether your team, AI tools, another agency or we wrote it. When a check finds something, the same team can fix it, so there is no second supplier to bring in.

Why software assurance matters now

AI tools can now write most of the code in a new system, and in ours they do. That makes software faster to produce. It does not tell you whether the result is secure, does what was asked for, or will keep running when the person who built it moves on.

Software assurance answers those questions with evidence. We check software against recognised standards, test it, run it under an agreed service level, and record what was checked. In our own delivery, 91.6% of our code is AI-authored, and 100% of it is reviewed by senior engineers and validated by ISTQB-qualified QA. We apply the same standard to code we did not write.

An example of software assurance end to end: a two-week readiness review, fixes that each pass five checks, then managed support. Illustrative data for a fictional client.

Assess, assure, operate and evolve

Each service answers a different question about a system in production. Most clients start with an assessment, then move to support, with the same checks running on every change.

Software assurance services around a live system: assessment, ongoing support, and the checks every change passes
Software assurance services around a system in production, whoever built it: your own developers, AI tools, or a supplier, including another agency or Talk Think Do. On the left, assessment: the Production Readiness Review, a fixed-fee, two-week review with an evidence pack; the Maintainability Review, for due diligence and handover; and the AI Delivery Assessment, for teams building with AI. On the right, operating and evolving the system: managed support from business hours to 24/7, managed support for AI-built software we did not build, and the Daily AI Operations Brief, a checked morning summary. Beneath, the assurance that runs on every change: static analysis on every pull request, secure coding validation against OWASP ASVS, and functional, accessibility and load testing.

The checks every change passes

Our QA practice, applied in our delivery and managed support work, to our own code and to code we did not build.

Static code analysis

Static code analysis with GitHub Advanced Security, extended with our own in-house rules, runs automatically on every pull request.

Expert-led secure coding validation

Senior engineers validate AI-generated code against the OWASP Application Security Verification Standard (ASVS) and our own suite of checks, built from the findings of penetration tests on previous projects. The reviewer is never the person who wrote the change.

Functional and regression testing

Manual and automated functional and regression testing as standard. Where automated regression suites exist, we maintain them as part of managed support.

Accessibility testing

Automated accessibility testing against WCAG 2.2 AA, plus standard techniques and tools.

Load, stress and soak testing

We use Azure Load Testing to find and fix scalability problems, design scaling strategies such as Kubernetes autoscaling, and size infrastructure and cloud SKUs for performance and cost.

Penetration testing, through a specialist

We do not carry out penetration tests. When you need one, commission it from a CREST-accredited tester, and we fix its findings alongside our own.

How we hold ourselves to the same standard

We develop software under an ISO 27001:2022-certified information security management system, which governs our secure development lifecycle, change control and supplier management. We are also accredited to Cyber Essentials Plus. Code is deployed into client-managed cloud environments, and runtime security in those environments remains the client's responsibility, in line with our defined ISMS scope.

We publish how we build every quarter in the AI Velocity Report, including the checks every AI-written change passes and what a measured change actually took.

Seen enough? Let's talk through your requirements.

Book a free consultation

Frequently asked questions

What is software assurance?

Software assurance is the work that gives you confidence a system is safe to depend on: checking the code against recognised standards, testing it, running it under an agreed service level, and producing evidence of what was checked. For us it also includes fixing what the checks find, so you do not need a second supplier.

Do you only assure software you built?

No. We review and support code we did not build as well as our own, whether your team, AI tools or another agency wrote it. For AI-generated codebases we did not build, the Production Readiness Review is the first step before ongoing support.

Where should we start?

It depends on the question you need answered. If you need to know whether software is safe to put in front of users, or a buyer has asked for security evidence, start with a Production Readiness Review. For due diligence or a supplier exit, start with a Maintainability Review. If your own engineers build with AI and you want to know whether it is working, start with the AI Delivery Assessment.

Do you carry out penetration testing?

No. Our secure coding suite is built from the findings of penetration tests on previous projects, so issues that real tests have found are checked for on every review. If a customer or insurer needs a penetration test, commission it from a CREST-accredited tester, and we can fix its findings alongside ours. Our guide to penetration tests and production readiness reviews explains which to do first.

Can you guarantee our software is secure?

No. Nobody can guarantee that a system is secure. What we do is describe exactly what we checked, against which standard, and what was out of scope, then fix what we find and keep checking every change. Every review report lists the requirements we checked and the ones we did not.

What does it cost?

The Production Readiness Review is £5,500, fixed, over two weeks. The AI Delivery Assessment is £9,500, fixed, over three weeks. Managed support starts from £1,590 a month for conventional codebases and from £2,450 a month for AI-generated codebases we did not build. See our pricing page for current figures.

See how AI is changing how we build software

Our quarterly AI Velocity Report tracks real delivery metrics from live projects: how much of our code is AI-authored, how delivery timelines compare to baseline, and which tools are making a measurable difference. No marketing spin, just honest data from a team that builds software every day.

Read the latest AI Velocity Report

Make someone accountable for your software

Book a consultation and we will tell you which assessment fits, what it costs, and what you get at the end of it.

Book a consultation

or call 01202 006729