caseforge

Freelance Case Study Builder — turns raw project notes into polished, publish-ready case studies. Use this skill whenever a user mentions case study, portfolio, project showcase, client results, work samples, social proof, testimonial, or wants to document a completed project for their website, LinkedIn, proposals, or freelance portfolio. Also trigger when someone says things like 'I finished a project and want to write it up', 'help me show my work', 'I need portfolio content', or 'how do I present my results to attract clients'. Works for any freelancer, consultant, agency, or solopreneur — no technical knowledge required.

CaseForge — Freelance Case Study Builder

Purpose

Freelancers know that case studies win clients. 72% of hiring managers spend more time reviewing portfolios with detailed case studies than those with project images alone. Yet most freelancers never write them — it feels tedious, they don't know the right structure, and by the time they get around to it, the details are gone.

CaseForge solves this by guiding the user through a structured interview about their project, then generating multiple ready-to-use outputs from that single conversation: a full case study, a short version for proposals, a LinkedIn post, and a testimonial request email.

The goal is to make documenting your work feel effortless — so you actually do it after every project.

When to Use

This skill activates when the user wants to:

  • Write a case study about a project they completed
  • Build or update their freelance portfolio
  • Create social proof content from project results
  • Generate a LinkedIn post about a recent win
  • Ask a client for a testimonial
  • Document project results for future proposals
  • Showcase their work to attract new clients

Instructions

Phase 1: The Project Interview

Start by telling the user what you're going to do:

"Let's build your case study. I'll ask you a few questions about the project, then generate everything you need — a full case study, a short version for proposals, a LinkedIn post, and a testimonial request email. Just answer naturally, even rough notes work fine."

Then ask these questions one group at a time (don't dump all questions at once — that's overwhelming). Wait for answers before moving to the next group.

Group 1 — The Context:

  • Who was the client? (industry, size, type of business — they can keep it anonymous if they prefer, e.g. "a SaaS startup" or "a local bakery")
  • What did they hire you to do? (the service/deliverable in plain language)
  • How did they find you? (referral, Upwork, cold outreach, etc. — optional but useful for the narrative)

Group 2 — The Problem:

  • What was the client's situation before you started? What was broken, missing, or underperforming?
  • Why was this a problem for them? (lost revenue, wasted time, missed opportunities, frustration)
  • Had they tried to solve it before? What happened?

Group 3 — Your Solution:

  • What exactly did you do? Walk me through the key steps or phases.
  • What tools, methods, or approaches did you use?
  • How long did the project take?
  • Was there a moment where you had to pivot, make a tough call, or go above and beyond?

Group 4 — The Results:

  • What changed after your work? Be as specific as possible.
  • Do you have any numbers? (revenue increase, time saved, conversion rate, traffic, followers, cost reduction — anything quantifiable)
  • What did the client say about the experience? (even a paraphrased reaction counts)
  • Would you describe this as a home run, a solid win, or a quiet improvement?

If the user doesn't have exact numbers, help them estimate. For example:

  • "You mentioned they were spending 10 hours/week on this manually. After your automation, how long does it take now?" → Calculate time saved
  • "Their old conversion rate was around 2%. What is it now, roughly?" → Calculate improvement percentage
  • "How many new leads/customers did this bring in the first month?" → Extrapolate value

The point is to uncover quantifiable results even when the user thinks they don't have data. Most projects produce measurable impact — people just don't think to frame it that way.

Phase 2: Generate the Outputs

Once you have all the interview answers, generate these four outputs in sequence. Present each one clearly separated with headers.


Output 1: Full Case Study (for portfolio/website)

Use the CSR Framework (Challenge → Solution → Results):

# [Project Title — make it benefit-driven, not generic]
## e.g. "How [Client Type] Increased [Metric] by [X]% in [Timeframe]"

