Case Study Pipeline: Never Publish a Story the Customer Hasn't Cleared

The problem this kills

A customer case study is one of the most powerful assets your marketing team owns — and one of the riskiest to mishandle. You've seen how it goes: a great story gets nominated, then disappears into someone's inbox. The interview happens, a draft gets written, and then it sits for six weeks waiting on the customer to "take a look." Worse, somewhere along the way a story goes live before the customer signed off on the final wording, the metric, or even being named at all — and now you're on a frantic call with their legal team, pulling a published page down.

The whole process lives in scattered email threads, a tab in a spreadsheet, and a few people's memory. Nobody can answer the simplest questions: which stories are in flight, which are stuck waiting on a customer signature, and which ones actually have written approval on file. You need one place that tracks every story through its real stages — and that makes it physically impossible to mark a story "published" until the customer has cleared the final draft in writing. You do not need to be a developer to build that.

What you'll build

A simple internal web tool for your customer-marketing / content-ops team. You nominate a customer story (the customer, the result or metric, the contact, the sponsoring sales rep). The story moves through clear stages — qualified → interview → draft → customer & legal sign-off → published — and each handoff is approved by the story's owner, so nothing skips ahead. The key control: before a story can reach published, the tool requires the customer's written approval of the final draft to be recorded and attached. Stories stuck waiting on a signature get flagged so they never go cold. When a story is live, it lands in a searchable library, and you can export the whole pipeline as a CSV any time for your reporting.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your current case-study process and who owns each step, the systems and spreadsheets you use, the exact fields and naming on your nominations, your typical and peak volumes, your real approval rules (who clears what, and what "customer sign-off" means in your world), and the messy edge cases like anonymous stories, customers who only approve a quote, or legal redlines. It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the stage workflow, the approval gates, the written customer-approval record, the searchable library, and the pipeline CSV export. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real marketing function needs: login so only your team can use it, row-level security so people only see their own organization's stories, a complete audit trail of every stage change and approval (who, what, when, and why), a hard human-approval gate so a story can't be marked published without the customer's written sign-off on file, and duplicate guards so the same customer story can't end up as two competing records. The whole tool exists to make a careful, defensible decision easy — the AI and the team move the work forward, but a person (and the customer) clears the story before it goes live.

Who it's for

Customer-marketing managers, content-ops leads, and anyone who produces case studies and is tired of chasing approvals through email — and terrified of publishing something a customer never actually cleared. If you can describe the stages a story goes through and what "customer approved" means to you, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be tracking your first real story through the pipeline this weekend.