Julia Schottenstein: evaluation

Transcript context

…Today's episode is brought to you by AssemblyAI. If you're looking to build AI powered features in your audio and video products, then you need to know about AssemblyAI, which makes it easy to transcribe and understand speech at scale. What I love about AssemblyAI is you can use their simple API to access the latest AI breakthroughs from top tier research labs. Product team that startups and enterprises are using AssemblyAI to automatically transcribe and summarize phone calls and virtual meetings, detect topics in podcasts, pinpoint when sensitive content spoken and lots more. All of AssemblyAI's models which are accessed through their API are production ready. So many PMs I know are considering or already building with AI and AssemblyAI is the fastest way to build with AI for audio use cases. Now's the time to check out AssemblyAI, which makes it easy to bring the highest accuracy transcription plus valuable insights to your customers. Just like Spotify, CallRail and writer do for theirs. Visit assemblyai.com/lenny to try their API for free and start testing their models with their no code playground. That's assemblyai.com/lenny. I know you also spent a lot of time thinking about pricing and willingness to pay and things along those lines. Is there anything you could share about which is what you've learned about how to think about pricing for a tool like this or even in general? Pricing and willingness to pay is such a hard conversation and lots of startups don't do this early enough in their company journey. Likely a side effect of zero interest rates where investors were happy funding GitHub stars and usage and companies never thought about how am I going to make revenue or make money, which is it's important. So for us at dbt Labs, I don't claim to be perfect at it, but we're trying to get a better muscle around it. And I always think about Madhavan who wrote this book Pricing Innovation. I know you've had him on the show before, but he shares that you don't get to decide if you're going to have a pricing or willingness to pay a conversation. You only get to decide what. So it's much better to have that conversation before you build the product than have it when your sales team's trying to sell something and people aren't excited about what you've built, aren't willing to pay for it. And at dbt Labs we have this value, it's one of our core values that says we are more concerned with value creation than value capture. And we really mean this. When we talk about what is the value of dbt Labs to our customers, they often talk about how it's either 20 to 35% as valuable as what they spend on their cloud data warehouse. But what we charge our customers is a very small fraction of that 20 to 35% and that's by design. And last year we did our first ever pricing change in the company history and you learn a tremendous amount when you have that event because you get to test the price elasticity by of your customers. And it's so important to learn that lesson while the company is still smaller or the stakes are lower because pricing just is always evolving. It's not a fixed thing, it gets more complex over time. So we have to think about it quite a bit because my team builds proprietary software for dbt cloud and when we lose a deal we most often lose it to dbt open source and we like it that way. We're happy to lose to ourselves, but we have to really think very deeply about what are people willing to pay for and what moves the needle for them and focus on that. I'm so curious what that pricing process was like to figure out what to change. Is there anything you could share about just what that was for you or what are some just surprises that came out of that process or just like, "Wow, we didn't expect that in these conversations?"…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.