Software audit
If you’ve been paying for software for a while and have no independent way of knowing what you’ve got, a software audit is how you find out. I read the codebase the way someone who’d have to live with it would, and tell you how well it’s built and what’s hiding in it, in plain English you can act on whether or not you’re technical.
What this is
This is a senior, independent assessment of the code itself: its quality, its structure, its test coverage, how readable and maintainable it is, and how much risk is sitting in it that nobody’s told you about. I read the code the way someone who’ll have to live with it would, and I report back on what’s solid, what’s fragile, what’s missing, and what it means for you in money and risk terms — not in jargon.
The job I’m really doing is translation. A non-technical owner is in a hard spot: the people who write your code are the only ones who can tell you if it’s any good, and they’re the last people who can be neutral about it. An audit gives you a read from someone with no stake in how it turns out. I’ll tell you if the code is clean, well-tested, and built to last, or if it’s a tangle that one bad week will turn into an outage — and I’ll tell you in words you can take to a decision.
It’s not an architecture review and it’s not a security audit, though it borders both. An architecture review judges the shape of the system; this judges the craft of the code inside it. A security audit hunts specifically for exposure. A code audit is the general health check: is this codebase an asset you can build on, or a liability you’re paying interest on every month.
When you need this
You need this when you’re relying on software you can’t independently vouch for, and the cost of it being worse than you think is real. The familiar situations:
- You’re a non-technical founder or owner paying for development and you genuinely can’t tell if the money’s buying good work.
- Everything is taking longer than it should and bugs keep coming back, which usually means the code underneath is rotting.
- You’re about to take over, inherit, or depend more heavily on a codebase you didn’t build and don’t understand.
- A developer or agency relationship is ending and you want to know what state they’re leaving the code in before you bring in whoever’s next.
The thread is dependency without visibility. You’re betting the business on code you can’t see clearly, and an audit is how you get the lights on before something forces the issue.
How working with me goes
I read the actual code — not a checklist run by a scanner, which tells you about style and misses everything that matters. I look at how it’s structured, how it’s tested, how readable it is to someone new, how the risky parts are handled, and the things that don’t show up in any tool: the clever bits only the author understands, the corners cut under deadline, the parts everyone’s quietly afraid to touch.
Then I report back in plain English, headline first: is this codebase healthy, and if not, where’s the trouble and how serious is it. I rank what I find, because a list of two hundred minor issues helps nobody — you need to know the handful that actually threaten you and what they’ll cost to fix, separated from the noise that can wait or be ignored. The difference between this and an automated report is judgement: a person who’s maintained real systems telling you which problems are real, in order, with the reasoning. The last time I audited an inherited codebase, the headline wasn’t the long list of warnings — it was the one undocumented module the whole business ran on that exactly one freelancer understood.
What you walk away with
- A plain-English verdict on the real state of your codebase — asset or liability, stated clearly.
- A prioritised list of what’s wrong, ranked by what it actually costs you, not by tool severity.
- A clear read on maintainability and key-person risk: how hard is this to work on, and how much of it lives in one person’s head.
- A realistic sense of the technical debt you’re carrying and what it’d take to bring it under control.
- A two-page summary you can hand to a board, an investor, or the next developer, with the detail underneath.
Who this isn’t for
If you want a clean bill of health to reassure yourself, this isn’t it — I report what I find, and inherited codebases rarely come back spotless. This is for owners who’d genuinely rather know the state of the thing they’re depending on than keep assuming it’s fine.
When you need a team instead
An audit tells you what’s wrong and what it’ll take to fix. If the answer is a substantial cleanup, refactor, or rebuild, doing that work is sustained delivery — a team’s job, not an auditor’s. That’s my agency, Digital Royalty: taking the findings and doing the remediation at scale, with the team and process to bring a codebase back to health without stopping the business. I can pass the audit straight across so the work starts from a clear, prioritised map.
Talk to me
If you’re depending on code you can’t independently vouch for, that’s exactly what this is for. Tell me about your situation and I’ll tell you what the audit should cover and how fast it can be done. If your worry is more about whether the system will scale than how the code reads, an architecture review fits better; if you’re an investor sizing up a whole company rather than a codebase, that’s technology due diligence; and the other ways I help cover the rest. If you want to get sharper at judging code and developers yourself, how to evaluate a developer is where I’d start you.