Case study generator
One project, one document,
published where people will read it.
Tell it what happened. It writes the case study and lays it out as a LinkedIn document post in your own colours and fonts, then publishes it. It will not invent a number to make a page look finished.
What ends up in it
The situation, without the throat-clearing
Who it was, what was wrong, and why it mattered. This is the page most people over-write, and the one a reader decides on.
The numbers you actually have
Real figures only. Nothing gets invented to fill a page, so a study with two honest numbers reads better than one with six plausible ones.
A quote that sounds like a person
If you have one, it goes in as they said it. If you do not, the document does not pretend you do.
Published as a native document
The PDF goes to LinkedIn as a document post, so it is swipeable in the feed rather than an image somebody has to open.
The reason most case studies never get written
It is not the writing. It is that a case study feels like it needs sign-off, a design pass, and a number nobody has measured, so it stays on the list. The version that actually gets published is shorter than that: a real situation, a real thing you did, and whatever outcome you can stand behind, laid out well enough that somebody swipes to the end.
This is the piece a B2B services company most often owes itself. If you win contracts by looking established, the proof is the work you have already done ten times and never written up: the account you took over, the site you cover, the migration nobody noticed because it went well.
The honest constraint is the same one that makes it credible. If you have no numbers, you have an account of a project, and that is still worth publishing. What is not worth publishing is a percentage nobody can source, which is why this will not write you one.
Questions
- What does it actually produce?
- A LinkedIn document post: a multi-page PDF that renders as a swipeable card stack in the feed, laid out in your own colours and fonts. Plus the caption to go with it. You can publish it from here or download the pack and send it to whoever publishes.
- Will it invent the numbers?
- No, and this is the part that matters most for a case study. The writing engine has a hard fabrication ban: no invented statistics, no invented quotes, no invented people or events. If you do not give it a number it will write around the absence rather than fill it in. A case study with a plausible fake percentage in it is worse than no case study.
- What do I need to have ready?
- Less than you think, and all of it real: who the client was or how you can describe them without naming them, what the problem was, what you did, and any outcome you can actually stand behind. A sentence of a real quote beats a paragraph of an invented one.
- Can I keep the client anonymous?
- Yes, and often you should. "A B2B logistics company with forty staff" carries the credibility without the permission problem, and it is what most people can publish without a two-week approval round.
- How many pages?
- Usually between six and ten. A document post is read with a thumb on a phone, and a case study that needs twelve pages is generally two case studies.
- Is a document different from a carousel?
- Technically they are the same upload: LinkedIn calls the format Documents and Presentations, and both are PDFs. The difference is shape and intent. A carousel is punchy and portrait; a document is longer, and Blendin also offers a 16:9 landscape presentation layout for when it is closer to a deck than a post.
Start with the one you keep meaning to write
The first one you make can be the document: a new account gets one free generation of anything the paid plan can make. Publish it, or download it and send it on. After that it is a 14 day trial of Starter, card required, no charge today, then $59 a month, cancel anytime.
Start free trial