Understand
From the first quote to the cash.
What happens between “this customer wants to buy” and “the money is in the account” — explained without assuming you know Salesforce.
How claims are labelled
What we are talking about
Quote-to-Cash is the whole chain of a sale. It starts when someone puts an offer together, and it ends when the payment is collected and booked.
In between there are more steps than people expect: picking the right products, working out the right price, issuing a quote, turning it into an order, turning that into a contract, producing invoices at the right rhythm, applying the right tax, chasing payment, and finally recording the accounting entry.
In many companies those steps live in different tools — a CRM for selling, a spreadsheet for prices, an accounting package for invoices — and that is precisely where the time and the money leak away.
The symptoms it fixes
People usually recognise the problem before they know its name. These are the sentences that come up most often:
- “Every rep has their own pricing spreadsheet.” Two quotes for the same configuration come out at two different prices, and nobody knows which one is right.
- “We key the same thing in three times.” Once in the CRM, once in the quote spreadsheet, once in accounting. Every re-entry is a chance to get it wrong.
- “We do not know what is being billed.” Subscriptions live in people’s heads and in files, not in a system that produces the invoices by itself.
- “Billing takes three days a month.” Manual, repetitive, and late the moment somebody is away.
- “We find out about amendments too late.” A customer adds licences in March and billing notices in June.
None of these is an isolated tooling problem. They are the signs of a chain that is not joined up end to end.
A sale, step by step
Here is the full chain. Each stage produces something the next one needs — which is why a break in the middle is so expensive.
What a CRM does, and what it does not
A CRM (customer relationship management) answers: who is this customer, who spoke to them, where is the deal, what is it worth.
What it does not do natively: assemble an offer from options that must be compatible, apply a price list with volume tiers, produce a three-year billing schedule, work out tax from the billing country, or generate the matching accounting entry.
That is what Revenue Cloud adds on top — the “what we sell, at what price, and how we bill it” part. Salesforce has renamed it Revenue Management, and you will still meet both names.
Where to start
You do not have to take all of it at once, and trying to is the most reliable way to deliver nothing. Three starting scopes, lightest first:
- Quoting only. Catalogue, offer configuration, price calculation, quote document. Stop before the order, and leave billing where it is. This is the scope that fixes “every rep has their own spreadsheet”.
- Through to order and contract. Add what commits: the order, the contract, and what the customer actually holds. This is what makes amendments and renewals manageable.
- Through to invoice and payment. Add schedules, invoices, tax and the link to accounting. The heaviest scope, and the one that frees the most time.
The split is not only about budget: each floor assumes the one below is clean. A badly modelled catalogue does not produce good invoices, however well billing is configured.
The questions to settle first
These are the ones whose answers decide the architecture. If they are not settled at the start, they get settled by default, and rarely well.
- Who is invoiced, and is it always whoever buys? The answer decides the billing model, and how tax will be worked out.
- What sells per unit, and what sells by tier? A flat price and a volume-dependent price are not configured the same way, and confusing them weighs down the whole catalogue.
- Can the customer change the contract mid-term? If so, you need to know what they hold at any moment from day one — that is a structural constraint, not something you bolt on later.
- Where does Salesforce stop and accounting start? Draw the boundary at a record type, not at a field, and have finance sign it.
- Who will maintain the catalogue in two years? A model only its author can change is a model that will freeze.
Switch to the technical view
You have the business mechanics. What comes next — the objects, the configuration, the traps — is in the Configure path, written for administrators and architects.