Product Management · Legal

Write a full product requirements document for Legal

Use this before handing a feature to the team. Written for a mid-sized law firm.

Your prompt is ready 4 brackets to fill
You are a senior product manager, working with clients, partners and associates at a mid-sized law firm.

## Goal
Write a PRD engineers and designers can build from.

## What matters in Legal
- How customers decide: clients choose on expertise, trust, responsiveness and fees; companies want predictable costs and plain-language advice.
- Numbers that matter: matter turnaround; billable utilisation; realisation rate; client retention; win or settlement rate.
- Rules and standards that usually apply: client confidentiality and privilege; bar council and professional-conduct rules; the law of the relevant jurisdiction; limitation periods and court deadlines; conflict checks; every output is a draft for a qualified lawyer, not legal advice.
- Tools commonly used: document and case management; research databases (Westlaw, SCC Online, Manupatra); Word with tracked changes.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Feature: [NAME AND IDEA]
- Users and problem: [WHO AND WHAT PAIN]
- Business goal: [GOAL]
- Constraints: [TIME, TECH, BUDGET]

## What to do
1. Describe the problem with evidence.
2. Define goals and success metrics.
3. Write user stories with acceptance criteria.
4. Describe user flows and edge cases.
5. List non-functional requirements, risks and open questions.

## What to deliver
- Complete PRD
- User story table
- User flow in Mermaid syntax
- Launch checklist

## Rules
- Keep client confidentiality, professional-conduct rules and jurisdiction (the output is a draft for a qualified lawyer to review, not legal advice) in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to matter turnaround and billable utilisation.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- Each feature is tied to a user problem and a measurable outcome.
- It is written for a mid-sized law firm; nothing in it would read the same for any other business.
- Every item under "What to deliver" is included.
Open in ChatGPT Claude Perplexity

How to use this prompt

  1. Copy the prompt. Press Copy prompt and the full text goes to your clipboard.
  2. Fill the brackets. Use the form above, or replace [NAME AND IDEA], [WHO AND WHAT PAIN], [GOAL], [TIME, TECH, BUDGET] with your own details.
  3. Paste and send. Paste it into ChatGPT, Claude, Gemini and Microsoft Copilot and send. Ask follow-up questions to refine the answer.

Why use this Write a full product requirements document prompt?

This write a full product requirements document prompt is written for a mid-sized law firm. It tells the assistant who the answer is for (clients, partners and associates) and the limits it must respect: client confidentiality, professional-conduct rules and jurisdiction (the output is a draft for a qualified lawyer to review, not legal advice). That context is what turns a generic reply into one a Legal team can use straight away.

Most people type a single line and get a generic answer back. This prompt gives the assistant the role, the context and the structure it needs, so the first answer is already close to what you would hand to your team. Because it is written for Legal, it keeps the focus on what that industry measures: matter turnaround and billable utilisation.

How to get the best answer

  1. Be specific in the brackets: real names, numbers and dates give a far better answer than placeholders.
  2. Paste real material: where the prompt asks for notes, data or text, paste the actual content rather than a summary.
  3. Refine in the same chat: ask "make it shorter", "turn it into a table" or "add more detail on step 2".
  4. Check the result: review it against what you know about matter turnaround and billable utilisation before you share it.

Other industries

Same prompt for other industries

The same write a full product requirements document prompt, rewritten for each industry.

FAQ

Frequently asked questions

Which AI assistant works best with this Write a full product requirements document prompt?

It works in any chat assistant. It suits ChatGPT, Claude, Gemini and Microsoft Copilot best. Paste it in, send it, and ask follow-up questions in the same chat.

What do I need to replace before sending it?

Replace the 4 highlighted brackets – [NAME AND IDEA], [WHO AND WHAT PAIN], [GOAL], [TIME, TECH, BUDGET] – with your own details. The more specific you are, the better the answer.

Is this prompt only for Legal?

This version is written for a mid-sized law firm. The same prompt is also available for 15 other industries, listed on this page.

Is it free to use?

Yes. Copy it as often as you like and use it in your own work. No sign-up is needed.

Can I trust the answer?

Treat it as a strong first draft. Check facts and figures yourself, especially anything with legal, financial, medical or safety consequences.

Keep exploring

Browse more Legal prompts