Interested in your thoughts on A/B testing pricing and packaging, on opaque vs. transparent pricing, and on how companies should approach things like cancellation policies etc.
A/B testing is hard (on its own) for bottoms-up SaaS pricing just because you won’t have the volume you want to make quick, informed decisions. Always start with user research. Ask free customers for feedback on pricing pages over Zoom, have non-customers give feedback on checkout flows, etc. Narrow down your options before thoughtfully deploying A/B tests.
I'm primarily interested in bottoms-up SaaS, which relies on transparent pricing to function. But something people often miss is this: high quality product writing is the packaging. This applies to all parts of the product, but is especially important that your customers be able to understand what they are buying and how to buy it. Even companies with great traction are always leaving money on the table with unclear writing. Hire writers who have good design taste.
Re: cancellation policies et al. Not quite sure what your question refers to, but you should always be good to your customers. Give them the benefit of the doubt, be nice, treat them with respect, answer their emails, and let them cancel without calling someone on the phone.
This question is part of an AMA with Merci Victoria Grace.View entire AMA with Merci Victoria Grace.
Let's say you have an API you want to document and you want to: - Let your users test their calls to the API thanks to a "playground" like the one on the Figma API - Be able to customize it to matc...
Do you have a favorite survey or poll tool to get feedback, or a unique process to get actionable insights from your users about your design, product features, pricing, and more? There was an inte...
I've been using Confluence since 2013, and in my opinion, it's the best document collaboration tool. Lately, I've seen that Notion is getting trendy. Any Notion heavy user around?