How to Write Case Study from Competitor Research (With Citations)

The Competitor Case Study: Strategic Learning From the Public Record

Founders and solo operators who track competitors closely accumulate more strategic intelligence than they ever convert into organized learning. Pricing changes, positioning shifts, market entry decisions, failed product bets, and successful pivots are all documented in the public record — in blog posts, customer reviews, press releases, founder interviews, and independent analysis — but rarely assembled into a format that makes the strategic lessons accessible.

A competitor case study from your research collection does exactly this: it takes your accumulated competitor intelligence and structures it as a narrative of what a specific competitor did in a specific situation — what challenge they faced, what they decided to do, what happened, and what a founder in your position can learn from it.

This is strategic pattern learning, not intelligence gathering. The goal isn't to expose a competitor's internal operations or copy their tactics. The goal is to understand how a company navigated a market situation you might face, so you have a data point beyond your own assumptions when making similar decisions.

---

The Ethical Boundaries: Only Public Information

Competitor case studies from public research have one non-negotiable rule: every source must be publicly available information that anyone could access.

This means:

• Publicly visible pricing pages (but not pricing obtained through deception)
• Published product documentation and changelog announcements
• Public customer reviews on G2, Capterra, Trustpilot, App Store
• Press releases, blog posts, and company-published content
• Founder interviews, podcast appearances, and conference talks
• Independent journalism, analyst reports, and community discussions
• Public financial filings (SEC filings, investor letters if published)
• Public job postings (these reveal organizational priorities)

This does not mean:

• Information obtained by misrepresenting who you are to a competitor
• Internal documents shared by ex-employees or current employees without authorization
• Information from paid tools that aggregate proprietary data

A competitor case study built on public information is a legitimate strategic learning tool. One built on misrepresented access or stolen internal information is not, regardless of how compelling the learning.

---

What Competitor Case Studies Are Best For

Not every competitor situation warrants a case study. The format is most valuable for:

Situation	What the case study illuminates
A competitor navigated a pricing model transition	How they communicated it, what churn looked like (if reported), what they learned
A competitor entered a market you're targeting	Their go-to-market approach, the obstacles they hit, what traction they found
A competitor failed to retain a customer segment you're competing for	What drove the dissatisfaction, what they changed (or didn't)
A competitor successfully expanded upmarket or downmarket	Their positioning changes, feature investments, how long it took
A competitor recovered from a public crisis	What they did, in what sequence, what the public record shows about recovery

In each case: one specific situation, documented from public sources, with lessons that apply to your own decisions.

---

The Competitor Case Study Structure

A competitor case study follows the same arc as any case study, adapted for the public-sources-only constraint:

COMPETITOR CASE STUDY: [Competitor Name] — [Specific Situation]
[Date] | Research period: [Date range of sources] | Prepared by: [Name]
For: [Internal use only — not for distribution]

CONTEXT
Who is this competitor? What market position and scale did they have 
entering the situation? What was the relevant market context?
(All from public sources: company website, funding announcements, 
 press coverage, product description)

THE SITUATION THEY FACED
What specific challenge, opportunity, or decision point were they dealing with?
When did it become visible in the public record?
What was at stake for them?

WHAT THEY DID
What did they publicly announce, ship, or change?
In what sequence? With what timeline?
Based only on: press releases, blog posts, changelog, job postings, interviews

WHAT HAPPENED (from public record)
What do customer reviews say?
What did analysts or independent coverage report about outcomes?
What did the company itself report (with appropriate source attribution)?
Be explicit about what's self-reported vs. independently observed.

WHAT I TAKE FROM THIS
2-3 lessons specific to our situation.
Under what conditions does this competitor's experience apply to us?
What's different about our context that might make their experience not generalize?

SOURCES
[All public sources: company, independent journalism, reviews, analyst — 
organized by section with URLs and access dates]

---

Step-by-Step: Write a Competitor Case Study From Your Research

Step 1: Define the Situation and the Learning Question

What specific situation in your competitor's history are you studying, and what do you want to learn from it?

The best-defined learning questions have two parts:

1. "What did [Competitor] do when [specific situation]?"
2. "What does their experience suggest about how we should approach [related decision]?"

The second question is what makes this strategic rather than just informational. You're not documenting the competitor for its own sake — you're extracting a data point for a decision you're facing or likely to face.

Step 2: Audit Your Research Collection for Public Source Coverage

Check what you have against the five case study sections:

CONTEXT coverage: Do I have public information establishing who they are 
and what their market position was before the situation?

SITUATION coverage: Do I have sources documenting when and how the situation 
emerged in the public record? (Press coverage, their blog, customer reviews 
showing a shift)

APPROACH coverage: Do I have documentation of what they specifically did? 
(Press releases, changelog, feature announcements, founder interviews)

OUTCOME coverage: Do I have independent evidence of what happened? 
(Review platforms from the relevant period, analyst coverage, 
press reports — not just their own claims)

