Turn raw customer interview notes into a case study post that reads like proof, not an ad

You are turning raw customer interview notes into a case study blog post. The post's credibility depends on reading like evidence a skeptical prospect would trust, not like a testimonial an ad team wrote — which means every claim, quote, and causal statement has to trace back to what the customer actually said.

INTERVIEW NOTES
Ops director said: "We were losing about 4 hours a week just reconciling the two spreadsheets before this." Mentioned they also hired a new ops hire around the same time, and switched project tools in Q2 — result likely a combination of all three, not the tool alone.

CUSTOMER NAME AND ROLE
Priya Nair, Director of Operations at a 60-person logistics startup (real name, company approved for use)

QUANTIFIABLE RESULT
Reconciliation time dropped from roughly 4 hours/week to under 30 minutes/week

PERMISSION CONSTRAINTS
Company name and Priya's name and title are approved for use; specific revenue figures mentioned in the interview are not for publication.

AUDIENCE
Ops leads at similarly sized logistics or fulfillment companies evaluating whether to switch tools

CASE STUDY RULES
Lead with the specific, quantified result, not the product name or a generic "success story" framing — a reader deciding whether to keep reading needs the concrete number in the first few lines, not buried after three paragraphs of company background. Structure the body as problem, approach, result, and what changed for the customer specifically — not a feature list dressed up in narrative language; a case study that just walks through the product's feature set with the customer's name attached reads as a product page wearing a disguise, not as evidence. Use direct quotes only where the interview notes actually contain that language — never construct a first-person quote that sounds like something the customer would plausibly say based on the general sentiment of the interview; if the notes describe a sentiment but don't contain a quotable line, paraphrase it in third person instead of manufacturing a quote and attributing it to a real, named person who never said those exact words. Apply the permission constraints exactly as given — if something is marked as not for publication, it does not appear in any form, including a lightly reworded paraphrase that would still let a reader identify the specific detail; if anonymization is required, apply it consistently throughout, not just in the first mention. Be honest about causality: if the interview notes describe the result as influenced by multiple factors — a team reorg, a pricing change, a new hire — alongside the product change, phrase the outcome as "moved after" or "coincided with," not as sole cause, unless the notes genuinely support a direct causal claim; a case study that overclaims causation is the fastest way to get challenged by a prospect's own team during a sales evaluation, and challenged claims damage the whole case study's credibility, not just the overstated line.

OUTPUT FORMAT
1. The case study, structured as problem, approach, result, and impact on the customer.
2. A quote log: every direct quote used, each one confirmed as present in the interview notes verbatim.
3. A note confirming every permission constraint was applied, and where.
4. One sentence stating how causality was framed and why that framing matches what the notes actually support.