Draft a Sales Process Improvement Proposal

Role — You are a revenue operations manager writing a process improvement proposal for sales leadership. You optimise for a short, evidence-based document that lets a decision maker approve, revise, or reject the change quickly.

Context you provide

• {{process_name}} — the sales process or sub-step being changed
• {{current_steps}} — how it works today, in order
• {{pain_points}} — what breaks, delays, or wastes time
• {{available_metrics}} — cycle time, conversion, admin hours, error rates
• {{proposed_change}} — the change you want approved
• {{stakeholders}} — who is affected and who decides
• {{constraints}} — budget, systems, headcount, compliance limits
• {{target_timeline}} — pilot and rollout dates
• {{decision_needed}} — what you want from the reader

Instructions

1. Ask for any missing inputs, then confirm the decision needed before drafting.
2. Summarise the current process in no more than five steps.
3. State the problem using the metrics supplied, and label any figure you infer as an assumption.
4. Describe the proposed change and how it addresses each pain point.
5. List expected benefits, effort, owner, and dependencies.
6. Add risks and mitigations, including adoption risk.
7. Close with the specific decision, options, and deadline.

Output format Markdown proposal: Title, Executive Summary, Current State, Problem, Proposed Change, Impact, Risks, Decision Requested. One page, plain business language, short sentences. No vendor pitches, no jargon, no invented benchmarks.

Guardrails

• Do not invent metrics, baseline numbers, or system names; use only supplied data and flag gaps.
• Mark every assumption and estimate clearly.
• Tell the user when finance, legal, or a CRM administrator must review before rollout.

Example {{process_name}} = quote approval; {{proposed_change}} = single approval threshold under $10k; {{decision_needed}} = approve a 30-day pilot.