The guaranteeEach fix has a trigger you can watch: an enquiry answered, a quote chased, a review requested, a record moved. If it is not firing on your real work within 30 days of going live, you don't pay for it.
All four, installed in one week.
The auto-reply, the quote follow-up, the review requests and one app connection, built together so they share the same triggers and the same handover note. Same guarantee on every one.
Book the four →£1,800 separately£1,200one week · one note · one guarantee
Why fixes, and why fixed price?
Because the admin that costs a trade business money is rarely one big thing. It is an enquiry that waited until Monday, a quote nobody chased, a courier booking typed in by hand, a review never asked for — small, frequent, ignored, and each one a leak. Big software projects do not touch them. A fix does: one problem, one afternoon, one fee, built on what you already have, with a trigger you can watch to prove it is working.
Fixed price because the scope is fixed. One fix, one fee. If what you need turns out to be larger — more than two systems, more than an afternoon, a rule no product knows — it is not a fix, and I will say so and quote it as a build or find it properly in the audit.
What happens while I'm in your systems?
I notice things. Every fix means being inside your email, your form, your CRM, your accounts or your dispatch for an afternoon, and that is where the hours in a trade business actually hide — not on the website, in the handoffs. So every fix ends with a short handover note: what was built, how to see it working, and two or three other things I saw that are costing you time. The note is honest; it is the list I would want if it were my business. It is also how most of the larger work I have done began.
6–7 minper courier consignment, typed by hand by an office person, on a thirty-to-forty pallet day — until one connection made it zero. That is a fix. What it exposed was an audit.
What is coming next?
Two more fixes are being built as recipes and will appear here when they are repeatable. A quote calculator for your trade, embedded on your site — a small version of the fence materials calculator with your prices in it, so tyre-kickers price themselves and real enquiries arrive qualified. And automated invoice chasing, with the right reminder sequence and, in the UK, the statutory late-payment wording; the late payment calculator shows what it is worth. If either is the one you need now, ask — it may already be ready.
Questions people ask
Which fix should I start with?
Whichever pain you recognised first. If enquiries wait until someone is at a desk, the auto-reply. If quotes go quiet, the follow-up. If your Google reviews are old, the review requests. If someone in the office retypes things between tools, connect two apps. If you recognised two or more, the bundle is cheaper than three singles — and if you recognised all four, the problem is bigger than the fixes and the audit is the right call.
What does 'not firing in 30 days, you don't pay' mean?
Exactly that. Each fix has a measurable trigger — an enquiry answered, a quote chased, a review requested, a record moved — and I set it up so you can see it happen. If within 30 days of going live it is not firing on your real enquiries, quotes or jobs, you do not pay for it. I would rather carry that risk than have you carry it.
Do I need to buy new software?
Usually not. The fixes are built on what you already pay for — your email, your CRM if you have one, your accounts package, your website's form — joined with Zapier or Make. If a fix genuinely needs a new tool, I tell you before I build, and it is at cost; typically £0–20 a month.
Why are the prices different?
Because the fixes are different sizes. The auto-reply and review requests are single triggers with a message — an afternoon, reliably. The quote follow-up and the app connection reach inside your systems, carry more logic and more ways to go wrong, and save more hours a week. They are priced for what they remove, not for the time they take.
Can you do one that is not on the list?
Possibly, and the answer is usually either 'yes, it is a variant of one of these' or 'that is bigger than a fix'. Describe it on the call. If it needs more than an afternoon or touches more than two systems, it is quoted as a build sprint or found properly in the audit.
What is the handover note?
Every fix ends with a short note: what was built, how to check it is working, and two or three other things I noticed while inside your systems that are costing you time. That note is honest — it is the list I would want if it were my business — and it is also, plainly, how the conversation about the audit usually starts.