The lesson
Lead with the scale of the customer’s system, then use the story to show why the old database model broke down.
The page opens with the title “From DigitalOcean to PlanetScale: Scaling Mintify to 30TB and 2T+ records,” a short subhead, a founder quote, the Mintify logo and four proof points: “30 terabytes of data volume anticipated in < 12 months,” “Calculations performed on 2+ trillion records,” “150,000 smart contracts with trillions of records,” and “3 developers on Mintify's internal team.” It then explains Mintify’s ambition in “Building the Bloomberg trading terminal for NFTs” before moving into “Challenges,” where CPU and RAM limits, downtime, senior hiring pressure, cost and support problems are listed. The middle of the story uses “Features and capabilities” to translate each operational pain into a required database capability, then “Choosing PlanetScale” uses Evan Varsamis’s quotes to make the buying process part of the proof.
Don't copy Mintify’s NFT trading terminal positioning, DigitalOcean comparison or car analogy. Keep the structure of scale proof first, customer ambition second, operational constraints third and required capabilities fourth.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.