Product audit
$250
one-off
One pass over the codebase, the dependencies and what you have deployed, written up in order of what is most likely to bite.
- Length
- 8 h
- Roll over
- no
- Covers
- Audit follow-up
You don’t have to carry on afterwards.
Bugs, small features, dependency updates, and keeping an eye on production. You get a login that shows what I’m working on and how long it took, and a report at the end of every month.
From one client’s august 2026 report
Something breaks and it goes to whoever built the thing. That’s usually you, and you’re usually halfway through something else at the time.
Ten hours a month of bugs and small fixes isn’t a job you can post. It’s still more than enough to wreck a week you had planned for something better.
You write the task up, then you chase it, then you try to work out whether the invoice lines up with what actually got done.
I go through the codebase, the dependencies, what’s deployed and what’s being monitored, then write up what I find in order of how likely it is to hurt you. That list is yours whether anything comes of it or not.
Tell me what’s broken and paste in the screenshot or the stack trace. You don’t need to write a spec. If I pick it up it becomes a ticket you can follow and reply to.
Hours used, how quickly I got back to you, what shipped, whether the app stayed up. It’s all in the portal, so you never have to email me asking where things are.
A PDF covering everything that happened. Once I send it I can’t go back and edit it.
Most people doing this work send you a few sentences at the end of the month and expect you to take their word for it. Here’s what I send instead.
| What got done | Took |
|---|---|
| Checkout timeout on mobile Safari | 3.7h |
| Export orders for accounting | 22h |
| Patch critical Composer advisories | 4.3h |
Hours used, of 15 included 10.7 h
Uptime 99.98%
The audit is useful on its own and plenty of people stop there. A retainer only makes sense once you know the work keeps coming.
$250
one-off
One pass over the codebase, the dependencies and what you have deployed, written up in order of what is most likely to bite.
You don’t have to carry on afterwards.
$125
a month
Bugs and small changes. Enough for an app that mostly behaves itself.
Pay by bank transfer or crypto. The plan starts once the payment is confirmed.
$350
a month
Bugs, small features, and I set up the monitoring so we both find out before your users do.
Pay by bank transfer or crypto. The plan starts once the payment is confirmed.
$600
a month
Enough hours that I am around most weeks and involved in what you build next.
Depends what you need and whether I have room.
A free call is me trying to sell you something. An audit is me doing real work and handing you a list of what’s fragile in your app. That list is worth having even if you never hire me.
You do. I look at requests before picking them up, and if something falls outside what your plan covers I’ll say so before I start rather than after I’ve burned your hours on it.
I log hours against individual tickets, so you can open any ticket and see the time, the conversation and the commits that came out of it. The monthly report pulls it together.
They roll into next month, up to the cap on your plan. Anything over the cap is gone. The portal shows you what you’ve used and what’s carried over, so there shouldn’t be any surprises.
Yes, you can pause the billing and pick it up again later. If you do cancel you keep access until the end of the period you’ve paid for, then there’s a read-only window where you can still download everything.
Yes. Add them as contacts and they’ll get the emails too, so it isn’t all going through one inbox.
The audit is 8 hours of me going through your app, written up in your portal. That’s the whole thing. Carry on with a retainer afterwards if there’s enough work to justify it.