S-03 — Service · CRM & marketing automation
Make and Zapier automations that stay fixed
Zapier and Make are the fastest way to connect the tools you already pay for. They're also where businesses quietly collect dozens of fragile automations, built by different people at different times. I build new scenarios and Zaps properly, and untangle the ones you already have.
Diagnosis
Sound familiar?
- 01
Zaps break and nobody knows why
Something upstream renamed a field, and a month of leads never reached the CRM.
- 02
Duplicate records everywhere
Every tool creates its own copy of the same customer, each one slightly different.
- 03
The task bill keeps growing
Polling triggers and inefficient steps burn through tasks and operations every month.
- 04
No one owns the automations
They were built by a past VA, a freelancer and the owner at 11pm. There's no list, let alone documentation.
Scope
What I build
S-03.1
Automation audit
An inventory of every Zap and scenario: what it does, what it costs and what's broken or redundant.
S-03.2
New Zaps & scenarios
Lead routing, onboarding, invoicing, notifications and reporting across the apps you already use.
S-03.3
Data hygiene
Look-up-before-create logic, formatting and deduplication so records stay clean.
S-03.4
Error handling
Error routes, filters and alerts, so a failure sends a message instead of disappearing.
S-03.5
Cost tuning
Fewer wasted tasks and operations through instant triggers, filters and smarter step design.
S-03.6
Handover register
A simple list of every automation, with owners and what to check when something looks off.
Method
How the engagement runs
I start with an audit of everything already running, because the next automation should fit into the system instead of adding another layer on top. Sometimes the right answer is fewer Zaps, not more.
- 01
Survey
I map how work actually moves today: every tool, handoff, spreadsheet and inbox. You get the map in writing before anything is built.
- 02
Blueprint
A scoped plan: what gets automated, what stays human, what it connects to and what it will cost to run. You sign off before I build.
- 03
Build
Delivered in stages your team can test with real data, with error handling and logging from day one rather than bolted on later.
- 04
Handover
Documentation and a recorded walkthrough, so your team can run it and change it. Your accounts, your data, your system.
Questions
Questions people ask
Make or Zapier: which should we use?
Zapier is simpler and has the widest app library. Make is more visual and handles branching and data transformation for less money. If you already use one, I'll usually improve it rather than switch.
Can you fix automations someone else built?
Yes, and it's a large share of this work. I audit, document and repair first, and only rebuild what can't be made reliable.
When should we move off Zapier or Make?
When per-task costs start to hurt, or when workflows need real error handling and custom code. At that point n8n is often the better home.
Do we need to give you our passwords?
No. You invite me as a team member or collaborator in each tool and remove access whenever you like. Your accounts stay yours.
Contact