Speed wins when the buyer still remembers the call. Most SaaS teams lose deals in the gap between enthusiasm and the proposal landing.
The one-hour proposal sprint
- 0-10 min: Pull call notes into a structured brief (goal, budget band, timeline, decision makers).
- 10-25 min: Select scope blocks from your library. Do not rewrite from scratch.
- 25-40 min: Apply pricing rules. Let the sheet or system calculate totals.
- 40-50 min: Internal sanity check, delivery lead confirms capacity, not just sales enthusiasm.
- 50-60 min: Export and send while you still have a thread open with the buyer.
Prepare these once, reuse forever
- Five scope narratives you actually deliver (not aspirational service pages).
- Three pricing tiers with clear upgrade paths.
- Two case studies matched by industry or problem, not logo prestige.
- A one-page "how we work" appendix clients stop asking about in calls.
Measure what matters
Track median hours from discovery call to proposal sent. If it is over 24 hours, fix process before you fix copy.
Use this as a working checklist inside your team first. When the same steps repeat every week and spreadsheets start breaking, that is usually the moment to scope a reusable pricing flow with plan rules, trial logic, internal sign-off and checkout-ready handoff as an owned system. See the relevant Standen service · More guides · SaaS ops audit.