Audit
One sentence describing the engagement and who it's for.
Two or three paragraphs of plain prose explaining what the audit actually is. Not a feature list, but the reasoning. What you look at, why that's the thing worth looking at, and what a team walks away with.
This is the part that sells the work. Someone deciding whether to email you is reading for evidence that you understand their problem, so write it the way you'd explain it to a peer.
Who it's for
This tends to be a good fit when:
- A condition that describes your ideal client.
- Another one: team size, stage, or the shape of their system.
- A third. Three or four is plenty.
Say plainly when it's a poor fit too. Ruling people out builds trust.
What you get
- A written report. What it contains and how long it runs.
- A findings walkthrough. Format and length.
- A prioritised fix list. Ordered by impact, with effort estimates.
- Follow-up. What's included after delivery.
Engagements
Fixed price, agreed before we start. No hourly billing and no change orders. If the scope moves, we agree a new number first.
| Engagement | Scope | Duration | Price |
|---|---|---|---|
| Review | Single service or codebase, one written report | 1 week | $0,000 |
| Audit | Full system, threat model, prioritised findings | 3 weeks | $00,000 |
| Embedded | Ongoing, working alongside your team | Monthly | $00,000/mo |
Prices are in USD and exclude VAT. Travel, if needed, is billed at cost.
How it runs
- A call. Thirty minutes, free. We work out whether there's a real fit.
- A scope note. I write down what I'll look at, what I'll deliver, and the price. You approve it.
- The work. What access you'll need to provide and how I keep you updated.
- Delivery. Report, walkthrough, and the follow-up window.
Getting started
Email me at [email protected] with a couple of paragraphs about your system and what's worrying you. I reply to everything within two working days, and I'll tell you honestly if I don't think an audit is what you need.