What does personalising a proposal at scale mean?
Personalising a proposal at scale means producing a lot of proposals without any of them sounding like a mass mailing. It is not repeating the same document with a different name: it is reusing a common base, stable and proven, while adapting for each client what decides conversion, the need restated in its own words, the proof that speaks to it and a price tied to its situation. Volume is the means, adaptation is the end.
The difficulty lies in this tension: the more you produce, the more the tone drifts towards generic, and a generic tone signals a seller who has not listened. Personalising at scale means holding specificity where it matters while the rest gets reused.
How do you personalise without starting from zero every time?
Personalising without starting from zero every time means separating what stays stable from what adapts, then investing effort only in the part that adapts. The approach comes down to four points:
- A common base: the stable blocks, presentation, method, terms, written once and kept up to date.
- Identified personalisation points: the restated need, sector-specific proof, the price.
- Reused client data: what you already know about the client feeds the adaptation, with no re-keying.
- A freshness check: every reused block is checked to still be true before sending.
This separation concentrates the seller's time on the three points that convert, and leaves the common base to handle the rest. It is the opposite of surface personalisation, which polishes the form and leaves the substance identical.
What should you personalise, and what should stay common?
What needs to be personalised is what the client checks; what stays common is what it only reads once. The table allocates the elements of the proposal.
| Element of the proposal | Stays common | Gets personalised |
|---|---|---|
| Company presentation | yes, with a stable base | the angle that speaks to this client |
| Understanding of the need | no | entirely, in its own words |
| Proof and references | a common pool | the choice of references that speak |
| Method and terms | yes | adaptations specific to the file |
| Price | a common logic | the client's scope and options |
How do you adapt from client data (CRM, CPQ, PIM)?
Adapting from client data means reusing what the company already knows about the client, held in its management tools, rather than re-keying it. Three families of tools often feed personalisation: the CRM (customer relationship management, which keeps the client's history and context), configure-price-quote software (known as CPQ, which builds a consistent priced offer) and product information management (known as PIM, which keeps descriptions up to date). This data often contains personal data; the data protection regulation applicable in your market governs its processing, where it applies (in the United States, sectoral privacy laws and state laws such as the CCPA; in the United Kingdom, the UK GDPR and the Data Protection Act 2018). The point to check is where this data is processed and the regime that applies to it.
The concession that clarifies everything
For a small number of proposals, personalisation is done by hand, and any dedicated setup would be overkill: the seller knows each client and adapts as they go. The line is volume: as files multiply, manual personalisation gives way, the tone drifts towards generic and proof ages without anyone noticing. At scale, what protects conversion is not personalising more, it is personalising where the client checks, leaving the common base to handle the rest.
On the Optivalue.ai platform, which publishes this site, production can mobilise up to 100 sub-agents in parallel, so that the volume of proposals does not come at the price of a uniform tone.
The personalisation-at-scale mistakes
- Personalising the form, not the substance: changing the header and leaving the need generic.
- Reusing out-of-date proof: taking up a reference from an old file that has become false.
- Re-keying what already exists: manually copying data already held in the CRM.
- Diluting specificity: producing so many proposals that none names its client anymore.
- Forgetting where the data sits: losing track of where the client's data is processed.
Frequently asked questions
Is personalising at scale the same as a mail merge?
No. A mail merge changes variables in a fixed text. Personalising at scale adapts the substance, the restated need, the proof and the price, while reusing a common base for the rest.
How do you keep a personalised tone across many proposals?
By reserving the seller's effort for the points the client checks, and leaving to an up-to-date common base what it only reads once. Specificity holds where it matters, not everywhere.
What client data can you reuse?
The data already held in the company's tools: history and context in the CRM, priced-offer elements in the configure-price-quote software, descriptions in product information management, in line with the data protection regulation applicable in your market, where it applies.
How do you avoid spreading out-of-date proof at scale?
By checking the freshness of every reused block before sending. At scale, false proof does not circulate on one file, it circulates on every one that reused it.
Sources cited
- Data protection covering client data reused for a proposal: in the United States, sectoral privacy laws and state laws such as the CCPA; in the United Kingdom, the UK GDPR and the Data Protection Act 2018; the applicable rule in each market should be verified.
Work a real consultation on your own documents
Bring a real client consultation. You see the need-extraction coverage, the sources cited on the page and the gap analysis on your proposal, not a scripted demo.
Book a demo