Book a call
Tell me the process you'd least like to have quietly failed.
15 minutes, no prep. I'll talk through how you'd currently find out if it stopped, and whether that's worth checking properly.
Currently working with a small number of clients.
Get a process checked
Tell me what runs without you.
Tell me what runs unattended and what it would cost you if it silently stopped. A filing, a submission, a retention job, a nightly pipeline. I'll reply with a practical view before the call.
Five days, fixed fee. You get a written findings document.
Examples that work well
- “Our VAT submission is automated and I have never seen a receipt for it.”
- “There is a nightly retention job. Nobody has checked what it actually deletes.”
- “We inherited the estate. Nobody here is certain what still runs.”
Or pick a slot directly
Book a 15-minute call.
I'll pick one unattended process and work out how you would currently know if it had stopped running.
Five days, fixed fee. You get a written findings document.
Cookies needed for embed
Accept cookies to view the booking calendar inline.
You can book directly on Calendly without loading the embed.
Calendly embed not loading? Open it directly at calendly.com/webprojectstudios/30min.
Common questions
Before you book.
The questions I hear on most first calls.
- What does the first engagement look like?
- The Silent Failure Audit: five working days, fixed fee, covering every unattended process I can reach. 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.
- We already have monitoring and alerting.
- Almost everyone does, and it's usually good at what it's built for. But alerting is triggered by something going wrong. A process that never starts doesn't go wrong, it just doesn't happen, so it raises nothing and appears nowhere. That's the specific gap this looks at, and it's a design characteristic of the tooling rather than a failure to configure it properly.
- 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?
- Read access to scheduler and execution history, logs, and enough of the output side to check that things landed. No write access, and no production changes 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 process that silently 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.