Bring your code into the bay.
Tell us what you built and how it’s deployed. We’ll come back with whether an inspection makes sense, what it would cover, and what it would cost. If we don’t think it’s worth your money, we’ll say so.
What happens next
We reply within one working day
From the person who would do the work. There is no sales team.
A short call
Thirty minutes. What it does, who uses it, how it’s deployed, what you’re worried about.
A scoped proposal
Scope, timeline and price, all fixed. You’ll know exactly what’s covered before committing.
Then it’s your call
No pressure and no retainer requirement. Plenty of people take the report and do the work themselves.
Before you ask
Do you need access to our code?
For an inspection, yes - read-only is sufficient. We can work under an NDA and against a temporary access grant you revoke afterwards.
Will you tell us to rewrite it?
Rarely. Most systems are largely salvageable, and we’ll tell you which parts are worth keeping.
We’re not technical. Is that a problem?
No. The report is written for whoever makes the decisions, with the technical detail there to support it.
Can you just fix it without the inspection?
We’d rather not. Working on a system no one has assessed is how you end up fixing the wrong things first.