Copy the last one and change the name
A scope is agreed: an external infrastructure test and a web application test with an API, with a retest included. Your sales lead opens last month's proposal for a similar client, saves a copy, and starts editing. The methodology section is fine. The scope table needs rewriting. The days and rates are recalculated in a spreadsheet and typed in. The terms paragraph about retests is different in this proposal from the one in the template on the shared drive, and nobody is sure which is current.
The proposal goes out. Two days later the client points out that page six still mentions the previous client's application by name.
Once they sign, someone writes the statement of work by copying sections from the proposal into another template. The retest terms are copied from the other version of the paragraph. When the retest request arrives months later, the proposal and the statement of work say different things.
Multiply that by every engagement you quote, and a meaningful share of a senior person's week is spent on documents rather than on selling or testing.
Why proposals are slow and risky
- Proposals are built by copying the last similar one, carrying over its errors.
- Standard clauses (retests, cancellation, testing windows, limitations) exist in several versions.
- Days and rates are calculated outside the document and typed in.
- The statement of work is a separate document written from the proposal, so the two drift.
- Every proposal needs a senior person to check it, because nobody trusts the process.
What slow proposals cost
| Problem | Result |
|---|---|
| Old client's details left in | Embarrassment, and a confidentiality worry |
| Clauses differ between documents | Disputes about retests and cancellations |
| Days miscalculated | Engagement underpriced or overpriced |
| Slow turnaround | Client signs with a firm that replied first |
| Senior time on documents | Less time on selling and testing |
The mismatch between proposal and statement of work is the one that bites later. It rarely matters on the day of signing. It matters months afterwards, when a client asks for a free retest or postpones at short notice, and the two documents give different answers to the question of who pays.
The proposal generation we build
- The agreed scope and day estimate come straight from your scoping record, so the proposal starts from facts rather than a copy of an old document.
- Your rates, discounts and any framework or partner pricing are applied from a rate table, with discounts beyond a set limit sent for approval.
- Standard sections (methodology per test type, team, approach to reporting) are held as approved blocks, one current version each.
- Clauses (retests, cancellation and postponement, testing windows, limitations) are held as approved blocks too, and chosen by rule: a retest clause appears only if a retest is included.
- The proposal is produced in your branded format as Word or PDF, with the client's details filled in from the CRM. Nothing from any other client is present, because nothing was copied.
- When the client accepts, the statement of work is generated from the same data and the same clauses, so the two documents agree. It can go for e-signature alongside the authorisation form.
We can build this inside your CRM, such as HubSpot or Salesforce, if it supports document generation, or as a small tool connected to it.
What your sales lead gets back
A proposal that needs checking, not writing. The senior review becomes a read-through of scope and price, not a hunt for leftovers from another client. Statements of work match proposals exactly. Clauses are updated once when your terms change, and every new document uses the new version.
Turnaround improves because the slowest part, rebuilding a document, has gone. The time goes back into the scoping conversation, which is where proposals are really won.
Signs your proposal process needs attention
- Proposals start as a copy of an old one.
- A proposal has gone out with another client's details in it.
- Your proposal and statement of work have disagreed on terms.
- Rates and days are calculated in a separate spreadsheet.
- Only one or two people can produce a proposal.