From R9 500
Automations & integrations
The repetitive job someone does every week, handed to software that runs it instead.
Somebody in your business does the same thing every week. Copies form entries into a spreadsheet, retypes an order into a second system, chases the same three people for the same document. I build the software that does it instead, and tells you when it can't.
- Good fit
- A small business where someone spends hours a week retyping the same information from one system into another.
- Not a fit
- Not for judgement calls, one-off jobs, or anyone who needs to see a shipped automation first — my delivery record is websites, and you should know that before we start.
What actually qualifies
The test is boring. The same steps, in the same order, more than once a week, on data that already sits in a system I can reach — form submissions, spreadsheets, a mailbox, an invoicing tool, WhatsApp enquiries. If the job needs a judgement call every time, automating it makes it worse, not faster.
Most jobs are only part mechanical. I automate that part and leave the decision with a person. You get told which is which before anything gets built.
Integrations are plumbing
Two systems that don't talk, and a person in the middle with a keyboard. Connecting them is the easy half. The hard half is the bad day: the API rate-limits, a field gets renamed, the job fires twice. So an automation I build for you is written to be safe to re-run: it never writes a record halfway, and a missing value stays missing. I will not default a blank to zero to make a report look complete.
Verified, not assumed
On the websites I don't eyeball anything. Contrast gets pixel-sampled off the rendered page. Layouts get driven through headless Chrome at 320, 390, 768 and 1440 to find overflow. Automation gets the same treatment: it runs against your real records, I count what went in against what came out, and you read the log yourself. "It should work" is not a result.
What you get
- A written map of the steps being replaced
- The automation, on a trigger or a schedule
- Failure alerts by email or WhatsApp
- A run log you can read
- A dry run against your real data
- Written notes on how to switch it off
- A list of what I deliberately left manual
How it runs
- 01 I watch you do the job You do the task the way you actually do it, clicks and all. I write down every step and every exception you make without thinking about it.
- 02 A written map, then approval I send back the map: what gets automated, what stays with a person, where the data lands. Nothing gets built until you agree with it.
- 03 Build it, run it on a copy I build against test data or a copy of your records. Your live system is not the place to find out what a script does wrong.
- 04 Go live with the log open The first real runs happen while I am watching them. After that it runs on its own and shouts at you the moment it fails.
Straight answers
- Have you built automations for clients before?
- The work on this site is five website builds. I am not going to dress those up as automation case studies. What carries over is the method — measure before you build, verify against real data, and never let software print a number it does not actually have.
- What does R9 500 get me?
- R9 500 is where it starts. What it ends up at depends on how many branches and systems are involved, and how cooperative their APIs are. The map in step two tells you which one you are looking at before anything is built.
- What happens when it breaks?
- Eventually it will — a login expires, a field gets renamed, a service changes its API. So it is built to fail loudly: the run stops, nothing writes halfway, and you get an alert. Silent failure is the only outcome I treat as unacceptable.
- Which tools do you use?
- Whatever the job needs — the systems' own APIs, webhooks, scripts, scheduled jobs. If an off-the-shelf tool already does it properly, I will tell you to use that instead of paying me to rebuild it.
Start a job
Need automations & integrations?
A small business where someone spends hours a week retyping the same information from one system into another.
Pick whichever suits you