LESSONS coverage: Do I have any retrospective accounts? 
(Founder interviews about the decision in hindsight, 
 analyst post-mortems, community retrospectives)

Missing outcome coverage from independent sources is the most common gap. Company-reported outcomes are self-selected and should be used with explicit attribution: "According to the company's published announcement..." not "the results were..."

Step 3: Date All Your Sources

Competitor research has a short shelf life. Before writing, note the date of every source you plan to use:

• Pricing claims → when was the pricing page last observed? (It may have changed)
• Customer reviews → which time period do they reflect?
• Product feature claims → from what changelog or announcement?
• Outcome statistics → when were they reported?

A competitor case study that includes outdated pricing as if it's current, or reviews from 2021 describing a product that's been significantly updated, is worse than no research.

Step 4: Draft the Case Study

I'm writing a competitor case study about [Competitor]'s [specific situation] 
from [date range] of public research.

Learning question: What does their experience suggest about [our related decision]?

My public sources by section:

CONTEXT:
[Source type: company website / press coverage]
Key facts: [Market position, scale, relevant background]
Source: [Publication, date, URL]

THE SITUATION:
[Source type: press coverage / customer reviews showing shift]
What became visible: [What the public record shows about when and how]
Source: [Publication, date, URL]

WHAT THEY DID:
[Press release / blog post / changelog / interview]
Actions: [Specific decisions or announcements, with dates]
Sources: [Publications, dates, URLs]

WHAT HAPPENED:
[Customer reviews — period: ___] showing: [...]
[Independent press coverage] reporting: [...]
[Company-reported — note: self-reported]: [...]
Sources: [All, with dates]

My proposed lessons: [With conditions on our context vs. theirs]

Draft:
CONTEXT (1-2 paragraphs, public sources)
THE SITUATION (1-2 paragraphs, dated)
WHAT THEY DID (2-3 paragraphs, sequenced with dates)
WHAT HAPPENED (1-2 paragraphs, distinguish self-reported from independently reported)
WHAT I TAKE FROM THIS (2-3 bullets with conditions)
SOURCES (all public sources, URLs and access dates)
Flag any outcome claim based only on company-reported data.

Step 5: Write the Lessons With Honest Scope Conditions

The most important part of a competitor case study is the scope conditions on the lessons. One company's experience in one market situation is a single data point. It tells you what was possible or what happened in their context — not what will happen in yours.

Useful scope conditions:

• "This applies to us if we're considering a similar pricing transition, but our installed base is X% smaller than theirs was — the churn risk may be proportionally different"
• "Their experience with this go-to-market approach applied to a market where [condition]. Our market has [different condition], so their experience is a partial guide at most"
• "Their response took 18 months to show results. If we face a similar situation, expect a similar timeline rather than faster resolution"

Scope conditions make the lessons more useful, not less. A lesson without conditions implies universality that a single case can't support.

---

Before/After Worked Example

Context: A founder is considering whether to introduce a free tier for their B2B SaaS product. She wants to learn from how a competitor made the same decision two years ago.

Public research collected:

• Competitor's Product Hunt launch post from 2022 (context: product description at that time)
• TechCrunch article about competitor's Series B, 2022 (context: scale, market position)
• Competitor's blog post announcing the free tier, March 2023 (what they did)
• G2 reviews from Q1-Q2 2023 (customer response to free tier)
• Competitor's blog post: "One Year With Our Free Tier" (retrospective, March 2024)
• SaaS Metrics report covering freemium conversion rates in their category (industry context)

Before (informal notes): "[Competitor] added a free tier in 2023. It seems like it worked? Their reviews are pretty good and they're growing. Maybe we should do the same."

Not useful for decision-making. No specific facts, no timeline, no conditions on the lesson.

After (competitor case study):

---

COMPETITOR CASE STUDY: [Competitor] — Introduction of Freemium Tier, 2023 January 2025 | Research period: 2022–2024 | Prepared by: [Founder Name] For: Internal use only

CONTEXT [Competitor] launched in 2020 in the [category] space. By March 2023, when they introduced the free tier, they had raised a Series B of $X million and were reportedly serving approximately 800 paying customers (TechCrunch, 2022). Their pricing at that point was $49/month starter, $99/month professional — a two-tier paid structure with no free option. Their Product Hunt profile (2022) positioned the product as "enterprise-grade [category] for SMBs."

