HN user
The discussion here is exactly why we started the conversation.
Certainly, if we go this route, we'll make sure our users can readily monitor their usage so as to minimize surprises. Even still, we don't want our customers to have to kill the service in the middle of a billing cycle.
Is this about my ROI on the carrot juicer? I really tried to avoid fuzzy math in here and stick to concepts. Specific examples would be helpful. I'll get the numbers cleaned-up, if possible.
Radical transparency != make shit up.
(Disclosure: I wrote the post)
These are all great questions. Thinking long-term, the answer should be yes to all of those questions. We should save time (and therefore money) and be a vehicle for increased revenue. And, we intend to do a lot more writing about how folks are using/could use/should use our product. At the same time, in the long run, we’re all dead. So, in the present, we’re looking to work with Series-A type companies who are in the midst of early product development. We want to work alongside them to understand their analytics needs and tweak our roadmap accordingly.
Those customer sketches/white papers are extremely important to us. We’re still learning (and probably always will be). It’s my hope that we will be in a position to blog about customer experiences soon. Dominos are certainly lining up for that.