Make it a user testimonial. Then explain the benefit: almost always time, money, or risk-reduction, but it could be something like "Build things you could only

Make it a user testimonial. Then explain the benefit: almost always time, money, or risk-reduction, but it could be something like "Build things you could only imagine before...". If the testimonial does this, you can skip this one. Then explain what it does and how. Not necessarily on the first page. If you can't tell me why I need it, maybe I don't need it. Ideally, you have some class of customer who will recognize the benefit when they see it because they're dying for it. It's usually better to talk to those people than to the great mass of app developers.