Home

/

Resources

/

Glossary

/

Quote-to-cash

Quote-to-cash is the end-to-end process from scoping an offer to cash collected. Seven sub-processes, six teams, and where revenue leaks between them.

Quote-to-cash

Quote-to-cash is the end-to-end business process that starts when a company scopes and prices an offer and ends when it collects and recognises the cash. It links quoting, contracting, order management, invoicing and collection across Sales, Legal, Finance and Operations. Its purpose is to turn a qualified deal into revenue without loss.

Why quote-to-cash matters now

Every scoped deal passes through quote-to-cash. This is where a qualified deal becomes contracted revenue and then cash, or does not. In 2024, 61% of companies missed their revenue target, with leakage in the revenue process as the primary cause (Clari), and 93% of high-growth SaaS scale-ups lost more than 10% of ARR after signature, to payment delays, defaults and post-signature friction (Ratio Tech). None of this shows up as a lost deal. It shows up as a discount nobody approved, an invoice sent three weeks late, a renewal missed because the billing terms changed and Finance found out at month-end. For a CFO, quote-to-cash is the shortest path to recovering revenue already earned. For a CRO, it is the difference between a booking and cash.

The seven sub-processes of quote-to-cash

Quote-to-cash starts earlier than most teams think, at scoping the offer. A CIO in an industrial group put it plainly: a scoping error surfaces 18 to 24 months later, during integration. From there, the envelope covers seven sub-processes, each with an owner, and none with an owner for the handoff to the next. In a mid-size enterprise one deal crosses six or more divisions, more than 15 roles, more than 10 systems and around 30 people. Quote-to-cash is seven processes that only deliver when they move as one.

The seven sub-processes, who usually owns them, and the handoff nobody owns.
Sub-process Usual owner The handoff that leaks
Quote and order accuracySales, pre-salesScope sold is not the scope delivered
Contract and pricing complianceLegal, deal deskA discount approved in a chat, a clause nobody checked
Subscription lifecycleRevOps, Customer SuccessTerms change at renewal and Finance learns at month-end
Audit trail and close readinessFinanceApprovals scattered across threads, rebuilt at close
Invoicing and cash collectionFinance, billingFinance learns about the signature 48 hours later
Incentive compensationFinance, sales opsCommissions computed on a deal that changed after signature
Revenue and retention metricsRevOps, CFONobody can point to the step where the revenue left

Where quote-to-cash breaks: between teams, not inside them

The failure pattern is the same in most companies. Sales closes in the CRM, Finance invoices from a spreadsheet, Customer Success onboards from an email thread: three systems, three realities, and no orchestration between them. The CRM stores the deal, and it never sees the handoffs, which live in Slack, Teams and email, invisible and untraced. A Director of Sales Administration at a software company describes the result: Finance sometimes learns about a signature 48 hours later, and Customer Success discovers the client at the kickoff. Her daily reality: “I feel like I am harassing teams: is it done? is it done?”. Each gap costs days, days cost cash, and nobody can point to the step where the revenue left. Quote-to-cash: where revenue leaks between teams, from scoping to cash walks through each leak and what it costs.

Watch one deal run from quote to cash, with Legal, Finance and Customer Success in the loop, in four minutes

Quote-to-cash vs order-to-cash, lead-to-cash and CPQ

The terms overlap, and the differences matter when you scope a project. Order-to-cash starts once an order exists, so it skips quoting, contracting and pricing approval. Lead-to-cash starts earlier, at lead qualification, and includes the whole sales cycle. Quote-to-cash sits between the two: from scoping and pricing the offer to cash collected. CPQ (configure, price, quote) is a tool category rather than a process: it produces an accurate quote, and does not carry the contract to Legal, the terms to Finance or the commitments to Customer Success. The revenue lifecycle is the wider frame, a cycle of three movements in which quote-to-cash is the core, after lead-to-opportunity and before the client lifecycle.

How to run quote-to-cash well

Start by mapping the handoffs rather than the tasks. Each team already knows its own steps; what nobody owns is the moment a deal leaves one team for the next. Give every handoff an owner, a deadline and a trace. Move approvals onto a governed path: discount thresholds, payment terms and contract exceptions decided by the right person, recorded once, visible to all. Make the signed terms travel with the deal, so Finance invoices what Sales sold and Customer Success onboards what the customer bought, which is what the sales to customer success handoff depends on. Measure the cycle end to end, days from quote to cash rather than days per team. And keep people in the loop: quote-to-cash carries contractual, financial and legal weight, so speed comes from coordination, not from removing judgement.

