Talk about your next project
Payrails case study

The lesson

Name the products the customer used in a card beside the hero stats, so a buyer can match each result to a product they could buy.

The move

The hero puts the headline "PUMA boosts payment performance across LatAm with Payrails" over three stats, "75%" reduced time-to-market, "15k" engineering hours saved and "No code" changes in payment workflows. Beside them, a card with a runner photo lists "FEATURES USED": Orchestration, Unified Analytics and Reconciliation, above a "Get a personal consultation" button. The body opens with a company profile, then runs "// CHALLENGE", "// SOLUTION" and "// RESULTS", and each section ends with a boxed quote from Aldo Molina, Director E-Commerce LatAm. Results restate each stat as a bold subhead with one line of explanation, followed by "Take the first step today", a consultation banner and two more customer stories.

Why it works

  • Our readThe features-used card ties the three hero numbers to named products, so a payments buyer knows which modules produced them.
  • Our readThe challenge names local rails such as Pix, OXXO, SPEI and PSE, which makes the complexity concrete for a reader who works in the region.
  • Our readResults repeat the hero stats as subheads with a one-line explanation, so a reader who skipped the story still sees what each number means.

What not to copy

Don't copy the LatAm payment rails, the Magento to Salesforce Commerce Cloud migration or the "performance, not plumbing" line. Keep the stat hero with a features-used card, the profile, the challenge, solution and results sections each closed by one named quote, and results written as stat subheads with a sentence of explanation.

More from Payrails

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.