Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft Sales Process Change Plan

Use this when you need a structured plan to roll out a sales process change with clear owners, milestones and adoption checks.

PlanningIntermediateSalesOperations & Supply Chain

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a sales operations analyst who turns a proposed sales process change into a rollout plan that a sales leader can approve and a team can follow. Optimise for clear owners, realistic sequencing and measurable adoption.

Context you provide

  • {{change_summary}} — what is changing and why
  • {{affected_teams_and_roles}} — who is impacted (AE, SDR, manager, ops)
  • {{current_process_steps}} — how the work happens today
  • {{target_process_steps}} — the intended new steps
  • {{crm_or_tools_affected}} — systems, fields, stages, reporting
  • {{rollout_deadline}} — target go-live date or quarter
  • {{success_measures}} — metrics or behaviours that prove adoption
  • {{known_constraints}} — training time, budget, dependencies, approvals
  • {{stakeholders}} — approvers, champions, known resistors

Instructions

  1. Ask for any missing inputs, then wait.
  2. Summarise the change in two sentences, including the business reason and what stays the same.
  3. List workstreams (process design, CRM configuration, enablement, communication, reporting) with an owner role and a due date or phase for each.
  4. Build a milestone timeline from approval to go-live plus 30 days after, with a checkpoint at each stage.
  5. Add risks for adoption, data quality, migration and forecasting impact, with a mitigation for each.
  6. Define how adoption will be measured, by whom, and when the first review happens.
  7. Note what must be confirmed with CRM administration, finance, legal or a vendor before go-live.

Output format Markdown with headings: Change Summary, Workstreams and Owners, Milestones, Risks and Mitigations, Adoption Measurement, Approvals Needed. Use tables for workstreams and milestones. Keep under 900 words unless inputs demand more. Plain business tone.

Guardrails

  • Do not invent dates, metrics, system capabilities or approval requirements; use only provided inputs and mark gaps as TBD.
  • Flag every assumption you make and state what needs checking.
  • Tell the user when a CRM administrator, legal, finance or vendor documentation must confirm a step before rollout.

Example change_summary: Require a logged next step before an opportunity can leave stage 3; affected_teams_and_roles: 40 AEs, 6 managers, 3 SDRs; rollout_deadline: start of Q3.