What a Lead to Invoice Workflow Is
A lead to invoice workflow (sometimes called lead-to-cash) is the complete path a single piece of client work travels through your business: from the moment a prospect first appears, through qualification, closing, delivery, and time tracking, to the invoice going out and the payment landing. Eight stages, one thread.
The defining idea is that it's one record making the whole journey. The contact captured in stage 1 is the same contact the deal attaches to in stage 3, the same client the project belongs to in stage 4, the same account the invoice bills in stage 7. When each stage instead creates its own copy—a row in the outreach spreadsheet, a card in the CRM, a project in the PM tool, a customer in the invoicing app—you don't have a workflow. You have four unrelated databases that happen to mention the same company name, spelled three different ways.
Workflow vs system
This guide is about running one deal through the eight stages cleanly. Its companion, the agency operations system guide, is about building the five-layer machine those deals run through. Read this one to fix a leaky handoff this week; read that one to redesign the plumbing.
The workflow applies to any client-service business—agency, consultancy, freelancer, studio. The stages don't change with size; only the number of people touching each stage does.
Where the Workflow Breaks: The Four Dangerous Handoffs
Ask where a deal died and the answer is almost never "we designed a bad homepage." It's a seam between stages, where the record changed hands—or changed tools—and something fell out. Four handoffs cause most of the damage:
Capture → qualify: the lead that never entered the pipeline
The prospect replied on LinkedIn, or in a Telegram group, or on Upwork—anywhere but the CRM. It stayed a chat message, got buried by Thursday, and no one ever qualified it. The most expensive leads are the ones you never knew you lost.
Close → project: the context that stayed in the seller's head
The deal closes; delivery hears about it in a kickoff scramble. The scope, the two revision rounds promised on a call, the "we'll throw in the landing page"—none of it travels. The team re-discovers the promises when the client enforces them, unbilled.
Deliver → track time: hours attached to nothing
Time gets logged—in a separate timer app, against a project name typed from memory, with no link to tasks or budget. The data exists but proves nothing and bills nothing. When the project overruns, nobody can say which part overran.
Track time → invoice: the month-end reconstruction
Invoicing means exporting timesheets, cross-referencing the contract, and retyping line items into the invoicing tool. It's slow, so it happens monthly; it's manual, so it drops line items. Every dropped line item is delivered work you gave away.
Each broken handoff has the same root cause: the record doesn't flow, so a human re-creates it—late, partially, or not at all. The checklist in the next two sections exists to guard exactly these seams.
The 8 Stages of the Lead to Invoice Workflow
Capture
Every prospect—from forms, referrals, cold outreach, platform bids, DMs—becomes a record with a source the day it appears. Multi-channel outreach tracking is what makes this stage complete instead of "whatever landed in the CRM."
Qualify
Decide fast whether this is worth pursuing: budget, fit, timeline, red flags. Qualified leads become deals with a value and a stage; disqualified ones get closed with a reason—not left to rot as "maybe."
Close
Proposal, follow-up cadence, negotiation, signature. The deal record accumulates everything agreed—scope, price, payment terms, promises made on calls—because whatever isn't written here gets re-litigated later.
Project
The won deal converts into a project—same client record, scope attached, budget carried over, tasks and milestones created with estimates. This is the handoff from sales to delivery, and it should take hours, not weeks.
Deliver
The work itself: tasks move across the board, milestones get hit, the client sees progress on a fixed cadence, and out-of-scope requests get caught at the door instead of absorbed silently.
Track time
Hours land on tasks daily, flagged billable or not, burning visibly against estimates. This stage runs in parallel with delivery—it's listed separately because it's the stage teams skip, and it's the one that makes stages 7 and 8 automatic.
Invoice
Within 48 hours of a milestone or period end, an invoice generates from tracked time and completed milestones—line items from records, not memory—and goes out with clear terms.
Get paid
Payment tracked against the invoice, reminders firing automatically on a schedule, and—once the money lands—the project closed out with a margin number that feeds the next pricing decision.
Stages 1–3 are the sales half; stages 4–8 are the delivery-and-money half. The seam between 3 and 4 is where the two halves of most businesses stop talking to each other—which is why the checklist below treats every stage's exit criteria as a contract with the next stage.
Stage-by-Stage Checklist (Copy This)
One row per stage: who owns it, what triggers it, and the exit criteria that must be true before the record moves on. Copy it, replace the owner column with names, and pin it where the team works. A stage without a named owner is a stage that will silently stop happening.
| Stage | Owner | Trigger | Exit criteria (all true before next stage) |
|---|---|---|---|
| 1. Capture | Whoever made the touch | Any inbound or outbound contact with a prospect | Contact record exists with source and channel; logged same day; no duplicates |
| 2. Qualify | Sales lead | New captured lead, within 2 business days | Budget, fit, and timeline assessed; deal created with value and stage, or closed with a disqualification reason |
| 3. Close | Deal owner | Qualified deal enters proposal stage | Signed agreement; scope, price, payment terms, and all verbal promises written on the deal record; outcome + reason recorded |
| 4. Project | PM / delivery lead | Deal marked won — within 48 hours | Project created from the deal (not blank); scope attached; tasks estimated; milestones dated; kickoff scheduled |
| 5. Deliver | PM | Kickoff complete | Milestones hit and accepted; weekly status sent; out-of-scope requests logged as change orders, not absorbed |
| 6. Track time | Everyone delivering | Daily, while stage 5 runs | All hours on tasks (not just projects); billable flagged at entry; overruns flagged at 80% of estimate |
| 7. Invoice | PM or ops | Milestone accepted or billing period ends — within 48 hours | Invoice generated from tracked time / milestones; every line item traceable to a record; terms and due date on the invoice |
| 8. Get paid | Ops / bookkeeper | Invoice sent | Reminders automated (day 7/14/21 past due); payment matched to invoice; project closed with actual margin recorded |
The two 48-hour triggers (stages 4 and 7) are the load-bearing numbers. They convert the two most dangerous handoffs—close→project and time→invoice—from "when someone gets to it" into a deadline someone can miss visibly.
Worked Example: A $12,000 Deal Through All 8 Stages
A four-person design studio, hourly cost of delivery around $60/person, selling a marketing site rebuild to a B2B software company called Northwind. Here's the deal's actual itinerary:
Stage 1 — Capture (Day 0)
Northwind's head of marketing replies to a cold email. A contact record is created the same day: source "cold email — March campaign," channel, and the thread attached. Total effort: two minutes. Those two minutes are what later makes revenue attributable to the campaign that earned it.
Stage 2 — Qualify (Day 2)
Discovery call. Budget "around $10–15k," decision maker on the call, timeline eight weeks. Deal created: value $12,000, stage "In Discussion." A second inbound that week—a $900 logo tweak with a red-flag client—gets closed as "Disqualified – no budget" instead of haunting the pipeline for a month.
Stage 3 — Close (Days 5–16)
Proposal sent Day 5: six page templates, CMS setup, two revision rounds, $12,000 fixed, 40% deposit, Net 15. Silence—then a follow-up on Day 9 and another on Day 13 revive it. On the closing call Northwind asks for a blog migration "if it's not a big deal"; it's written on the deal as excluded, quoted separately at $1,800. Signed Day 16. Everything agreed lives on the deal record.
Stage 4 — Project (Day 17)
Within the 48-hour window, the PM converts the deal into a project. Client, scope, exclusions, and budget arrive attached. Tasks created with estimates—wireframes 16h, design 40h, build 60h, CMS 24h, QA 12h: 152 hours planned against a $12,000 price (about $79/hour expected). Deposit invoice for $4,800 goes out the same day—the first cash arrives before the first pixel.
Stages 5+6 — Deliver and track time (Weeks 3–9)
Work proceeds; hours land on tasks daily. Week 5: the design task hits 80% of its 40-hour estimate with one template still unstarted—the flag fires. The PM finds the cause (a third homepage concept, requested informally) and, because the deal record says two revision rounds, sends a change order: $1,400, approved in writing. In week 7 the blog migration comes back—now a quoted $1,800 add-on, not a favor. Weekly status reports keep Northwind approving milestones on schedule.
Stage 7 — Invoice (Days 38 and 66)
Milestone invoice at design approval (30%, $3,600) goes out the day after sign-off. Final invoice on launch: $3,600 balance + $1,400 change order + $1,800 migration = $6,800, every line item traceable to an approved record. Nothing reconstructed, nothing forgotten.
Stage 8 — Get paid (Day 74)
The final invoice drifts past Net 15; the day-7 automatic reminder shakes it loose without an awkward call. Project closes at $15,200 collected against 176 tracked hours (~$60/hour cost ≈ $10,560): roughly a 31% delivery margin, $86/hour effective rate. The post-mortem notes design was underestimated by 25%—the next proposal prices it accordingly.
Count what the workflow earned versus the leaky version of the same deal: the third concept billed instead of absorbed (+$1,400), the migration quoted instead of gifted (+$1,800), the deposit collected three weeks earlier, and a real margin number at the end. Same client, same work—roughly $3,200 and several weeks of cash flow separated the two outcomes.
Want to run this math on your own last project? The project profitability calculator computes delivery margin and effective rate from your revenue, hours, and costs.
Operating Rules That Keep the Record Flowing
The checklist tells you what each stage must produce. These five rules keep the whole chain honest between checklist reviews:
- 1.One record, extended—never copied. The deal becomes the project becomes the invoice by conversion and linking, not by retyping. Every manual copy is a future discrepancy with your client's name on it.
- 2.If it isn't logged, it didn't happen. Calls, promises, scope changes, approvals—on the record, same day. The workflow's memory has to outlive everyone's inbox.
- 3.Handoffs have deadlines, not vibes. Lead qualified within 2 days, project created within 48 hours of winning, invoice out within 48 hours of the milestone. Deadlines make dropped handoffs visible while they're still cheap.
- 4.Money events attach to work events. Deposits attach to kickoff, invoices to milestones and tracked time, reminders to due dates. When billing is coupled to delivery, getting paid stops being a separate project.
- 5.Close the loop. Every finished deal reports its margin and its estimate error back to stages 2 and 3. A workflow that never updates your pricing is a conveyor belt, not a system.
If you're an agency running many of these threads at once, the scaling patterns—who owns which stage as the team grows, how the stages map onto your tool stack—are covered on the Corcava for agencies page and in the agency operations system guide.
One Record, One System
You can run this workflow across separate tools—a CRM, a project tracker, a timer, an invoicing app—if you enforce every handoff rule by hand. Some teams manage it. Most don't, because the workflow's failure mode is precisely the seams between tools, and willpower is a bad patch for plumbing.
The alternative is running all eight stages on one client record in one system. In Corcava, the captured lead becomes the deal, the won deal converts to the project, hours land on the project's tasks, and the invoice generates from those hours—the handoffs in this guide are what the software does by default. The CRM with invoicing page shows the two ends of the chain—stage 1 and stage 7—working from the same record.
Run your lead to invoice workflow in Corcava
Capture, qualify, close, deliver, track, invoice, get paid—one record the whole way. Set up the 8 stages from this guide in an afternoon.
No credit card required