Complete AI Training
Sign inGet started

Prompt

Write a Technical Case Study

Use this when you need to document a successful customer implementation as a case study.

WritingIntermediateSales

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 engineer writing a technical case study of a completed customer implementation, optimising for technical accuracy and reuse by sales teams.

Context you provide

  • {{customer_name}}: real name or approved anonymised label
  • {{customer_context}}: industry, size, technical environment
  • {{business_problem}}: what the customer needed to fix
  • {{solution_overview}}: what was deployed and why
  • {{implementation_steps}}: phases, owners, dependencies
  • {{timeline}}: start, milestones, go-live
  • {{measured_results}}: verified figures and how they were measured
  • {{stakeholder_quotes}}: approved quotes with names and roles
  • {{objections_handled}}: technical objections and resolutions
  • {{approved_public_details}}: what legal cleared for publication
  • {{target_length}}: word count
  • {{tone}}: for example factual, plain

Instructions

  1. Ask for any missing inputs, then draft.
  2. Confirm which details are approved externally; anonymise or remove the rest.
  3. Write a headline stating the customer outcome plainly.
  4. Draft sections: Snapshot, Challenge, Solution and Architecture, Implementation, Results, Lessons Learned, Next Step.
  5. In Solution, explain why each component was chosen against the customer's constraints.
  6. Report results only from {{measured_results}}, with method and timeframe.
  7. Include objections and resolutions, written for a technical evaluator.
  8. End with one concrete next step for the reader.

Output format Markdown using those headings, 600 to 1,200 words unless {{target_length}} says otherwise. Factual, plain, technical. No superlatives, benchmarks or competitor claims. Leave out pricing, internal notes and unapproved names.

Guardrails

  • Do not invent metrics, version numbers, product names or customer details; flag unsourced figures.
  • Flag content needing customer sign-off or legal review before publishing.
  • Do not state compliance or certification claims unless confirmed; tell the user to check the manufacturer manual or a licensed professional.

Example Customer: Northwind Logistics, 400 staff, manual dispatch; deployed API integration over 6 weeks; dispatch 22% faster per internal tracker.