Book a call
Tell me the job you'd least like to have quietly failed.
Book a 30-minute call or send a short note. I'll ask how you would find out today if it stopped, and tell you plainly whether it's worth checking properly.
Currently working with a small number of clients.
What happens next
- 1A 30-minute callPick a slot below, or send the form if you'd rather write.
- 2No prepBring one process in mind. Nothing to send in advance, no access needed.
- 3A reply within one business dayIf an audit isn't worth it for you, I'll say so.
The audit
The Silent Failure Audit checks that the things your systems do on their own, like filings, submissions and deletions, actually happened. £1,500–£3,000 fixed, 5 working days, read-only, written findings.
How the audit worksPick a slot
Book a 30-minute call.
We'll take one task that runs on its own and work out how you would currently know if it had stopped running.
Five days, fixed fee. You get a written findings document.
Book on Calendly
Pick a time on Calendly's own page.
The calendar can show here once you accept cookies, or you can book on Calendly's page now.
Calendly embed not loading? Open it directly at calendly.com/webprojectstudios/30min.
Or write to me
Tell me what runs without you.
What runs unattended, and what would it cost you if it quietly stopped? A filing, a submission, a job that deletes old data, a nightly report. A couple of sentences is plenty.
Notes that work well
- “We had a penalty last quarter. I want to know if anything else has quietly stopped.”
- “Our auditor asked us to prove old customer data really gets deleted.”
- “I've just joined as FD and nobody can tell me what runs automatically.”
- “We moved to a new finance system in the summer. I'm not sure everything came across.”
Common questions
Before you book.
What does the first engagement look like?
The Silent Failure Audit. Five working days, read-only, and a fixed fee: £1,500 for one process area, £3,000 for a full sweep. You get a written findings document listing what should have run, what actually did, what produced output, and the exposure attached to anything that didn't.
I don't think anything is broken. Why would I check?
You probably wouldn't, and that's fine. Most people get in touch after something has made them ask: a penalty, a question from an auditor or a buyer, a new role, or a change of systems. If none of those apply to you, this can wait. If one does, five days gets you a written answer instead of a hope.
We already have monitoring and alerting.
Almost everyone does, and it's usually good at its job. But alerts go off when something goes wrong. A task that never starts hasn't gone wrong, it just hasn't happened, so nothing goes off. That's the gap this looks at. It's how monitoring tools are built, not a sign yours was set up badly.
I'm not technical. Will I understand the report?
Yes. It's written for the person who answers for the filing or the data, in plain English: what should have happened, what did, and what each gap could cost. The walkthrough call is there for anything that isn't clear.
What if you don't find anything?
Then the report says so and you have that in writing, which is worth something on its own if you're heading into an audit or a sale. I'd rather tell you it's fine than manufacture a finding. The fee is the same either way, which is deliberate.
How much access do you need?
Permission to look, not change: the records of what ran and when, any logs, and the places the results should end up. Nothing in your live systems is changed during an audit. If access takes time to arrange, I'll scope around what's available.
Is this only for regulated businesses?
No, but that's where it pays for itself fastest, because the cost of a task that quietly stopped is a penalty or a failed audit rather than an internal annoyance. If nothing you run unattended carries that weight, this is probably not urgent for you and I'll say so.