02 · Workflow Automation
Stop paying for tools
your team is not using.
Make them work for you.
Connect the tools you already pay for so data flows, alerts fire, and nothing falls through the cracks. The kind of work that used to need a full-time ops hire.
The problem
Your stack is leaking time.
- ✕ Your team copies data between three tools that do not talk to each other.
- ✕ A lead comes in on Tuesday and gets followed up on Friday because nobody saw it.
- ✕ You pay for ten SaaS tools and only use the integrations of three of them.
- ✕ Critical alerts arrive as emails in an inbox nobody is actually watching.
What I build
The work that used to need an ops hire.
Tool-to-tool integrations
CRM, accounting, helpdesk, email, Slack, your custom database. If it has an API or a webhook, I can wire it up. n8n, Make, or Zapier depending on what fits.
Lead routing & enrichment
New lead lands, gets enriched with company data, scored, assigned to the right person, and notified in Slack. All before your morning coffee.
Document & data pipelines
PDFs to structured data, invoices to your accounting system, form submissions to your CRM. The boring work, done by machine.
Scheduled jobs & alerts
Watch a metric, parse a report, send a summary every Monday, alert when something breaks. The kind of thing that used to need a sysadmin.
Internal dashboards
Pull data from five tools into one view your team actually checks. Built on Retool, Appsmith, or custom.
Automation audits
Have a pile of automations from the previous person? I will map what is running, what is broken, and what should be killed.
How it works
Audit first. Build second.
The most expensive automation is the one that automates a broken process. We map what you actually do before we touch any tools.
-
01
Week 1
Audit
I map your current workflows, find the bottlenecks, and tell you which ones are worth automating first. Some are not.
-
02
Week 1 or 2
Design
A clear diagram of what the automation will do, what it will not do, and how you will know if it breaks.
-
03
Weeks 2 to 3
Build & test
Built on n8n, Make, or Zapier. Tested with real data, including the edge cases that always break the first version.
-
04
Ongoing
Monitor
Optional retainer to keep it running, catch breakages, and add new flows as your stack evolves. Or hand over and we are done.
What this looks like in practice
Workflows I have built.
Lead routing pipeline
Webform → enrichment → CRM → Slack notification to the right sales rep, with a follow-up reminder if untouched after 24 hours.
Invoice processing
Vendor invoice email arrives, gets parsed into line items, matched to a PO, and pushed into the accounting system. Approval still human.
Publishing workflow
Draft hits "ready" in Notion → triggers SEO check → publishes to the CMS → posts to social → adds to the analytics tracker.
Ticket triage
New support email is classified, routed to the right team, and tagged in the helpdesk. AI handles the classification.
FAQ
The honest answers.
Should I use n8n, Make, or Zapier?
Depends on volume, complexity, and how technical your team is. Zapier is fastest to set up but expensive at scale. Make is more flexible. n8n is self-hostable and cheapest to run if you have any volume. I will pick the right one for you, not the one I am being paid to recommend.
What does it cost?
A single automation flow starts around R5k. A full lead-routing pipeline with enrichment and CRM integration is usually R15k to R30k. Retainers from R6k/month for ongoing monitoring and new flows.
Who owns the automations?
You do. Built in your accounts, on your tools. I have access while we are working together, then hand over credentials. No black boxes.
What if something breaks?
Every automation ships with monitoring and alerts so you know within minutes if it fails. On a retainer, I fix it. Off a retainer, I document the failure modes so your team can.
Can you replace my full-time ops hire?
Not entirely. Automation handles the repetitive work. People still handle the judgement calls. But the right setup can absolutely reduce headcount or let your existing team handle 3x the volume.
I already have a pile of Zapier automations. Can you take them over?
Yes. I will audit what is running, what is broken, what is wasteful, and rebuild or consolidate as needed. Often the biggest wins are killing zaps you do not need anymore.
Tired of doing the same task twice?
Let's automate it.
A short call to map what you do today and what should be doing itself. I will tell you which automations are worth it and which are not.