Choose evidence-rich stories

Select customers who can describe the problem they faced, how they used the product and what changed. A positive quote alone is not a case study. Include the context that helps a reader judge whether the experience is relevant to their own situation.

Secure the right permissions

Agree how names, images, quotations and business details may be used through the appropriate approval process. Give the customer a chance to check factual details. Do not imply that one person endorses every feature or future roadmap item simply because they described a good experience.

Avoid manufactured precision

Use numbers only when their definition and source are understood. If the story is qualitative, present it that way. A credible account of a smoother customer conversation can be more useful than an unsupported claim that the product increased revenue by a dramatic percentage. Preserve the date and product context of the customer’s experience. A story about an earlier configuration should not imply that every current package or planned service produced the same result. Context makes the reference more useful to a prospective buyer.

Imagine this

Illustrative operating example

A hypothetical case study explains that a consultant replaced several separate follow-up links with one profile journey. The consultant can demonstrate a clearer workflow. A claim of revenue growth needs separate evidence.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.