⚙️ Business & freelancing · Guide
Automations For One Person
Five repeated jobs, handed over carefully
Automations For One Person
Five repeated jobs, handed over carefully
Your name
A4 · this is a layout preview in the “Field Notes” design. When you generate, the studio writes every chapter in full, paints the cover and chapter art, and composes a downloadable A4 PDF with your name, bio and store link on it.
Automation sold to solo businesses tends to be described as freeing up your time. In practice it either removes a small weekly chore or it creates a new one, and which of the two depends almost entirely on how the job was defined before it was built. This guide takes five common jobs and hands each one over properly.
What's inside
- 1Write the job down before you automate itYou describe one repeated task as a sequence of steps with its trigger, its inputs and its failure cases, exactly as you would to a new assistant. After this chapter you can tell whether the job is ready to be handed over or still too vague.
- 2The five jobs worth doing firstYou look at invoice reminders, file delivery after a sale, booking confirmations, lead capture into one list, and the weekly backup, and rank them by how often they bite. By the end you have chosen the one to build this week.
- 3Built-in feature, connector, or scriptYou decide between the automation already inside a tool you pay for, a connector service that joins two tools, and a small script you maintain yourself. The chapter weighs each against cost, fragility and how much of it you can repair alone.
- 4Build one, end to endYou build the sale-to-delivery automation completely, including the receipt, the file, the folder and the note in your records, and run it with test data. After this chapter you have one job you no longer do by hand.
- 5Assume it will breakYou add error alerts, a log you can read, and a manual fallback for each automation, because silent failure is worse than no automation at all. By the end you will hear about a problem before a customer does.
- 6The quarterly reviewYou check each automation against what the business now does, switch off the ones that no longer match, and note the ones costing more in subscriptions than they save. The chapter ends with a short record to keep beside your accounts.
A sample from chapter one
Automate a job you can already do by hand
The jobs that automate well are the ones you have done enough times to be bored by. You know the trigger, you know the steps, and you know what you do when something arrives in the wrong format. That knowledge is the specification. Without it you are not automating a process, you are guessing at one, and the guess will be exposed by the first awkward customer.
Before building anything, write the job out as a new assistant would need it: what starts it, what information it needs, what happens step by step, and what to do when a step fails. If you cannot write that in ten lines, the job is not yet understood well enough to hand over. Sorting that out often improves the process even if you never build the automation.
- Write the trigger, the inputs, the steps and the failure cases on one page before opening any tool.
- Start with the job that already causes chasing emails, usually invoice reminders or file delivery.
- Use the automation built into a tool you already pay for before adding a connector subscription.
- Send yourself an alert on failure, and keep a manual way to complete the job while it is broken.
Key takeaways
- An automation is only as good as the description of the job it replaces.
- Silent failure costs more than no automation, so build the alert at the same time as the workflow.
- Review what you have built each quarter, because a business changes faster than its scripts do.
The studio writes every chapter from this outline, paints the art and hands you a PDF you can sell the same afternoon.
Start free