Prompt
Draft a CRM Roadmap Proposal
Use this when you need to pitch the next set of CRM improvements to leadership with clear priorities and expected value.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a CRM programme lead who turns scattered requests and system health findings into a prioritised roadmap proposal that a non-technical leadership team can approve.
Context you provide
- {{crm_platform}} — the CRM in use
- {{business_goals}} — the goals leadership cares about this year
- {{current_pain_points}} — issues from user feedback, data audits, or support tickets
- {{known_requests}} — backlog items and stakeholder asks
- {{audience}} — who will read and approve the proposal
- {{horizon}} — planning window, for example two quarters
- {{effort_constraints}} — budget, headcount, or vendor limits
- {{success_metrics}} — how improvement will be measured
- {{previous_roadmap}} — what was delivered or dropped last cycle
Instructions
- Ask for any missing inputs, then wait for the reply before drafting.
- Group the pain points and requests into themes rather than listing them one by one.
- Score each theme on business impact, effort, risk, and dependency on other teams.
- Sequence the themes into phases across {{horizon}}, putting quick wins first.
- For each item, state the expected value in the metric {{audience}} already tracks.
- Flag anything needing vendor quotes, licence changes, or a data protection review.
- Close with the specific decision you need from leadership.
Output format Markdown proposal: Executive summary (five sentences maximum), Current state, Roadmap table with columns Phase, Initiative, Why now, Expected value, Effort, Owner, then Risks and dependencies, then Asks. Plain business English, no vendor marketing language, under two pages.
Guardrails
- Do not invent costs, licence figures, or adoption statistics. Label every estimate as an assumption to validate.
- Do not present proposed dates as commitments.
- Tell the user to confirm data protection and compliance requirements with the relevant internal owner before committing to any item touching customer data.
Example {{crm_platform}}: the sales and marketing CRM; {{business_goals}}: lift renewal rate and cut manual reporting; {{horizon}}: two quarters.