Talk about your next project
Fly.io case study

The lesson

Explain what the customer's product does for its own users before you mention yours, so the technical problem has real stakes.

The move

Under a wide illustration of students walking, the headline sits with the author, a "4 MIN" reading time and share icons. The story opens on New Zealand's multi-track high schools, then spends two sections, "Building an Intentional Curriculum" and "Easy, Portable Information Sharing", on MyMahi's own features. Only then does "Serving Lots of Students = Managing Massive Data" name the stack and the AWS Lambda payload limit of five megabytes that pushed them to Fly.io. It closes with "Moving Fast Enough to Keep up With Teenagers", a section on the two-developer team and a long quote from CTO Stefan Charsley.

Why it works

  • Our readReaders learn that the platform is used in over a hundred schools and that students own their data before the sync problem appears, so they understand what was at stake when the payload limit was hit.
  • Our readNaming one concrete constraint, a five megabyte payload limit that MyMahi hit regularly, gives a developer audience a specific reason for the switch instead of a vague complaint.
  • Our readEnding on the team of two developers and the CTO's quote about a short list of commands ties the vendor's benefit to a constraint other small teams share.

What not to copy

Don't copy the education framing, the college-years opening, the digital backpack image or the Tigris aside. Keep the order: customer's product first, then one named technical limit, the decision with a short customer quote, and a closing section built around team size and a longer quote from a named leader.

More from Fly.io

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.