Automate the follow-through,
not the relationship.
A free playbook for founders. Automate the follow-through, not the relationship: what to hand to a machine first, how to build it so it behaves, and how to know when to switch it off.
// 29 PAGES · FIVE PARTS · THREE CHECKLISTS · FREE
Seven things to know about automation.
Each is a mechanism you can plan around, and the guide is plain about the limit.
It closes the gaps where intent leaks away
Interest is perishable. The moment someone raises their hand is the moment they are most willing to hear from you, and that willingness decays with every hour of silence.
It makes the hundredth person get the same treatment as the first
When you have five leads, you remember every one of them and you follow up carefully. When you have fifty, the careful follow-up becomes a best effort, and the best effort quietly favours whoever was most recent or most memorable.
It moves the internal work, not just the external messages
Most people picture automation as emails going out. The more valuable half is invisible to the customer: a task created for the right person, an owner assigned to a new lead, a record tagged so the next step can find it, a teammate notified that something needs their judgment.
It turns a process into something you can see
Most small companies run on processes that exist only in someone's head. "When a lead comes in, I usually check their site, then send them the overview, then follow up in a few days if I haven't heard back." That is a process, but it cannot be examined, improved or handed over, because it is not written down.
It frees attention for the parts that need a human
The goal is not to remove you from the relationship but from the bookkeeping around it. When reminders, assignments and routine confirmations happen on their own, the attention you spent remembering them goes into the conversation itself: the careful reply, the call that needed making, the judgment about fit.
It compounds with every new person who enters
A well-built workflow is written once and runs for every contact who meets its trigger, for as long as it stays switched on.
And now the honest limit
Automation amplifies whatever process it runs, including a bad one. If your follow-up is clumsy by hand, a workflow will make it clumsy at scale and on a schedule.
Five parts, and a last page.
Parts one to five are the thinking and the doing, worth your time even if you never touch a piece of software. The last pages show how to run it in one place.
The Honest Case
Decide What to Automate Before You Build Anything
Build It Simply: Triggers, Conditions, Actions
Guardrails, Review and the Off Switch
The checklists and the mistakes
Do it all in one place
Nine mistakes, all of them avoidable.
None is about talent. They are failures of method, which is good news, because method is something you can set up in advance.
Automating a process that has never worked by hand
You are not automating a process, you are automating a guess, and your customers find its flaws for you.
Automating the relationship instead of the follow-through
Complaints, bad news, negotiation and the first serious conversation belong to a person. A template in those moments reads as indifference.
Starting with outward messages
Internal tasks, assignments and notifications are cheap to get wrong. Customer messages are not. Earn trust in your triggers before you point them at people outside.
Designing the entry and forgetting the exit
Without a goal that removes people, your automation keeps chasing someone who already said yes.
Allowing silent re-entry
The same person enrolled twice receives everything twice, and learns exactly how much attention is being paid.
Branching on data you do not actually have
A condition on a half-empty field quietly sends half your contacts down the wrong path.
Building one long workflow that does everything
Long chains are hard to read, hard to change and easy to break. Several short workflows that hand off to each other are easier to trust.
Measuring that it ran instead of whether it worked
A perfectly executing workflow that does not move the outcome is overhead with a progress bar.
Never switching anything off
Workflows outlive their processes, their owners and their purpose, and keep talking to people on your behalf long after anyone remembers why.
Twenty-nine pages.
Yours in one click.
Five parts, three checklists and the nine mistakes. One email with the link, no drip sequence, and we do not sell the list.