2026-08-09
What a Case Study Is For
The case study is the most persuasive format in music marketing and the least reliable, and both for the same reason: it is a story about somebody who succeeded. A related workplace perspective is covered in Monitask’s remote employee monitoring software.
The survivorship problem
You only ever read about the ones that worked.
The same tactics were run by people it did not work for, and those campaigns are not written up. So the case study describes the winners of a lottery and the ticket-buying strategy of the winners, which are different things.
This is not a reason to discard them. It is a reason to read them for mechanism rather than for method. For additional current music-industry context, see Beatport.
What actually transfers
The mechanism, if the piece names one.
Our 2010 case study of a small band making money online reads well now, and the reason is that the transferable part was never the platform — it was that a small committed audience buying directly outperformed a large one listening passively. That is arithmetic, and arithmetic transfers.
The constraints they were under. Budget, time, existing audience size. A case study that omits the starting position is unreadable, because you cannot tell whether the outcome was the tactic or the head start.
And what they stopped doing. Rarely reported and frequently the most useful part.
What does not transfer
The specific channel. It will not be there in three years.
The numbers. Different genre, different audience, different moment.
And the sequence. "First we did X, then Y" describes an order that worked once, and post-hoc ordering is where most of the false confidence in this format lives.
Five questions to read one with
What was the starting position? Existing audience, budget, connections.
What is the mechanism? Why would this have worked? If no answer is given, the piece is a story.
What else were they doing? Campaigns do not run in isolation and the write-up usually isolates one.
What is the denominator? Ten thousand streams from what — a hundred posts or one?
And who wrote it? A service writing up its own campaign is describing its own product.
Writing an honest one
If you are producing case studies rather than reading them.
State the starting position. State the spend, in money and hours. Give the denominator. Say what did not work in the same campaign, because every campaign contains some.
And say what you cannot attribute. Almost no outcome has a clean cause, and pretending otherwise is what makes the format unreliable.
A case study with those five is worth more than ten without, and almost nobody publishes one.
The short version
- You only read about the campaigns that worked, so a case study describes lottery winners and their ticket strategy
- Read for mechanism rather than method: the transferable part is why it worked, not what was done
- Also transferable: the constraints they were under, and what they stopped doing
- Not transferable: the channel, the numbers, and the sequence — post-hoc ordering is where false confidence lives
- Five questions: starting position, mechanism, what else was running, the denominator, and who wrote it
- An honest one states spend in money and hours, gives the denominator, names what failed, and admits what cannot be attributed