Quote to cash is every step from the price you send a client to the payment recorded in your books. For a small MSP, that's the quote, acceptance, project or contract, time and parts, invoice, accounting entry, and payment follow-up. Money leaks at the handoffs between them.
Below: seven steps, the leak at each handoff, a worked example, a checklist, and five measures. They come from the team behind SherpaDesk, a helpdesk and PSA (professional services automation) a small IT team can run alone. Two founders who ran their own MSP have built it since 2001.
Key takeaways
The quote-to-cash process (Q2C) is the chain from the price you offer a client to the payment recorded in your books, including the work in between. Order-to-cash is one part of it, starting at the documented order.
Three terms cover different stretches of the same chain:
| Term | Starts at | Ends at | In a small MSP |
|---|---|---|---|
| CPQ (configure, price, quote) | The client's request | A priced quote | A price list and a few quote templates |
| Order-to-cash | The documented order | Payment recorded in the ledger | Parts ordered, work done, invoice sent, payment entered |
| Quote-to-cash | The quote | Payment recorded in the ledger | All of the above, plus acceptance and the project or contract setup |
At enterprise scale, sales, legal, and finance run separate stages and tools. In a five-person MSP, the owner often writes the quote, a technician does the work, and the owner bills it on a Friday night. The chain is the same; the handoffs are between people and tools, not departments.
Customer payments are a small firm's main source of cash, and the quote-to-cash process is how a services firm turns finished work into them. The Federal Reserve's Small Business Credit Survey puts it plainly: "timely collection of customer payments is critical to firms' cash flow."
Its 2024 payments report surveyed US small employer firms (1 to 499 employees) across industries in late 2023, not MSPs alone. Of the firms answering each question:
The project and hourly work an MSP bills after delivery is in that last group, so for that work the quote-to-cash process doesn't end when the work does. Every day between finished work and a sent invoice is a day of cash you've earned but can't use. One r/msp member asked: "How do you make sure you have a closed loop for everything that's bought?"
Earned revenue waiting to be invoiced
monthly billings for work invoiced after it's done × average days ÷ 30, an estimate that assumes the work is spread evenly across the month. Your numbers stay in the browser.
With net 15 from the invoice date, the payment clock starts only when the invoice goes out.
Five things make the quote-to-cash process below work on a small team:
One r/msp member repeats the late-fee terms wherever the client signs or pays. "It is in our MSA, and on every quote/proposal in bold above the signature line, also on every invoice."
Seven steps, each ending with a record the next step can check.
List each line with quantity, unit price, and whether it's one-time or monthly. Add what's out of scope, an expiry date, and the payment terms. Every later step in the quote-to-cash process checks against it.
Example: "4 laptops for new hires at $1,200 each, one-time. Setup, fixed $1,200. Managed service for the 4 new devices at $40 each per month, from Dec 1. Valid 14 days. Net 15 from the invoice date."
Common mistake: no expiry date on hardware, so a quote from March gets accepted at March prices in June.
Acceptance is the first handoff in the quote-to-cash process. Get a written, dated yes to a numbered quote version. A client's edit to the price or scope isn't a yes. Send a revised quote and get that version accepted.
Common mistake: starting on a verbal yes. One r/msp member buys no hardware or licenses "until a proper quote was issued, accepted (either by the client or us) and converted to sales order."
One-off work gets a project with the quote's budget. Recurring lines change the client's contract, with a start date. Time and parts need a home before anyone works, or they land on the wrong bill.
Common mistake: leaving the contract change until after the install. One r/msp member's list of breakdowns includes "billing change status doesn't get applied."
Order from the accepted quote, and put the client and quote number on every purchase. Log time on the ticket or project the same day. Our billable hours tracking guide covers time capture.
Common mistake: a technician adds a dock on site, and nothing records it. Stop at the scope line and send a short add-on quote first.
Before it goes out, compare four columns per line: quoted, bought, logged, billed. Fixed-price lines bill at the quoted price, whatever the hours. Hourly lines bill reviewed billable hours at the agreed rate and billing rules.
Common mistake: building the invoice from the timesheet alone, which drops every part bought on a separate order.
This is where the quote-to-cash process meets your books: each invoice enters your accounting system one time, by sync or by file import. The final order-to-cash step is recording the payment in the general ledger. Match each purchase bill to an invoice line.
Example: one r/msp member suggests separate ledger accounts for hardware sales and purchases: "If purchase is larger than sales you have a problem." How revenue is recognized is a question for your accountant.
The quote-to-cash process ends when the payment is recorded, not when the invoice goes out. Put every open invoice on one list with its due date and an owner. Send a reminder on the due date, then a formal notice on a set day after it.
Example: one r/msp member's sequence is "a friendly reminder first followed up by a formal overdue notice." Late fees belong in your agreement; ask your attorney what your state allows.
For the proposal before step 1, see our managed services proposal template.
The quote-to-cash process rarely fails inside a step. It fails where work passes from one step, person, or tool to the next.
| Handoff | How money leaks | The check |
|---|---|---|
| Quote to acceptance | Verbal yes; price cut in a meeting with no revised quote | Written, dated acceptance of a numbered quote version |
| Acceptance to project or contract | Monthly add-on never reaches the contract | Contract changed the day the quote is accepted, with a start date |
| Project to purchasing | Parts bought on a separate order, never tied to the client | Every purchase names the client and the quote |
| Work to time and expenses | Unlogged hours; extras added on site | Time and parts logged on the ticket or project the same day |
| Scope change | Out-of-scope work done before anyone quotes it | Pause at the scope line; written add-on quote |
| Time and parts to invoice | Invoice built from memory; quoted lines missing | Quoted, bought, logged, billed: one check per line |
| Invoice to accounting | Invoices retyped, duplicated, or missed; bills with no sale | One entry per invoice; each bill matched to a sale |
| Invoice to payment | Nobody owns follow-up | Open invoices on one list with an owner and fixed follow-up days |
The scope change is the hardest leak to fix after the fact. One r/msp member invoiced a day of out-of-scope work, and the client pushed back: "you should have told me it was billable." A reply in the same thread watches for "out of scope tickets exceeding 2hrs time entry to ensure large unexpected invoices are communicated."
Scope can also grow after the work is done. Another r/msp member cut a project quote after the client balked at the price. Then the "client held the invoice ransom and tried to expand scope after the project was done." A revised, accepted quote is what you point to when that happens.
If you decide to give work away, show it. One r/msp member's advice: "Invoice them but add a 100% discount to that line item." Your quote-to-cash records stay complete, even at $0.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Example: a 12-person accounting office hiring four people accepts a revised version of the step 1 quote that adds four docks at $180. On site, the client asks for a fifth dock, and you send a $180 add-on quote that the client accepts by email. Setup takes 10 hours instead of the 8 planned.
The first draft invoice is built from the laptop order and the fixed setup line. The docks, bought on a separate order, are missing. The check against the quote finds the gaps:
| Line | Quoted | Bought or logged | First draft | After the check |
|---|---|---|---|---|
| Laptops at $1,200 | 4 | 4 bought | $4,800 | $4,800 |
| Docks at $180 | 4, plus 1 on an accepted add-on quote | 5 bought on a separate order | $0 | $900 |
| Setup, fixed price | $1,200 | 10 hours logged | $1,200 | $1,200 |
| Managed service, 4 new devices at $40 | $160 a month from Dec 1 | Contract not changed | Not billed | $160 a month added to the contract from Dec 1 |
| One-time total | $6,900 | $6,000 | $6,900 |
The check recovers $900 of revenue and starts the $160 monthly fee on Dec 1. The two extra setup hours aren't billable on a fixed price. They cost margin, and they're a reason to price setup for 10 hours next time.
The corrected $6,900 invoice goes into accounting once, with the laptop and dock bills matched to it, and onto the open list with its net 15 due date. When the client pays, you record the payment against it. Quoted, bought, approved, invoiced, paid, and recorded now all agree.
Run this checklist for every accepted quote. Each item is a yes or no.
Five numbers show where the chain leaks. Read them once a month and fix the worst one first; each points to a step.
| Measure | How to read it | A bad month points to |
|---|---|---|
| Days from quote sent to acceptance | Median, for quotes accepted this month | Step 1 or 2: no follow-up, or the quote needs revising |
| Average days from finished work to invoice sent | Work invoiced after it's done, this month: sum of (invoice amount × calendar days) ÷ total of those invoices | Steps 4 and 5: invoicing waits for month end |
| Quote-to-invoice variance | Invoices where the billed total differs from the accepted quote, with the reason | Steps 3 to 5: unrecorded changes or missed lines |
| Purchases with no matching sale | Purchase bills not tied to an invoice line | Step 4: parts bought outside the quote |
| Days to payment | Median, from invoice sent to payment recorded; share past due | Step 7: no owner or no fixed follow-up days |
The second measure is the days input in the calculator above. For the month-end billing run itself, our MSP billing software guide compares the tools.
How this works in SherpaDesk
Per the SherpaDesk quoting page, accepted quotes convert into contracts and projects. Projects track estimated revenue and expenses, and each account can have its own rate plan. Time logs and expenses collect in "Ready to Invoice" by account contract.
For QuickBooks Desktop, you export invoices, time logs, and payments as .IIF files. Quotes can be assigned to a ticket, accepted or rejected, and synced with QuickBooks Online, Xero, and FreshBooks.
A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.
Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever, and the trial is 14 days free with no card.
Who this isn't for
Companies that run quote-to-cash through enterprise CPQ with product configuration rules, or that need revenue-recognition schedules. If you quote, deliver, and bill your own work as a small IT team, you need a helpdesk and PSA, not a CPQ suite.
TechTarget lists six. The order is documented, then fulfilled or scheduled, then shipped or performed. Accounts receivable sends an invoice, the customer pays, and the payment is recorded in the general ledger. Order-to-cash starts at the order, so it's one part of quote-to-cash.
A quote is your price for the scope written in it, until its expiry date. If the client changes the scope or the price, treat it as a new quote, and get that version accepted before work starts. Whether an accepted quote binds both sides is a legal question; ask your attorney to review your terms.
It's the front half of the quote-to-cash process. You send the quote, follow it up, revise it if needed, and get a written acceptance. Then you turn it into something you can act on: a purchase order for parts, a project for one-off work, or a change to a recurring contract. Delivery, invoice, and payment follow.
In TechTarget's words, CPQ is software that "helps sales representatives and self-service customers quickly generate accurate quotes for configurable products and services." If you sell a few standard laptop models and a monthly service, a price list and quote templates cover that part of the quote-to-cash process. CPQ earns its cost when quotes have many dependent options.
Give each handoff one owner. Often the owner writes quotes and records acceptance, a lead technician runs delivery, and whoever does billing owns the invoice and the follow-up. Then name one person to read the five measures every month and fix the worst step.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.