The MotherDuck Pricing Calculator is live!! I'm especially proud of this one. Let me explain. What's the user problem? A customer who is unfamiliar with your infrastructure product wants to have a ballpark estimate of the overall cost. They know very little about your product. They know a lot about their own workloads and use cases. Where most pricing calculators fail is they ask users questions users are not ready to answer. How many CPUs do I need? For how long? How many hours per week would I need to use this product for? People don't know... and a pricing calculator that multiplies X by Y and spits out Z is just not that interesting. We at MotherDuck decided to meet customers halfway. We're asking them, what workloads do you intend on running with us? We know from aggregate telemetry and decades' worth of experiences the impact of the various workload archetypes on infrastructure and we came up with a ballpark but very simple heuristic that helps get a feel for costs. Try it out here! https://lnkd.in/g7EVcc8J And we trust that if you know you'll need 1000 core-hours with MotherDuck, you're capable of multiplying that by $0.40 :)
Love it and you always think differently Tino! So true to see from your calculator that ETLs are expensive workloads.
Congrats Tino Tereshko 🇺🇦 and MotherDuck. As a customer/user (maybe a bit more on the complicated side) - the pricing calculator gave a great UX to get from standard to custom pricing (where we expected to land). I was able to use to tool to think about how we can do some embedded pricing in our product for when we give our own customers access to a Duckling.
Congratulations on launching the MotherDuck Pricing Calculator! It's great to see an approach that truly considers user needs and simplifies the process. What challenges did you encounter during development, and how did you overcome them? Looking forward to hearing more about your journey!
Brilliant! Or worse, how many credits do you need?
Pricing calculators are the best!
Nice! Not being able to help prospects get a sense of what a solution costs based on use case (or even at all) is a frustrating point of friction in the sales cycle. Hopefully this quickly yields results
Cool!
Senior Data Engineer at Harness | Open Source Software Developer | DevOps 🦄 (Series D - 3.7 Billion)
6moNice, I like this approach a lot -- very user friendly. One thing I noticed. The compression slider makes a big difference. Not sure if I am looking at it the right way, but I see compute goes down when we say data is not compressed, which makes sense since decompression is CPU heavy. But why does storage also go down (by quite a lot)? Shouldn't that go up if data is not compressed? Enabling compression blows up storage size.