Teardown No. 60 · Case studies

87 pages of context before the first prompt: how Stan Rymkiewicz writes customer case studies with Claude Code

Stan Rymkiewicz is Head of Growth at Default. He wrote a customer case study for his employer with a Claude Code workflow. Before sending any prompt, he compiled a Google Doc of over 87 pages from sales calls, onboarding calls, emails, Slack DMs and a case study interview. From that doc and a positioning memo he built a story map, a style guide in the customer's own language and an outline. Then he generated the full draft and edited it. He says the whole thing took about 2 hours and claims the output is "5x better than a team of writers." He does not state any distribution results.

Stan RymkiewiczVerified Oct 26, 2026Markdown copy

The problem

He opens with “I used to hate writing case studies.” He describes the work as “time-consuming” and says it “feels hard to outsource.” He calls case studies “Expensive, yet critical.”

The blueprint (as he describes it)

  1. Gather context first. “Before I sent a single prompt, I gathered context.” For this one customer he pulled:

    • All sales call transcripts (2 calls)
    • All onboarding calls (2 calls)
    • All emails and Slack DMs (45+ messages)
    • A case study call transcript (1 meeting)
    • Case study notes (1 page)

    He compiled these into a Google Doc with over 87 pages of content. Then he opened Claude Code.

  2. Build a story map. He used the positioning memo and the context doc to create a “story map.” This document stated the facts about the customer, their situation, competitors and pain points. He says he “reviewed it heavily” to match what he heard on the case study call and the story he wanted to tell.

  3. Build a style guide from customer language. He used several other customers’ transcripts. He asked an LLM to use only the grammar, vocabulary and sentence structure the customer used when describing the problem on calls.

  4. Outline. He fed the positioning memo, context doc, story map and style guide in to create an outline. He used Claude to choose the content format that best highlighted his key value proposition, then edited as needed.

  5. Generate and edit. He generated the entire case study from all the previous documents and started editing. He calls this “the easiest step.” He says it “one-shotted” large documents with multiple versions for each paragraph, so he could pick the version he liked best.

  6. Bonus: images and quotes. He ran a specific “illustrator prompt” and “testimonial prompt” to suggest images and quotes to add to the case study.

Stated results

  • About 2 hours total: “1 hour of setup. 1 hour of editing and fine-tuning.”
  • “less than a day of turnaround for an asset.”
  • His claim that the workflow “produces content 5x better than a team of writers.” This is his own assessment. The post does not describe how he measured it.
  • Distribution results (traffic, pipeline, deals): None stated.

Caveats

  • He is Head of Growth at Default, and the case study is for his employer’s customer. The case study is marketing for Default. The post does not sell a course, kit or template.
  • This is a Claude Code workflow that he runs and reviews step by step. It is not an autonomous agent.
  • The positioning memo appears from Step 1 onward but is not in his list of gathered context. The post does not describe what it contains.
  • The post does not share the “illustrator prompt” or “testimonial prompt” text. The LLM used for the style guide is not named.
  • The post says “full example below” and “Check out the output below,” but the captured text does not include the finished case study.
  • The post does not say whether gathering the 87 pages counts toward the 1 hour of setup.
  • The post is roughly 9 months old as of 2026-10-26.
  • Handles: LinkedIn linkedin.com/in/stanrym (verified 2026-10-26: post author). X, Bluesky, Threads, Instagram, Mastodon, TikTok: not verified, not tagged.

Sources

Want agents like these working your distribution? Get It Built. Get new teardowns weekly: subscribe (double opt-in).

Get one teardown a week.

Same format, a new operator every issue. Double opt-in.