Run that way, one deal looks like this. The rep scopes the offer with pre-sales before the quote exists, so the scope sold is the scope delivered. The quote is assembled from the pricing policy and the account’s existing contracts. The discount sits at 25%, so the approval goes to the COO rather than the sales director, with the analysis attached, and the COO approves in one click. Legal receives the two clauses outside the matrix, not the whole contract. At signature, Finance and Customer Success get the deal the same day, contract and commitments attached, and the invoice goes out on the terms Sales agreed. Each step carries its owner and its timestamp, so at close nobody rebuilds the approvals from chat threads.

Where agentic steps help along the way:

  • Assemble the quote from the pricing policy, the catalogue and the existing contracts, for the rep to check.
  • Check the discount and the payment terms against policy and route the exception to the right manager.
  • Compare the customer’s redlines with the approved clause matrix, so Legal reads only the exceptions.
  • Flag a gap between what was sold and what Delivery can commit to, before signature.
  • Draft the handover brief for Finance and Customer Success from the signed contract and the scoping notes.

In each case, a person validates the result before the deal moves on.

Callout · Three signs your quote-to-cash leaks

  • Finance learns about a signature days after the fact, from an email thread.
  • Discounts above policy get a yes in a chat, with no trace of who said it.
  • Customer Success starts onboarding without the contract terms in hand.
Learn more: see how operations and sales teams run quote-to-cash with Ofelia, and what agentic orchestration adds to it.

Ofelia Agentic and quote-to-cash

Ofelia Agentic orchestrates quote-to-cash across the teams and systems the CRM never sees. The deal stays in the CRM. The handoffs run in Slack and Microsoft Teams, where Sales, Legal, Finance and Customer Success already work.

With Ofelia Workflow, a documented quote-to-cash procedure becomes a running workflow: Ofelia drafts it from the documentation, the process owner refines it in a no-code editor, tests it and publishes it into Slack or Teams. Discount approvals route to the right manager by threshold, and the routing survives the next reorganisation. Contract terms, payment conditions and commitments travel with the request, files included. Agentic steps draft the order summary or check pricing compliance, and a person decides. The process is deterministic, the execution is agentic, the decision stays human. Every step lands in the audit trail. AI native to the CRM sees what is inside the CRM; Ofelia orchestrates beyond it, and includes the contributors who never had a CRM seat.

MGI Research estimates that at least 3 to 5% of a company’s revenue leaks through quote-to-cash. Run as one orchestrated process, that revenue is recovered or brought forward. Under the hood, Ofelia builds on Bonita BPM, which has run enterprise processes for more than 15 years at more than 130 enterprise customers.

Download the Revenue Lifecycle one-pager (PDF).

See Ofelia handle your actual workflows in a personalised session
Get a demo

‍

Reading time: 5 min
Table of contents
‍
Frequently asked questions
‍
What does human-in-the-loop mean?
It means a person sets the limits an AI system works within, decides at the critical points and can step in at any time. The agent researches, analyses, acts and proposes inside those limits, and a person validates the outcome. Every step goes on record. The term is best known from machine learning, where people correct a model’s outputs to train it. It now extends to AI agents, which act with real autonomy. In automated and agentic processes, it applies to execution: the steps that commit the company.
Does the EU AI Act require human-in-the-loop?
The EU AI Act requires human oversight and record-keeping for high-risk AI systems. Human oversight means a person can understand, intervene and override. Human-in-the-loop by design is a practical way to meet that requirement. Whether a given process falls under the high-risk category, and from when, is a legal question for your counsel.
Where should a human stay in the loop in a sales process?
At the points that commit the company. A discount above policy goes to the sales director, the COO or the CEO, by threshold. A contract clause outside Legal’s approved matrix goes to a lawyer. The scope of the offer deserves a human eye too: a CIO of an industrial group notes that a scoping error at the offer stage surfaces 18 to 24 months later. Everything else, an agent can prepare: the quote, the standard clauses, the handoff to Finance and Customer Success.
What is BPMN and why does it matter in BPM?
BPMN, Business Process Model and Notation, is the standard notation for describing processes: tasks, decisions, roles, events and flows. Business and IT read the same diagram, and a BPM platform can execute it directly. A process modelled in BPMN is both the documentation and the application logic.