Loading
Rate cards are the price lists quotes are built from. Each rate card sets a price for every product and service in a given currency and term — a standard list, a partner tier, or a single customer’s negotiated prices. Every version has an effective date, so a quote always uses the prices that applied on its date, and finance can schedule a price change without reps doing anything.
Because a negotiated price is agreed in a call, noted in a contract PDF and remembered by one account manager. When they leave, the customer remembers the discount and you do not.
A rate card is a set of prices that applies to a customer, currency and contract term, with an effective date — so pricing is a record with a history rather than a current state.
Cards are held in Books and read by Flow. Each has an effective date, so raising prices in April leaves January's quotes and invoices reading the rates that actually applied then.
A 6% uplift went live on 1 April. Quotes issued in March held their prices to expiry, renewals after that date picked up the new card, and no historical invoice changed — which is what made the audit uneventful.
They price what you sell. What a piece of work costs to deliver sits in Loop, and margin is the comparison of the two rather than something a rate card knows.
The quote builder prices from it, Books bills from it, cohort analysis reads it when comparing deals across periods, and discount approvals measure against it.
| Price list spreadsheet | One price per product in the CRM | Treepie Flow | |
|---|---|---|---|
| Customer-specific prices | A tab per customer, if at all | Discounts applied by hand | A rate card per customer |
| Currencies | Converted on the fly | One currency, converted | Set per currency, never converted |
| Price changes | Emailed to the team | Overwrite the old price | New version with an effective date |
| What a past quote used | Unknown | Lost when the price changed | Kept on the quote, with the version |
| Who can change prices | Anyone with the file | Anyone with admin | Finance, with every change audited |
Yes — by currency, by term, or by product line. The quote resolves which applies.
Finance, in Books. Flow reads them, which is the point.
The renewal picks up the card effective on its start date, and the change from the previous term is shown.
Yes. Each rate card is set in one currency, so a customer billed in GBP has GBP prices rather than converted USD ones.
Yes. A rate card can hold different prices for monthly, annual and multi-year terms, and the quote picks the one that matches.
Yes. Create the new version with a future effective date. From that date new quotes use it automatically.
No. A quote keeps the prices of the rate card version it was built from. Re-pricing a draft is an explicit action.
Yes. A line can carry price breaks by quantity, and the quote applies the tier that matches.
If you allow it. Cost is held in Books and margin can be shown to chosen roles in the quote builder.
Create a rate card per partner tier and attach it to partner companies. Their deals quote from it automatically.
Yes. Import a CSV per rate card, with the effective date, and check it in the sandbox before it goes live.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.