The lesson
Prove a speed claim by running the old per-case time against a real batch of work, and show the total hours it would have cost against the hours it actually took.
The headline carries both results, followed by a seQura logo panel and a three-figure stat bar: "88 %" first-time right, up from 50%, "14.9 min" per KYB review, down from 4h, and "76%" conversion increase. A summary paragraph sits beside an "On this page" list, and the body then answers its own section heads in order: "How KYB worked at seQura before Duna", "Why seQura chose a policy engine over a workflow tool", "How seQura reboarded 1,700 merchants for periodic reviews" and "How seQura raised first-time right from 50% to 88%". The reboarding section works out that 243 minutes per case would have meant nearly 7,000 analyst-hours, against roughly 420 analyst-hours on Duna, and a later list headed "The numbers, from seQura's dashboard" defines each metric. A boxed quote from a named seQura leader follows most sections, and the page closes with "About Duna", a contact line and "More case studies".
Don't copy seQura's KYB vocabulary, the periodic review regulation, the policy engine versus workflow tool argument or Duna's funding line. Keep the results-in-the-headline, the three-number stat bar, the question-style sections with a customer quote after most of them, the before-and-after workload math and the defined metric list.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.