Founders ask us 'what should we automate?' expecting a tool list. The honest answer is that the tools barely matter — the sequence does. These are the five workflows we deploy first for almost every service business, in the order that makes each one compound on the last.
1. Speed-to-lead: answer in minutes, not days
When someone fills your contact form, the clock starts. Response within five minutes versus thirty makes an enormous difference in whether that lead ever becomes a conversation — and most service businesses respond in hours or days, because the form goes to an inbox and the inbox goes to 'when I get to it.'
The first automation is always this: form submission → contact created in the CRM with source and context → instant acknowledgment to the lead that sets a real expectation → notification to a human only if the lead is qualified enough to warrant one. No AI cleverness required yet. Just the guarantee that no lead ever sits unanswered overnight again.
This goes first because it pays immediately and visibly — usually within the first week there's a booked call that would previously have gone cold. That win buys patience for everything else.
2. Follow-up sequences: the money is in the third touch
Most service businesses send one reply, maybe two, then stop. Prospects aren't rejecting you when they go quiet — they're busy running the business that made them need you in the first place. The follow-up that lands three days later, referencing what they originally asked about, is the one that converts.
Once workflow #1 exists, sequences are cheap to add: the lead is already in the CRM with context, so a three-to-five-touch sequence over two weeks costs nothing to run. Write the touches like a person, space them honestly, and always give an easy out. The out matters — it keeps the list clean and keeps you out of spam folders.
The compounding trick: every reply a sequence gets feeds workflow #3.
3. Inbox triage: stop letting email drive your day
The founder inbox is where operations go to hide. Client questions, supplier invoices, warm leads, newsletters, and spam all arrive in one stream, and the founder becomes a human router — often the most expensive router the business has.
Triage automation classifies before you read: this is a client with an active project, this is a new lead, this is a bill, this is noise. Each class gets a lane — some get auto-drafted replies for approval, some get filed to the project, some get archived on sight. The founder reads a briefing, not a backlog.
This one goes third rather than first because it needs the CRM foundation to classify against. With workflows #1 and #2 live, the system already knows who your leads and clients are — triage inherits that context for free.
4. Project status: kill the 'quick update?' email
Every 'can I get a quick update?' email from a client is a small failure of the operations layer — it means the client's uncertainty outran your communication. Multiply it across every active project and you get hours per week of interruptions, all reactive, all urgent-feeling.
The automation: project milestones live in one system, and status flows outward on a schedule — a short weekly note per active project, generated from what actually moved, reviewed by a human before it sends. Clients stop asking because they stop wondering.
The internal version matters just as much: anything overdue, unowned, or stalled surfaces daily to the team before the client notices. Risks age terribly. Surfacing them three days earlier is often the whole difference between a calm correction and an apology call.
5. Getting paid: invoices that chase themselves
Unpaid invoices are the least fun thing to chase and the most expensive thing to forget. Founders defer the awkward reminder email for days — meanwhile cash flow, the thing that actually kills small businesses, tightens quietly.
The automation is simple and slightly ruthless: invoice issued → polite reminder before the due date → firmer reminder after → escalation to a human at the threshold where a relationship conversation is needed. The sequence never feels awkward because the sequence doesn't feel anything. Founders consistently report this one pays for the entire system.
It goes last not because it matters least but because by this point the plumbing exists: contacts, projects, and communication history all live in connected systems, so 'who owes what and how overdue is it' is a query, not an archaeology project.
The order is the strategy
Notice what the sequence does: each workflow makes the next one cheaper to build. Lead capture populates the CRM. Sequences enrich it. Triage classifies against it. Status reporting reads from the project layer. Collections reads from everything.
This is why 'we bought an AI tool for X' so often disappoints — a point solution with no shared foundation automates one task while the operational context that would make it compound doesn't exist.
Start with speed-to-lead. Prove it in a week. Then go down the list in order. By workflow five you won't have five automations — you'll have an operating system.