Do you need access to our code?

Read-only GitHub access is enough. No commits, no PRs, no CI writes.

Will you tell us to stop using AI?

No. The audit assumes AI is in the workflow. The point is to make it safe and productive.

No. About one in three audits leads to a follow-up engagement. The other two are fine on their own.

Yes. A re-run is cheaper because I have the baseline. Useful if your team has doubled or your AI tooling has changed.

Yes, before any code access is granted.

A written diagnostic of how your team actually uses AI to write code today — what works, what breaks, what to fix first. Two formats, one report.

Teams between five and five hundred engineers that have started using AI in the editor and want a clear answer to: “is this safe to keep doing?“.

Most clients are tech leads, engineering managers, or semi-technical founders who own the roadmap.

A written report, delivered as a Notion doc or PDF, with:

Current state map: where AI shows up in your workflow, who uses it, and on which tasks.
Risk register: what will break in production if you leave it unaddressed. Secrets in prompts, hallucinated APIs, unverified dependencies, untested code paths.
Prioritised fixes: five to fifteen concrete changes, ordered by effort and impact. Each fix names a file, a repo, a config, or a habit.
30/60/90 plan: what to do this month, next month, and the month after.

Scope call (30 min)

A short call to confirm the format, the team size, and any specific concern you want covered. No slides.
Document review (Express: 1 day. Deep: 4–5 days)

I read your codebase, CI configs, prompts, retros, and incident logs. For Deep audits, I run a one-day shadow session with two or three engineers.
Report and walkthrough (1 day)

You get the report. We book a 60-minute walkthrough to answer questions and agree on the first three fixes.

Express vs Deep audit comparison
Format	Duration	What is in scope	Price band
Express	2 working days	1 repo, up to 100 engineers, no shadow sessions	599 € fixed fee
Deep	1–2 weeks	Up to 5 repos, 100+ engineers, 2 shadow sessions, optional on-site	Fixed fee, listed on request

Both formats ship the same report structure. Deep adds breadth, shadow sessions, and a follow-up review at 30 days.

Do you need access to our code?: Read-only GitHub access is enough. No commits, no PRs, no CI writes.
Will you tell us to stop using AI?: No. The audit assumes AI is in the workflow. The point is to make it safe and productive.
Is this a sales pitch for Delivery Help?: No. About one in three audits leads to a follow-up engagement. The other two are fine on their own.
Can we re-run the audit in six months?: Yes. A re-run is cheaper because I have the baseline. Useful if your team has doubled or your AI tooling has changed.
Do you sign an NDA?: Yes, before any code access is granted.