Library/Sales Operations, CRM & Productivity/Sales Tech Stack Hygiene/Write a PRD for a Sales Tool or RevOps Initiative
TestedSales Operations, CRM & ProductivitySame-Day Use (under 30 min)

Write a PRD for a Sales Tool or RevOps Initiative

Generate a structured internal PRD with problem statement, user stories, acceptance criteria, and success metrics.

About this prompt

This prompt helps RevOps specialists and sales managers write a lightweight product requirements document for a sales tool, process improvement, or automation initiative. It takes the initiative name, the problem it solves, who it's for, current and desired states, success metrics, estimated effort, and priority, then produces a structured PRD with seven labeled sections. Use it when you need to hand off a RevOps initiative to an engineering team, operations team, or external vendor and need a clear written spec.Most RevOps initiatives fail not because the idea is wrong but because the requirements were never written down clearly enough for someone else to build. This prompt generates a seven-section internal PRD — problem statement, proposed solution, user stories, acceptance criteria, out-of-scope items, risks and dependencies, and 30/60/90-day success metrics — from a short set of inputs about your initiative. Fill [INSERT] fields for initiative name, problem, current state, desired future state, and success metrics with specifics; vague problem descriptions produce vague PRDs. The user stories section ([PERSONA], [ACTION], [OUTCOME]) requires you to name the actual users who will interact with the tool — AEs, SDRs, sales managers, or RevOps — which forces a useful clarity about who the initiative is really for. The out-of-scope section is often the most valuable part of a PRD; the prompt will draft it, but review it carefully to make sure it excludes things your team will otherwise assume are included. Use this prompt when requesting engineering or operations work, not for internal planning documents that don't require a handoff. For initiatives that need formal product management involvement, this prompt produces a starting draft rather than a final document — expect one revision cycle with the receiving team.

The prompt

You are a Revenue Operations product manager. I need to write a PRD for the following initiative: Initiative name: [INSERT] Problem it solves: [INSERT] Who it's for: [E.G. AES, SDRS, SALES MANAGERS, R
The rest of this prompt is Pro.Copying the full text is Pro. Browsing stays free, and 100 prompts are free in full.
Copy prompt
☆ Save to library
Send to a teammate
Email it
Link copied — paste it in Slack
Copying the full text is Pro.

Variables to replace

INSERT | E.G. AES, SDRS, SALES MANAGERS, REVOPS | SMALL / MEDIUM / LARGE | HIGH / MEDIUM / LOW | PERSONA | ACTION | OUTCOME

How to run it

  1. Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot — it's tuned to run in any of them.
  2. Replace the variables — swap each bracketed token for your deal's specifics. The variables list above explains every field.
  3. Make it yours — run it, keep what's strong, and tighten your inputs on the next pass. The prompt improves with your context.

What good output looks like

Make it yours

StageOngoing/Cross-Stage
SeatRevOps / Sales Ops, Sales Manager
DifficultyIntermediate
Time to valueSame-Day Use (under 30 min)
Works withAI-Agnostic
CategorySales Operations, CRM & Productivity
Promptifi ProFull text of all 2,900+ prompts, every workflow, unlimited saves.Start Pro — $4.99/moor $99 once, lifetime
You're ProFull library open. Copy, save, and chain anything.

Stop rewriting. Start closing.

Copy prompt
Start Pro — $4.99/mo