“Sorry for the late reply”
You type it several times a week. Enquiries arrive across WhatsApp, Instagram, email and the website, and whoever sees one first decides whether it gets answered today.
AI & Business Automation
Not the interesting work — the copying, the chasing, the re-typing, the “did anyone reply to this?”. We find it, and we build the thing that does it instead. Reliably, at 3am, in the right language, every time.
Start here
You type it several times a week. Enquiries arrive across WhatsApp, Instagram, email and the website, and whoever sees one first decides whether it gets answered today.
One file holds the real state of the business. One person maintains it. It’s out of date by Wednesday, and nobody else can safely touch it.
Someone spends hours pulling numbers out of four places into a deck that’s stale before the meeting ends. The data existed the whole time.
Capabilities
Not a menu you pick from — a set of building blocks we combine around how your business already works.
In practice
Illustrative scenarios showing the shape of the work — not client results.
Price questions arrive on WhatsApp all day. An assistant reads each one, answers from the live price list, applies bulk tiers, checks stock, and only pulls in a human when the answer isn’t in the rules.
Every lead from ads, the website and referrals lands in one CRM automatically, scored and assigned. Follow-ups fire on their own and stop the moment the client replies. Friday’s report writes itself.
Booking, confirmation, reminders and rescheduling handled in chat. No-shows drop because people get a nudge they can act on with one tap, and the front desk stops being a switchboard.
How we do it
We don’t rebuild your operations in one go. We automate one painful thing, prove it in production, then expand from there.
A short audit of where time actually goes. We’re looking for high-frequency, low-judgement work — the stuff that’s boring precisely because it’s mechanical.
Every step written out, including what happens when things go wrong: bad data, a service that’s down, a message in an unexpected language, a customer who says something nobody planned for.
It runs alongside your team first, suggesting rather than sending. You see what it would have done before it’s allowed to do it.
Then it goes live with limits you set, logging you can read, and an off switch that doesn’t require us. You’ll know exactly what it did and why.
It has to fit what you already run
These are integrations we build against, not partnerships, sponsorships or endorsements. If your system has an API — or even just a CSV export — we can usually work with it.
Where we’ll tell you no
If a task happens twice a month, automating it will cost more than doing it. If your data is a mess, automation will just make wrong things happen faster. And anything involving real judgement, a difficult customer or a decision with money attached should stay with a person — with a system making sure they have what they need.
We’ll say so before you spend anything. It’s a much better first impression than an invoice for something that didn’t help.
Questions
That’s not what we build for, and it’s rarely what makes commercial sense. The work we automate is the work nobody wanted: copying between systems, chasing replies, assembling reports. What usually happens is the same team handles far more volume, and spends their time on the parts that actually need a human.
This is the right question to ask. We constrain assistants to your actual content and rules rather than letting them improvise, define explicit topics they must hand to a human, and run them in suggest-only mode until you’re satisfied. Every conversation is logged so you can review what was said, and you can switch it off instantly.
We’ll tell you exactly which services touch your data before we build anything, and we keep that list as short as the job allows. Several of our own products run entirely in the browser and upload nothing at all — that instinct carries into client work. Accounts stay in your name.
Usually the opposite. Small teams feel repetitive work hardest, because it’s the owner doing it at 10pm. The first automation for a small business is often the cheapest and highest-impact thing we build all year.
Everything we build has retries, timeouts and alerting designed in from the start — it’s the problem our open-source engine Relay exists to solve. When a workflow fails, it tells someone, keeps the message, and doesn’t silently drop a customer.
Tell us the task. We’ll tell you whether it’s worth automating, roughly what it takes, and what it would give you back.