THE SITUATION THEY FACED In January 2023, [Competitor's] founder mentioned in a podcast interview that their trial-to-paid conversion rate was "lower than we'd like" and that many trial users were "not yet at the stage where they could justify the [pricing]." This suggests a market qualification problem — potential customers who needed more time or smaller initial commitment to reach readiness to pay. (Podcast interview, January 2023 — publicly available)

WHAT THEY DID In March 2023, [Competitor] launched a free tier with a seat limit (up to 3 users) and feature limitations (no integrations, no analytics, no team sharing). Paid tiers remained at $49/month and $99/month. The free tier was announced on their blog as "a way for teams to see value before committing." A separate blog post the same week from their founder described the decision: "We wanted to make the no-brainer choice for someone who wasn't sure yet." (Blog post, March 2023)

WHAT HAPPENED G2 reviews from Q1-Q2 2023 (47 new reviews in that period) showed predominantly positive response from users who started on the free tier — "finally a way to try without the credit card" appearing in multiple reviews. One negative review noted that the free tier's limitations became limiting faster than expected.

One year later, the company's own blog post ("One Year With Our Free Tier," March 2024) reported that "the free tier now accounts for 40% of new signups, and we convert at approximately the same rate as our paid trials previously." This is self-reported and was not independently corroborated, but the framing is specific enough to be useful as a directional reference. (Company blog, March 2024)

Industry context: SaaS Metrics research on freemium conversion rates in B2B software shows a wide range (1-5% for broad freemium; 10-15% for product-qualified-lead-focused freemium), suggesting the "40% of signups" statistic doesn't reveal the conversion rate that matters most. (SaaS Metrics Report, 2024)

WHAT I TAKE FROM THIS

• Free tiers may reduce conversion rate friction without changing qualification: [Competitor's] founder described a trial-conversion problem before the free tier. One year later, self-reported conversion was similar to paid trials — which suggests the free tier didn't solve the qualification problem, it changed the channel. We should expect the same unless we have evidence our current trial structure has a different root cause.
• Seat and feature limits on free tiers drive upgrade urgency — but also early churn: the one G2 review noting feature limits "became limiting faster than expected" suggests some users hit the wall without converting. Our product's limiting factors would need to be selected carefully to create genuine upgrade motivation, not frustration.
• Self-reported metrics from competitors require calibration against industry benchmarks: the competitor's "40% of signups" statistic is interesting but incomplete without conversion rate data. We should define our own success metrics before launching a free tier, not benchmark against their stated conversion.

SOURCES

1. TechCrunch. "[Competitor] raises Series B." 2022. [URL]
2. [Podcast name]. Founder interview. January 2023. [URL]
3. [Competitor] Blog. "Introducing our free tier." March 2023. [URL]
4. G2 Reviews: [Competitor]. Q1-Q2 2023. g2.com. Accessed January 2025.
5. [Competitor] Blog. "One Year With Our Free Tier." March 2024. [URL]
6. SaaS Metrics Report. Freemium Conversion Benchmarks. 2024. [URL]

---

Specific timeline, all sources public, self-reported metrics flagged, lessons with conditions on our specific context.

---

Prompts to Reuse

Competitor Case Study

I'm writing a competitor case study about [Competitor]'s [situation] 
from [date range] public research. For internal use only.

Learning question: What does their experience suggest about [our decision]?

Public sources by section:
CONTEXT: [Source + facts + date]
SITUATION: [What became visible, when, from what public source]
APPROACH: [Announcements, product changes, interviews + dates]
OUTCOME: [Customer reviews — period; independent press; company-reported — note]
RETROSPECTIVE: [Any later accounts — dates]

My context vs. theirs: [How our situation differs]
Proposed lessons: [With scope conditions]

Draft:
CONTEXT (public sources)
THE SITUATION (dated)
WHAT THEY DID (sequenced with dates)
WHAT HAPPENED (distinguish self-reported from independent)
WHAT I TAKE FROM THIS (lessons with scope conditions)
SOURCES (all public, with URLs and access dates)

---

Key Takeaways

1. Only public information: pricing pages, customer reviews, press releases, published interviews, SEC filings — not information obtained through deception or unauthorized access.
2. Distinguish self-reported outcomes from independent evidence: company blog posts about their own success are self-selected; customer reviews and third-party analyst reports are more reliable for outcome assessment.
3. Date everything: pricing changes, customer reviews that reflect a specific product version, and company-reported metrics are time-sensitive.
4. Write lessons with scope conditions: one competitor's experience is a single data point — the conditions under which it applies to your situation matter as much as the experience itself.
5. This is for internal use: a competitor case study belongs in your internal knowledge base or strategy file, not in external communications about the competitor.

---

Conclusion

A competitor case study from your research collection is the most directly strategic output format in this cluster — it converts competitive intelligence into structured learning about how a specific market situation unfolded and what the lessons are for your own decisions. The constraint to publicly available information isn't just ethical — it's also practical: public sources are independently verifiable, which makes the case study more credible than one that relies on contested internal information. Write with specific dates, distinguish source types, flag self-reported outcomes, and end with scope conditions that connect the competitor's experience to your own context.

Try WebSnips free — clip competitor press releases, product announcements, customer reviews, and founder interviews into organized research collections, so your next competitor case study starts from a research base that's already organized by company and time period.