Quality audit · 5 days · on-site
A full overview of your software quality
A comprehensive on-site assessment for mid-to-large organisations. Our engineers spend time embedded in your organisation, interviewing stakeholders, reviewing documentation and architecture, and examining your full development lifecycle, then deliver a written report and stakeholder presentation with prioritised findings.
What the audit covers
- Vision, strategy & roadmap
- Architecture & external/internal interfaces
- Full testing strategy — all test levels
- SDLC, quality gates & release process
- CI/CD pipeline & deployment safety
- Security & compliance posture
- Tooling & infrastructure
- Organisational structure & team composition
- Historical issues & incident patterns
For organisations where quality has become a strategic question
This audit is designed for mid-to-large organisations where quality problems have outgrown individual fixes, and where leadership needs a rigorous, independent assessment to understand the full picture before making structural or investment decisions. It's particularly well-suited to organisations in regulated industries, such as finance, medtech, pharma, insurance and enterprise SaaS, where the stakes of quality failure extend beyond UX to compliance, risk, and liability.
- CTOs & VP Engineering
- Product Owners & Managers
- Compliance & procurement
- Leaders after M&A or restructuring
Not sure you need an audit yet?
Start with the Release Risk Self-Check: five dimensions, twenty-five questions, about fifteen minutes. You get your score by email, with the cheapest first move for your weakest dimensions. If the result points to deeper problems, the audit is the natural next step.
A full assessment across every dimension of quality
We don't just look at your test suite. We assess the full system, strategy, architecture, process, people, and tooling, and connect every finding to a business outcome.
Vision & Strategy
- Product vision and roadmap clarity
- Short-term priorities and risk awareness
- Quality culture and ownership
- Hiring plans and capability gaps
Architecture & interfaces
- Component and service structure
- Data flow and critical transaction paths
- External integrations and SLA assumptions
- Internal interface contracts
Testing Strategy
- All test levels — unit through E2E
- Test environment and data management
- Automation coverage and strategy
- Exploratory and non-functional testing
SDLC & Quality gates
- Requirements sources and validation
- Code review and definition of done
- Release readiness criteria
- Historical defect and incident patterns
CI/CD & Deployment
- Pipeline structure and safety checks
- Deployment frequency and rollback capability
- Feature flag and canary release usage
- Build reproducibility
Organisation & Tooling
- Team roles, responsibilities and gaps
- Collaboration between dev, test, product & UX
- Tool stack assessment
- Incident response and post-mortem process
Structured. Thorough. Delivered in five days.
The engagement follows a tested structure: broad discovery first, technical deep-dive second, synthesis and recommendations third. Every stakeholder is heard. Every finding is evidence-based. We request access to key documents before arriving (roadmaps, architecture diagrams, test strategies, CI/CD tools and code repositories), so we spend on-site time in conversation and investigation, not administration.
- 1
Before engagement
Discovery call & document request
We align on scope and timeline, and send a document checklist: roadmap, architecture docs, test strategy, CI/CD access, code repository, and a list of stakeholders to interview.
- 2
Before engagement
Proposal & confirmation
We formalise the engagement scope, confirm the interview schedule, and agree on deliverables.
- 3
Day 1
Broad discovery & initial interviews
High-level stakeholder interviews — founders, CTOs, product owners, tech leads. Product vision, roadmap, quality culture, and risk appetite. Document and architecture review begins.
- 4
Day 2
Technical deep-dive
In-depth interviews with developers, testers, DevOps, and security. Systematic review of architecture, test strategy, CI/CD pipeline, and tooling. Codebase walkthrough where relevant.
- 5
Day 3
Synthesis & initial report draft
Consolidating findings from Days 1 and 2. Short follow-up interviews where gaps remain. First draft of the written report begins — findings, risks, and strengths identified.
- 6
Day 4
Recommendations & report completion
Consolidating all findings into the report. Quick wins, medium-term improvements, and long-term roadmap drafted. Prioritisation based on business impact and implementation effort.
- 7
Day 5
Final report & stakeholder presentation
Report polished and delivered. All findings presented to the full stakeholder group — leadership, engineering, product. Everyone leaves aligned on priorities and next steps.
Quality Audit vs. Focused Quality Audit
Both engagements share the same rigorous approach and report structure. The difference is depth, stakeholder coverage, and the type of organisation each is designed for.
| Feature | Focused Quality Audit | Quality Audit |
|---|---|---|
| Target organisation | Fast-growing startups and mid-market companies | Mid-to-large companies |
| Duration | 1 day (can be tailored) | 5 days (can be tailored) |
| Stakeholders interviewed | Founders, tech leads, product | 10+ roles across all functions |
| Security assessment | Overview only | Full security posture |
| Compliance & regulatory | – | Covered where relevant |
| Detailed appendices | Summary recommendations | Comprehensive technical appendices |
| Incident pattern analysis | – | Historical review |
| Hiring recommendations | Light | Full hiring appendix |
| Stakeholder presentation | Yes | Yes |
The audit identifies what to fix. These services help you fix it.
Questions we often get
Who is the Quality Audit for?
Mid-to-large organisations where quality problems have outgrown individual fixes, and where leadership needs an independent assessment of the full picture before making structural decisions.
How long does it take, and how is it organised?
Five days on site, which can be tailored. Broad discovery first, then a technical deep dive, then synthesis and recommendations. The report and a presentation to the full stakeholder group come on the last day.
What do we need to give you access to?
Your roadmap, architecture documentation, test strategy, CI/CD access, the code repository and a list of stakeholders to interview. We send a checklist after the first call.
What do we get at the end?
A written report with quick wins, medium-term improvements and a long-term roadmap, prioritised by business impact and effort, with comprehensive technical appendices, and a presentation to your stakeholders.
Can you work in regulated industries?
Yes, and we do today. The Quality Audit suits organisations in finance, medtech, pharma, insurance and enterprise SaaS, where a quality failure becomes a question of compliance, risk and liability.
What does it cost?
We quote every audit individually. Send us an enquiry with a few lines about your organisation, and we'll come back with a proposal.
Do you sign an NDA?
Yes. We sign a non-disclosure agreement before we start.
Start the conversation
Fill out the form, and we will get back to you as soon as possible.