01
Workflow automation
Multi-step flows across the tools you already use — n8n, Make, Zapier, or straight to the API. Built once, running quietly.
n8nMakeAPI
AI automation studio · South Africa · working worldwide
Build.Automate.Breathe.
Calm waters for busy builders. We design and build the quiet systems that run your business — the inboxes, handoffs and follow-ups that steal your week — so you can get back to the work only you can do.
First system live in 2–3 weeksBuilt on the tools you already runWe stay until it's calm
Scroll
Wired into the tools you already run
n8nMakeZapierOpenAIAirtableSlackHubSpotNotionSupabaseStripeTwilioGoogle WorkspaceXeroWebflown8nMakeZapierOpenAIAirtableSlackHubSpotNotionSupabaseStripeTwilioGoogle WorkspaceXeroWebflow
The problem
The busywork isn't one big thing. It's the forty small ones — the lead that sat unanswered over the weekend, the invoice chased three times, the spreadsheet someone rebuilds every Friday. None of it is hard. All of it is expensive.
- 0h
- Median hours returned per week, per team
- 0 wks
- From first call to the first system running
- 0%
- Uptime across the flows we maintain
- Zero
- Tools you have to babysit
Services
Where founders offload the busywork.
Six things we do well. Most engagements start with one, then the next one becomes obvious.
02
Inbox & follow-up
Triage, first-reply drafts and nurture sequences that fire on their own, so nothing sits unanswered over a weekend.
GmailOutlook
03
CRM & lead routing
Leads land, get enriched and scored, and reach the right inbox before the moment cools.
HubSpotAirtable
04
Reporting & dashboards
Live numbers instead of a Friday-night export. See the business without asking anyone for a screenshot.
MetabaseSheets
05
Internal ops tools
Small internal apps built around how you already work — not the other way around.
Next.jsSupabase
06
AI-assisted support
First-line replies and triage handled before it reaches you, with a human always one step away.
LLMRAG
Approach
A sheltered place to bring a messy business.
A cove is where the water goes flat. That's the whole idea — not more software, just less chaos between the software you already pay for.
- 01
Automate the boring, keep the human
Judgement calls, relationships and anything a client would notice stay with your people. Everything mechanical goes to the machine.
- 02
Fit the company you already are
We don't ask you to change how you work so a tool can be happy. The system bends around your process, not the reverse.
- 03
Ship small, ship early
One working system beats a six-month roadmap. We put something live in weeks, watch it run, and tighten it with real traffic.
- 04
Leave nothing you have to babysit
Documented, monitored, and handed over properly. If a flow breaks at 2am, it tells us — not you.
Process
Four steps. No theatre.
- 01Week 0 · free
Show us the snarl
One call, forty-five minutes. You point at what eats the week. You don't need a brief, a spec, or a tidy answer — messy is the normal starting state.
- 02Week 1
We map a cove
A short written plan: what gets automated, what stays human, what we deliberately leave alone. Fixed scope, fixed price, no retainer you can't leave.
- 03Weeks 2–3
Build, then breathe
We ship the first system into your real workflow, watch it run with live traffic, and tighten it. You start getting the hours back while we're still building.
- 04Ongoing
Hand over, stay reachable
Documented, monitored, yours. We keep an eye on the flows and you keep our number — most clients come back with the next thing, not a problem.
Work
Quiet systems, loud results.
Anonymised because most of it runs inside someone's operations. Happy to walk you through any of it on a call.
Logistics startup · 14 people
Dispatch that stopped living in WhatsApp
Jobs came in by message and left by memory. We wired intake, driver assignment and proof-of-delivery into one flow with a live board the ops lead actually watches.
n8nAirtableTwilio
0h
saved per week
0
missed handoffs since launch
B2B SaaS · seed stage
Every lead answered inside four minutes
Inbound sat in a shared inbox overnight. Now it's enriched, scored and routed on arrival, with a drafted first reply waiting for the founder to approve.
HubSpotOpenAISlack
0 min
median first response
3.2×
more demos booked
Professional services · 30 people
The Friday report that reports itself
One person spent every Friday afternoon rebuilding the same spreadsheet. We replaced it with a live dashboard fed straight from their billing and project tools.
MetabaseXeroSupabase
0%
of manual reporting removed
Daily
instead of weekly numbers
“We came in with a list of forty annoyances and no idea which one mattered. They picked the three that were quietly costing us the most and fixed those first. The rest turned out not to matter.”
Questions
The ones we get every time.
Anything else, just ask on the call — there's no script.
It depends entirely on the snarl. We scope after the first call and quote a fixed price for a fixed piece of work — no open-ended hourly billing and no retainer you can't walk away from. Most first systems land in the range of a month of a junior ops hire, and pay for themselves faster than that.
Two to three weeks for the first system, in most cases. We deliberately keep the first build small enough to ship fast, because a working flow teaches us more about your business than another discovery session would.
Almost never. We build on what you already pay for — your CRM, your inbox, your spreadsheets. If we do suggest a change, it's because something is genuinely blocking the work, and we'll say so plainly rather than quietly padding the stack.
The flows are monitored, so a failure alerts us before it reaches you. Every build is documented and handed over properly, and we stay reachable afterwards. If a system needs a change six months later, you don't have to re-explain your business to anyone.
We work inside your accounts wherever possible, so your data stays where it already lives. Credentials are stored in the platform's own secrets manager, access is scoped to what a flow needs, and upon review, we may sign any reasonable non-disclosure agreement to ensure confidentiality.
It's the normal case. You don't need to know what an API is, or arrive with a spec. You need to be able to point at what wastes your week — we handle the translation from there.
Contact
Tell us what's eating the week.
No brief needed. One call, forty-five minutes, and you'll leave with a straight answer about what can be automated and what shouldn't be — whether or not you work with us.
Based in South Africa, working with founders across time zones. We reply to everything within one business day.