· 8 min read

Operations & Systems

Quote to Cash: The 7-Step Process That Ensures Nothing Drops

From first lead to final payment: 7 documented steps, the failure mode at each, and the checklist that prevents revenue from falling through the cracks.

Quote to Cash: The 7-Step Process That Ensures Nothing Drops

Most freelancers lose more revenue to process failures than to price objections. A lead that doesn’t get a follow-up within 24 hours. A proposal that never got a Day 7 follow-up because you forgot. A project that closed 3 weeks ago and still hasn’t been invoiced because you’ve been busy with the next thing. These aren’t client problems, they’re system problems. And system problems have system solutions.

The quote-to-cash process is the documented sequence from the moment a lead enters your world to the moment the final payment clears. Seven steps. Each one with a trigger, specific actions, a defined output, and a handoff to the next step. When every step is documented and the failure modes at each are known, the gaps close.

A documented quote-to-cash process doesn’t make sales automatic. It makes sure nothing falls through the floor between steps, where most of the silent revenue loss happens.

Step 1: Lead captured in CRM

Trigger: A lead fills out your contact form, emails you for the first time, or a referral reaches out via any channel.

Actions:

  1. Add the lead to your CRM immediately, name, email, company, how they found you, what they’re looking for
  2. Set the deal stage to “New Lead”
  3. Send an automated or manual confirmation within 24 hours: “Got your message, I’ll review and follow up by [specific day]”
  4. Create a follow-up task: “Respond to [lead name], due [tomorrow]”

Output: Lead is in CRM with a confirmation sent and a follow-up task scheduled.

Failure mode: No same-day acknowledgment. A lead who hears nothing for 48 hours has already contacted 2 other people. Your first message sets the tone for what it’s like to work with you. Slow response signals slow work.

The fix: Automate the confirmation. A Typeform or Tally form submits → Zapier → confirmation email auto-sends in 60 seconds. You still do the personal follow-up, but the lead knows immediately that their message was received.

Step 2: Discovery call scheduled and held

Trigger: You’ve reviewed the lead’s information and decided to proceed. Or, more accurately: you haven’t decided to decline.

Actions:

  1. Send a scheduling link (Calendly) with the message: “Happy to connect, here’s my scheduling link for a 45-minute discovery call”
  2. Include 3–5 pre-call questionnaire questions (budget, timeline, what they need, what they’ve tried)
  3. Review their questionnaire answers before the call
  4. Hold the discovery call, run the structured discovery framework: understand the problem, confirm budget range, confirm timeline, identify decision makers, assess fit

Output: Discovery call completed. You know whether to proceed with a proposal. Deal stage updated to “Discovery Complete” or “No Fit” (if not proceeding).

Failure mode: The call happens without pre-call information. You spend the first 15 minutes of a 45-minute call gathering basic facts you could have had in advance. The call covers less ground, and you write a less targeted proposal.

The fix: Make the pre-call questionnaire required, build it into your Calendly booking flow. No form, no booking. 95% of leads complete it; the 5% who don’t are often the ones least likely to close.

Step 3: Proposal drafted and sent

Trigger: Discovery call ended with mutual interest and verbal agreement that a proposal should proceed.

Actions:

  1. Draft proposal within 2–5 days of the discovery call (not immediately, let the conversation settle; not 2 weeks later, the urgency fades)
  2. Use the proposal template (from your Notion library), 3 pages maximum: problem statement, proposed solution + scope, investment and terms
  3. Review the proposal aloud before sending, a rough sentence is always a rough sentence
  4. Send with subject: “Proposal: [Project Name], [Your Name]”
  5. Update CRM to “Proposal Sent”
  6. Set Day 3 and Day 7 follow-up reminders in your calendar or automation

Output: Proposal sent, CRM updated, follow-up reminders set.

Failure mode: The proposal goes out without a follow-up system. 48 hours after sending, you’re waiting to hear back. Day 5: still nothing. Day 10: the prospect has moved on and you’ve missed the window. You had a warm lead and lost it to silence.

The fix: The follow-up sequence is part of the proposal process, not an afterthought. When you update the CRM to “Proposal Sent,” the Day 3 and Day 7 reminders fire automatically (or you add them to the calendar manually at that moment, not later). A Day 3 follow-up email takes 3 minutes and recovers a meaningful percentage of deals that would otherwise go cold.

Step 4: Contract signed

Trigger: Prospect verbally accepts the proposal or sends written confirmation.

Actions:

  1. Prepare the contract using your standard template, fill in client name, project scope, investment, payment terms, start date, timeline
  2. Send via e-signature tool (DocuSign, HelloSign, or PandaDoc), not a Word document attachment
  3. Do not begin work until the contract is signed and the deposit is received
  4. Once signed: update CRM to “Contract Signed,” file the signed contract in 00-Intake client folder
  5. Send the deposit invoice (50% upfront) and a “What happens next” email

