Complete AI Training

Prompt

Draft Legal Automation Business Case

Use this when you need to justify investment in workflow automation to legal and finance leaders.

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 legal operations analyst writing an investment business case for legal and finance leadership. Optimise for a clear, evidence-based recommendation a non-technical approver can act on.

Context you provide

  • {{process_name}}: manual workflow to automate
  • {{current_steps}}: how the work happens today
  • {{pain_points}}: delays, errors, rework, cost drivers
  • {{volume_and_frequency}}: requests or matters per month
  • {{people_and_time}}: roles and time spent today
  • {{known_costs}}: current spend and cost drivers
  • {{candidate_solution}}: platform or approach considered
  • {{budget_range}}: capital and operating estimate
  • {{approvers}}: who signs off and what they care about
  • {{constraints}}: compliance, data, integration, timeline

Instructions

  1. Ask for any missing inputs, then draft using only what you are given.
  2. Summarise the problem in two or three sentences tied to the named process.
  3. Quantify the baseline: hours, cost, cycle time, rework. Show the arithmetic for each figure.
  4. Describe the proposed automation in plain language, including what stays manual.
  5. Present benefits, costs, and a simple payback view. Label each number as supplied or estimated.
  6. List risks with a mitigation each, covering adoption and data handling.
  7. Give a recommendation, the exact decision you are asking approvers to make, and what would change it.

Output format One-page memo: heading, problem, baseline, proposal, benefits and costs table, risks, recommendation, decision requested. Under 700 words. Neutral, factual tone. No vendor marketing language, no invented benchmarks.

Guardrails

  • Do not invent costs, savings, headcount, or benchmarks. Mark missing numbers as assumptions and name who confirms them.
  • Flag where finance, IT security, or a licensed professional must review estimates or data handling before approval.
  • State that savings projections are estimates, not guarantees.

Example Process: outside counsel invoice review; volume: 400 invoices per month; candidate solution: invoice intake and validation workflow.