The lesson
Break a customer story into numbered use cases, each a job the customer needed done, so readers find the one that matches theirs.
The move
A purple hero carries the Figma logo and "How Figma built a living data foundation to orchestrate every GTM motion", then a pull quote from Kyle Ketchum, Marketing Operations. The body is tagged "USE CASE 01", "02" and "03", each with a plain job title such as "Turning self-serve accounts into enterprise pipeline", then a "CLAY'S IMPACT" section.
Why it works
- Our readEach use-case heading reads as a task an ops person might have on their own list, so a visitor can jump to theirs.
- Our readNaming the specific tools involved (Salesforce, Snowflake) and the problem before the fix makes the product feel like plumbing for a known stack.
What not to copy
Don't copy the Figma stack or the feature names. Keep the numbered, job-titled structure and a final section that sums up what changed.
