Automation
Proposal automation: how to stop rewriting the same document every week
Proposal automation means the document is assembled from structured answers rather than copied from last time and edited. You fill in what is different about this client; the scope, the pricing, the terms and the appendices assemble themselves.
Proposal products cost roughly £25 to £150 per user per month and suit teams sending a similar shape of proposal repeatedly. Building it into systems you already run starts at £1,950. The part worth automating is the assembly and the chasing, not the argument.
What actually goes wrong with proposals
Nobody has a proposal problem in the abstract. They have one of four, and they need different fixes.
It takes too long to produce. Someone opens the last one, saves a copy, and spends two hours finding every place the previous client's name, scope and numbers are buried. This is the one automation genuinely solves.
It goes out wrong. The old client's name survives in one paragraph, or the pricing table does not match the covering email. This is the same problem wearing a more embarrassing hat, and it has the same fix.
It goes quiet. Sent, and then nothing, because following up feels like nagging. Automating a couple of well-timed, genuinely polite follow-ups recovers a real share of these, and it is the cheapest thing on this page.
It does not win. If the proposals are going out fast, accurate and followed up and you are still losing, the document is not the problem. That is worth knowing before spending anything.
The three parts worth automating
Assembly
The proposal stops being a file and becomes an output. Someone answers a short set of questions: which service, which options, which rate card, which terms apply, what the dates are. The document is built from those answers using blocks that are maintained in one place. Change your standard payment terms once and every future proposal has them.
The gain that surprises people is not the two hours. It is that the proposal becomes consistent, so when something in it is wrong you fix it once rather than in whichever copies happen to inherit it.
Sending and tracking
Sent from the system, logged against the client, with a record of when it went and what version it was. If you want to know whether it has been opened, most proposal products do that; it matters less than people think and it makes some sellers behave oddly, so treat it as a nice-to-have.
Chasing
Two follow-ups, spaced sensibly, that stop the moment the client replies or the proposal is accepted. This is a single automation and it starts at £650. Of everything in this article it has the best ratio of cost to recovered revenue, and it is the one most businesses never get round to.
What should not be automated
The part that explains why you, for this client, on this job. If that paragraph can be generated, it was not worth reading, and the buyer can tell. Automate the scaffolding so there is time to write the one page that actually persuades.
The same goes for anything that commits you: a price that has not been checked, a date nobody has confirmed, a scope nobody has read. Automation should assemble the document and then stop, with a person approving it before it goes.
Buy or build
| Route | Typical cost | Where it fits |
|---|---|---|
| A good template and discipline | Nothing | A few proposals a month, one person writing them. |
| A proposal product | Roughly £25 to £150 per user, per month | A repeatable shape of proposal, several people sending, e-signature needed. |
| Automated sending and chasing | From £650, one-off | Almost everyone, whichever of the above you use. |
| Assembly built into your own systems | From £1,950 | The proposal needs live data from your CRM or pricing, or the shape varies too much for a product. |
We do not resell any of these products. Where one is the right answer we will name it and you will buy it directly, because a supplier with a commission has no business recommending software.
Who this is not for
If you send two proposals a month and they win, leave it alone. If your proposals are genuinely bespoke every time, with no repeating structure at all, assembly automation will fight you and you should automate only the chasing. And if the real problem is that nobody is asking for the work, this is the wrong page: that is a search and enquiry problem.
Not sure which of those you have? That is exactly what the free systems audit is for, and it is allowed to conclude that you need none of this.
Questions I get asked about this
What is proposal automation?
Building the proposal from structured answers rather than copying the last one and editing it. You supply what is different about this client and the scope, pricing, terms and appendices assemble themselves from blocks maintained in one place.
How much does proposal automation cost?
Proposal products typically run from about £25 to £150 per user per month. Automating just the sending and chasing starts at £650 as a single job. Building assembly into systems you already run, so the proposal can use live pricing and CRM data, starts at £1,950.
What should not be automated in a proposal?
The part that explains why you, for this client, on this job. If that paragraph can be generated it was not worth reading. Automate the scaffolding so there is time to write the page that persuades, and keep a person approving the document before it goes.
Do I need a proposal tool or a bespoke build?
Buy a product if your proposals share a repeatable shape and the fields fit. Build only when the document needs live data from your other systems, or when the structure varies so much that a product becomes an expensive template.