The five processes every business should automate first
Lead response, invoicing, onboarding, reporting and data entry, ranked by payback.
AUTOMATION GUIDES
Automation guides for removing manual work
These guides show how to map a manual process, decide whether to automate it, choose between no-code and custom automation, and measure the hours returned. They cover lead routing, invoicing, onboarding, reporting and cross-system data flow.
Automation only pays when the process is understood first. Every guide starts with process mapping, then tooling, then the build.
The aim is fewer handoffs and fewer copy-paste steps, not more software.
Guides in this category
Published progressively in the journal. Ask for any of these and it moves up the queue.
How to map a process before you automate it
A one-page method for capturing steps, owners, systems and exceptions.
n8n vs Zapier vs Make: choosing an automation platform
Cost at volume, self-hosting, complexity ceilings and when to go custom.
Calculating automation ROI honestly
Hours, error cost, build cost and payback period in one simple model.
Connecting systems that were never designed to talk
API, webhook and sync patterns for legacy tools and spreadsheets.
Why automations break, and how to make them fail safely
Retries, alerting, idempotency and exception queues.
Checklists
Process automation checklist
- Every step, owner and system is written down
- Exceptions and their frequency are listed
- Volume per week is measured
- Required approvals are identified
- Success is defined as a number, not a feeling
- An owner is named for monitoring after launch
Integration readiness checklist
- Each system has an API or export path
- Credentials and access are available
- A single source of truth is agreed per field
- Duplicate and conflict rules are defined
- Error alerting has a destination
Comparisons
- n8n vs Zapier for growing teams (planned)
- No-code automation vs custom scripts (planned)
- Point-to-point integrations vs a central automation layer (planned)
Automation Guides FAQs
Which process should we automate first?
+
The one you repeat most with the fewest exceptions. Lead response and invoice or document handling are the most common first wins because volume is high and rules are clear.
Should we use n8n, Zapier or a custom build?
+
Zapier suits simple, low-volume links between popular tools. n8n suits complex logic, self-hosting and higher volume at lower cost. Custom code wins when the workflow is core to the business or needs logic these platforms cannot express.
How much does business process automation cost?
+
Most single-process automations run $3,000 - $10,000 and take 2 - 8 weeks including mapping, testing and handover.
What happens when an automation fails?
+
Well-built automations retry, log the failure, alert an owner and push the item to an exception queue for a human, rather than silently dropping work.