Way more time coding than I thought on product features and pricing page
Building an app is one thing. But I did not know releasing something to the public was going to cause me to spend so much time, energy, and effort on one particular part that should be so simple and straightforward. I guess I never gave it too much consideration how important it is to actually let people quickly and concisely know the value of the benefits they are getting by using your product. Working on this page actually caused me to rethink the entire structure of my project multiple times. It even lead to the change of pricing and creation of multiple features.......
What process did you use or how did you determine the layout of your product features and pricing page? At what point in the development process do you give attention to this page?
Replies
Same thing happened to us. Writing the pricing page was where we found out what the product actually was. What helped: build each tier around the one job a buyer is trying to get done, not a feature checklist, and make the step from one tier to the next a single sentence. If you cannot say why someone upgrades in one line, the page is not the problem yet. I start that page early now, because it keeps changing the build.