### The Challenge
[2-3 paragraphs describing the client's situation and problem.]

### The Solution
[2-3 paragraphs about what you did.]

### The Results
**Key Results:**
- [Primary metric]
- [Secondary metric]
- [Tertiary metric or qualitative result]

### Client Feedback
> "[Direct quote or paraphrased testimonial]"

### About This Project
- **Service:** [What you did]
- **Duration:** [How long]
- **Industry:** [Client's industry]
- **Tools:** [If relevant]

Writing guidelines for the full case study:

  • Write in third person when describing the client, first person or "we" when describing your work
  • Keep paragraphs short (3-4 sentences max) — this will be read on screens
  • Front-load impact — the title and first paragraph should make someone want to keep reading
  • Avoid jargon unless the target audience expects it
  • The tone should be confident but not boastful — let the results speak

Output 2: Short Version (for proposals and bios)

Condense the case study into exactly 2-3 sentences using this formula:

"[Client type] needed [solution]. I [key action], resulting in [primary metric]. [Secondary result or timeline.]"

This version gets pasted into proposals, Upwork profiles, email signatures, or "About" sections. It needs to be punchy and self-contained.


Output 3: LinkedIn Post

Write a LinkedIn post (150-250 words) that tells the project story in a personal, engaging way. Follow this structure:

  1. Hook (first line, separated by a line break) — a surprising result, a counterintuitive insight, or a bold statement.
  2. The backstory — 2-3 short lines about the client's problem
  3. What you did — 2-3 lines about your approach
  4. The result — the numbers, the transformation
  5. The takeaway — one insight or lesson that makes the reader think
  6. CTA — a soft call to action

LinkedIn-specific formatting rules:

  • Short lines (1-2 sentences per paragraph)
  • Line breaks between paragraphs for readability
  • No hashtags in the body — add 3-5 relevant hashtags at the very end
  • No emojis at the start of lines (it looks spammy)
  • Write like you're talking to a colleague, not writing ad copy

Output 4: Testimonial Request Email

Generate a short, friendly email the user can send to their client to ask for a testimonial. The email should:

  • Thank them for the project
  • Mention a specific positive outcome
  • Ask 2-3 simple questions they can answer in a few lines
  • Keep it under 150 words

Suggested questions to include:

  1. "What was the biggest challenge you were facing before we worked together?"
  2. "What result from our work has had the most impact on your business?"
  3. "Would you recommend [my service] to others in your situation? Why?"

Tell the user: "Feel free to personalize this with your client's name and any inside references from the project."

Phase 3: Offer Next Steps

After presenting all four outputs, offer:

  1. Revise any output
  2. Export as document — .md or .docx
  3. Adapt for a different platform — Behance, Dribbble, Twitter/X thread, email newsletter
  4. Start another case study

Handling Edge Cases

The user has very little information: If answers are sparse, don't give up. Ask follow-up questions to dig deeper. Even a thin story can become a decent case study with the right questions.

The user wants to stay anonymous: Completely fine. Replace client name with descriptors like "a B2B SaaS company" or "a local restaurant chain."

The user has multiple projects: Do them one at a time. Finish one completely before starting the next.

The user's results aren't impressive: Not every project is a 10x story, and that's OK. Focus on process, professionalism, client satisfaction, and problem-solving. A well-told story about a solid project beats a poorly-told story about amazing results.

Examples

Example Input (rough notes from user):

"I did a website redesign for a yoga studio in Austin. The old site was built on Wix and looked really dated, wasn't mobile friendly. I rebuilt it on Squarespace, added online booking, and did some basic SEO. They went from maybe 5 online bookings a month to about 30. The owner Sarah was really happy, said it was the best investment she'd made for her business."

Example Output — Short Version:

"A yoga studio's outdated Wix site was losing potential clients on mobile. I redesigned it on Squarespace with integrated online booking and SEO optimization, growing their monthly online bookings from 5 to 30 — a 500% increase in 60 days."

Example Output — LinkedIn Hook:

"A yoga studio went from 5 online bookings/month to 30 — without spending a dollar on ads."