The automation library

This is the idea machine, and it is the chapter to raid rather than read. What follows is a library of automations organised by the part of the business they serve, each entry in the same compact shape: the trigger, what happens, and what it saves. None of them is exotic. Every one is machinery that large companies have run for years, now available at your scale, and most are an afternoon's build once the foundations from this series exist. Take what stings, leave the rest, and remember chapter four's rule: the best candidates are the ones already on your own week's list.

A note on reading the entries: what it saves is measured in the honest currencies, hours of ferrying, leads that stopped leaking, mistakes that stopped happening, and the quiet one, things no longer carried in anyone's head.

Trigger: any enquiry arrives, form, chat, message.

What happens: the enquirer receives a warm, specific reply within the minute, and the owner gets the alert.

Saves: the first and biggest leak, because the business that answers first wins, and this answers first every single time, at midnight, on your busiest day.

Trigger: a call rings out.

What happens: the caller instantly receives a text, sorry we missed you, with a callback promise or a booking link, and the missed call becomes a logged lead with a task.

Saves: the hottest, most perishable lead there is, the one that was literally calling you.

Trigger: a business enquires through the website.

What happens: the system quietly looks up who they are, gathers what is publicly knowable about their situation, assembles a short briefing, and drafts the reply, so that what lands in your drafts folder is not a blank page but a prepared, personalised response with the homework attached, waiting for one human review and one click.

Saves: the half hour of research per serious lead, and something money struggles to buy, the experience on the other end of replying to an enquiry within the hour with an answer that clearly understood them. This one is a signature, and chapter nine takes it apart bolt by bolt.

Trigger: a quote is sent.

What happens: the sequence from this series' CRM book arms itself, the gentle touches, spaced and decaying, stopping the instant the client replies.

Saves: the second great leak, the quote that went quiet, which is where most businesses lose more revenue than anywhere else.

Trigger: a new lead sits untouched past a set number of hours.

What happens: the owner is nudged, and past a second threshold, escalated.

Saves: the lead lost not to a decision but to a busy Tuesday, which is most of them.

Trigger: a deal is marked won.

What happens: the invoice drafts itself, the onboarding email sends, the job appears wherever jobs are managed, the file structure is created, and the team is told.

Saves: the fifteen fiddly minutes after every yes, and the occasional catastrophe of a won client nobody actually onboarded.

Trigger: a deal is marked lost.

What happens: the why-lost reason is captured, and quarterly, the patterns are summarised and sent to the owner.

Saves: losing the same deals the same way forever and calling it luck.

Trigger: a new article is published.

What happens: drafts are generated for the social posts, the newsletter mention, and the repurposed formats, queued for human review, never auto-published.

Saves: the multiplication work that makes content sustainable, and it is the spine of this series' content book.

Trigger: a job completes or an order is delivered.

What happens: the review request goes out at the moment satisfaction peaks, with the direct link; a good review triggers a thank-you, a poor one alerts a human immediately, before it becomes public history.

Saves: the steady reputation-building that never happens when it depends on remembering, and the occasional saved relationship.

Trigger: someone comments a keyword on a social post.

What happens: they receive the promised link by direct message, and arrive tagged in the system as a lead from that post.

Saves: the gap between social attention and owned ground, the exact gap where social effort usually evaporates.

Trigger: someone joins the list, downloads the guide, subscribes.

What happens: a short, warm sequence introduces the business over the following days, ending with an easy next step.

Saves: the awkward silence after someone raises their hand, which is where most captured interest quietly expires.

Trigger: a good client's silence passes its honest threshold, months for some businesses, a year for others.

What happens: the check-in that references the real history, drafted for human review.

Saves: the third great leak, the client you already won, drifting back to the open market.

Trigger: an invoice passes due.

What happens: the polite reminder, then the firmer one, then the escalation to a human for the conversation automations must never have.

Saves: the most universally hated chore in business, and real cash-flow days, because chased invoices get paid weeks earlier than remembered ones.

Trigger: a booking approaches.

What happens: the reminder lands the day before, with reschedule handling built in.

Saves: no-shows, which for appointment businesses is not admin but revenue, directly.

Trigger: a deal reaches a stage, or a form completes.

What happens: the proposal, agreement or welcome pack assembles itself from the record's details into the clean template.

Saves: the retyping, and the retyping's errors, the wrong name in the contract that a client never quite forgets.

Trigger: a new client, or a new staff member, is confirmed.

What happens: the full checklist of tasks spawns, assigned and dated, so nothing depends on someone remembering the eleven steps.

Saves: the wildly uneven first impressions that happen when onboarding lives in heads.

Trigger: information arrives anywhere it arrives, the emailed PDF, the filled form, the uploaded document.

What happens: the details are extracted and land where they belong, the job system, the records, the folder structure.

Saves: the purest form of the ferrying tax, a human retyping what a machine already held.

Trigger: anything with a date approaches it, the domain, the insurance, the certification, the subscription worth reviewing.

What happens: the right human is told with time to act.

Saves: the small category of misses that are cheap to prevent and mortifying to explain.

Trigger: a message arrives in the shared inbox.

What happens: it is read, classified, and routed, the sales question to sales, the support issue to support, the invoice query to accounts, each with its context attached.

Saves: the triage hour, and the message that sat three days in the wrong queue.

Trigger: a common question arrives, the hours, the pricing structure, the how-do-I.

What happens: the answer drafts itself from the knowledge base for a human to approve, or, where confidence is genuinely high and stakes genuinely low, sends, clearly signed as automated help with a human one reply away.

Saves: the repetition, while the gating saves the reputation.

Trigger: work completes.

What happens: the short feedback ask goes out; scores flow to the dashboard; anything below the bar alerts a human the same day.

Saves: finding out about unhappiness from a public review instead of a private message, which is the expensive way.

Trigger: seven oclock, every morning.

What happens: one message assembles itself, yesterday's leads and their sources, today's follow-ups due, anything overdue, anything that failed overnight.

Saves: the twenty minutes of checking five systems, and the surprises that used to arrive at Friday's end instead of Tuesday's start.

Trigger: Friday afternoon.

What happens: the week's movement, the board's honest total, and the deals with no next step, summarised to the owner.

Saves: walking into Monday's review cold, and the slow drift of a board nobody is watching.

Trigger: the numbers that should agree, the system's takings and the bank's, the CRM's won deals and the ledger's invoices, are compared on schedule.

What happens: matches pass silently; mismatches get flagged while they are one line, not one quarter.

Saves: the archaeology, as the e-commerce book in this series calls it.

Trigger: a number moves in a way it should not, enquiries suddenly zero for a day, a cost suddenly double.

What happens: a human is told the same day.

Saves: the silent fortnight, the broken form discovered as a mysteriously quiet month, which this series keeps returning to because it keeps happening to businesses without this one automation.

Thirty-odd entries, and the honest patterns worth noticing before you raid it. Almost every entry is when this happens, do that, chapter two's plain anatomy, no magic anywhere. The highest-return items cluster where this series keeps pointing: the speed of the first response, the persistence of the follow-up, and the watching of the numbers. Nearly everything customer-facing drafts for human approval rather than firing blind, a line chapter six turns into doctrine. And nothing here requires the everything-machine; each entry stands alone, which is exactly what lets chapter four's quick-win ordering work.

The menu is served. The next chapter is how to run the kitchen: the daily rhythm, the approval gates, and the habits that keep several dozen of these running without anyone holding their breath.