
Mission 6 of 8
Deliver client work from a template, not from scratch every time.
If the fifth client build takes as long as the first, you have a job with invoices. You'll build the delivery playbook for the lead-response package: kickoff, template, staging test, handover and SOPs.
What you'll do
Get access, tone, rules and the go-live date agreed in one call, so the build never waits on a question.
Build the lead-response workflow in n8n with an LLM, and replay 20 real past enquiries before anything goes live.
Record the handover, set up monitoring, and write the SOPs that let someone else deliver client six.
- A reusable build template with one switch from staging to live
- A rules file that works as prompt, test cases and contract disclaimer
- Monitoring that tells you before the client
- n8n running somewhere. If it isn't: your own Zapier with n8n for the basics, self-host n8n on a VPS for a client-grade install
- An Anthropic API key (or another LLM provider; the shape is the same) and Python 3 for the replay script
- Claude Code installed (Claude Code in your first hour) for the custom parsing and anything the nodes can't do
- A signed client, or a pretend one: use your own inbox and a free HubSpot account to build the template before you have a client
Your progress0/7
- 01The kickoff: one call, everything agreed10 min
- 02The build template: n8n, an LLM, and whatever the client already uses12 min
- 03The lead-response workflow, node by node20 min
- 04The brain: rules.md, the replay script, and Claude Code for the custom bits15 min
- 05Staging with the client, then go live and watch the first ten10 min
- 06The runbook and the handover video8 min
- 07Monitoring, alerts and the SOPs that let someone else deliver it15 min
The kickoff: one call, everything agreed
Leave the kickoff with access requested, rules written and a go-live date, so the build never waits on a question.
Delivery projects go late for one reason: waiting. Waiting for CRM access, waiting for someone to say what the tone should be, waiting to find out whether replies should go out at 2am.
The kickoff call exists to ask every one of those questions in thirty minutes and write the answers down.
Send the checklist below as the agenda the day before the call.
Kickoff checklistKICKOFF CHECKLIST (send as the agenda, tick on the call, email the ticked copy) BEFORE THE CALL [ ] Agreement signed, 50% invoice paid (no kickoff without both) [ ] Client folder created: /clients/[name]/ with runbook.md, access.md, rules.md, tests/, handover/ [ ] Shared password vault created for the client (Bitwarden/1Password) [ ] Staging n8n workflow duplicated from the template, renamed ON THE CALL (30 min) [ ] Named client contact + their response commitment (2 working days) [ ] Enquiry sources confirmed (list each: form tool, inbox, portal, WhatsApp) [ ] Calendar: which one, whose, working hours, buffer between bookings [ ] CRM: which one, which pipeline/stage new enquiries land in, required fields [ ] Tone: who writes the best replies today; they send 20 past enquiries AND the replies they'd have liked to send (not the ones they sent) [ ] Rules: the "never" list from the sales call, read back and confirmed [ ] Out-of-hours behaviour: reply at 2am, or hold until 7am? (ask; it varies) [ ] Hand-off: what gets escalated to a human and to whom (complaints, existing customers, anything with a price question) [ ] Daily digest: who receives it, what time [ ] Go-live target date written down, with the staging test date before it AFTER THE CALL (same day) [ ] Access requests sent, one email, every item listed, with a deadline [ ] rules.md written from the call and sent for a one-line "approved" [ ] Week-2 build block and week-3 test block in your calendarTick it on the call, and email the ticked copy afterwards.
Three items that matter more than they look
The 20 past enquiries and the replies they'd have liked to sendNot the replies they sent (those were rushed); the ones they'd have sent with time. That's your tone data and your test set in one.
The 'never' rules, read backYou collected them on the sales call; now they get confirmed and they become rules.md, which the client approves in writing. When the system later declines to quote a rent, the client remembers approving that.
Out-of-hours behaviourSome owners love a 2am reply; some think it looks automated. Ask.
After the call
Send one email with every access item listed and a deadline. Access is the thing that slips.
Chase it kindly on the deadline, and if it slips a week, the go-live slips a week and you say so in writing. Your timeline clause (mission 3) makes that fair.