Loading
A quote builder creates a priced quote from inside the CRM. In Treepie Flow a rep picks products and services from the catalogue, the price fills in from the customer’s rate card, and discounts past your threshold route to a named approver. The quote is attached to the deal, versioned, sent for e-signature, and — once accepted — becomes the delivery plan and billing schedule.
Because sales quotes from a copy of the price list and finance bills from the real one. The gap is discovered at invoicing, and it is resolved by whoever is least willing to argue.
The quote builder assembles line items from the product and service catalogue Books maintains, applies the rate card that governs this customer, and produces a priced document attached to the deal.
There is no copy. The quote reads the same catalogue and rate cards finance owns, so an out-of-date price is not something a rep can select. Overrides are possible, visible and routed for approval.
A quote for Bexley Group picked up their contracted rate and a term discount automatically. The rep's own spreadsheet had used list price, which would have overcharged them by £4,100 and cost a week of goodwill.
It will not invent a price for something not in the catalogue. A genuinely bespoke line is entered explicitly and flagged as such, so finance sees it before it becomes a commitment.
Books prices it and bills from the accepted version, Loop opens delivery from its sold lines, and version history keeps every revision that was sent.
| Spreadsheet & Word template | Standalone CPQ tool | Treepie Flow | |
|---|---|---|---|
| Where prices come from | Copied from the last quote | A price list maintained separately | The customer’s rate card, owned by finance |
| Discount control | Nobody checks | Approval rules in another system | Routed on the deal, decision recorded |
| Customer details | Retyped | Synced from the CRM | Read from the deal and company |
| Versions | Files with suffixes | Kept in the tool | Every version on the deal, with a diff |
| After it’s signed | Retyped into projects and invoices | Exported to other tools | Becomes the project and billing schedule |
Yes. Rate cards are per currency, and the quote records the rate that applied on the day.
Up to whatever threshold you set. Past it, discount approvals route it to whoever carries the margin.
They are kept. Version history shows what changed between them and who asked for it.
Yes. Licences, fixed-price packages and day-rate services can sit on the same quote, each priced by its own rule.
Yes. Each line has a billing type — one-off, monthly or annual — and the quote shows first-year and recurring totals separately.
Yes. Rate cards are set per currency, and the quote is issued in the currency the customer is billed in.
Reps and approvers can see margin per line and in total, based on cost held in Books. You choose which roles see it.
Yes. Mark a line as optional and the customer can include or remove it before signing; totals update to match.
Yes. Duplicate a quote onto the same or another deal; prices are re-read from the rate card so nothing stale is copied.
From a proposal template you design, with sections that pull values from the deal, company and quote when the PDF is generated.
No. Flow keeps its own catalogue when Books is off. Switch Books on later and pricing moves to the rate cards finance owns.
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.