Output: Signed contract on file, deposit invoice sent, deal stage updated.

Failure mode: Beginning work on a verbal agreement before the contract is signed. This happens more than it should, a client says “go ahead” and you start work because you’re excited and the scope is clear. Three weeks later, they want changes to the scope and there’s no signed document defining what was agreed. Every hour you work before the contract is signed is at risk.

The non-negotiable rule: No work starts without a signed contract. Period. “I trust them” is not a contract. “They said yes” is not a contract. A signed contract takes 10 minutes to prepare and eliminates most payment disputes.

The gap between proposal acceptance and signed contract is where optimism lives. The client is excited, you’re excited, work feels like it’s started. It hasn’t. Revenue is not real until the contract is signed and the deposit is received. Everything before that is a conversation.

Step 5: Kickoff scheduled and held

Trigger: Signed contract on file and deposit payment received.

Actions:

  1. Send the welcome email (from your template library) with onboarding questionnaire
  2. Request access to all required systems (brief, brand assets, logins)
  3. Review questionnaire answers before kickoff
  4. Hold kickoff call, confirm scope, set expectations for communication, agree on milestone dates
  5. Send kickoff recap email same day: what was confirmed, first deliverable due date, communication norms
  6. Create the client workspace in Notion, link to project overview, milestone tracker, open questions log

Output: Client onboarded, kickoff complete, project structure established in Notion, both parties clear on scope and timeline.

Failure mode: Kickoff call happens but no recap is sent. The conversation was clear in the meeting, 72 hours later, the client remembers it differently than you do. Scope drift begins immediately after any kickoff without a written confirmation.

The fix: The kickoff recap email is mandatory, sent the same day as the call. It confirms everything in writing and gives the client 48 hours to flag any misalignment before work starts.

Step 6: Delivery completed and approved

Trigger: Deliverable is complete and ready for client review.

Actions:

  1. Deliver the work with a clear context note, what you built, what decisions were made, what feedback you need
  2. Request explicit written approval, “Please confirm approval in email so I can proceed to the next phase” (or “to the invoice”)
  3. Track all revision requests, if they fall outside agreed scope, address them explicitly: “This request is outside our original scope, I can include it as a change order at [cost]”
  4. Receive written approval, documented in the client workspace (Notion) and preserved in email

Output: Deliverable approved in writing, revision count documented, scope changes (if any) priced and agreed to.

Failure mode: Proceeding to invoice without written approval. The client received the work, liked it verbally, and you invoiced assuming approval. Two months later, they claim the work wasn’t fully complete and contest the invoice. Written approval closes this gap entirely.

The critical sentence: Every deliverable email should include: “Please reply to this email to confirm the work is approved, I’ll trigger the invoice once I have your confirmation.”

Step 7: Invoice sent and payment received

Trigger: Written approval received for final deliverable (or milestone billing event reached).

Actions:

  1. Send invoice same day as approval, don’t wait until the end of the week or month
  2. Invoice via your accounting tool (FreshBooks, QuickBooks, Wave), not a PDF attachment from a Word document
  3. Include: invoice number, due date (Net 14 from today), payment instructions, project reference
  4. Update CRM: deal stage to “Invoiced”
  5. Day 7 (if unpaid): send reminder email (from template library)
  6. Day 14 (if unpaid): send firm reminder
  7. When payment clears: mark invoice paid in accounting tool, update CRM to “Closed Won,” file project in 05-Archive

Output: Invoice paid, deal closed, project archived.

Failure mode: Not following up on overdue invoices. An invoice sent and forgotten is revenue that takes the path of least resistance, which is not getting paid. Freelancers who send invoices and wait for payment collect less money than those who send invoices with scheduled follow-ups.

The payment protection sequence:

  • Day 0: Invoice sent
  • Day 7: “Just checking in, invoice [number] is due [date]” (3 sentences, friendly)
  • Day 14: “Invoice [number] is now 14 days overdue, please arrange payment this week” (firm, specific)
  • Day 21: Phone call or direct escalation

A Day 7 follow-up email takes 2 minutes to send and reduces average payment time by 5–8 days for overdue invoices.

The 7-step checklist

Print this or keep it in Notion. Check every item for every project:

  • Lead added to CRM, confirmation sent, follow-up task created
  • Pre-call questionnaire sent and answered before discovery call
  • Discovery call held, deal stage updated, next action documented
  • Proposal sent within 5 days, Day 3 and Day 7 follow-ups scheduled
  • Contract signed and deposit received before work begins
  • Kickoff recap email sent same day as kickoff call
  • Access to all required systems confirmed before first deliverable
  • Written approval received before invoicing
  • Invoice sent same day as approval
  • Day 7 follow-up scheduled in calendar if unpaid
  • Payment received, CRM updated, project archived

Eleven checkboxes. Every unchecked item is a failure mode waiting to happen.

Ready to send stronger proposals?

Build, send, and track proposals in one place so follow-up is easier.

Start your free trial →