Loading
Assumptions and exclusions are the sections people delete because they feel negative, and they are the reason quotes stop turning into arguments. Every assumption you write down — two stakeholders available weekly, one consolidated round of feedback, data supplied as CSV — is a variation you can raise later by pointing at a document you both signed, rather than by relitigating a conversation from six weeks ago.
Price in lines, not in a lump. A single figure invites one question, which is whether it can be smaller. Four priced lines invite a better question: which of these do we actually need now? Customers cut scope more readily than they extract discounts, and you keep the margin on what remains. Keep options in a separate block below the total so the headline number stays comparable.
State validity and mean it. Thirty days is normal, fourteen is fine when costs are moving, and either is better than a quote that stands forever. Where the quote is time and materials rather than fixed, put a not-to-exceed cap on the page and say plainly that work stops at the cap without written approval. Nobody has ever been annoyed by that sentence; plenty of people have been annoyed by the invoice that would have existed without it.
Then make accepting easy. Acceptance block on page one, a field for their purchase order number, and a note that a signed quote is the order. The PO field is the small mechanical detail that means the eventual invoice can be matched and paid without an email — which is the whole reason to use the same numbering across the quote, the order and the invoice.
Ardent Labs, a nineteen-person R&D consultancy, added assumptions and exclusions to a quote template they had used for years. Nothing else about how they sell changed.
A good template gets you a document that wins work and defines it. What it cannot do is stop the same lines being typed again into a project plan, and then a third time into an invoice — which is where the numbers start disagreeing with each other.
In Flow the accepted quote is the record: the same priced lines open the project in Loop and become the invoice schedule in Books, so what was sold and what is delivered and what is billed are one thing rather than three documents that nearly match.
By then it is a credit note conversation. Assumptions and exclusions move it to week two, where it is cheap.
Two versions of the scope exist immediately, and the delivery team is working from the wrong one.
Version three in someone’s sent items is not a system of record, and v2 is what got signed.
Usually because they are buried under the total instead of priced separately where they can be said yes to.
In most cases a signed quotation plus your terms of business forms a binding agreement, which is why the acceptance block and a reference to your terms are on page one. For anything substantial, have your terms reviewed once by a solicitor — then reuse them forever.
Thirty days is the norm and fourteen is sensible when material or salary costs are moving. The important thing is that a date exists; an open-ended price is a risk you are carrying for free.
No. Mixing a fixed price with the rates behind it invites a negotiation about the rates. Keep the rate card for the time-and-materials variant, where it belongs.
That is what the assumptions list is for. Price the variation as a change request against the signed document, referencing the assumption it breaks. It stays a commercial conversation rather than a dispute.
The structure travels; the tax line and the late-payment reference do not. Swap the VAT block for your local equivalent and delete the statutory interest sentence unless your jurisdiction has one.