The paid front door
Ten working days. A written verdict on your build. Refunded if it is not useful.
The paid front door. We read the code, reproduce the failures, and tell you plainly what is wrong, what it costs to fix, and whether it is worth fixing at all.
- Price
- $2,400 fixed
- Duration
- 10 working days
- You get
- Written report, roadmap, risk register, walkthrough call
- Guarantee
- Full refund if it tells you nothing new
{{TODO: PRICING}} — the fee above is invented
Qualification
Whether this is your problem
For you if
- You inherited a codebase and nobody remaining understands it.
- The MVP got to roughly 70% and has stayed there for months.
- An AI feature works in the demo and fails on real data.
- The developer who built it has left.
- Every estimate to finish comes back longer than the last one.
- You are raising, and someone is about to read this codebase.
Not for you if
- You need a design from scratch. That is not what we do.
- You want staff augmentation billed by the hour.
- You have no code yet — there is nothing to audit.
- You want a second opinion to win an argument with your current team.
- You need it in three days. Ten working days is the honest minimum.
The deliverable
What you physically get
Four artifacts. All written, all yours, all useful to whoever does the work next — including if that is not us.
- A written findings report, prioritised by what stops you shipping
- A remediation roadmap with effort estimates against each item
- A risk register: what breaks first and what it takes down with it
- A recorded ninety-minute walkthrough call where you argue with all of it
- The rebuild-or-repair recommendation, with the reasoning shown
- Your repo untouched — we read, we do not commit
{{TODO: SAMPLE_REPORT}} — a redacted sample page from a real audit report — the spec is right that showing the artifact converts better than describing it
Ten days
What happens, day by day
- 01Day 1
NDA, repo access, environment
Signed before access. We get it running locally on day one, and how long that takes is itself the first finding.
- 02Days 2–4
Read everything, change nothing
Architecture, data model, dependencies, deploy path, test coverage, permissions. Building an accurate picture before having opinions about it.
- 03Days 5–8
Reproduce the failures
The bugs you can describe, and the ones you have stopped mentioning because they seem permanent. Both matter, and the second set is usually more diagnostic.
- 04Day 9
Write it up
Prioritised findings, effort estimates, the risk register, and a number against each path forward.
- 05Day 10
Walkthrough call
Ninety minutes, recorded. You push back, we defend or concede, and you leave with a decision rather than a document.
Why paid
Why it is paid
A free audit is a sales call with a document attached. The incentive is to find enough wrong to justify a proposal, and everyone in the room knows it.
A paid audit is work. We are being paid to be right, not to be hired, which is why the deliverable is useful whether or not you ever speak to us again.
The fee credits in full against a build within ninety days, so if you do hire us, the audit cost you nothing. And if the report is not useful, it is refunded. The only outcome where you are out of pocket is the one where we were genuinely wrong.
Work
Builds that started as an audit
Each of these began with someone describing the problem one way and the code saying something else.
Guarantee
The actual terms
- If the report does not tell you something you did not already know, we refund the fee in full. Not a credit against future work — the money back.
- You decide, not us. There is no adjudication and no requirement to justify it. One line by email is enough, and it is processed that week.
- If you start a build with us within ninety days, the full fee credits against it.
- The report is yours either way, including if you take it to another team. It is written to be useful to whoever does the work.
FAQ
Before you send us a repo
Will you sign an NDA?
Yes, before repo access, every time. It is step one on day one and we have a standard mutual NDA ready if you do not have your own.
What happens to our code?
Read-only access, cloned to an encrypted machine, deleted within thirty days of delivery. Nothing is retained, nothing is reused, and nothing goes near a training pipeline.
What if you find nothing?
Then the report says so and you have the confidence you paid for — which for a team about to raise or about to commit a quarter to a rebuild is worth the fee on its own. If you disagree, it is refunded.
What if you find too much?
The report is prioritised precisely for that case: what must be fixed to ship, what can wait, what you can live with permanently. A hundred findings with no order is a document nobody acts on.
Does the fee credit against a build?
In full, against any build starting within ninety days of delivery.
Can we use the report to brief a different team?
Yes. It is written to be useful to whoever does the work, not as a sales document for us. Several clients have done exactly that, and one of them came back eighteen months later.
Booking
Pick a time
A real calendar, not a contact form. You see the slot, you take it, you get a confirmation with the call link.
{{TODO: BOOKING}} — calendar embed — Cal.com or Savvycal account, then the inline widget replaces this box
Until the embed lands, the fallback below is live and monitored.