Talk about your next project
Payrails case study

The lesson

Name the product features the customer used in the hero, then build the solution around those same features and give each result its own subhead.

The move

The hero puts the headline with the 11% figure beside a photo and a 'Features used' card listing PSP integration layer, Routing and APMs, above a 'Get a personal consultation' button. A stat row reads '+11%' uplift in payment approval rates, '-70%' less time-to-market and '+23%' revenue processed. The body runs '// CHALLENGE' ('Achieving high local authorization rates'), '// SOLUTION' ('Enabling local rails with fast time to market') with three strategy subheads, and '// RESULTS' ('Significant uplift in payment approval rates') with one subhead per number. Quotes from Vasiliy Everstov, Head of Fintech at inDrive, sit in the challenge and results, and the page closes with 'Take the first step today', a consultation block and 'More customer stories'.

Why it works

  • Our readThe 'Features used' card tells a buyer which modules produced the numbers before they read any body copy.
  • Our readEach of the three solution strategies matches a feature in the card, so the story checks its own claims as it goes.
  • Our readThe results section repeats each hero number as a subhead with a short explanation, so a skimmer who jumps to the end can see where each figure came from.

What not to copy

Don't copy inDrive's ride-hailing 'real-time deals' background, the gig-economy driver angle or the payments vocabulary. Keep the hero stat row, the features-used card with a CTA, the labeled challenge, solution and results sections, solution subheads that map to features, and one result subhead per number.

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.