Quoting and proposals covers building a priced quote from your catalogue, getting discounts approved, generating the proposal document, collecting signatures and tracking versions. In Treepie Flow quotes are priced from the rate card finance maintains in Books, discounts past a threshold route to a named approver, and an accepted quote becomes the delivery plan in Loop and the billing schedule in Books.
A quote builder that prices line items from the catalogue Books maintains, rate cards per client, currency and term with effective dates, discount thresholds routed to a named approver, proposal templates that resolve fields from the record, e-signature against the deal, and full version history.
When a quote is accepted it opens delivery in Loop and billing in Books from the same lines, so the accepted document is the specification rather than a summary of one.
Because sales quotes from a copy of the price list and finance bills from the real one. The copy is a spreadsheet, or a template, or a rep's memory of what was agreed last time, and it is accurate right up until the quarter prices changed.
The gap surfaces at invoicing, weeks after the customer has formed a view about what they are paying. It is then resolved by whoever is least willing to argue, which is rarely the outcome that protects the margin.
A rep cannot select an out-of-date price, because there is no second price list to select from. Discounts past a threshold reach an approver with the delivery cost attached, so the decision is made against margin rather than against enthusiasm.
And the executed contract lives on the deal. Two years later a scope dispute is settled from the record — the signed document, the version history showing what changed, and the date the customer agreed it.

It will not invent a price for something that is not in the catalogue. Genuinely bespoke lines are entered explicitly and flagged, so finance sees them before they become a commitment rather than afterwards.
And Treepie records the signing process and keeps the evidence; whether a given signature is binding in your jurisdiction is a question for your own advisers, not a claim this page makes.
Get the catalogue and rate cards into Books first. Quoting reads them, so a quote builder pointed at an incomplete catalogue reproduces exactly the problem it was meant to remove.
Then set discount thresholds low enough that they are used and high enough that they are not theatre. A threshold everyone routes around teaches the team that approvals are a formality.
Books owns the catalogue and the rate cards, bills from the accepted version and recognises revenue against it. Loop opens delivery phases from the sold lines and reports variance when delivery differs from what was sold. Pipeline reports read quote values, and cohort analysis reads the rate card that applied when the deal started rather than the one in force today.
| Documents & spreadsheets | Standalone quoting tool | Treepie Flow | |
|---|---|---|---|
| Prices | Copied from an old quote | A separate price list to maintain | The rate card finance owns |
| Discount approval | An email thread | Workflow in another tool | Routed on the deal, decision recorded |
| Versions | Final_v3_REAL.docx | Kept in the tool | Every version, with a diff and reason |
| Signature | Print, sign, scan | Separate e-signature tool | Sent and tracked from the deal |
| After acceptance | Retyped into projects and invoices | Exported | Becomes the project and billing schedule |
A rep cannot select an out-of-date price, because there is no second price list to select from. Discounts past a threshold reach an approver with the delivery cost attached, so the decision is made against margin rather than against enthusiasm.
It will not invent a price for something that is not in the catalogue. Genuinely bespoke lines are entered explicitly and flagged, so finance sees them before they become a commitment rather than afterwards.
Get the catalogue and rate cards into Books first. Quoting reads them, so a quote builder pointed at an incomplete catalogue reproduces exactly the problem it was meant to remove.
From rate cards maintained in Books, per customer, currency and term, each with an effective date.
Quotes past your threshold route to a named approver, who sees the deal and margin; the decision and reason stay on the deal.
Yes. Send for signature from the deal, track it, collect the countersignature and store the executed document.
Yes. Reusable sections pull values from the deal, company and quote when the document is generated.
Every issued quote is kept as a version, with a diff, the person who changed it and why.
Accepted lines become Loop delivery phases and a Books billing schedule, both pointing back at the quote.
Yes. Rate cards are set per currency, and the quote is issued in the currency it is sold in.
No. Flow keeps its own catalogue if Books is off; switching Books on later moves pricing ownership to finance.
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.