Consulting
Software and architecture audit
A software audit is an independent review of a system's architecture, code, performance and security. It is for companies that have inherited software, are about to scale it or want to know what they are buying, and for investors assessing a product. You receive a written report of the risks we find and a list of fixes in order of priority.
Know what you have before you decide
Software can work well on the surface while hiding problems that only appear as it grows: pages that slow down with more users, simple changes that take weeks, unsupported dependencies, unpatched security holes. An audit brings those risks into view while they are still cheap to fix.
A report for decision-makers
We don't hand over hundreds of automated warnings. Each issue is explained in plain language, with its business impact, the risk of leaving it and the relative effort to fix it. Recommendations come in order, so you know what to tackle this month, what can wait and what is only a detail.
Common audits
- Reviewing a system delivered by a supplier, before the final payment
- Assessing a product ahead of an investment round or an acquisition
- Finding out why software has slowed down as users grew
- Drawing up a modernisation plan for an ageing system
- A second opinion on a proposed architecture before it gets built
After the audit
With the report in hand, you can fix things with your own team, your current supplier or with us. If you need someone to oversee the fixes and the decisions that follow, a fractional CTO carries the work forward. For a review focused on data protection or accessibility, there are dedicated audits under consulting.
What you get
- A review of the architecture and how the parts of the system talk to each other
- An assessment of code quality, tests and documentation
- A check for outdated dependencies and known vulnerabilities
- Performance testing and an assessment of how well the system can scale
- A review of security, backups and the handling of personal data
- A written report with risks, recommendations and the relative effort of each fix
- A presentation session for management and the technical team
Best for
- Companies that inherited software from a supplier or a team that has left
- Teams getting ready to grow in users or features
- Investors and buyers who need technical due diligence
- Managers who want a second opinion on what they have been delivered
Typical features and modules
Integrations & automation
Visibility & SEO
- Performance optimisation
Compliance & security
- Security hardening
- GDPR pack
- Accessibility
Hosting, e-mail & maintenance
- Monthly maintenance
How we deliver it
A conversation to agree what worries you and what the audit should answer
Read-only access to the code, documentation and environments
Analysis of architecture, code, performance and security
A written report with risks and fixes in order of priority
A walkthrough of the findings and answers to your team's questions
Frequently asked questions
Do you need access to the code?
Yes, to a copy of the code and, ideally, a test environment. We don't need write access or real customer data. If your company requires one, we agree a non-disclosure agreement before receiving any files.
Which technologies can you audit?
The most common web and mobile technologies. Before we put a proposal together, we ask which languages and services the system uses and tell you whether we are the right team to audit it.
How long does it take?
It depends on the size of the system and the questions to be answered. An audit focused on one area, such as performance, is shorter than a full review. The timeline is set out in the proposal.
Will you do the fixes afterwards?
We can, but you don't have to use us. The report is written so that any team, yours or another supplier, can follow it. You can start with the paid audit and then decide whether to continue with us on a fix or rescue project.
Is it suitable for due diligence before an investment?
Yes. In that case we focus on the risks that affect the product's value, such as reliance on key people, technical debt, security and the ability to scale, and write the report for the people making the decision, not just for developers.
How much does it cost?
Every project is quoted by hand from your requirements, so pricing is on request. Tell us which software you want audited, roughly how large it is and what concerns you. Request a quote
Shall we talk about your project?
Tell us what you have in mind and what you want to achieve.