Product audit

    You built something fast. Now find out if it holds.

    A structured assessment of your product: the code, the architecture, security, and how far it will scale. You find out what is solid, what carries risk, and what to fix first.

    Two engineers reviewing code together on a large screen in a sunlit meeting room.

    For a product that is already live, and about to be tested.

    Winning a bigger client

    An enterprise client will review your product before they sign. Know what they will find before they find it.

    Built fast

    You shipped quickly, perhaps with AI building tools, and now need to know what is actually underneath.

    Growth is showing the strain

    Things are starting to behave unexpectedly under real load, and the next order of magnitude is coming.

    Inherited a product

    You have taken over a codebase and need a clear picture of what you are working with.

    Heading towards investment? Read this first.

    Investors look at the codebase, the architecture, the security posture and the decisions that got you here. What they find shapes how they value the business, and whether they proceed at all.

    Most founding teams do not know what due diligence will surface until it surfaces. An audit gives you that picture first, so you walk in knowing what you have, with time to fix anything that matters.

    What we check.

    Your product is assessed against the same standard we hold our own builds to: 17 areas in six themes, each answering one plain question.

    1. 01

      Security

      Who can get in, and what can they reach?

    2. 02

      Data

      Is your data protected, and can you get it back?

    3. 03

      Reliability

      When something fails, does anyone notice, and does the rest keep running?

    4. 04

      Change

      Can you change it quickly without breaking what already works?

    5. 05

      Running it

      Could someone else run it, and does it cost what it should?

    6. 06

      AI

      Can the tools that built it also break it?

    See all 17 areas
    1. 01Secrets and credentialsWould your credentials survive the repository becoming public, or a person leaving?
    2. 02Identity and accessDoes the front door hold?
    3. 03Authorisation and tenancyCan one user reach another user's data?
    4. 04Data protection and lifecycleIs data protected in transit, at rest, and at the end of its life?
    5. 05Application securityDoes the application resist the ordinary attacks?
    6. 06Dependencies and supply chainIs the code you did not write safe to run?
    7. 07Source control and change managementAre changes to the system controlled and attributable?
    8. 08Build and deploymentAre releases repeatable and reversible?
    9. 09Infrastructure and environmentsIs it arranged so a mistake stays contained?
    10. 10Cost and efficiencyDoes it cost what a system of its size should cost?
    11. 11Observability and alertingWould a failure be noticed by a person who will act on it?
    12. 12Backup and recoveryCan it be brought back?
    13. 13Operability and continuityCould someone other than the person who built it run it?
    14. 14Testing and verificationCan a change be made without breaking what already worked?
    15. 15DocumentationCould the next person understand it?
    16. 16AI controlsCan the tools that built the system also break it?
    17. 17Third-party servicesDoes it survive something else failing?

    Validate. Harden. Scale.

    01

    Validate

    The audit itself. What is working, what is carrying risk, and what the codebase will and will not support as you grow. Every engagement starts here, and it can stand on its own.

    02

    Harden

    Where the foundation needs strengthening, we strengthen it: security gaps, stability issues, missing functionality, duplicated or fragile code. Sequenced so the product keeps running while the work happens underneath.

    03

    Scale

    Products built for early users were often not built for the next order of magnitude. We find the limits and remove them before they become the reason growth stops.

    What you leave with.

    • A clear view, area by area, of what is solid and what needs attention
    • The risks that matter most, in plain business terms
    • A prioritised list of what to fix first, and why
    • What the product will and will not support as it grows

    Sometimes the audit shows a product is in better shape than the team feared. Either way, you know where you stand and what to do next.

    Book a product audit

    Questions, answered.

    We built it ourselves. Do we need an audit?

    You know the intent behind every decision. An audit tells you what actually got built. What it finds is usually not what the founding team was worried about, but what they did not know to look for.

    Can't we fix things as they come up?

    You can, but fixes made under pressure, with users affected, cost more and do more damage. The audit gives you a prioritised list of what to fix before it becomes urgent.

    We are not raising money. Is it still relevant?

    Yes. Investment is one trigger, not the only one. A new enterprise client, a growth push or a new hire who will read the code all put a product under scrutiny. It is better to find out first.

    Do you take the product offline?

    No. Hardening work is sequenced so the product stays live throughout.

    What happens after the audit?

    The audit can stand on its own. If you want help with what it finds, we scope the hardening work from its findings, and treat scaling as a separate conversation once the product is stable.

    A coffee roaster weighing beans at the counter while a colleague carries in a sack.

    When did someone last look at your product independently?

    Not what was built, not what was intended: what is actually there. Tell us about your product and what is coming next.