Building the Lead-to-Invoice Line
10 min read
This is the flagship workflow of the course: the full path from "someone filled out the website form" to "the invoice is out and the thank-you is scheduled." It chains three skills and four checkpoints, and once it runs, the Sunday-night quoting session from Lesson 1 stops existing. We build it for the HVAC company; every piece translates to a salon, a design studio, or a consultancy by swapping the nouns.
The skills on this line
Three workers, all on the skill rung, all reading the same Brain:
- First Responder: turns a raw inquiry into a qualified reply. Built from the inquiry-reply patterns in the toolbox, customized in an afternoon.
- Quote Builder: site-visit notes to a priced quote. If you took the skills course, you built this one already.
- Invoice Chaser: completed job to invoice draft, plus the polite-but-firm reminder ladder for slow payers. Adapt the finance analyst or build from the five-section template.
The runbook
WORKFLOW: Lead to Invoice
TRIGGER: Event. Inquiry arrives by form, email, or phone
(phone: office manager types a two-line note).
1. [Skill] First Responder drafts a reply: answers the
question, states the service-call fee, proposes
two visit windows. Flags anything outside our
service area or trades.
2. [You] CHECKPOINT (2 min). Send, adjust, or decline.
3. [You] Site visit happens. Tech voice-notes findings;
office manager pastes the transcript.
4. [Skill] Quote Builder drafts the quote from the notes
and the Brain's rate card. Missing rates surface
as [PRICE NEEDED], never as guesses.
5. [You] CHECKPOINT (5 min). Verify scope and numbers
against the notes. Send same day as the visit.
6. [Skill] If no reply in 5 business days, First Responder
drafts one follow-up. One. It restates the quote
expiry and asks a single question.
7. [You] CHECKPOINT (1 min). Send or let it go.
8. [You] Job completed and confirmed by the tech.
9. [Skill] Invoice Chaser drafts the invoice from the final
scope, plus a thank-you note for two weeks out.
10.[You] CHECKPOINT (2 min). Send invoice. Schedule the
thank-you.
DONE WHEN: Invoice sent and logged, thank-you scheduled,
or the lead is marked declined/no-reply.Why the seams are where they are
The checkpoints sit exactly where money or reputation changes hands: before the first impression (step 2), before a price commitment (step 5), before a nudge that could annoy (step 7), and before a bill (step 10). Between checkpoints, the skills run without supervision, because between checkpoints nothing leaves the building.
Notice step 4's [PRICE NEEDED] convention, carried straight from the skills course. On a workflow, it matters double: a guessed price in a standalone draft wastes a minute, but a guessed price flowing into step 5 on a rushed Friday becomes a quote you are honor-bound to eat. Loud gaps beat quiet guesses at every seam.
Notice also what the workflow refuses to do. One follow-up, not a drip campaign. A flag for out-of-area work instead of a creative attempt to serve it. Restraint is written into the runbook so it does not depend on anyone's mood.
The half-day build
Build order, tested at each stage:
- Confirm the Brain passes its spot-check (Chapter 2). The whole line reads from it.
- Build or adapt the three skills. Test each alone on one real past example: last month's actual inquiry, actual site notes, actual completed job.
- Run the full line once on a fake lead you write yourself, playing customer.
- Run it live on the next real inquiry, expecting to touch things up. First runs are rough; the runbook is what makes run five smooth.
Try it now
Do stage 2 for one skill today: pick whichever of the three your business bleeds the most time on, adapt it from the toolbox or your skills-course build, and run it on a real example from last month, with the Brain attached. Compare its draft with what you sent back then. Most people meet a draft that is 85% of theirs in 3% of the time, and the missing 15% is exactly what the checkpoints in this runbook exist to add.