Session summary
Eliza Carbines separates two ideas that bidders often use interchangeably. A win theme is an internal decision about what the bid will focus on to win, made before anyone starts writing. It is short, and most bids need only one or two, with three as the limit before the focus starts to dilute. A unique value proposition, or UVP, is the external expression of that decision: a customer-focused statement that answers the question 'why you?' The theme drives the UVP, not the other way around. Most competitive tenders are not won on capability alone, because everyone on the shortlist can probably do the work. The difference is who communicates their value most persuasively.
A strong theme sits where a genuine strength meets a client hot button and is backed by past performance. Eliza works through hot buttons, discriminators and the competition. A discriminator with no matching hot button is irrelevant, however impressive, and a hot button with no matching discriminator is a vulnerability. Incumbents are warned against assuming they already know what their client cares about. When a bidder has not done that groundwork before release, the evaluation criteria are the place to look: the schedules, the weightings and the number of questions on a topic all show what really matters. The 'so what' test then exposes thinking that has not gone far enough.
Every UVP has three parts: a feature, the benefit to the client, and proof. The session offers a draft formula for writing the statement, along with an 'unlike' line that sharpens internal thinking but is risky to carry into a bid. Competitors should never be named directly. UVPs need revisiting bid by bid, because clients and competitors change. A bidder that cannot articulate a clear UVP may also have reason to revisit its bid or no-bid decision.
Themes are not a section of the proposal. They run through every part of it, with the executive summary as the strongest opportunity to persuade, and repetition should leave evaluators able to recall them from memory. Eliza also asks approvers and peer reviewers to look past spelling and accuracy and test whether the strategic case is there. In the Q&A she suggests handling long technical responses with an introductory statement that carries the themes, smaller sections and graphics, and shares practical tips for hard-copy and emailed submissions.
Key takeaways
- Decide on one or two win themes before you write a word of the proposal.
- Build each UVP from a feature, the benefit to the client and the proof that you can deliver it.
- Find hot buttons in the evaluation criteria, including what the schedules emphasise and what they leave out.
- Apply the 'so what' test to every theme, UVP and response.
- Carry your themes through the whole proposal, starting with the executive summary.
