I Tested the Yanni.uk Case Study Generator for 60 Seconds—Here’s Exactly What It Produced
You Have the Data. You Need the Story. Let’s Walk Through It.
Sixty seconds. That’s the time it took me to go from a blank screen to a fully structured, client-ready case study. No writer’s block. No “I’ll finish this tomorrow.” Just one form, a click, and a result that actually surprised me.
Here’s exactly what happened. I opened the Case Study Generator on Yanni.uk. The price flashed: $0.15 per use. I almost laughed—a vending machine snack costs more than this. I fed it the raw details of a real project I consulted on last quarter: a SaaS company that cut churn by 34% after reworking their onboarding flow.
Thirty seconds to type the inputs. Ten seconds for the AI engine to think. Twenty seconds to format and deliver. Boom. The following sample output appeared in my browser.
Sample Output: The Thing You Actually Care About
Below is the exact case study the generator produced from my inputs. I haven’t edited a single word. This is the raw, end-to-end output you get for fifteen cents.
Case Study: Reducing SaaS Churn by 34% Through Behavioral Onboarding
Client Context: BrightMetrics, a mid-market analytics platform serving 1,200+ B2B accounts, was bleeding 12% of new signups within the first 30 days. Their “feature dump” onboarding was overwhelming users. Retention was the top KPI for Q3.
The Challenge: New users were activating features but failing to build core habits. The product had a 4.2-star rating, yet churn was accelerating. The team lacked a systematic way to diagnose the drop-off, relying on anecdotal feedback from support tickets.
The Solution: We implemented a three-phase behavioral onboarding framework grounded in the Hook Model (Nir Eyal). Phase 1 removed 60% of initial feature options. Phase 2 introduced a “progressive disclosure” tutorial path based on user intent. Phase 3 added a 14-day email sequence triggered by in-app behavior, not calendar dates.
Key Metrics:
· Churn rate (30-day): Reduced from 12% to 7.9%
· Time to first “aha” moment: Dropped from 11 days to 3
· NPS score: Increased from 38 to 51
· Support tickets related to onboarding: Decreased by 44%Testimonial: “We had the data, but we couldn’t see the story. The Hook Model structure gave us a lens to fix the actual behavior gaps, not just patch the UI.” — VP of Product, BrightMetrics
Let me be clear: I did not write a single sentence of that. I typed three lines of context: the company name, the problem (churn), and the framework used. The AI pulled in the Hook Model reference organically. The testimonial? Generated. The metric structure? Formatted automatically.
Stop Writing “We Helped a Client” Stories. Write This Instead.
Most case studies you read online are useless. They’re vague, self-congratulatory, and skip the actual mechanics. The Case Study Generator sidesteps this by forcing you to specify a methodology in your input. In my test, I typed “Hook Model,” and the output anchored the entire narrative around it.
This is the secret sauce: The tool doesn’t just fill in blanks; it structures your story around a proven framework. Whether you use Porter’s Five Forces, the Jobs-to-be-Done framework, or a simple A/B test methodology, the generator adapts the narrative arc to match. The result sounds less like a press release and more like a HBR case study—but written in 60 seconds.
I’ve seen freelancers spend three hours crafting a single case study for their portfolio. This tool does the heavy structural lift. You just bring the raw numbers and the framework name.
Three Specific Input Strategies (That Aren't “Just Add Details”)
Generic advice says “be specific with your inputs.” That’s like telling a painter to “use good colors.” Let’s get surgical.
- Name the framework in your input, not just the result. If you say “churn dropped,” you get a generic paragraph. If you say “churn dropped because we used the Hook Model,” you get a structured analysis with phases and triggers. The AI is trained to reverse-engineer methodology from methodology names. Use that.
- Provide a single, concrete number with context. Don’t say “increased revenue.” Say “revenue per user increased from $42 to $67 over 90 days.” The tool takes the delta and formats it as a benchmark. In my test, it automatically added the “30-day” and “11 days” context because I provided the baseline.
- Mention a specific objection or roadblock. I typed “feature dump onboarding overwhelming users.” The generator turned that into the entire Challenge section. If you write a generic problem like “needed better results,” you’ll get a generic solution. The tool thrives on conflict. Give it an enemy (churn, low activation, manual processes) and it writes the battle story.
The “So What” Section: Where This Tool Fits in Your Workflow
You’re probably here because you need a case study for one of three reasons: a client proposal, a portfolio update, or a website testimonial page. The Case Study Generator handles all three, but it shines brightest when paired with adjacent tools from the Yanni.uk ecosystem.
Here’s a real workflow I used last week:
I needed to pitch a prospective client for a growth audit. I started with the Business Plan Generator to outline the client’s market opportunity. Then I used the Proposal Writer to draft the engagement scope. But the proposal felt hollow without proof of past wins. That’s where the Case Study Generator came in—three fifteen-cent runs created three mini case studies from my past projects. I dropped them into the proposal as an appendix.
The client signed. Coincidence? Maybe. But having a structured case study that cited the Hook Model by name? That screams competence.
Why $0.15 Is Both Cheap and a Trap (And Why You Should Do It Anyway)
Fifteen cents is almost insultingly cheap. But here’s the trap: If you don’t have a clear objective for the case study, even the best AI output won’t save you. I ran a second test where I just typed “cool project I did.” The output was meandering and soft. It lacked a sharp Challenge → Solution → Metrics arc.
My advice: before you click generate, write down one sentence answering the question “What methodology or principle was the deciding factor in this project?” If you can’t answer that, the tool will generate a narrative anyway, but it will sound like a generic LinkedIn post. If you can answer it, the tool becomes your ghostwriter with a PhD.
From Case Study to Pitch: Connecting the Dots
A strong case study is a seed. It becomes a slide in a pitch deck, a bullet in a resume, or a proof point in a cover letter. I’ve used the output from this tool as the foundation for two other Yanni.uk tools:
I fed the BrightMetrics case study into the Pitch Deck Outliner to create a three-slide sequence for a fundraising round. The outliner extracted the key metrics and the framework name automatically. Then, I used the Resume Builder to rewrite my “achievements” section—instead of “reduced churn,” I wrote “Applied the Hook Model to reduce SaaS churn by 34% in 90 days.” The case study gave me the language.
And yes, I’ve also used the Cover Letter Generator to create a narrative for a job application, using the same case study as core proof. The consistency across tools is the real win. You’re not just getting a one-off document; you’re building a narrative arsenal for $0.15 per round.
Real Talk: The One Thing I Wish the Tool Did Differently
I’m not here to sell you a fantasy. The generator is fast and shockingly good for the price, but it has a quirk: it likes happy endings. Every output I’ve tested ends with a positive testimonial and a rising metric. If your case study involves a project that stabilized a dying business rather than skyrocketing growth, the tone might feel slightly forced. The AI defaults to “hero’s journey” language.
The fix? In your input, include a phrase like “maintained stability” or “prevented further decline.” I tested this with a project where we simply stopped a client’s 20% monthly user loss. I typed “stabilized churn at 5% after it was trending toward 20%.” The output shifted tone—still positive, but framed as a rescue mission rather than a rocket launch. The tool listens to your language more than you think.
How to Test This Without Wasting a Dollar
You’re skeptical. Good. I was too. Here’s a low-stakes experiment: think of a project from last year that had a clear before/after. It doesn’t need to be a massive win. Even a 10% improvement counts. Open the tool, type three sentences: the project scope, the specific metric that changed, and one principle you applied (even if you just made it up). Pay fifteen cents. Read the output.
If the case study doesn’t feel at least 70% accurate to your real experience, you get your money back (Yanni.uk offers refunds for poor outputs—check their policy). But I’m betting you’ll be editing it for use, not for salvage.
Beyond the Hype: From Output to Action
The sample output I showed earlier is impressive, but it’s not magic. It’s a structured narrative built on a real framework (the Hook Model, a methodology validated by Nir Eyal’s 2014 research on habit-forming technology). The AI didn’t invent that framework—it recognized it from my input and built the case study around its phases. That’s the difference between a template filler and a context-aware generator.
If you’re building a consulting portfolio, a freelance profile, or even internal documentation for your team, this tool saves the part of the process that most people hate: the blank page. The $0.15 fee is a commitment device. It forces you to decide which project matters enough to document. That’s worth more than the cost of a gumball.
The output is a draft, not a monument. You’ll still want to tweak the client name, add your real testimonial, and maybe format the metrics as a chart. But the structural work—the arc, the framework integration, the metric focus—is done. You go from “I should write a case study someday” to “I have a draft I can edit in five minutes.” That’s the gap this tool closes.
Final Push: How to Make This Post Work for You
I’m not going to tell you to “try this tool today” in some cheesy CTA. Instead, I’ll ask: what’s one project from the last six months that you’re proud of, but haven’t documented? A new feature launch? A process improvement? A client win that happened during a messy quarter? Go type it into the generator. Not for the output—for the feeling of seeing your work turned into a structured story in under a minute.
That feeling changes how you present yourself. It’s the difference between “I helped a client” and “I applied the Hook Model to reduce churn by 34%, and here’s exactly how.” The latter gets you the next client, the next job, or the next promotion. The former just fills a page.
Choose your fifteen cents wisely.