The Automation Playbook Automate the follow-through. Keep the relationship.
You do not lose customers to a weak pitch. You lose them in the gaps between one step and the next. This guide shows which handoffs to hand to a machine first, how to build them so they behave, and when to turn them off.
A dropped handoff does not make a sound.
Someone fills in your form on a Friday evening and nobody replies until Tuesday. A call ends with "I'll send that tomorrow" and tomorrow is full. A new customer pays and the welcome depends on whether you remember. Each one is a handoff from you to yourself, a few days later, and there is nobody to catch it. Together they cost more than any objection a prospect ever raised.
None of them is "save time".
Interest is perishable. A raised hand gets an answer even when you are in a meeting, asleep or away. This is not about volume. It is about never leaving a raised hand unanswered.
At five leads you remember everyone. At a thousand there is no best effort left, only what the system does. A workflow has no favourites and does not get tired.
A task created for you, a lead routed to the right list, a record tagged so the next step can find it. This is where handoffs actually drop.
Building a workflow forces you to write the steps down. Many people find the process they thought they had is not the one they run.
Take the bookkeeping out of the relationship and the attention goes into the careful reply and the call that needed making.
Written once, it runs for everyone who meets the trigger. Every improvement applies to everyone after, on evenings you spend doing something else.
Automation is the staff you do not have.
Not to talk for you. To remember for you. A way to make sure the things you already decided to do happen, every time, for every person, at the right moment.
Five parts, in order.
Six mechanisms by which a reliable machine beats a well-meaning person on a busy week, and the honest limit: it amplifies whatever process it runs, including a bad one.
Start with the handoffs that get dropped, automate only what already works by hand, begin with actions that touch only you, and write down what you will never automate.
Triggers, conditions and actions. Write it as sentences first, trigger on events that definitely happened, branch on facts you record, one job per action.
Duplicates, stale messages, testing on yourself, honouring opt-outs, reading what your workflows actually did, and when to switch one off.
Choose and design, before you switch it on, and the monthly review. Each line is a box you either can or cannot tick.
Nine ways automation turns from reliability into risk. All of them are failures of selection, design and attention, not of tooling.
Write down the handoffs that actually get dropped, not the messages you wish you sent. Rank them by how often they happen and what each one costs you, and start at the top.
Two or three plain sentences: when this happens, if that is true, do these things. If you cannot write it that way, it is not designed yet, and a visual editor will only hide the confusion.
A task for you, a tag, a reminder. These can be wrong without anyone outside knowing. Earn trust in your triggers before you point them at customers.
- You run a one-person business and want to scale it without hiring someone to send follow-ups.
- You know things fall through on your busy weeks and you want them to stop.
- You are willing to do a process by hand before you automate it.
- You want a method you can review yourself, not a pile of workflows nobody checks.
- You want to send more messages to more people and call it growth.
- You expect a machine to make someone feel known.
- You want a walkthrough of one specific tool, button by button.
- You want to automate complaints, bad news or negotiation.
Let it keep the promise. Keep the relationship yourself.
Most promises are not broken by a decision. They are broken by a Tuesday. A machine cannot make anyone feel known, and that part stays yours. What it can do is make sure every raised hand gets an answer and every promise reaches the day it was meant for. Never ask either one to do the other's job.
Luis Gonçalves
Twenty years in digital product development. Led the agile transformation at Nokia. Teaches at Porto Business School. Has spent the last decade working with founders across Saudi Arabia, Portugal, Brazil, and the broader emerging-market startup ecosystem.
He calls himself the Dark Entrepreneur because he believes the founder world is allergic to honesty. No success theater. No highlight reels. Just the real work that has to happen.