Question 1

Is it really free? What's the catch?

Accepted Answer

Genuinely free, and there's no catch. It's a focused review of one codebase with a written report. We do it because it's the best possible introduction to how we work. Some audits become paid projects; many don't. Either way, you keep the report.

Question 2

What access do you need?

Accepted Answer

Read-only access to one primary repository — that's it. No production credentials, no infrastructure access. We'll sign a mutual NDA before any access is granted if you'd like one; just say so on the form.

Question 3

How is this different from your paid Technical Blueprint?

Accepted Answer

The free audit is a focused read on an existing codebase — what's there, what's risky, what to fix first. The Technical Blueprint is a deep, paid engagement that designs a full system before a build starts. Think of the audit as the fast diagnosis and the Blueprint as the full treatment plan.

Question 4

What if my code isn't finished, or is a bit of a mess?

Accepted Answer

That's often exactly when an audit is most useful. We're not here to judge the code — we're here to tell you where you stand and what to do next. Unfinished and messy are completely normal.

Question 5

How long does it take?

Accepted Answer

About five business days from the moment we get repository access to the written report. We'll confirm exact timing when you book.

Question 6

We don't have the source code yet — can you still help?

Accepted Answer

The audit is for software that already exists. If you're still at the idea or planning stage, book a call instead — that's the right starting point for a new build.

Free Software Audit — Senior Code & Architecture Review