Prompt Details
Model
(claude-5-opus)
Token size
540
Example input
[Client, Project, or Customer Context]: B2B SaaS startup redesigning its website before a product launch
[Challenge or Starting Situation]: Messaging was too generic, product value was unclear, and the homepage did not reflect the new target audience
[Approach, Process, or Solution]: Customer interviews, positioning workshop, homepage messaging framework, revised copy, proof restructuring
[Results, Evidence, or Outcomes]: New messaging was approved by leadership, launch materials became more consistent, sales team reported clearer positioning in conversations
[Audience, Tone, and Additional Requirements]: B2B marketing audience; strategic, concise, professional; avoid implying conversion improvements without data
Example output
## π Case Study Overview
A B2B SaaS startup undertook a website redesign ahead of a product launch to address generic messaging and unclear product value. The team ran customer interviews, held a positioning workshop, and rebuilt homepage messaging and proof points. Leadership approved the new messaging, launch materials gained consistency, and the sales team reported clearer positioning in customer conversations. No quantitative performance data (conversion rates, traffic, pipeline impact) was supplied, so this case study is framed around clarity and internal alignment outcomes rather than performance metrics.
## π·οΈ Title & Subtitle Options
**Titles:**
1. "From Generic to Grounded: A Pre-Launch Messaging Overhaul"
2. "Finding the Right Words Before Launch Day"
3. "Repositioning a SaaS Homepage for a New Audience"
**Subtitles:**
1. How customer interviews and a positioning workshop clarified product value before launch
2. Rebuilding homepage messaging to match a shifting target audience
3. A structured approach to fixing unclear positioning ahead of a product launch
## π― Recommended Story Angle
The strongest angle is **"clarity as a launch prerequisite."** Rather than framing this as a growth or conversion story (which the data doesn't support), position it as a story about a team recognizing a messaging gap before it became a launch-day liability, and fixing it through structured discovery rather than guesswork. The narrative tension is: *the product was ready, but the story around it wasn't.* This keeps the case study honest and lets the real outcomes β leadership buy-in, cross-team consistency, sales clarity β carry the weight instead of implied performance gains.
## β οΈ The Challenge
Ahead of a product launch, the startup's website no longer matched where the business was headed. Three specific problems surfaced:
- **Generic messaging** that could have described nearly any SaaS product, giving visitors little reason to connect with the offering
- **Unclear product value**, making it hard for prospects to understand what problem was actually being solved
- **A homepage misaligned with the new target audience**, likely a holdover from an earlier positioning or ICP
Left unaddressed, this risked undermining the launch itself β new prospects would land on a site that didn't reflect who the product was now for or why it mattered.
## π οΈ The Approach
The team treated messaging as a discovery problem, not a copywriting problem. The process moved in five stages:
| Stage | Purpose |
|---|---|
| Customer interviews | Surface real language, pain points, and priorities from the actual target audience |
| Positioning workshop | Align internal stakeholders on what the product is, who it's for, and why it wins |
| Homepage messaging framework | Translate positioning into a repeatable structure for headline, subhead, and value props |
| Revised copy | Apply the framework to actual homepage content |
| Proof restructuring | Reorganize existing proof points (customer logos, testimonials, use cases) to support the new positioning |
## π The Process
1. **Started with listening, not writing.** Customer interviews came before any copy changes, ensuring messaging reflected how real prospects described their problems rather than internal assumptions.
2. **Forced alignment early.** The positioning workshop appears to have been the pivotal step β it's the point where scattered internal opinions about "what we do" would have been reconciled into one shared narrative.
3. **Built a reusable framework, not a one-off page.** Creating a messaging framework (rather than just rewriting the homepage) suggests the team wanted consistency across future launch materials, not just a single page fix.
4. **Rebuilt proof to match the new story.** Restructuring proof points β rather than generating new ones β indicates the goal was to make existing evidence support the new positioning, a detail worth highlighting since it shows resourcefulness within real constraints.
*(Note: the specific timeline, team size, and who conducted the interviews/workshop weren't provided β flagged below as a proof gap.)*
## π The Outcomes
- **Leadership approved the new messaging** β indicating the positioning workshop successfully resolved internal disagreement or uncertainty about direction
- **Launch materials became more consistent** β suggesting the messaging framework was adopted beyond the homepage alone
- **Sales team reported clearer positioning in conversations** β a frontline signal that the new narrative was usable in real prospect interactions, not just internally approved copy
No conversion, traffic, engagement, or revenue data was provided, and none should be implied. These outcomes are about **internal alignment and message usability**, not performance lift.
## π¬ Proof & Evidence
**What's currently supported:**
- Leadership approval (stated as fact)
- Sales team feedback on clarity (stated as fated)
- Increased consistency across launch materials (stated as fact)
**Where this case study is currently thin, and what would strengthen it:**
- A direct quote from a sales rep or leadership on the "before vs. after" experience
- A side-by-side comparison of old vs. new homepage headline/subhead copy
- Any quantitative signal post-launch (even directional, e.g., "sales cycle conversations shortened" or "fewer clarifying questions from prospects")
- Specifics on the customer interview sample (how many, what roles) to lend the discovery phase more weight
- A visual of the messaging framework itself, which would double as a reusable artifact for readers
## π§ Key Lessons & Takeaways
- **Messaging problems are often positioning problems.** The fix started with interviews and workshops, not a copywriter rewriting the homepage in isolation.
- **Internal alignment is a real, measurable outcome.** Leadership approval and sales adoption are legitimate wins even without traffic data β they reduce internal friction that would otherwise resurface post-launch.
- **Proof doesn't always need to be created from scratch.** Restructuring existing proof points to fit a new narrative is a practical, resource-light way to support repositioning.
- **A framework outlasts a single page.** Building a reusable messaging structure paid off in cross-material consistency, not just homepage quality.
## βοΈ Short Case Study Version
*For proposals, sales decks, or a website snippet:*
> Ahead of a major product launch, this B2B SaaS startup faced a familiar problem: generic messaging, unclear product value, and a homepage built for the wrong audience. Rather than rewrite copy in isolation, the team ran customer interviews and a positioning workshop to rebuild their messaging from the ground up β then translated that into a reusable homepage framework and restructured proof points to match. The result: leadership signed off on the new direction, launch materials became consistent across the board, and the sales team reported clearer, easier positioning conversations with prospects.
## π£ CTA & Repurposing Ideas
**CTA options (choose based on placement):**
- "Facing a similar messaging gap before launch? Let's talk about your positioning."
- "See how a structured discovery process can clarify your product story before you scale it."
- "Book a positioning audit before your next launch."
**Repurposing ideas:**
- Pull the 5-stage approach table into a standalone "How We Approach Messaging" service page
- Use the short version as a LinkedIn post or newsletter case study teaser
- Turn the "Key Lessons" section into a checklist lead-magnet for prospects evaluating their own messaging
- If a before/after headline comparison becomes available, that single visual could anchor a much stronger social or ad creative version of this story
---
**One flag before this goes anywhere external:** since there's no quantitative outcome data, I'd avoid any headline or pull-quote that could be read as implying a performance or conversion improvement β the current draft sticks to alignment and clarity claims, which is the honest and defensible framing given what's supplied.
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View SelectBy purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
Turn real project or client results into clear, credible case studies with challenge, strategy, process, outcomes, proof points, and lessons learned. This prompt helps agencies, consultants, freelancers, SaaS teams, service businesses, and marketers transform raw project notes into polished case studies without inventing results or exaggerating impact. ππ
...more
Added over 1 month ago
