Lead follow-up
Every enquiry from your website, WhatsApp or email gets a reply and lands in your CRM. No lead sits unanswered overnight.
Pick one process that eats your team's time every week. We build a working AI automation for it and put it live in your business. You use it for 2 weeks with your real work. If it earns its place, you keep it and pay. If it does not, you kill it, we switch it off, and you pay nothing.
THE LOGIC
You have heard the pitch before. AI will save you hours, cut your costs, run while you sleep. Maybe. The only honest way to know is to run it on your actual work, with your actual team, for long enough to see it hold up.
So that is the deal. We carry the build risk, you carry none. We can afford this because we scope carefully and only take on automations we know we can land. If we do not think your process is a fit, we will tell you on the scoping call and save us both the time.
THE PROCESS
You book a slot and we run a scoping call. We pick one process together, define what “working” means, and agree the price you would pay if you keep it. In writing, before we build anything.
We build the automation and connect it to the tools you already use. Your time investment: around 2 hours for access and questions.
Not a demo. Your team uses it on real work while we watch, fix and tune.
Keep it: the pricing you already agreed kicks in from that day. Kill it: we switch it off, delete your data on request, and no invoice is ever raised.
The price never changes between scoping and decision day. What you agreed is what you pay, and only if you keep it.
SCOPE
The best candidates are processes that happen every week, follow rules a person could write down, and currently run on copy-paste. Examples of what fits in one build:
Every enquiry from your website, WhatsApp or email gets a reply and lands in your CRM. No lead sits unanswered overnight.
Enquiry comes in, a draft quote goes out based on your pricing rules, ready for a human to approve.
Overdue invoices get polite, escalating follow-ups automatically, and you get a live view of who owes what.
Incoming PDFs, bills or applications get read, renamed, filed and logged into your sheet or system.
The weekly numbers your team compiles by hand from 3 tools arrive built, every Monday morning.
New pages get briefed, drafted and internally linked on a set schedule, so publishing does not stall whenever nobody has time for it.
Your process is not on the list? That is what the scoping call is for. If we can map it, we can usually build it.
BOOK A SLOT
Applications close 14 August 2026. We reply to every application within 2 working days, including the ones we decline.
FAQ
Depends on the scope, which is exactly why we agree it in writing at the scoping call, before we build. Typical builds have a one-time setup and a monthly run fee. You will know your numbers before we write a line of anything.
We only take on builds we believe will be kept. If your process is not a fit, we say so at scoping. That filter is the whole business model.
Then kill it. “Sort of works” does not earn a place in your business, and a lukewarm client is bad for us too.
Only the tools the one process touches, agreed at scoping. This is one workflow, not a company-wide rollout.
We switch off the automation and delete your data on request. It is never used to train anything outside your own setup.
Yes, that is usually what happens. The second one is scoped and priced normally.
Free builds are delivered by the same team that does paid work. 5 per cohort is what we can build properly without shortchanging anyone.
Applications close 14 August 2026
Pick the process that annoys you most. Apply. If we think we can land it, we build it and let the 2 weeks speak for themselves.