Operated function · quotes and proposals
It is assembled the night before, from the most similar document anybody can find, by somebody senior enough to be doing something else. The writing is usually fine. What travels with it — a price from a different deal, a service level nobody approved, occasionally a name — is the part that costs.
It starts as a search: find the closest previous document. That is a sensible instinct and it is the origin of every problem downstream, because the closest previous document was correct for a different customer, a different scope, and a price that may have reflected a concession nobody recorded.
Then it is edited under time pressure, usually by the person who knows the deal, usually in the evening. The parts that get attention are the parts specific to this customer. The parts that do not are the boilerplate — the terms, the service levels, the assumptions, the appendices — which is exactly where the inherited commitments live.
Pricing needs an approval. The approver is busy, the deadline is tomorrow, and the request arrives with the whole document rather than with the specific thing needing approval — so it is approved on trust or it is late, and neither of those is a review.
The version that goes out is one of several on somebody’s machine. Which one was sent is knowable only from the email, and if a question arises three months later about what was promised, the reconstruction is archaeology.
Nobody knows what happens after it lands. It was opened or it was not, once or six times, by one person or forwarded to four — and none of that is recorded, so the follow-up is timed by guesswork.
Proposals are assembled by duplicating the nearest previous document, so every term, price and service level not deliberately re-checked is inherited from a deal it was written for — and the deadline guarantees most of it is not re-checked.
The fix is not a better template, because a template still gets copied and edited under the same pressure. It is assembly from components that each have an owner and a current version: the pricing block, the service levels, the security appendix, the assumptions, the scope language. A document built from current components cannot inherit last quarter’s concession, because last quarter’s concession is not a component.
That also changes what approval means. Instead of a whole document arriving the night before, the approver sees only what is non-standard — the specific deviation from the current component, in isolation. That is a review somebody can actually perform in the time available, and it is the only version of approval that catches an inherited term.
Assembly is bounded, repetitive work and it is the part worth delegating: selecting the right components, filling the customer-specific fields, checking that every claim in the document maps to something the organisation actually offers, and flagging anything that does not. Deciding the price, granting the concession and making the commitment stay with your people.
And once the document is a known object rather than a file on a laptop, what happens to it becomes visible — opened, forwarded, gone quiet — which is the same signal the abandoned-purchase operation reads, applied to the highest-value documents you produce.
Documents built from current components rather than from a previous customer’s file — measured by proposals assembled from the component set, as a share of all proposals sent.
Inherited terms and service levels — measured by non-standard clauses found at assembly that nobody had approved for this deal, counted rather than discovered later.
What an approver actually reviews — measured by deviations presented in isolation versus whole documents forwarded, and the time from request to decision.
Time from opportunity ready to document sent — measured by elapsed hours against your own baseline, and how much of it fell outside working hours.
Senior time spent assembling rather than selling — measured by hours logged to document production by salespeople, sampled the same way before and after.
Whether a sent proposal was ever opened — measured by open and forward evidence per document, against a baseline where follow-up was timed by guesswork.
any pricing, discount, commitment or contractual decision. Nothing here sets a number, grants a concession, agrees a service level or binds your organisation. It assembles from what you have approved and flags anything that departs from it — a system that could decide a price would be deciding the commercial terms of your business.
The component set is yours: written by your people, versioned, each with a named owner. It has to be, because it is the record of what your organisation actually offers — and if it lives only inside a vendor, the day the vendor leaves is the day you go back to copying the last document.
Documents are produced in the format and system you already send from, so a customer receives what they have always received and your legal team reviews what they already know how to review.
Pricing comes from your price book rather than from a previous quote, which is the specific mechanism that stops a concession travelling.
Nothing is written into a proposal that does not map to a component your organisation owns or a field your salesperson supplied. Where a requirement has no matching component, the document does not get a plausible sentence — it gets a flag, because an invented capability in a proposal becomes a contractual commitment when it is signed.
Every document carries a record of which component versions it was built from, so if a component turns out to have been wrong, every proposal carrying it is findable rather than estimated.
Deviation approval is enforced rather than advisory. A document with an unapproved deviation does not become sendable because a deadline is close.
Operational access is not permission to train. Your pricing, terms and customer scope — which together are close to a complete description of your commercial position — do not become material improving anything serving another organisation, least of all one that bids against you.
Legal owns the clause components, and this is the part of the operation that most improves their position: a component set with owners and versions replaces a situation where the operative terms are whatever survived the last copy-paste.
Whoever owns pricing owns the deviation rules — what counts as standard, what requires approval, and what is never permitted regardless of deadline. Those need to exist before assembly is delegated, because assembly without them is just faster copying.
Where a proposal responds to a formal solicitation with its own compliance requirements, those are established at scoping, and the claim-mapping discipline becomes a compliance control rather than a quality one.
The last twenty sent proposals — read-only, nothing produced — compared against your current price book and clause library, to find what was inherited.
The audit is the phase that justifies everything after it, and it produces no document. It finds the terms, service levels and prices that appear in sent proposals and do not match anything currently approved — inherited from an earlier deal, carried forward, and in some cases signed.
That output is worth having on its own. Several organisations discover a commitment in circulation that nobody would have approved, and the correct next action is legal review rather than a proposal operation.
If you continue, the first step is building the component set — your clauses, your terms, your price blocks, each owned and versioned. Assembly is delegated only after that exists, because delegating assembly without it produces faster copies of the same problem.
A template is a starting document, and the failure this addresses is what happens after somebody opens it: it gets edited under deadline, saved as a copy, and next quarter that copy becomes the template. Components differ because they are referenced at their current version rather than duplicated, which is what makes an inherited concession structurally impossible. The audit settles whether your templates are holding — it looks at what was actually sent rather than at what the template says.
The customer-specific scope usually is bespoke and stays that way — it is supplied by your salesperson and nothing here writes it. What is almost never bespoke is the terms, the service levels, the security appendix, the assumptions and the price structure, and those are where the inherited commitments live. The audit measures the ratio directly, and if your documents are genuinely bespoke throughout, this is the wrong purchase.
Nothing decides a price. Numbers come from your own price book, deviations go to your approver in isolation, and no discount or commitment is made here. If reading the price book is itself out of scope for you, a narrower version exists — assembly of the non-price components only, with the commercial section left entirely to your team. That is a smaller operation and it still removes most of the inherited-term risk.
The deadline does not change; what changes is what has to happen inside it. Most of the evening is spent finding a document, re-checking boilerplate, and chasing an approval on a whole file. Assembly from current components removes the first two, and deviation-only approval makes the third something an approver can do quickly. If your bids are late for reasons upstream of the document — scope arriving too late to respond — that is a different constraint and this will not fix it.