A software company has twelve customer stories. Does it need a thirteenth? The answer depends on what a buyer needs to understand and whether the existing material answers that question. Counting logos will not tell a case-study writer which project to suggest.
Start with a coverage audit. Its output is a small matrix linking buying questions to usable evidence, followed by one proposed story brief. This is useful once you understand the company’s offer. If you are still deciding whether an account fits your service, start with the company-fit guide.
Look for unanswered questions, not an empty category
Industry is one way to browse a library. For example, Zendesk’s public customer library has industry groupings. Your audit can also examine the task, implementation setting and person whose experience is described. These are different dimensions; a story tagged with an industry may still leave a practical buying question unanswered.
Write down three questions from the client’s actual sales or customer conversations. If you do not have access to those conversations, record your questions as hypotheses for the client to check. Do not turn a competitor’s taxonomy into assumed demand.
A useful question is specific enough to investigate: “How did an operations team introduce the workflow while keeping its existing ticket system?” is easier to assess than “Do we have enough enterprise content?” The second wording could justify almost any commission.
Read the assets before scoring them
Open each relevant story. Record its URL, the date you reviewed it, the customer context, the experience described and the evidence available. A headline mentioning onboarding does not establish that the article explains rollout. A quote about helpful support does not answer a question about data migration.
Use three plain statuses: answered, partly answered and not found in this review. The last status describes your bounded review, not the absence of evidence everywhere. Include an “ask the client” column for private decks, unpublished interviews or existing material that your search could not reveal.
Keep sales usefulness separate from asset quality. A beautifully produced story can answer a different question. An older, modest article may contain precisely the implementation detail a salesperson needs.
A completed coverage matrix
Fictional exercise: a service-desk SaaS supplier wants to explain expansion from one support team to several departments. The three assets and all decisions below are invented teaching material, not customer results.
| Buying question | Material reviewed | Coverage decision | Next check |
|---|---|---|---|
| Can one team start without replacing its ticket system? | Story A describes a small support rollout and names the existing system | Partly answered: coexistence is stated, setup is unexplained | Ask whether an implementation diagram can be shared |
| Who owns the process when a second department joins? | Story B discusses a larger rollout but only quotes the original sponsor | Not found in this review | Check whether an operations participant is available |
| What did staff need to learn? | Story C explains training sessions and the participant’s responsibilities | Answered for this setting | Reuse the approved passage instead of commissioning a duplicate |
The resulting brief is not “write another SaaS case study.” It is: “Explain the handover of ownership when a second department joined, using the experience of someone who managed that handover.” That focus gives the interview a job.
Turn the gap into a commission decision
For the fictional ownership gap, the writer’s proposed assignment reads:
Audience: an operations lead considering a second-department rollout. Question: who made and maintained the shared workflow decisions? Required participant: someone directly involved in the handover. Evidence sought: the sequence of responsibilities before and after expansion, with an example the customer can describe. First deliverable: a written account of that process. Open condition: customer access and permission to publish have not been confirmed.
The client can now accept the question, suggest an existing asset or explain that the issue is not commercially relevant. Any of those answers is more useful than agreement to a vague content quota.
Do not promise a measurable business result before the interview. The customer might have a strong process story with no publishable performance figures. Equally, a promising topic might fail because the only available participant did not take part in the relevant work.
Decide whether research, editing or a new interview is needed
Choose the smallest task that closes the gap. If an approved story already contains the answer, improve the route to that passage or prepare a sales excerpt within its permitted use. If the evidence exists in a transcript, a focused edit may be enough. Commission another interview when the missing experience genuinely needs a participant’s account.
When a new company or function must be researched, use the role-and-evidence guide first. A selected LinkedIn profile sample can help you inspect possible functions through the CSV research method. It does not establish that someone owns the story, can approve it or wants to buy your service.
Keep the audit usable after the meeting
Finish with one selected question, its current evidence, the next check and a named owner for that check. Keep rejected ideas with a short reason so another writer does not repeat the same proposal next week.
After the client confirms the assignment, move into a customer interview brief. Judge the audit by whether it helped the team choose, reuse or decline a concrete project. More rows and more proposed stories are not, by themselves, a better editorial decision.