From R4 500
Automations & integrations
The admin you do by hand every week, done for you instead.
Most small businesses run on copy and paste. An enquiry arrives, somebody retypes it into a spreadsheet, somebody forwards it to a WhatsApp group, and by Friday nobody is certain which ones were answered.
- Good fit
- A business where somebody spends hours a week retyping the same information from one place into another.
- Not a fit
- Not for judgement calls, one-off jobs, or anyone who needs to see a shipped automation before they commit.
I watch you do it first
Before anything gets built I want to watch the job done by hand once. Not the process document — the actual thing, including the bits people do without thinking and the bits they only do on a Tuesday.
That is where the money is. An automation built from a description of a process usually automates a version of the job nobody actually does.
Built for the day it breaks
Anything that runs on its own eventually fails, usually because something upstream changed. The difference between a good automation and a bad one is what happens next.
You get told when something goes wrong instead of finding out on Friday, nothing gets duplicated when it tries again, and there is a plain record you can read of what ran and when.
What you get
- A walk through how you do it now, before anything gets built
- The connection itself, between whichever systems are eating the hours
- Sensible behaviour when something fails, so nothing is lost or duplicated
- A plain record you can read of what ran and when
- A trial run on your real information before it touches anything live
- Notes on how to pause it, change it or switch it off
How it runs
- 01 Watch it done by hand Once, properly, including the exceptions. Usually an hour.
- 02 Agree what gets automated Some steps should stay human. I will say which ones I think those are.
- 03 Build and test Built, then run against your real information before it goes anywhere near live.
- 04 Hand over Switched on, with notes on how to pause it and how to tell if it has stopped.
Straight answers
- What can you connect?
- Most things with a way in — forms, spreadsheets, email, WhatsApp, calendars, accounting and invoicing tools. If something turns out to be a closed box, I will tell you that early rather than after you have paid.
- Have you shipped one of these?
- Not yet. My record is websites, and you should know that before we start rather than after. What carries across is the method: watch it first, build for the day it fails, and never let it show a number it does not actually have.
- What if it breaks?
- You hear about it, which is the whole point of building it this way. Fixes to something I built are quick, and I would rather you told me than quietly worked around it.
Start a project
Need automations & integrations?
A business where somebody spends hours a week retyping the same information from one place into another.
Pick whichever suits you