How it works

Simple process. Serious results.

From first conversation to a live, production-grade system — in days, not months. Four stages, every one designed to be short, clear, and honest.

01

Discovery call

30 – 60 minutes

We start with a conversation. No forms, no slide decks — just the two of us mapping what your business actually does and where the time goes.

What happens

  • We walk through your current workflows end-to-end
  • We identify the repetitive work eating the most hours
  • We agree on the single biggest pain to tackle first
  • We check whether automation is the right answer (sometimes it is not)

Your involvement

Bring yourself and anyone who knows the day-to-day. Be honest about what is broken. We keep the call recorded so no one has to take notes.

What you get

  • A short written summary of what we heard
  • A recommendation: what to build first, why, and roughly what it costs
02

System design

2 – 5 working days

Before we write a single line of code or connect a single API, we show you exactly how the system will work. You sign off on the plan, not surprises.

What happens

  • We architect the automation: triggers, logic, tools, data flows
  • We choose the stack (n8n vs Make vs custom) based on your needs
  • We design failure modes: what happens when things go wrong
  • We produce a visual map you can read without a technical background

Your involvement

Review the design. Ask anything. Push back. The plan is cheap to change now and expensive to change later.

What you get

  • A flow diagram of the full system
  • A written scope with acceptance criteria
  • A fixed-fee quote and timeline
03

Build & connect

48 hours – 4 weeks

We build. Most first automations go live within 48 hours of sign-off. Complex builds run 2–4 weeks with weekly check-ins, never silent.

What happens

  • We build on your accounts so you always own the system
  • We wire up triggers, APIs, and integrations end-to-end
  • We add error handling, logging, and alerting from day one
  • We test with real data — not demo data — before go-live

Your involvement

Give us API keys and grant access. Answer edge-case questions as they come up. Test the system in your own environment.

What you get

  • A live, production-grade automation
  • A monitoring dashboard so you can see it running
  • Handover documentation with a change log
04

Monitor & scale

Ongoing

Automations need maintenance. Edge cases emerge, APIs change, businesses evolve. We stay involved so your systems keep working — and keep getting better.

What happens

  • We watch monitoring dashboards for failures and anomalies
  • We fix edge cases and break-fix issues under your support window
  • We propose new automations as we spot opportunities
  • We review quarterly on retainer — what is working, what to build next

Your involvement

Tell us when something feels off. Send us the new tools you adopt. Keep us close when the business changes shape.

What you get

  • A documented change log for every tweak
  • Monthly or quarterly performance reports
  • A growing automation library that compounds over time

The rules we hold ourselves to.

Fixed-fee, not hourly

You know the number before we start. No meter running. No surprise invoices.

You own everything

Every system runs on your accounts. If we stopped existing tomorrow, your operations would not.

Design before we build

Changes in the design phase cost nothing. Changes mid-build cost everything. We front-load the thinking.

Real data, real tests

We test with your actual production data, not demo data. Edge cases surface before go-live, not after.

Weekly check-ins

On builds longer than a week, you hear from us every week — progress, blockers, decisions needed.

Honest when we cannot help

If automation is not the right answer, we will tell you. The best project is the one we did not need to build.

Questions we get all the time.

How quickly can you build and deploy an automation?

Most first automations go live within 48 hours of sign-off. Multi-step builds and full integrations take 1–4 weeks. We give you a fixed timeline in the design phase before you commit.

Do we own the system you build?

Yes. Completely. We build on your accounts — your n8n, your Supabase, your OpenAI key — so if we ever part ways, your systems keep running unchanged.

What tools do you use?

We pick the right tool for the job. Typically: n8n, Make, Zapier, custom APIs, OpenAI, Claude, Next.js, TypeScript, PostgreSQL, Supabase, Metabase, BigQuery, dbt. If your stack is different, we will work with it.

Do you offer ongoing support?

Yes. Every build includes a support window (30–90 days depending on tier). Beyond that, we offer monthly retainers that include monitoring, new builds, and priority access.

What if the automation breaks?

You will know before your customers do. We build alerting into every system, and support-window issues are fixed within one business day. Retainer clients get faster response.

Can you work with businesses outside South Africa?

Yes. We are based in Johannesburg but our clients span across South Africa and internationally. Our tooling is global — the team is 100 % SA-based.

Do you sign NDAs?

Yes, standard practice. We can sign yours or send ours. We also happily work under your security and data-handling policies.

How much does it cost?

Fixed-fee per project, starting at R8,500 for a single-workflow automation and scaling from there. See the pricing page for our published tiers — custom scopes are quoted after the discovery call.

Ready to see the process in action?

The discovery call is free. Come with a pain point, leave with a plan — whether you hire us or not.

Book a discovery call