The lesson
Summarize the customer, challenge and solution in three labeled lines, then list the customer's stack and compliance needs so a technical buyer can check fit before reading the story.
Under the Mercari logo, the title and a FINTECH tag, a gray grid shows three scope figures: "27" GitHub Organization-level roles, "54" Google Workspace groups and "5353" Okta entitlements. A bold one-sentence summary leads into three labeled lines, "Company", "Challenge" and "Solution", followed by an "Operating Environment" list of identity providers, core systems, workforce and compliance needs such as APPI and PCI-DSS. The body runs "Challenge", "Goals" and "Opal Solution" as short sections and bullet lists, tells the 2021 supply chain incident and the in-house tool Carrier, gives a long quote from Allan Wirth, Manager of Platform and AI Security, and ends on a short "Strategic Impact" paragraph before an "Explore more" row of three other customer stories.
Don't copy Mercari's incident history, the Carrier tool name, the Zero Touch Production language or the Japanese regulations. Keep the stat grid under the title, the three labeled summary lines, the operating environment checklist, the challenge, goals and solution sections, and one long named quote before a short impact paragraph.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.