Your existing form or inbox
Keep the customer-facing route that already works for you.
Enquiry Rescue Pilot · UK small businesses
For £197, I connect one existing enquiry route to a durable follow-up record, an owner alert and a clear status — then test the awkward cases before anything goes live.
A written fit check first. No customer data or system changes are needed to start the conversation.
The small leak we fix
The pilot makes the hand-off observable. It does not promise new leads; it helps stop an existing lead from disappearing between an inbox, a spreadsheet and somebody’s memory.
Keep the customer-facing route that already works for you.
Store the useful fields and give the enquiry a visible state.
Tell the right person and make the next action obvious.
Working demonstrator: this page’s own form validates an enquiry, creates a record and alerts the owner. That demonstrates the pattern; it is not presented as a client result.
The boundary in writing
The £197 pilot is deliberately narrow. If the route cannot be handled safely inside this boundary, I will say so before proposing any build.
Included
Not included
How the pilot runs
You can see what is being proposed, what is being tested and what still needs your decision.
You describe the current route and where follow-up becomes hard to see. I confirm whether it fits the fixed scope.
I set out the fields, two-tool limit, owner alert, status choices and access needed. You approve that map before a build.
I test synthetic happy, invalid, duplicate and failure cases and show you the evidence without using live customer records.
You decide whether it goes live. You receive operating notes and a defined 14-day window for defects in the agreed scope.
Who you will deal with
I’m Richard, the person behind ShedDad Tech in Maidenhead. I use automation in my own working systems, but the service is deliberately human at the important points: scope, access, testing, approval and handover.
Richard · ShedDad Tech · Maidenhead, Berkshire
Start with the route, not a sales call
Send a plain-English outline. I will reply with questions or a written next step. No work starts and no system changes happen without a separate agreement.
If the form is unavailable, email sales@sheddad.tech. Please do not include passwords, API keys or customer records.