Strategy
Part of Why proposal software strategy needs a plan before the 2027 buying cycle
Proposal software: a 90-day rollout plan
A practical proposal software rollout plan for an England-based firm, with three 30-day blocks, owners, measures, a worked example and checklist.
What to take away
- A ninety day proposal software rollout runs in three 30 day blocks: set the baseline, rebuild the templates, then measure. It suits a professional services firm in England with 8 to 12 people quoting from Word and email.
- Give one named owner per block. Without an owner, the plan becomes a software trial nobody finishes.
- Model the spend before you sign. A team paying £400 a month for quoting software adds £4,800 a year to its cost base.
- Keep an audit trail of who changed a price or a discount. That record protects you when a client disputes an invoice.
Why does a ninety day plan beat a slow rollout?
A long rollout lets bad habits harden. If your team keeps editing old Word documents while a new tool sits idle, you have paid for storage, not a quoting process.
Ninety days is long enough to change templates and short enough to hold attention. If you are still deciding what the plan should achieve, the proposal software strategy and planning guide for 2027 sets the objectives this plan then executes.
What should happen in days 1 to 30?
Days 1 to 30 are for the baseline. Pull the last 20 quotes and record four things: time to produce, rounds of edits, who approved the final price, and whether it was accepted.
Days 1-30 baseline audit
- Pull the last 20 quotes
- Record time to produce
- Record rounds of edits
- Record who approved final price
- Record whether accepted
- Name one owner for this block
Most firms find the bottleneck is not writing. It is waiting. A quote sits in an inbox while a director is in meetings, and the client cools.
Name one owner for this block. That person should confirm which outcome claims your sales team makes. UK advertising claims are governed by the CAP Code and the sanctions the ASA can apply for non-compliant marketing.
What should happen in days 31 to 60?
Days 31 to 60 are for rebuilding. Build one master template with locked pricing tables, optional modules and an expiry date on every quote.
Parallel week: new tool vs old
New tool
- Team split
- Half the team
- Measure
- Time to first draft
- Ignore
- Satisfaction scores
Old method
- Team split
- Half the team
- Measure
- Time to first draft
- Ignore
- Satisfaction scores
Then run a parallel week. Half the team quotes in the new tool, half stays on the old method. Compare time to first draft, not satisfaction scores.
If your firm sells to public bodies, check what evidence of supply chain control your buyer expects. Use that requirement when assessing the software and its supplier.
What should happen in days 61 to 90?
Days 61 to 90 are for measurement. Publish three numbers weekly: quotes issued, median days to acceptance, and manual price overrides.
A high override rate means your pricing rules are wrong, not that your salespeople are careless.
Document the process as a one-page checklist and store it where the team works. Set a review date 90 days out. Teams that skip this step repeat avoidable errors, many catalogued in proposal software strategy mistakes in England.
Use this one-page process checklist:
- Name the owner and confirm the outcome for each 30-day block.
- Check the master template, pricing tables, optional modules and quote expiry date.
- Confirm who approves final prices and how price changes are recorded.
- Record the parallel-week comparison and whether the team will switch.
- Log quotes issued, median days to acceptance and manual price overrides each week.
- Set the review date and record the reason if the team reverts.
Worked example
A ten-person consultancy in Leeds quotes about 30 times a month. Assume an average deal value of £6,000 and a current win rate of 25 per cent.
If faster turnaround lifts the win rate to 28 per cent, that is one extra won deal a month, about £6,000 of revenue. Against a software cost of £400 a month the payback is clear, but only if the change is real. Track it over two months.
How do you keep the plan honest?
Keep a simple log of the date, the change made, and the number it moved. Review it monthly with the owner of the next block.
Avoid adding features mid-plan. Every new field or approval step slows the quote and gives the team a reason to go back to email. Long-run context helps: business population data from GOV.UK's 2019 estimates shows how the small-firm base has shifted over time. That is useful when you set targets for a sector rather than one client.
Common questions
How much should a small firm budget for the first 90 days?
For a team of ten, budget software plus internal time. One labelled example: £400 a month, plus 20 hours of setup in month one at your own internal rate.
Do we need legal review before switching tools?
Consider legal review if your terms, data processing or retention rules change. If the tool stores client pricing or related personal data in another country, check whether the UK GDPR's international-transfer rules apply and consult the ICO's guidance before migrating live quotes.
What if the team refuses to move off Word?
Run the parallel week in days 31 to 60 and publish the time difference. Peer evidence changes behaviour faster than an instruction.
When should we stop the plan?
Stop only if median time to acceptance has not improved after two full months of parallel running, and record why before reverting.
