Qumulo CEO Bill Richter on the Benefits of Enterprise Partnerships

In this episode of Founded and Funded, Madrona Managing Director Matt McIlwain and Partner Aseem Datar sit down with Qumulo CEO Bill Richter to talk about developing meaningful partnerships. Madrona was an early investor in Qumulo when it launched in 2012, and the company recently partnered with Microsoft to launch Qumulo on Azure as a Service. Startups often partner with large enterprise companies to accelerate growth, but there are benefits to both parties, and in this episode, we take a look at it from both perspectives.

Transcript below

Welcome to Founded and Funded. I’m Coral Garnick Ducken, the new Digital Editor for Madrona Venture Group. And in this week’s episode, Madrona Managing Director Matt McIlwain and partner Aseem Datar sit down with Qumulo CEO Bill Richter.

Bill is no stranger to Madrona bringing 20 years of technology experience to the team when he joined as one of our Venture Partners. Madrona also invested in Isilon back in 2001, and Bill was the CFO when that company went public in 2006 through its $2.5 billion sale to EMC four years later.

Then, of course, Madrona was also an early investor in Qumulo when it launched in 2012. In simple terms — if we can talk about the cloud and data storage simply, Qumulo is a cloud-based data management platform that gives companies more flexibility when it comes to storing, managing, and running massive unstructured data workers.

The company, of course, partners with Microsoft Azure, which is what sparked the idea for the conversation on partnerships today. Yes — we’re talking about partnerships. They are often thought of as an important tool to scale from a startup into a growth phase company and then onto becoming fully mature.

But why partner? What are the actual benefits? And when you do partner, how do you make it work and leverage that partnership to truly bring value to your customers. These are the questions that Bill and Aseem, who was previously an Azure executive, are going to break down for us today.

So, let’s kick it off.

 

Matt: Thanks everybody for joining us for this Madrona podcast. I am Matt McIlwain and one of the managing directors at Madrona, I am just delighted to have one of my fellow partners Aseem Datar here with me as well as CEO Bill Richter of Qumulo. And what’s fun about this conversation is that we’re going to be able to look at.

How companies partner with large enterprises with large platforms and, look at that journey from a couple of perspectives. let me start with Bill. And I think there’s a more abstract question here to ask, which is, why does a rapidly growing private company want a partner? What are the benefits of that to you? Vis-a-vis going directly to market with customers.

Bill: Hey, Matt, for you and the Madrona gang, and Aseem, I just want to say it’s absolutely great to be here with you. I’ve had the distinct pleasure of being able to work across four or five companies now with the Madrona community and it is just, it’s been an outstanding experience.

Okay. For your question, why do it? That’s a great place to start. Look, I think in any successful startup or growth-stage company, like Qumulo, focus is everything. And we constantly ask ourself this question over and over again, inside the company: what are the one, or very small number of things, that we’re going to do better than anybody else in the world. And I think that’s a very wise strategy. The other side of it though, is if you’re doing one, two or three things extremely well, that implies that there are dozens, if not hundreds of other things that you don’t do. And by being able to partner and complement best-in-class capability with somebody else’s portfolio in service of customers, it’s a very sort of simple and sound strategy.

Bill: And that’s really where the notion of partnering comes in for us.

Matt: So within the context of your strategic focus, are there ways to get leverage out of partnering with others – that’s leverage that is mutually beneficial?

Bill: That’s right. Leverage is a great way of expressing the kind of business element of this. And that’s something that’s obviously important. And um, I say customer leverage like customer value leverage. So, we have customers — nearly a thousand that know and rely on us for a very specific set of capabilities and helping them manage their unstructured data at scale. They know that they can rely on us as incredibly powerful, reliable, and capable, and then they have all sorts of other things. They want to be able to create more and more connections with their applications. They want users to be able to harness that information more readily and rapidly. They want to be able to use the environment of their choice. And that’s, I think we’ll get into Azure a little bit later, but a lot of our customers have made the decision to standardize on Azure.

And so, when you think about those things, the discreet capabilities that those customers want, and then the power of choice, freedom, and flexibility to run their applications, where they want. That’s a very powerful value proposition for customers. And then if you take the power of that value prop for customers and work backward to a partnership, things make a lot more sense to both sides, much more quickly.

Matt: Yeah, that customer centricity, I think, we’ll keep coming back in, in our conversation, but Aseem, when you had your Microsoft hat on for many years and you were working with third parties outside of Microsoft, why partner from that perspective? What were the goals of a big company around partnering with other software companies?

Aseem: Yeah, it’s a great question. And I think Bill alluded to some of it, which is, it starts with the customer, so I won’t repeat that point in terms of deriving customer value, but I think two things are super critical. One is, in general, Microsoft has always been a platform-centric company — like the companies built platforms. If you go all the way back to the Windows days, and even with Azure, like it’s a horizontal platform. And from a customer standpoint, platforms are great. But you also need solutions on top of the platform. And that’s when the focus that Bill talked about, that Qumulo delivers combined with the power of the platform will complete the solution in that particular scenario.

And while platforms get bigger and richer, the value that somebody like Qumulo provides is completing the solution, getting deeper and deeper into those verticals. And doing, you know, not just based on the value prop, but also last mile, you know, excellence that creates value for customers.

The second part of that is scale. Microsoft operates at a lot of verticals, a lot of customers and while I think somebody like Qumulo starts off with a deep focus, Microsoft, as a company also sees varieties of those applications applied in different industries.

And so, to be able to use the power of the field, the power of the sellers, the power to transcend industries is what gets you massive scale. So, Bill and team can focus on building great product, and Microsoft can work with them hand-in-hand to go achieve that scale once a flywheel is established.

Matt: That’s really helpful. And maybe we can jump into this actually, Bill, before we get to Azure. Let’s talk about one of your other prior partners. One of the very unique and differentiated things around Qumulo is that it’s a software-only solution that scales across any type of hardware.

Whether it’s a box or a cloud, and a lot of your customers even still today prefer to have their implementations in the private cloud. And so that took you down a path of partnering with some hardware companies. Tell us a little about that.

Bill: Yeah, sure. And this was one of those things that just happened. It started with an individual customer. I’ll tell you a story. We had a customer — it was a well-known animation studio in Los Angeles. One that makes many of the movies that we all enjoy, and they became enamored with our technology. They tested. They loved our software and then they told us, “Hey, Qumulo, we actually have a private cloud agreement with HPE. (Hewlett-Packard Enterprise) That’s the standard that we’ve chosen for our private cloud.” And actually, they put it to us. They said, look, you’re a software-defined. That’s why we bought you. Now. We want you to deploy on HPE. Now what a great way to start a conversation off with HPE. Where one of their large global customers is saying, “Hey, I like you and I like them. I want you to work together.” I will tell you that experience cuts through so many barriers that might entail a partner program and a step-by-step process because it gets the attention and the emotion of senior executives on both sides.

And so we started with that customer. It was an easy certification for us. That’s the value and the power of our software. They deployed it. And then we worked backward from there to start asking, hey, this use case is now established. There are so many other customers, like Aseem mentioned the notion of a flywheel, and that’s what everybody’s looking for in these partnerships. And we began to dominate that vertical of media and entertainment. And then very quickly after we started stacking up the adjacent verticals where we really serve customers, places like life sciences and healthcare organizations and oil and gas companies and research centers.

That was about four or five years ago. If you fast forward today, that is an at-scale partnership that’s been enormously successful for Qumulo. It’s enormously successful for HPE and both sides would say, Hey, we’re just getting started. And maybe one last point, and then I’ll pause is just the strategic fit.

Bill: HP is a great brand. It’s legendary in Silicon Valley. In fact, many would attribute it to starting Silicon Valley. But what they didn’t have is a scalable, unstructured data service, like Qumulo, and they recognize that. And what we didn’t have is global scale with tens of thousands of customers in every country around the world.

And so, you put one and one together and it really does make 11 rather than one and a half or two and a half. And I think that’s the secret to our success.

Matt: Let me pick up on two things there. One is this idea that the partner has something complementary to you and in this case, not only a complementary go-to-market organization, but also an international one, I’d love you to speak a little bit to that, that the leverage that gave you in the company and working with HPE from an international perspective Well, I’ll start there.

Bill: Working with any large organization, the power of their geographic presence is enormous. We have Qumulo deployed today in something like 50 countries around the world, all the big ones that you’d expect, all the major economies, but also some of the smaller ones all across South America, all across Asia into Africa.

And then of course, with a lot of concentration in the economic centers, that’s incredibly difficult for an emerging company to do on its own. And also, not just the logistics of it servicing customers around the world, but the brand recognition. If you’re way out and Chile or South Africa or in Taiwan the brand recognition of a global company, whether it’s Microsoft or HPE or some of the others really matters to those companies, it gives them a sense of trust.

The flip side of it, is you sort of think like, well, what’s in it for the big company or what’s in it for the platform player. I think it’s a real disappointment for customers if they’ve adopted a platform player, even the biggest companies on Earth, and then they get the feeling that they’re in a walled garden and the only services or products that are available to them are branded by that company.

Bill: Because they know that there’s going to be parts of that stack that are either missing or very underdeveloped. And so, it’s the open organizations the ones that open up their platforms and let customers know, hey, when you come here, you’re either going to get the best product that we’ve created that leads the category, or very easily, you’re going to be able to adopt other technologies that are best in their space. And you’ll never have a walled-garden experience. I think that’s very powerful, and we’ve seen that certainly with our partnership with Azure and some of the others as well.

Matt: No, I think that’s really well framed. And the other dimension here is the time and timing. You said, hey, look, we’re four to five years into this HPE partnership. It’s now really at scale. And I think sometimes it’s hard for younger companies to know that something’s going to take, two to three years, let alone two to three months to build out. These partnerships do take time. So, I’d love to hear When are these companies far enough along that they’re ready to actually work with a platform player.

Bill: Look, there’s a, there’s a sine curve of emotions when you’re developing these partnerships. There’s the excitement of getting the attention of a larger company in the early work people strategize together and see the opportunity. There’s a dip somewhere along the way where you realize, hey, there’s some really hard integration work to do or figuring things out there’s commercial agreements and stuff like that, that um, is hard work but necessary.

But then, the real thing that has to happen is you have to find your first customer. One is the hardest one to get. But one makes three and three makes nine and nine make a hundred.

And there is an element of being steadfast about recognizing the strategy, knowing it’s going to take time, knowing it does start with one. And being able to create some repeatability there because especially for a larger company the first thing that their fields will ask is, hey, how many of these have we sold? Or how many customers have we made successful? And so, every incremental win together makes that easier. And then the flip side of that is the early wins are the hardest.

Aseem: My perspective on this is I think it really comes down to two buckets. And I think the first bucket is what gets the technology companies and platform providers interested. And I think it starts with incremental value that you can go create for your customers.

Like the solution that you have as a platform and the solution that in this case Qumulo brings — can that create incremental value for customers that then creates differentiation in market. So, I think, the question that a platform provider would ask is, so why does Qumulo plus Microsoft make it better than any other solution in the market?

And is that something that’s long enduring and can that continue to provide customers the value that they need over time, and can it only grow? So, I think that addresses. The why question? And can we go tackle these white spaces? Which gets everybody interested. And then the how and what of that is really around what I call the Happy Meal Litmus test. Which is, do we have five happy customers using the product day in and day out? And it’s hard to get the first five. And, as much as people think that Microsoft is a very, orchestrated big ship, you know, my boss used to say it the best, which is it’s a bunch of mini canoes all going in the same direction. And to align all those things from the outside in is incredibly hard, but nothing gets the attention more than customer demand and customer usage. And if you’ve gotten a path to get five happy customers on the platform you start to identify all these friction points as companies partner, and then it’s a matter of like, how do you smooth these out over time, one by one. And then the sixth gets easier. The seventh gets easier and then very quickly everybody including engineering, product, go-to-market, sales, like these things start to sing in, in one integrated fashion. And that’s when I think the flywheel gets established.

Matt: Well, That’s I think really helpful, strategically, conceptually. I’ve heard you both talk a lot about, bringing the customers. Bill. Maybe you can talk us through now bringing us forward into the Qumulo, Azure partnership and some of the early days of getting that partnership going and finding that first customer.

Bill: I guess the first thing to talk about is just to spend a little time on the tech. Qumulo has built the world’s most powerful software defined, scalable, unstructured, and file data management service. And what all that translates to for our customers is they have petabyte-scale environments with millions or billions of pieces of unstructured data. It could be a genetic sequence. It could be a radiological record. It could be a PDF document, but they’re at scale. And those customers derive value by being able to consolidate that information into a single place and then be able to reason over it.

And the at-scale part is really hard. In fact, we just won our 35th patent last month as we’ve built this technology. And when you look through the Microsoft catalog, there’s obviously Azure has an enormously powerful services, but in this section, they were missing something. And so, by working together and being able to help customers build these environments in Azure, it’s really win-win-win. Azure will end up allowing a customer to get more out of their services and deploy more applications, more thoughtfully and more rapidly. Qumulo wins for obvious reasons that for us, it’s a SaaS service sale. And these customers, it’s a real problem for them that we solve together. And before we embarked on this partnership, you can imagine that we spent a lot of time interviewing our customers about what they were trying to achieve, particularly in the public clouds. How they wanted to do it, how they wanted to consume our software and then we got a lot of advice from Microsoft as well. Like, Hey, what have other partners done? How has it been successful? What are the pitfalls? And we took all that aggregated knowledge together, and as Aseem said, you always have to start with one. And um, know our first one was one just within the last six months. And when we explained to the customer Hey, what can we offer you together? They jumped on top of it, and that one lights up the imagination of the Microsoft field in our field.

Bill: And we’re able to go to customers that are like for like, and solve that same problem for them. And then the flywheel has begun. That’s a little bit of the journey. And again, it starts with technology and maybe a better way to put that is the unique value on the problem that you’re solving and who solves what problem and who doesn’t. And then that forms the framework for what I’d say is a healthy partnership.

Aseem: If I might add to that. The other nuance to consider is that the first couple of customers you get are more product-led sales versus go-to-market motions. And I remember the engineering team in Azure, leaning into partner with Bill, as we talked to, I think it was Casepoint if I remember right. Leaning in and saying, look what must be true and what must we do in order to make the product deployment super successful for Cause on Azure. And I think that’s an important nuance to call out because the go-to-market, the sales motions are not established because they’re not there.

And so engineering leading in, making sure that, you’re around 24/7 in a services world to make it successful, to get mission critical applications on the platform. It is really the first, I would say P Zero step to success. Once you’ve got that nailed down, then I think, you know that you’ve got a product that works.

And then I think things follow on the go-to-market and the sales side and the partner programs kick in. But that, that I think mindset of product-led sales is important to begin with.

Matt: Yeah, I agree. I agree with that. Go ahead Bill.

Bill: I was just going to jump in because I don’t want to lose this point here. It’s super important and it is a nuance. Aseem is right. We spent a lot of time with really great product folks and engineers inside the Azure organization. And that’s where it should start. If you haven’t solved it there, then it the solution probably won’t get off the ground.

What I learned along the way is that to know the difference between a product sale and a field-led sale and know where you are, as Aseems’ pointing out in that journey, because, the, I think the failure mode here that ought to be avoided is sort of assuming that since you’ve solved the product part this equation with the products in an engineering organization that, “automagically,” the field will know what to do And so there is a sort of a transitional period where you have to move you maintain and continue to invest in your product relationships with these organizations and then know that there’s more work to be done and really accessing, and frankly, making it’s brain dead simple for the field to be able to bring to their customers if it’s even remotely complex, most fields will stay away from it.

Matt: Aseem, you, you’ve got a wealth of experience in these areas, helping, outside companies navigate Azure. What are your perspectives on these topics?

Aseem: Yeah. Great. Going back to that model of, I think once you’ve gotten your first five, I’d entertain that next step and say, okay, you’ve gotten the crawl now let’s get the walk. And how do you go from five to a hundred? And in that sense, I think it’s important to probably pick a few industries to target. And like Bill mentioned, make it super easy to succeed in that industry and you probably have some proof points for the first five, right? So, let’s pick media and entertainment as an example that Bill, you were on, and say, okay, great. Now let’s make every seller in the field, who is a media seller, equipped with what they need to go sell. And it includes battle cards, compete cards, and really compelling case studies of others in the industry like you use Qumulo and here’s why they found success and here’s how it was successful. So that way you start to nail that industry and it’s almost like you’ve got to establish your birthright in that industry and say, Hey if this is an industry that I’m going after, I won’t fail. And every opportunity will be Qumulo plus Microsoft opportunity. So once you’ve established those set of hundred customers, then I think you can say, okay, what are the adjacent industries that are then easier to go into, so then you’ll go from a hundred to the next hundred and beyond.

There is an interesting element here on, even within the hundred, as you’re chasing those, given that these are highly involved technical sales, you’ve got to bet a little bit on the sellers who are very tech savvy, who are forward-leaning and who want to take a long-term bet. Which is not just how do I meet my quota in a quarter, it’s almost like, how do I make my year? Which is, you know, the next year and the year after that. So, I think a colleague of mine put it very well when I was at Microsoft — you’ve got to bet on the heroes. And I think you’ve got to curate the global black belts, as we would call it within Microsoft, which is an elite group of sellers who would be incentivized to not just sell, but also make sure that the deployment is done and there’s high amount of customer satisfaction. So, you’re shepherding, not just the sale, but also the customer experience.

Matt: I love the bet on the heroes, and I think you’re right. Finding these champions that not only are aware of this better solution, but they really want to deliver differentiated value to their end-user customer. And they’re technically savvy enough and they listen to their customer enough to want to be the hero on solving a problem better than they can solve it. Otherwise, which gets into an interesting question, and this kind of issue varies from partner to partner, but oftentimes, certainly in the case of the cloud service providers, they also have their own first-party solution that’s similar to your third-party solution. So, Bill, I think that’s probably an area that you’ve had to wrestle with before. I know that we’ve had across a bunch of our portfolio companies, including the likes of the Snowflakes and Amperities but how has that journey been for Qumulo?

What lessons do you have that you’ve learned there?

Bill: If you put yourself in a customer’s shoes and there is a first-party service that meets your needs and it’s great. And it’s owned by the platform player, you should have a working assumption that will continue. And look, we do everything in service of customers and if I were them, I would probably do the same thing. That’s the easy button. So, understanding that to start off with, I think is really helpful. I meet a lot of fellow CEOs that are like, Hey, why isn’t the cloud provider selling my stuff more — they ought to do that for me. And maybe they should, but that’s just not realistic. So, the approach that we’ve always taken is, Hey, I have to be 10 times better from a starting point against whatever sort of neighboring first-party service might exist. And then I have to continue to be better. And that kind of mentality will solve a customer’s problem in a unique way that’s powerful for them — meaningful for them — and it will enable the platform player to want to take you seriously and move forward with you. I’ll sum that up, have to be wide-eyed, you have to start with the customer, and you frankly just have to be fundamentally better.

One of the things that Qumulo offers is cross-environment capabilities. You can run Qumulo on Azure. You can run it on AWS. You can run it on GCP and you can run it in your private cloud. That’s just a capability that any first-party service cannot offer and that’s strategic for customers and it’s powerful.

Matt: Yeah, that’s a really great point. One of the things sometimes the earlier stage. Get a little bit frustrated with and caught up in is you referenced certifications before and becoming a pro in the preferred program and complying with a whole bunch.

Kind of rules and at some level I think we all get this that, the big companies need to know and be able to be competent in the third-party solutions are recommending. But sometimes that feels like a little bit, being lost in the desert a bit for a while before you’re seeing any of the fruits of your labor in terms of customer wins.

Bill, can you speak a little bit.

Bill: Yeah, and this is I think a really good topic. It’s something that we’ve learned a lot about as we’ve done this over the years. Putting myself in the shoes of the platform player. You’re lending your brand to a smaller company, and you want to have some level of credibility that you’ve vetted it and that you’re willing to put your customers on it, so I completely understand the notions of the certification programs. The other thing is for the big platform companies, there’s hundreds or thousands of ecosystem partners and they need some way to scale that organization or scale those interactions. So, it’s all understandable. I think the mistake is to believe that all those enabling steps are results. The results will come from the customers. And so, if you go through the. 15 step process, and then you’re done. And then you wake up one morning and go, okay, now, great. Where’s all the sales.

I think you’ll wake up very unhappy that day. If you deploy some amount of resource to make sure that you’re partnering well and working with these platform players and the way that they like to work with, but at the same time, making sure that your organization knows their job is to add value to customers and win customers, hearts, and minds.

That is really the best practice, so ones necessary, but not sufficient. And you really have to do both.

Matt: I think we’re getting a little bit more now into some of the, the nuts and. I’m curious in order to build beyond the necessary pieces, the programs and stuff. What’s the cadence and the resources that you would recommend, it doesn’t strike me it’s enough just to have a quarterly business review between the CEO of the company and some key partner leader at the other company, there’s got to be more resources and weekly daily activity going on in the field.

Bill: Hey, Aseem. I’d love to hear jump on this one.

Aseem: I can’t answer the resourcing question, Bill, that’s you, but to the stage of engagement, especially when you’re trying to get your first couple of customers or your first five, I think quarterly is not enough because what typically happens is both teams get together, they decide on some activity, people go and work on their own and they come back in, in quarter and realize, Oh we’ve barely made any progress, even though they’ve been at it. I think, to the extent of setting mini-milestones in saying, Hey, what needs to happen in six weeks, and treating it as a sprint is something that’s really been worthwhile. And what I’ve seen work in really successful cases where you’ve got a customer, you’ve got a three-way essentially between the customer, the company like Qumulo and Microsoft. Because then all three parties are equally involved in all three parties want to make it successful. That’s the recipe for success. And I think faster turns to get to outcome. Is where I would put my bed on versus a quarter cadence. I think once you graduate from first customer to fifth, yeah, you can go to the quarter, but I think the first two or three, like it’s gotta be like a 6-week type of sprint.

Bill: Yeah. I agree with that. I, I would just say in general more is better. You have big company and small company. And one of the expectations of a big company, they know that they might be slow because it’s, there’s a lot of people and organizations to manage. And so on. The expectation is the small company would be fast. That’s one of the reasons why I think some of these larger companies like partnering they learn from startups about how fast things can get done. But that also implies, as the emerging growth company, you have to live up to that you have to be fast. And by the way, our cadence is more like weekly with our partners, if not more frequently. And the idea is to be incredibly responsive as Aseem said, have a lot of turns really quickly because that’s what generates momentum. The thing I wouldn’t do is defer to the larger partner, just simply run at their cadence because they have a lot going on. And um, you know, you might find that in the conversations with them, they’re like, geez, you’re slow. And you’re like, no, I’m working at your cadence. And they go, that’s what I mean.

Matt: well, hey, let me, just really briefly touch on. To two topics that kind of come from the same thing, but from different angles, which is the, how do you approach getting to the contract and the economic alignments in these partnerships, which sometimes feels like it drags on forever. But then conversely, how do you build genuine people-based trust relationships, which I think is the more enduring thing cause inevitably, both sides of these partnering relationships are going to have moments where they surprise and exceed expectations, and there’s going to be disappointments and falling short of expectations.

Bill: Oh boy. Yeah. At least in the first point we, that’s probably another podcast, but look, it’s hard. The large organization has really long contracts that are very often, to Aseem’s point, not Built in is bespoke way. In other words, you look at the contract, you’re like this isn’t even written for me. And so that takes a fair bit of work. At some point, there is some element of holding your nose and, making sure that you’ve protected your organization, but moving on, which is I’d say some science and a lot of art and maybe even some legal fees.

I did model my daughter’s cell phone contract — my personal contract with my daughter about how much he cell phone, using one of these.

It was very one-sided, and I modeled it off of one of these contracts, not actually from Azure, but somebody else. But maybe more importantly on the other point around. Building trust in these relationships because you’re right, Matt. You hope for there to be nothing but a lot of success, but you also have to figure in day-to-day life something, at some point it goes wrong. and I would just say the single most important thing is transparency. It will be okay if you communicate well and you’re transparent, you do the right things. I, my sense is that any organization has seen plenty of challenges and know that you can work through them as long as you’re both sides are being transparent. Where it really breaks down is if somebody is worried about scaring somebody and, tries to sweep something under the rug that almost never ends well. So, if I had one word, it would be transparency.

Aseem: Yeah, I echo that, and we used to call it, embrace the red internally, which means that look, if you’re embracing it, you can own it. The only way to go is up. And, we have this notion around let’s not have watermelon metrics, where they look green on the outside, everything is great, but you ask two questions and it’s remaining red

Matt: Great. Well, hey, this has been fantastic. I really want to thank Bill and Aseem a lot of great nuggets of insights there. And I hope that this is helpful for other folks as they’re looking to partner with the big cloud service providers and other partners in the innovation ecosystem.

Matt: Thanks again, guys.

How SpiceAI is Tackling the AI Tooling Gap with Luke Kim

In this episode of Founded and Funded, partner Aseem Datar sits down with co-founder of Spiceai.io to talk about the power of building tools for developers, the difficulty of integrate AI (SpiceAI is making this easier for developers) and moving from a big company to building a startup.

Transcript below

Welcome to founded and funded, I’m Erika Shaffer from Madrona Venture Group. Today, partner Aseem Datar, sits down with founder Luke Kim of Spice AI. Spice is a new startup focused on helping developers integrate AI into their applications. The founders Luke and Phillip LeBlanc recognized that in order to integrate AI, developers need data engineers which is a high bar for startups, so they set out to build tools to alleviate this requirement.

The first implementation of Spice is focused on their blockchain data platform. This public platform, enables developers to access Ethereum and smart-contract datasets, like Uniswap, across real-time and historical data with a single SQL query.

Spice plans to extend the platform to other blockchains, like Bitcoin and Binance Smart Chain (BSC), and to traditional time-series datasets. It will be available in beta next month.

Aseem and Luke dive into the power of building tools for developers. They talk about the transition from working at a well established company to building a startup and the different skills that are necessary to make that successful and how AI is something developers want to leverage to build intelligent applications – but it’s not easy.

You can learn more at Spiceai.io

Aseem: Hey, Luke. Thank you so much for joining us today. I’m really excited to have you here and get the opportunity to chat.

Luke: Thanks, the same. It’s also good to be here. Yeah, I appreciate the warm welcome.

Aseem: Awesome. Awesome. What part of the world are you at?

Luke: I’m in Seoul, South Korea. And yeah, fun fact about me. The first thing a lot of people ask me about is my accent. I was born in Korea, but I grew up in Australia and spent most of my childhood and University there. And then came over to the U.S. about 12 years ago, spent the last 11 years working out of Seattle for Microsoft, which is of course where we first met.

Aseem: Yeah. It’s amazing that I was just recollecting and counting backwards. I think we’ve known each other for over 10 years now, which is amazing, and I think in cloud world, its dog years, so it’s a great to be reconnected.

I’d love for our listeners to know a little bit more about your background. How the journey at Microsoft? What did you do at Microsoft and what team you’re on? Any exciting projects you worked on? So, it would be great to start there.

Luke: Yeah. For sure. As I mentioned as that 12 years at Microsoft. Even before that, I had done internship and I was part of the student program. But in the last two years, I was in the office of the Azure CTO reporting to Mark Russinovich, which there which is just an amazing experience. I got to build an incubator there where we worked on a whole bunch of interesting projects.

Some have been released. Most of them were open source and some have yet to still be. Just an amazing opportunity. You got to work with people across Azure, the industry, a bunch of customers, and what comes from cool stuff. So, three years before that worked with Nat Friedman, who just stepped down as the CEO of GitHub, and built a bunch of the services and infrastructure behind both GitHub and GitHub actions. Along with a product that we had called AppCenter, which helps develop his build and operate mobile app mobile applications. And yeah, so most of my career been building tools and services to help developers build software be more productive.

Aseem: Well, that’s amazing. I think what a stellar career at Microsoft, working on two big products, of course, GitHub and then Azure. Tell us a little bit more about, what excites you. I know you talked a lot about like working with developers but give us a little bit more color on what is the exciting part, tell us a little bit more on the project you work at Microsoft.

Luke: Yeah, for sure. There are two things that come to mind. When I think about developers in kind of that track, I just think that it’s an amazing way to scale. If you think about the leverage that you have, you can, if you’re a developer, you can build an application. You could build that overnight, and that could affect millions of people, right?

That is there’s very few other places in the world where you could spend a week building something and affect so many people’s lives. I think. Now if you take building tools and services for developers to help them do that, you almost get this double leverage. I just think that’s an amazing way to contribute back to the world.

That kind of leads into the second thing, which excites me is, I think at some point we’re all asking the question, like how can we contribute back to the world? How can we contribute to people? For me this like amazing set of leverage through helping develop is help other people. I’ve been privileged enough to be in my career at Microsoft in positions where I’ve been able to do that and lead teams and build teams. I was literally hired out of a university as a grad hire. It was probably just a year into my career. I was working on visual studio, and I was working on the debugger like some deep level stuff. At the time we were just transitioning to Windows. And that’s a new architecture. So, we didn’t have the tools to write that software productively.

Those are set of tools called ‘system internals’. That helps you do diagnostics and write software. Mark Russinovich at the time, he had just had his company acquired by Microsoft, a technical fellow who had helped write the tools. I was like this grad hire and I was struggling with writing the software.

And so, I emailed him, and I said, “Hey, Mark, are these tools available for this new architecture? Because it would really help us run the software.” He replied, “No, sorry.” But it turns out that I was a little bit bolder and so I replied, and I said, “Hey, if they’re not available, would you be willing to give me the source code? And I will go and convert them and put them over to this new architecture, because it would really help me out my job.” And he said, “that’s an interesting idea.”

At the time, only just a couple of people in the company had access to the source code. So, he emailed me back. There was no Git at that time. So, he literally emailed me, “see files” and I started doing this port and I would email them back to him. I did a couple of tools and within about six months, a bunch of people across the company were using these tools to build windows.

That’s how we first got to know each other. From that point on, I was working. This is internal source for the rest of my career. For like the next 10 years, I was like a pseudo developer or manager for these insistent tools.

Yeah.

Aseem: How wonderful and I think it’s amazing to be a part of such a large enterprise yet have the personalization and the drive. Two things that you said stood out for me. One was the ability for you to work on scale projects. You talked about the two for one kind of thing. When you build tools for developers and when developers build solutions for the world, you get the double benefit and the second thing, which you also highlighted, right? Finding these white spaces, right? These spaces of opportunity that can then be converted into products that many people can use, which is the example that you cited working on working with Mark. So, coming back to what we were talking about, you had a wonderful journey at Microsoft and a wonderful career. You’re moving mountains. Tell us a little bit about this thing called DAPR that you worked on, where we’d love to understand what that was and how that has bearing into what you’re doing today.

Luke: When I first went and joined Mark’s team I said, “what should it work?” And he’s like, “well, there’s a couple of people in my team. They’ve been looking at this runtime that helps develop is build distributed applications.” Because as we’ve moved to the cloud and not just the cloud, but the cloud and edge, these applications have become more and more complex.

So now before you had an application, which was just on a single machine, 10 years ago, now you’re dealing with all these distributed pieces across the different servers, different infrastructure. How can we make that even easier and benefit developers so they can just focus on their business application?

What DAPR does, is it abstracts away a lot of the complexity. So, if you just need storage key value, you instead of going and having to, not only choose a technology if they must choose Reddis or Cosmos or some other store, but I can also just use a simple abstraction over HTTP rest APIs to store my state and focus on my application.

That’s what DAPR does, it provides a whole bunch of these building blocks in terms of state. It has Pubsub, it has Secrets Management, it has a whole bunch of these like basic things that you need to build a distributed application. It lets you just focus on building an application and not doing all the distributed systems behind the scenes.

At the beginning it was called Codename Actions. They’d spent maybe I think, two months on it at the time. I came in and we built an entire team around that and built up this project and released it probably within the first three months.

So, we released like a private preview of it. There’s a whole bunch of lessons from that, one of the things was that it was radical, it seems basic right now, but it was a radical idea when we first did it. We got a lot of pushbacks both internally and across the, I wouldn’t say necessarily across the industry, but a lot of developers ask, like why do we need this?

We just pushed through; we keep kept working on it. After about two years, when we developed it out, we had so many people come back and some of those same people are like, why do we need this? To say, this is a savior. This helps us be so much more productive.

I think as a founder you always go through these moments at the start where you’re doing something just a little bit crazy, just a little bit out there. A little bit beyond what people have as their normal mindset. And you’ve got to be able to see the vision and push through that.

What I say to some of the guys on my team, though, at the very start, they were getting a bit down because, they’re getting not as much of the attraction that they thought they were going to get. Look, I said to them, this seems like a crazy idea now, but wait, in two years’ time, some of these people will be telling us that it was their idea all along.

It was just so funny. Like two years after that we had people come back and say this was like our idea like we believed in this from the start. People will come around. If you truly have something. Yeah, I’ll say, in terms of the fanboy movement, was you just think this is just a small open-source project, but I had the opportunity to be in a Satya a staff meeting, and Satya knew about DAPR and he was supportive of the project. That was just super cool. Like we were part of these massive organization. I think it was like 140,000 people at Microsoft. Yet Saatchi, like he knew about DAPR. He knew how it worked and he knew how it makes life better for developers.

We were able to present that to him. One of my fanboy moments was, I was able to debate with him how we could make applications better in a staff meeting. So yeah, I thought it was cool.

Aseem: No, that’s awesome. I remember being in that meeting and I remember the red side but that’s a story for another day. Hey, as you, one thing I think our listeners would love to hear from you is, a great time at Microsoft. You’re on a meteoric rise as far as career is concerned, but then I think eight months ago you left to go build this thing called Spice. ai. Tell us a little bit about like, how you thought of the opportunity? What you’re seeing in the world.

What are the challenges that developers face today? You talked about building applications for the future, which is a theme. We call it as ‘intelligent applications’ over here at Madrona and we have a thesis around it. We’d love to hear from you on your, in your own words, on what challenges are you seeing today? What are the core value prop that you’re building forward and how do you expect to change developers’ lives in the future?

Luke: Yeah, that’s it. There’s a lot. That is a great question. In terms of transitioning from a big company to do a startup, it’s a journey, right? If you’re in a big company it’s, especially today in tech, it’s such, I think a great opportunity to you. You have the ability, have all these resources at your disposal to really go make a massive impact. Of course, you also have a bunch of the safety and security in terms of just regular paycheck and all that goes along with that. Stepping out into going and doing like into a bunch of ambiguity, a bunch of unknown, and doing something really takes I think, you to be intentional and make a choice about what direction you want to go in your life.

Coming back to what I said about this stuff, to me, you get to a point in your life where you want to decide, like how you want to contribute to the world. For me, I always knew, I had done some stuff like a long time ago, 12 to 13 years ago. I knew for me that the way I wanted to contribute back to the world is in like leaps of innovation, like in ways where we can really move the needle.

To me that was like doing a startup and doing my thing. Honestly, there was a lot of fear that we had to work through to get there. There’s a great book. It’s called Feel the Fear and Do It Anyway. That was the theme. It was like, yeah, it’s scary. At some point you got to choose how you want to contribute.

For me that was leaving the safety net of a big company and going, doing. Yeah, if you can find people to go do it with, I think there’s also something special about the start of a startup. I’ve heard this before in that it only ever happens once.

Like you can never go back and redo like the startup something, it’s like the start. And I think experiences are also even better when they’re shared. If you can go find a couple of your friends or a couple of people that you really respect, you can go and do that style of this startup and do it together and have a lot of fun. I think everyone should experience in my opinion, at some point in their life.

Aseem: That’s great. I’m going to, I’m going to bookmark that reference to that book and make sure I read it. But more importantly, I think what you said is as along the lines of finding your own tribe, right? Like finding the people that you deeply respect that you’ve worked with in the past and who would be allies in going and solving those tough challenges. So, coming to understanding the developer space like a space that, we’ve looked at from close quarters, both at our time at Microsoft and even now, like what challenges are you seeing in the ecosystem? How is Spice. ai positioned to think about solving those. Maybe I think I know the story, but it would be great to learn about how the idea came to you what you experienced in your time and how did you formulate this thinking around building Spice .ai?

Luke: Yeah. So, in terms of in intelligent, like you mentioned intelligent applications and you have a whole thesis around that. Well, it all really ties together with developers. I think there’s going to be a few challenges going forward. One I think a lot of people in the tech space already know, there’s just so much demand for skills. I think it was even back like 2018. I remember Saatchi, one of the conferences saying that more developers were hired outside the tech industry then within the industry. So, people who are lucky in banking or insurance or whatever, there’s more developers outside. That was just a, it was like an ‘aha’ moment to me, an amazing a statistic because if you follow that to directory, then this is going to be more and more demand for software, more and more demand for developers.

If we are going to meet that demand in the world, to make all the software and to make all these applications that people need. Then we’re going to need help to build software. To me, what I saw or both at Microsoft and across the industry, and in my own side projects, that it’s still too hard. One, I think to really be productive and build a software. But also, if you think about that demand for software, we’re going to need help. What I believe is that help can come from AI because AI is not a magic bullet.

It’s not like some magical thing that’s going to solve their problems, but what it does do, and it does do well, is it helps. It basically you write a program that runs program for you, right? So, like you could take a hundred developers in 50 years and do like a whole bunch of image processing and just normal code.

Or you could build an AI model that will go and write that code for you. So, what I believe as a thesis going forward is that intelligent applications are not just going to be a nice to have but are going to be required. It’s going to be a necessity in the next 5 to 10 years to not only compete, but just meet the demand of how much software that we need. Because we’ll use AI to help build software as developers, it’s still too hard to leverage AI, to help build applications and help you build a better application faster.

It’s really the thesis of the company. We want us to go out and solve that problem and solve that gap. It’s honestly a difficult problem to solve, but if we can help developers build better applications faster using AI, then I think it’s going to not only help developers but help us thrive in kind of this world going forward.

Aseem: That’s amazing. Look, and I think we share that worldview. Making lives easier by, by being able to create software at a faster pace. That’s more intelligent and that can self-sustain to a certain extent. I think one of the things that you said that’s most interesting is how you get the scale effect, right? If you’re able to empower developers, then you’re helping them write software faster, which means that you’re getting to the meat of the problem and the solutions faster in whatever industry. There’s a saying where every company is a software company and I see that true more and more in today’s day and age, especially because of distributed computing, because now you have access to all these tools, memory, compute, storage that otherwise you would you’d be hard pressed to get. So that’s a big point of view that I wanted to highlight.

Luke: It’s just like one anecdote on that in terms of scale, like we saw his company and they had spent three years building this algorithm to basically do routing on the edge. Then after the three years, someone came along and said, “Hey, I wonder what would, happen? Just as an idea, what would happen if we tried goodie and our AI model to see if we could do this right. Could we get Cyprus?” They spent like three months on that AI model, and they got better performance. They got like a ten for one scale by applying AI to the solution. Now, of course, like I said, AI is not a magic bullet, but it gives you an idea of just how much faster you can develop some things then just a traditional approach.

Aseem: Yeah, that’s cool. I think that sort of ROI is amazing from a developer point of view and who wouldn’t want that. So, following up on the Spice .ai conversation, tell us a little bit about, potential customers you’re talking to, any lessons learned so far, and maybe just give us a little flavor of the use cases that you guys are finding interesting, especially with Spice .ai at this early milestone.

Luke: Yeah. So, with this Spice the idea behind it was to help developers build these intelligent applications, not just do AI. I think there’s a ton of AI companies out there and we’ve made a ton of progress. But if we can use some of the techniques that we’ve really matured as an industry of the last 10 years, things like I really felt, Dev Loop, we live preview, so the idea is can we take some of these things and help develop is built in an intelligent application, faster, better.

If you think about, what you would do as an intelligent application, like what is the intelligence? For us, it boiled down to basically a decision engine as the main core thesis. If you think about what you’d want an AI to do in your application.

Well, we think it’s to help make decisions. If you think about a couple of use cases around that, we had a food delivery application and Uber Eats and they basically had to, when they got an order, they must decide about what delivery driver to route that order to, like what’s going to be the best. What’s going to get it to the fastest. That’s a decision. When they first started, they just use people, they just hired people. They would get orders and route it to people. Route it to these drivers. If you could take a decision engine and put that there, you can get the order, have AI decide fast, which is the best way.

There are so many different cases like that that you can choose. Everything from even just like retail trading, these days really took off with the things like Robinhood. But deciding like what stock to buy. That’s a decision, right? We had a case around, retail shops where you order online, and you pick up in store. Well, what store do you want to pick up that item from?

Right often it’s not actually the store that’s closest to you. And so, it’s a decision. What we started to really realize is there’s a lot of interesting cases where you can build an application where you’re making these intelligent decisions. We started really working on that, but of course, as a startup, you must really focus and where we started a small team, three people. What we found is there’s quite a lot of interesting use cases right now in the FinTech space. You can imagine there’s also a lot of decisions to be made. So not only just like trading decisions, but for example these days especially in the blockchain space, distributed finance there’s many different exchanges that you could, send your order to.

That’s a decision, right? What exchange is the best exchange throughout my order through. So, there’s quite a lot of different cases around this.

I think going forward into the future, especially around like web three, if you have things like, well, should I interact with this person or not? Does this new token, is this going to be a scam or not? And that’s really what we’re going after right now.

Aseem: Yeah, that’s amazing. I think the way I’m thinking of it is you’re really building out an intelligence platform or a decision engine that can have vetted applications all the way from FinTech to retail. Shopping to food delivery. It’s amazing that, so much of these decisions in the future can be thought of as intelligent and automated, which then saves, whole lot of logic writing as well as like individual point solutions. Which is what, what makes it very exciting. I’m privileged on behalf of Madrona to be a part of this journey with Spice.

So, thank you for that. We couldn’t be more excited to see these come to life soon. One of the shifts gears a little bit, Luke, and talk a little bit about, the journey of the startup and as you’re going through building Spice .ai, like how are you thinking about, building a team? Are you thinking about, any early lessons that you’ve seen and learned so far, that would be good to share with the people?

Luke: Oh, so many. One thing, I think just coming from big company to a startup, that a lesson that we learned, it’s a completely different mindset. So, what makes you successful in a big company often is the ability to be very responsive and very reactive, right? So, a problem comes along, and you go back and solve it, right?

We must respond to this thing in the market, then you go solve it and you can have a lot of success that way. Often the opposite, you must go make things happen. Customers don’t come to you, like you’d go out and make them. In fact, we hired an AI ML engineer. One of our first hires, the way that we found him is I literally went through Reddit posts, and I looked at people who had posted good analysis of deep learning frameworks at the time in the area that we were looking at.

I was like, this guy is he’s obviously written some really good content. I just DM’ed him. You’ve got to as a start, just go out and chase down these opportunities and make things happen. So, I think as a startup founder, that’s one thing that you really must switch your mindset from.

From having stuff come back for you, these opportunities show up and just going in and making things happen, chasing us down. So, we started really building this thing in July last year. When we first started, we knew this general thing that we wanted to help developers, but we had no idea how at all, like we literally had no idea.

So, we started 1st of July, by the end of July, we’d build a prototype. We just liked different ideas and we started showing that prototype around. We didn’t expect to do any funding or early raising at all. We thought we’d probably go for a year before we would have to, or even want to do that.

But we shared around and gelled with different people. We were excited, we have some awesome investors on board. People like Mark, for example. Nat Friedman as well as on board. Thomas Dohmke, the current CEO of GitHub, and these guys all really believe in the same philosophy, which is help developers help people. To what happened was in terms of the fundraising journey, people started asking to invest in. Once they saw this thing and so we decided to do a very small pre-seed round in about July/August and that I’d never raised before. Like I did everything from scratch.

Go find people who are like one or two steps ahead of you. So, we were like doing a pre-state. So, we found people in the seed round and a series A round. Who’d just been through that. Cause obviously things change and got advice for them. So, I have a good friend whose David Siegel, who’s a CEO of Glide Apps, which is like a No Code App platform solution. He’s two steps ahead. In between a seed round at the time. So, he gave me so much advice on how to do it. So as a founder, go find these people to do that. The second thing is, really lean on like a lot of VCs that are investors will come to you and say, look, how can I help?

Take that help, lean on it. So, with Madrona early on and with you, Aseem, it was the same. Also, Tim there at Madrona were just so amazing. So how can I help? And I just leaned, I said, look, this is all the ways you could help.

We need help hiring. We need help figuring out like this direction. We want to decide here and how should I also think about fundraising? Like how much money should I raise, for example. I think that support even for when we first did our PR and the kind of announcement about our raise. Madrona did so much help.

I had no idea how to do a PR thing. I had done some PR at Microsoft, but we had a team. The way I did PR at Microsoft was I go to the PR team and work through them. Madrona really helped us do that. So overall, it’s just it’s been a really been an awesome partnership together.

We have, I think, 33 investors all up and we fit them all into this small 1 million rounds. We were offered a whole bunch more money, but we turned it away because we really wanted to focus on solidifying what we’re building first, before we took a whole bunch of money. I would say, there’s a whole range of people who get really involved and help you out and people who, I’ll give you my money and you go, you run with it type thing.

So out of those 33 investors, I think Madrona just helped us out a ton and it’s clear to see who’s on point and on their game. Tim and you, Aseem, have really helped. So, thank you.

Aseem: I couldn’t be more thankful, thanks for the warm words, Luke. But I do think that you’re right about, it takes a village to go create something amazing and I’m so pumped to be a part of the journey. I’m positive that, we do build something amazing and you’re already on the journey. You’re two steps ahead in your own words on this journey. So, it’s amazing to see the progress that you’ve achieved in shadow such a short amount of time.

One last question before we let you go is, what’s your take on the Seattle ecosystem? We’ve talked a lot about the last 10 years, the growth that Seattle has seen, the Northwest is experienced with, the Amazon, the Microsoft, the Google, being in the backyard and becomes the cloud capital of the world. How are you thinking about hiring? How do you think about adding talent? Then any comments or observations of the Seattle ecosystem.

Luke: Yeah. I often think we tend, I’m not sure it was also developed is like this, but we tend to think things in like binary, like it’s this all bad. To me, I often look to think about things in hands, not ours. To me in terms of a lot of the world going to remote, I think that there’s benefits, obviously, remote there’s also benefits of coming together. I believe, Brian Armstrong from Coinbase has written about this quite a lot, it’s in terms of his transition from going to a remote first company. In that the reality is the chances of getting top talent.

The chances are that they’re going to be within, a 15-mile radius or whatever of your HQ is obviously very low, not true. So, if you want top talent, you’re going to have to go chase them around, chase them down across the world. At the same time, there’s a huge amount of benefit to like human connection, and really being together in the same place. I think there’s so much innovation and creativity. I think we’re moving to a world where you must chase down talent, wherever it is, and enable remote work at the same time, have opportunities for people to get together. So that might be like offsites, coming together once a quarter, meeting people in different places. In terms of this yellow tech ecosystem, I totally believe that it’s cloud capital.

If you want to, if you’re in distributed systems. Also, AI. There’s a whole bunch of AI stuff that happens in Seattle. So, if you’re anywhere in that space, in Seattle, it’s a great hub to do that. So, it’s like you have remote teams, but you also bring them together. I think Seattle is an awesome place to bring your team together. Also connect with other people in that ecosystem that really has deep experience in both cloud and AI.

Aseem: So cool. So cool. The way you think about it. I think what’s mostly energizing is there’s distributed systems, there’s distributed development, and now there’s distributed teams. So, you, I think you summarized it well. Talent first, and I think everything else follows, which is a great mantra to live by.

Hey, I’m so excited to have heard from you and, being a part of the Spice journey obviously, people know where to get ahold of you. I know, you’re hiding in the area and beyond, to anybody who wants to reach out to Spice. I think the best way would be to communicate with you and fill that.

Luke: Yeah, absolutely. So, if you just go to Spice ai.io/team. Sorry, slash career, that is careers. That’s where you can see our job postings. You can also just grab us on Twitter, LinkedIn, all the usual places as well. Yeah, so Phillip and I co-founders, you can search us out.

We have a tech crunch article out there, which also gives a little bit of background on what we’re doing as well. Just search for Spice .ai on Tech Crunch.

Aseem: Awesome. Hey Luke, it’s been an absolute pleasure talking with you and we’ll look, I know, you release updates about Spice on GitHub and that’s another place where developers can go to check you out and see the progress you’ve made. We’ll look forward to continued dialogue with you soon. Hoping to see more awesome news from Spice shortly.

Luke: Yeah, absolutely. Yeah. So, our project, the underlying engine we really believe is build up with the community. We are developers. So, it’s all opensource. You can go grab it, all free, and you can run it yourself. One thing, I just want to encourage founders as a last note is, if you take that story from the start where I was a grad hire, there was a technical fellow, you don’t often like just go email these people. I’ve emailed Saatchi before I’ve emailed all these people. Like I would say, as a founder, you’ve got to go do those things and don’t be afraid, be bold, right? So, if you must go email like a CEO, you must go reach out to somebody, go do that. I really encourage you to go make things happen. Don’t be afraid to be rejected or whatever it is, even if you think you don’t, you’ve got no writer to do this because of your position or whatever, just go after it.

If you email someone like you could lead into a great, like for me and Mark, led into 10 years of development together. Yeah. I just encourage you to go through those things.

Aseem: Awesome. Wise words, Luke. Thank you so much for making time out of your busy schedule. I know you’ve got a business to go build. Thank you so much for taking time.

Luke: Thanks, the same. It was a pleasure. Thank you.

 

 

 

Terray Therapeutics Building an Intersection of Innovation Company

In this week’s Founded and Funded, Madrona Partner, Chris Picardo, sits down with Terray Therapeutics founders (and brothers), Jacob and Eli Berlin as well as Terray’s lead data scientist, Narbe Mardirossian to talk about the power of bringing together transformational wet lab processes with ML and AI to speed drug development. Terray announced their $60 million Series A which Madrona led (and Chris wrote about here) in February of 2022. Terray Therapeutics brings together novel methods of creating vast amounts of data around small molecule disease targets, and then applies ML and AI to map the interactions between these molecules and the causes of disease. This is a company at the intersection of innovations between life and computer science and this was a great conversation. You can listen below or on any of the podcast platforms.

This transcript was automatically generated and edited for clarity.

Erika Shaffer: Welcome to Founded and Funded I’m Erika Shaffer from Madrona Venture Group. On this week’s Founded and Funded, Madrona Partner, Chris Picardo sits down with the team leading Terray Therapeutics. That is CEO and founder, Jacob Berlin, CFO, COO and founder, Eli Berlin, and Head of Computational and Data Sciences, Narbe Mardirossian.

Madrona first invested in Terray right before the pandemic hit and all business, especially wet labs, shut down. And we are excited to lead their 60 million Series A. Terray Therapeutics brings together novel methods of creating vast amounts of data around small molecule disease targets, and then applies ML and AI to map the interactions between these molecules and the causes of disease.

Based on research from founder, Dr. Jacob Berlin, the company was formed by brothers, Eli and Jacob to bring an interdisciplinary team, that works together to bring life saving new drugs to patients in need. This is one of Madrona’s intersections of innovation companies. And without further ado here is their conversation.

Chris Picardo: We’re thrilled to have the Terray Therapeutics team on the podcast today and also super excited to lead their Series A, having been a big participant in the seed, which all got announced recently and super excited to chat with Jacob, Eli, and Narbe on all things Terray Therapeutics and combining the wet lab with really cutting edge machine learning. So, before we jump into it, I’ll kick it over to Jacob, Eli, and Narbe to quickly introduce themselves.

Jacob Berlin: Thanks so much, Chris, it’s wonderful to be here today. It’s wonderful to be working with you and the team at Madrona and to be building a fabulous company here together. I’m Jacob, I’m the CEO and co-founder here. My background is all in science and chemistry. I started that all the way back in college at Harvard making small molecules and looking for applications to them, how we could make better drugs.

At Caltech, I also worked again on making new molecules. After a postdoc at MIT, I had done a tremendous amount of design and development of molecules, but also recognized that the way we were doing it as a field was slow and pretty hard. We’ll hit those themes a lot today.

I went to do a second postdoc at Rice University. Down there in Houston, I worked on nano materials and trying to ultra-miniaturized things and dramatically speed up how fast we could do things. That’s really where Terray started to come from, I really built it out here at City of Hope, where I was a professor for eight years. My lab there worked at the intersection of nanomaterials and synthetic chemistry. It’s there that we began the process of building the technology that became Terray. Over six and a half years, we built it before spinning out the company and I’m excited to tell you and the listeners all about it throughout the rest of this podcast.

When we launched the company in late 2018 and raised the seed round in early 2019, I left my tenured job to be here full time. Since then, it’s been a tremendous time with an amazing growth throughout the company. We’re seeing fantastic science and outcomes and excited to talk about it today and wonderful to be here.

I’ll turn it over to Narbe and we’ll close with Eli.

Narbe Mardirossian: Hey Chris, it’s great to be here as well. I’m excited to talk to your listeners. My name is Narbe Mardirossian, I’m Head of Computational and Data Sciences, here at Terray. My background is in machine learning and quantum mechanics, quantum chemistry, that’s what I got my PhD in. After I got my PhD, I moved to Amgen working in the therapeutics discovery organization and small molecule discovery on the computational side, of course, working on physics-based models, machine learning models, and moving all of our on-prem compute to the cloud. So I moved here in November of 2020 and have been here ever since.

Eli Berlin: Hey, I’m Eli, the Chief Financial and Operating Officer here at Terray. My background is all in finance. I did 10 years of private equity and growth equity before joining Jacob to co-found this business back in 2018 and I’m super excited to spend the time with you today, Chris. So thanks for doing this.

Chris Picardo: That’s great to have all you guys on, and I’d say it’s been a pretty awesome time already working together. Narbe remember when we hired you and how thrilled everyone was. So that’s exciting now to all get together. Before we dive in, I think it’s just interesting to note that, Madrona first invested into Terray right before COVID hit.

And I remember that round closed and then the world went into lockdown for two years, in some cases it still is. So it’s been a great time working together and I know you guys have had a lot of creative solutions of how to work through COVID and we to hit a bunch of those today.

It’s been amazing to see the progress you’ve made even with a bunch of unforeseen headwinds from the world in the way. So it’s been fun to be along the journey. Before we jump into the detail, I think it’ll be fun, Jacob, just to talk about how you decided to form a company around the academic research.

You’ve been at City of Hope for awhile and you decided to formerly spin it out and bring Eli into the fold. I’d love to know the motivations behind that.

Jacob Berlin: Thanks, Chris. It has been a wonderful journey and it’s always an interesting question. When is something ready to be commercial? Personally I’ve always been really fascinated and driven to have my work have impact on people in their everyday lives. I’ve been fortunate, as I mentioned in my background, that I participated in the development of a catalyst that is used across the world and saw compounds that I made in my first post-doc become part of preclinical drug development, and then had a lot of my work in my second post translate into start ups. So I’ve always had an eye on having my work have a real impact. I think the way to deliver solutions to make people’s lives better is through commercialization.

This is a project that honestly on day one, when we wrote it on the proverbial napkin, we were like, “Wow. This one is obviously a company someday. We’re building a technology that allows us to screen hundreds of millions of molecules in minutes and record their interactions with the causes of disease. Of course this is a drug development technology. That’s what we should use it for. That’s where it goes. This obviously doesn’t belong in academia because academia is not the place to develop a bunch of proprietary IP protected secret items that have to be developed, commercialized, scaled up, manufactured and sold.”

So from day one, I called Eli and was like, “man, this idea is so cool. This is going to be a company.” Eli is my closest friend and also harshest critic. He was like, “that sounds fantastic, Jacob. But does it work?” And I was like, “nah, it doesn’t even exist, but it’s a really cool napkin and we’re going to get after it.” And so my other co-founder Kathleen, who is still leads a lot of our R and D and development here today got going on it. We started working on it at City of Hope. And, as I told Eli, and I’ll tell everyone, science is hard and it takes a lot to make the machine work that we run today.

We spent six and a half years painstakingly developing all of the technology for it. Honestly, all along the way, I’d call Eli to talk about something and he’d be like, “does it work yet?” and year one, it was like “a little bit” year two is “yeah, most of it is looking pretty good.” Year three is “yeah, we’re starting to apply it” and by year six and a half, it was, “yeah, it totally does. We’re ready to roll. it’s reading out your interesting solutions to problems in academia. It’s ready to go provide solutions in the commercial space.” At that moment, we put our heads together and we launched the company, and we haven’t looked back. I think it’s been a fabulous home for the technology.

We’ve scaled tremendously. We’re using it to develop medicines to treat immunology disorders and bring therapeutic benefit to patients. I’ll kick it over to Eli for his side of that journey, but that’s really how it went from idea to company.

Chris Picardo: Yeah. Eli, before you jump in, I’m interested that you and Jacob are brothers. Obviously being the harshest critic is a nice natural role to inhabit. Then, at some point you guys decided to get together and actually build the company and backgrounds are a little bit different from what you’ve done professionally.

So it would be fun just for everyone to hear your perspective on the story and what has been like building the company together with your brother.

Eli Berlin: Absolutely! Look, for me, Terray is an exercise in, if you can’t beat them, join them. I did a decade of private equity and investment banking before co-founding Terray as I mentioned and the sort of short story here is that Jacob’s the smartest person I’ve ever met, and he’s disarming in his humility, and he rarely shows excitement for any of his achievements.

There’s this one time Jacob was in high school. So, I was in the middle school, and he tells my parents that there’s an award ceremony at school that we should go to. So we go, and he’s in like shorts and a t-shirt and it turns out it’s the Year End Academic Awards. And Jacob wins legitimately every single award that is given that night.

And, at one point, they tell him to stop going up to the podium and back to his seat. And, he had presented it to the family, like whatever, no big deal, I would have been like, I would have probably sent out invitations to my extended family. And, so for Jacob to show excitement about something is a really high bar and Terray, as you mentioned, was totally different from the start.

He was excited about it from day one. He used to say to me, we should make this a business. It took them a really long time to get it to a point of maturation where we could make it a business. I just always felt that Terray was an extraordinarily rare opportunity. If you believe that, you live and you die, this was one worth doing.

I believe that Terray deserved to exist as a commercial venture. And that for all the hard work in academia by the founding team and for all the promise, it deserved a chance. I’m convinced now four years in that the opportunity ahead of us is really extraordinary to transform drug discovery at an incredible scale.

So I think, it’s been there just aren’t that many opportunities in your life where you can work on a business with purpose where the end goal is advancing human health, do it with your brother and do it with novel technology. And so it’s been an extraordinary journey. As regards working with Jacob, there’s no, I just don’t think there’s any way to replicate the durable trust that we have being brothers.

It just drives us extraordinary efficiency. He talked about me being his harshest critic. That’s probably true. And I think the level of direct and honest communication that we can have because of that trust is totally unique. I also think, I’m not sure anybody listening to this would know, but we are very different people and have very complimentary skills and very separate responsibilities here at Terray.

That’s worked really nicely with a ton of mutual respect. And look, he’s my brother. So I know that before we go pitch investors in the morning, he should have breakfast and we make sure that’s on the calendar. So you know it runs the gamut.

Jacob Berlin: We are different. If Eli had won those awards in middle school, he probably would have rolled into the awards in a three-piece suit. But everything Eli has said right there is true. The durable trust, ability to build it together and work in complementary areas has tremendously accelerated the growth of Terray. We’re super excited to be here.

Eli Berlin: That’s just for listeners. That was like Jacob’s funniest joke ever. I’m also much funnier as the younger brother. And Chris, to your question, I don’t know, we’ve learned a lot over the years, but I think for me, this has been about confirming the thesis.

Jacob’s really, truly brilliant. He’s a tremendous listener. He’s a great strategic thinker. Terray is really novel and working together with purpose, is just a once in a lifetime opportunity. I can’t say enough good things about the opportunity to be on this journey.

Chris Picardo: I’ll say just for myself, it’s been fun working with everyone. I can second all of those things that you guys have both said minus the stories from high school. I want to ask you Eli one more thing before we jump into the platform, because I do want to talk a lot about the platform and the Teray difference and how we approach the world.

But I think one thing that’s really interesting for everybody in this kind of hybrid space between tech and software and traditional wetlab as teams are coming together, how do you join a company, or in your case, build a company where you might be the one with significantly less of the technical background. It obviously helps to have a brother who’s a world-class scientist and can talk to you about chemistry, but you and I have talked about this a bunch and I’ve seen your learning curve. I’ve had my own of right trying to just ramp up. How do you think about approaching that?

We talked to lots of more, less science-oriented people who’d love to go join a company like Terray, and they’re worried about the science side of it. So, what was your approach to moving up the learning journey there?

Eli Berlin: Yeah, I think there are two answers. I think it’s really hard to join a scientific organization from the outside without a scientific background if you’re trying to diligence the science, right? If you’d asked me four years ago, when we started this. How good was the science on a relative basis?

I would have said I spoke to a few folks, gray haired folks who spent a long time in drug discovery and development. They were excited about it, but I couldn’t underwrite the technology. I think that was a benefit because it gave me the leap of faith that, I just trust that Jacob is brilliant, the science is novel, the IP is there.

And so I do think that’s a hurdle. How do you get around, underwriting the technology as you’re thinking about joining a company? And what I would say is, I think you can learn a lot talking to a handful of folks in industry and get yourself over the hump. I think the second piece of it is, at its core, Chris, the technology is extraordinarily complicated.

When you get down into the technical weeds, which you’ve suffered through in a few board meetings, it is deeply complex, but you don’t need to know that. And I think that’s true of any Company like ours, you don’t need to know much about those details. You need to know about what it can do, the why in the technology. And I think it’s been a steep learning curve, but one that I’ve been being grateful for where. I understand the differentiation. I understand the competitive positioning and I understand the opportunity that’s in front of us. And none of that relies on figuring out the linker strategy for our core platform. That all is just transferable from one industry to the next.

For folks who are first and foremost technologists thinking about crossing over into a biotech business. I think it’s an extremely exciting opportunity. I think it’s one where you can work with purpose to advance human health, which is totally unique and gives every day new meaning.

I think there just shouldn’t be that hurdle, because I think it’s all imminently learnable, even if you don’t have full command of every one of the details.

Chris Picardo: Yeah, that resonates a lot with me personally, certainly on my own learning journey. I’ve felt that in board meetings, as we dive into the details. I think everything you said there is relevant for thinking about these opportunities. It’s also a perfect segue into kind of back to Jacob and Narbe talking about Terray’s approach itself. I think that the first question I want to ask there is, Jacob, when you think about small molecule drug discovery as it’s been traditionally done, give us the 30 second version of that, and then the slightly longer version of why and how Terray really is changing the game on the core platform.

Jacob Berlin: Yeah, thanks, Chris. I think we’ll spare the listener today the full deep dive into the specific chemical reactions and linkers and the chips and all the various technical pieces that make our whole enterprise run. But it is, I think, really important to spend a moment and think through the current canonical, small molecule drug discovery.

Just for context, when we talk about small molecules, we’re really talking about medicines that can be put in pills, taken orally and are convenient. They’re the bulk of what people take as medicines today. When we use the term, we’re separating them from antibody therapies or things like that. But for small molecules, the first problem is always (and, really, for any drug discovery the first problem is) figuring out the problem. So the biologists work really diligently to find the cause of disease.

What could be a protein or an RNA molecule that plays a role in developing this disease or perpetuating this diseas? We call that ‘target ID’, and it’s a target because it’s the thing we want to then go solve and fix. So at that point, you go into the drug development process where you need to now start to find your starting points.

We call these ‘hits’, which are molecules that do something of what you want to do with that target. So your end goal may be to say fully turn that cause of disease off, not change anything else in the body. An example of this end goal might be a drug with very nice safety thresholds that you can take a big pill of. You can, in some ways, think of those as like antibiotics. We all are familiar with taking those giant pills. They kill the antibiotic, the bugs, they don’t hurt you. You get better and feel great.

The question is, how do you get there? And so we get there by starting with these starting points called ‘hits’, and they typically do one of the things you want to do.

They either interact with that cause of disease very strongly. So they go and stick to it. We call it binding. Or they impact some of its behavior, but they may be lacking in some other property that ultimately you need to be able to put it in a pill and take it orally and have it work. Then you hit the phase of drug development we call ‘hit to lead’, where we’re taking these starting points and we’re turning them all the way into basically nearly candidates for giving to people. So we’re optimizing all the other aspects the molecule needs to do. It needs to be able to be taken by mouth. It needs to dissolve, it needs to go into the bloodstream. It needs to get where it needs to go into the cell where it needs to go. It needs to interact with the target where it gets there. There all these layers that you work through as a drug development company. Then ultimately the last stage is of course, ready for clinical testing, which involves manufacturing, reproducibility, toxicity testing, and a larger scale and trying it out in humans.

Today that process is typically quite long. These are often, ten-year plus development timelines, and it’s also really hard. We’ve done great as a human kind improving human health and developing therapies, but there are also thousands and thousands of causes of disease that we don’t know how to fix.

Also countless failures along that road, where only a small fraction of what we try to test on people actually works. There’s huge opportunity to deliver better solutions faster.

Chris Picardo: So that’s the traditional approach, Jacob, and you laid out the timeline and how long it takes. I’d be curious to hear how you reformulated this problem at Terray and how we’re thinking about solving drug discovery in a totally novel way.

Jacob Berlin: We sit at like an amazing moment in time with the revolution in the biology capabilities and the ability to discover these causes of disease. So things you may have seen or heard like Crispr, siRNA and Gene Knockout have just continued to unveil opportunities to create drugs, but the chemistry side hasn’t kept up.

There’s not an ability to look at enough molecules and diverse enough molecules, fast enough to really address that explosion of opportunities and bring those timelines down. And ultimately be able to go from discovery to therapeutic in a much shorter and much more reproducible fashion. That’s really at its core Terray’s bet.

We’ve built technology that lets us actually measure far more molecules than any other technology out there. We can actually go and build the loosely drawn map of chemical space quite quickly at enormous scale. Then I’ll kick it over to Narbe, because the next piece is that even with all of that throughput, even mapping and measuring hundreds of millions of compounds, there’s still an infinite amount of chemistry to go through.

So, filling in more of it and knowing where to go next and taking an efficient route through this infinite space to find the solutions you need, the proverbial needle in the haystack, we turn to AI and ML tools and computational tools that are the right fit for the scale of data we work with, to allow us to make the next set of compounds that go iteratively back and forth from large-scale chemical measurement to computational prediction and back to the wetlab measurement of that.

That’s what lets us really compress the timeline and deliver therapeutics where otherwise, we haven’t historically. So I’ll turn to Narbe to say a few words about that complimentary side, where we used the design to accelerate the wet lab throughput.

Chris Picardo: This is such an interesting point. You’ve told me before drug development, isn’t just an algorithm problem. It’s a data problem. So talk about what you mean by that and how that is actually executed on a day-to-day basis.

Narbe Mardirossian: Drug discovery is both an algorithm problem, and also a data problem. But I think first and foremost, it’s a data problem and probably the best way to motivate this is that, big pharma sits on tremendous sizes of data sets. But what you really need in drug discovery is the iterative capability which Terray has built and is expanding.

I think, a lot of these models that are very novel today, neural networks and beyond like they only work when they have the proper data, proper amount of data, proper amount of clean data to seed it, to feed it. Historically, it doesn’t really matter if you use traditional models such as partial least squares or random forest.

Like all of these are going to perform probably equivalently on datasets of the size of ten or a hundred or a thousand, which is really what you’re looking at for a specific target that you’re trying to drug therapeutically. The promise of Terray is really the ability to generate data quickly, iteratively, and at scale and at the quality that’s needed to power regressors.

That can truly optimize chemical space and to take a step back and hit on why this is such a tremendous problem. It’s truly a needle in a haystack; the size of chemical space is something like 1040 or 1060. It is a tremendously large space that you’re trying to explore. You really do need the help of these modern machine learning approaches, plus the data that’s fed into them to traverse that space efficiently. If you look at the traditional process in big pharma, it’s always going to be iterative, but you’re generating about 10 to 20 data points a week.

That’s just not enough to be able to power these models that are improving on a daily basis, and you’re improving because the data is being fed into it. So I think it’s certainly both, you need the data. Only with the proper amount high-quality data, will you be able to unleash the algorithms that are present in probably all aspects of our lives today.

Jacob Berlin: Yeah, I think Narbe is spot on there and we’ve seen this opportunity unfolded across so many other industries that I think everyone listening is probably familiar with. What you should get recommended to shop for on the internet, where are you going to go to dinner, and how to get there. What you’re going to watch a Netflix. All of those algorithms probably started out not that accurate, but they all drew on iterative data sources that are enormous, millions and millions of people clicking on things or driving places or buying things or watching things.

So we have that opportunity in drug development as well, if we can provide the data sets. Drug development is an even harder problem than all of those probably. The key is to be able to be a little bit or even a lot bit wrong the first time, but have a dataset then that gets you going back on track fast and to get better each and every round and run those rounds fast enough.

So that’s really where the compression in development is. It’s where the Terray differentiation is that we build and measure large enough that we can get our algorithm going, get the model going, and then rapidly refine it to really incredible accuracy and precision. And that’s the Terray difference.

Chris Picardo: Yeah, this is a point that I’d love to go one layer deeper on, which is that I think another way to frame that is in these broader machine learning problems, Terray closes the loop on the data side. Not only do we create a ton of data, we then test that and model that, and then we can validate it again with actual physical chemical data.

And I go back to Narbe for a second. When you think about that versus maybe the pure algorithmic approaches are purely in silico approaches out there, I looked at, get your perspective on the importance of being able to close the loops on the models and move as quickly as we can on the data side.

Narbe Mardirossian: Yeah, closing the loop is absolutely essential. Honestly it would be any computational chemists or machine learning scientists dream to be able to develop these models, make predictions, and actually see those predictions tested in real life. That is something that’s different from the traditional process, because, you only have so many shots on goal a week and you need to make, 10 or 20 compounds and you don’t really have that opportunity to make millions of compounds literally in a week and test them.

I think absolutely one of the benefits of Terray is the ability to iteratively benchmark and improve the models that we’re building. I’m not talking about only about machine learning models. Machine learning models are great for learning from experimental data, but even physics based models that are very popular these days in computational chemistry and other realms, these can also be improved by learning about how the predictions are right and wrong. So the ability to have this feedback loop is absolutely essential. Truly, I believe that Terray is probably one of the only places where you can actually test and hypothesize and, validate your hypotheses iteratively within weeks or even days.

Chris Picardo: Yeah, the power of the platform is pretty immense. I think one thing I wanted to ask too, and this goes back to the question I asked Eli earlier, say I’m a computational scientist or machine learning engineer, and I’m really curious about either these types of problems or joining a company like Terray.

What makes this data so special, and why would I get so excited about working at Terray and building the models that we’re building?

Narbe Mardirossian: Yeah, I think Terray is an exciting place for a variety of scientists and people with technical backgrounds. I guess, let me start with computational chemists and machine learning engineers — one, I would say the molecular data, we have at Terray both in terms of the quality and the scale is unparalleled.

Nowhere will you find datasets of size 10 million, hundred million. Where you actually have high quality, believable data that you can model. I’d say from, in those disciplines, the ability to model data and use the feedback to improve algorithms consistently, whether they be machine learning based or physics based is it doesn’t exist anywhere else, but, molecular data, isn’t the only type of data that Terray has.

We have tons of opportunities for data scientists. All of our readouts for molecules come essentially from images. Just the path from going from raw images to processed photometries to the output that is then used for hit discovery, and machine learning models and compchem, is full of custom algorithms that we’re developing every day at Terray.

And I think, beyond that for data engineers and software engineers, the amount of data we generate is tremendous. This year we’re gearing up to hit 20 to 30 petabytes of raw image data, and that doesn’t even include the processed data. So there’s tons of opportunities, whether from the domain, domain specific fields, such as compchem or machine learning, all the way to data engineers and software engineers that Terray offers.

Chris Picardo: Yeah, we talk a lot in Madrona about the combination of machine learning and life science and the wet lab. And I think what’s amazing about Terray is not just that you guys have actually built that and are running it on a daily basis. It’s that pretty much inside to raise. You’ve talked about Narbe.

Absolutely. Incredible data science software in engine engineering, machine learning challenge going on daily, that itself could be right, like a data science focused company. I think when we talk about integrating those two it’s pretty awesome to see how Terray like really fully, is as a data science and wet lab company and that you can’t really pull the two pieces apart.

Narbe Mardirossian: Yeah, absolutely. I just want to add that one of the, to me one of the beautiful parts of Terray is the fact that the wet lab and the computational side are fully integrated. That is also not something you see very frequently in in drug discovery companies. Typically the computational team is viewed as like a support function where they’re contributing maybe 10-15% to various requests or projects. But here, without the computational side, the wet lab would not be able to function and vice versa. So I think this 50/50 integration is truly what makes Terray an exciting place to work for both computational people and wet lab people.

Jacob Berlin: This one will probably make the listeners chuckle if they are in the field at all. We built this from the wet lab side, initially. We wanted to see if the technology could be built and we could make the core of our technology, which is these little chips, the size of a nickel – the world’s most ultra-dense microarray. If we can make them and we can put the compounds on them and we can measure these interactions, which is where our raw data comes from, as Narbe said, it allows us to measure hundreds of millions of compounds.

In the academic lab, that’s where we started and we wanted to see if we could get the chemistry to work. Could we get the microscope to work? Could we get the chips to work? Can we get all the parts of this interdisciplinary process to work? The first time we made it work, we had no data people working with us at all. We were like, oh man, we just measured like a hundred million things, what should we do with that? Maybe we’ll put it in a Excel and filter for the top hundred and then see what we can do with that. Then the next day we went out and looked for someone to help us on the data side.

Now, of course, there’s been many years of working at the intersection of data science and experimentation. It’s staggering, and it’s a cliche that’s true. Working with an interdisciplinary team makes all the difference. We see stuff go back and forth all the time where the data team makes predictions out of the data or identifies things in the data that changed the way we do the wet lab side and vice versa.

Terray wouldn’t run the way it does without the data team, the chemistry team, the biology team, the automation team, the production team. All basically sitting together and talking together each and every single day, and it’s what makes it so special here.

Chris Picardo: That’s awesome. I get to witness it pretty regularly and have been down to Pasadena many times and seen the lab myself. It’s pretty great to just see it in person and see it all come together.

Eli, why don’t you also briefly tell us about the Series A and our big fundraising milestone that we just achieved and who’s been part of that journey.

Eli Berlin: Yeah, I appreciate it, Chris. So we’re super excited. We just announced our $60 million Series A which brings our equity capital raised to date to just over $80 million, including our seed financing. One of the things that’s been tremendous about this journey has been the partners we’ve had in the venture community.

That includes you guys at Madrona. It includes Two Sigma Ventures, Digitalis Ventures, KdT Ventures, Goldcrest Capital, XTX Ventures, Sahsen Ventures, Greentrail Capital, and the folks at Alexandria. As well as a whole host of other folks who’ve supported us along the way. We’re super excited about this moment and the opportunity been supported by the Capitol to massively parallelize our processes and throughput to deliver for patients in need.

Chris Picardo: I want to throw it back now, as we’re starting to wrap up to a couple of broader questions that I’ll pose to everyone, so feel free to jump in and take them as you see fit.

I think the first one is, and this is one that will probably resonate with most people listening, building companies it’s really hard. I think building companies that have complexity on both sides, the wet lab side and the machine learning side and trying to do both of those things is potentially even harder or at least more complicated.

What’s been the biggest challenge so far the biggest set of challenges, maybe Eli and Jacob that you guys have faced, and how have you thought about those?

Jacob Berlin: Chris, that’s always the question that keeps you up at night and everyone asks you what’s the hardest either retrospective or what’s coming next, that’s the hardest. We think about it a lot. I spend a lot of time on it, I don’t know if the answers will be exciting, cause they’re probably the same ones thematically that everyone who starts a business that builds at this interface faces, which is hiring the team. Building the expertise around the table, just always takes a lot. It’s always a tremendous lift to find people who are mission aligned, vision aligned and passionate and, perform at an excellent level.

We’ve been really lucky now to build a team of 50 with a seasoned management team with biotech expertise, as well as ML computational experience. We’re joined by a wealth of expertise now on the business development side, the drug development side, the computation side, but it took a lot to bring that team together and be at this remarkable moment.

I think alongside that, personally going from academia, or I guess it could come from anyone. Back to the napkin sketch; the appreciation for what scaling and industrializing that discovery is like. It is, I think, harder than you would guess on day one, to be able to run the exact same process and a high number of replicates at incredible velocity and scale and know it’s right every single time. We’ve done that, but it took a number of years to really dial that all in. And so I don’t think that part should ever be underappreciated. Eli, what would you say?

Eli Berlin: It’s funny, Chris your comment really resonates. It is so hard to build a business. I think back to my days in Private Equity, where, I’d come into the board meeting and have a bunch of thoughts on what needs to get done and I used to walk out of the meeting and go back to San Francisco and it’s so hard. Execution is so hard, but it’s also got enormous joy to it, because you get to work with people day in and day out, you get to create work that is worth doing, and it’s all worth it in the end.

I think for me, the two are recruiting and for us, the recruiting piece is about, attracting candidates and helping separate signal from noise. There’s so many AI drug discovery companies out there, and we’re really different, right? If you believe that the data unlocks the opportunity, we’re the only ones with that capability in the whole landscape. It’s a competitive ecosystem out there, and it takes a lot to recruit folks and get them interested in our technology. We’ve been quiet up until a few days ago. And we have a lot of teaching to do, when we meet folks who are interested in Terray.

The second piece is, Terray is a massively interdisciplinary Company so we’ve got chemistry, biology, machine learning, and computational chemistry with robotics and automation that go to make the engine deliver for us and ensuring cross-functional communication and collaboration is done with excellence and precision to deliver is really hard. It’s taken a lot of work to get us to where we are, and we’ve got a lot of work to go from here, and those are the two for me.

Chris Picardo: That all resonates with me. I t’s been fun to watch you guys solve those challenges and we’ve been along for the journey for part of the way, and we’ll continue to be along for the rest of the way. It will be good to keep working through these together and I’ll go right to my last question.

I like to ask the couple of people that I’ve done these podcasts with this question. If you roll the clock forward 10 years and you’re looking at what we’ve achieved, at Terray, what does the big vision look like? What is success, and what will that look like when Terray is at scale and started to execute on a bunch of this stuff that you guys set out to do?

Jacob Berlin: Yeah, I picked my career, Chris, because the big vision is making people’s lives better. It’s allowing everyone to live healthier, enjoy more. For us, what does it look like for Terray? It means Terray is a drug development company at scale, working across multiple different types of diseases and delivering therapeutics to patients faster.

It is unlocking all of the opportunity in that biology revolution with a chemistry revolution, where we can really go from identifying causes of disease, to people enjoying medicines that make them better reproducibly, reliably, and quickly, so that’s what we’re building.

Eli Berlin: That resonates. I think about the opportunity to build a company is a tremendous opportunity, but the opportunity to build a company where the end result, if we’re successful, and when we’re successful is more therapies to patients in need, faster. It’s an extraordinary vision to be a part of.

It really resonates across the company. Everybody who works at Terray does so with purpose and with mission as their number one. It’s an opportunity to work with world-class science and, deliver the next generation of therapies to patients in need. It’s really a unique opportunity and a tremendous goal as we push everything forward here over the next handful of years.

Chris Picardo: I don’t think I could end our conversation on a better note than that. So I wanted to say that, for us at Madrona, it’s been really amazing to be part of the journey and we’re super excited to continue to be part of the journey. I know it’s a busy time, so I appreciate you guys taking the time to chat with me today and share about Terray for really one of the first times ever. This has been a real pleasure.

Jacob Berlin: It’s a delight, Chris. There are two things along the journey that really make it wonderful. One is the science and seeing what we can achieve and move human knowledge forward. And the second is the people. And so we’re, privileged to work with the people we work with here, you, and the rest of Madrona ecosystem supporting us and the rest of our investor ecosystem. We just want to thank you again for having us today and delighted to tell everyone about Terray.

Erika Shaffer: Thanks for joining us for Founded and Funded. If you want to learn more about Terray, they can be found on the web at www.terraytx.com. So that is, T E R R A Y T X.com. Thanks so much for joining us and tune in, in a couple of weeks for another episode of Founded and Funded.

Trevor Thompson of TerraClear on Leadership, AgTech and Building for Farmers

How do you join a company and lead from the day one? And how do you do that when you come from a completely different work experience than your startup? Trevor Thompson of Terraclear had a 14 year career in the Navy, including a decade as a Navy Seal, and is now president of AgTech company, TerraClear. In this episode of Founded & Funded, he talks to investor Elisa LaCava about the opportunity for companies to hire experienced veterans and how the company is executing on it’s mission to make a farmer’s life a little bit easier with their rock picker robot.

Trevor also talks about the DOD SkillBridge program – https://skillbridge.osd.mil/ which companies can use as a way to access talented veterans.

This transcript was automatically generated and edited for clarity.

Erika Shaffer: Welcome to Founded and Funded. I’m Erika Shaffer with Madrona Venture Group. And today I’m super excited to bring Trevor Thompson, who is the president of TerraClear here together with Elisa LaCava one of our investors. TerraClear is an agtech that is automating one of the worst jobs in farming, rock picking. Rocks rise to the surface each year and farmers most often have to pick them up by hand. And these are not small pebble size rocks. TerraClear’s end to end solution uses artificial intelligence combined with robotics to precisely map where rocks are in the field by size, and then remove them with the precision robotic implement. Today there is a farmer in the cab and tomorrow it is a fully autonomous solution to this age old problem. I’m just going to turn it over to you, Elisa, take it away.

Elisa LaCava : Trevor, thank you so much for joining us today. I’m really excited to have you here.

Trevor Thompson: Well, thank you for having me. Always exciting to talk to anybody with Madrona and talk about TerraClear.

Elisa: I was realizing today, we’ve worked together now for almost two years exactly. You’ve been at TerraClear for a few years at this point, and I’ve been able to join in part of the TerraClear story now for the past two. One thing, I would love to share with the rest of the world is how you got to TerraClear and your amazing background.

For those of you who don’t know Trevor, and you should, he has an incredible history, spending, I think was it 13 or 14 years in the Navy seals? 14 years as a Navy seal and, moved over to civilian life and joined TerraClear, directly after your time of service.

There’s so much in there, how did you think about the transition into startups after your service? What were you looking for? And then, critically for other veterans or soon to be veterans who are listening to this, what are some things that worked well in your kind of learning journey when you were thinking about your next steps?

Trevor: Where to start? I guess, I grew up here in the Pacific Northwest and was really focused on a career of service from a young age, just instilled in me from my family and my parents who had either served in the military or served in medical professions. So, I ended up attending the naval academy with that intent to serve in the Navy.

I was fortunate enough to have a couple of years at graduate school at Oxford, which was kind of a 180 in terms of cultural experience, and then went right back to basic seal training. That’s where I spent the next, more than a dozen years.

In that experience, it was exciting and challenging and what I think the highlights for almost anybody in that kind of environment, is the people and the team. You have this combination of an incredible peer group and talented people, that I got to work with from all different backgrounds, combined with hard problems.

When you can galvanize a group towards these hard problems, that’s really, I mean, it’s addicting, it’s fun and exciting. So as circumstances change in my life and kids started getting born and it was time for us to come back home and leave that exciting, fun world that is not super conducive to having multiple children.

Once we made that transition, that’s really what I was looking for again, that pattern of, I want an incredible team and I want a hard problem. You get the most personal growth from that and the most satisfaction. If you had asked me five years ago, if I would be operating farm equipment in central Idaho picking up rocks, the answer would obviously have been no. but I think—

Elisa: It’s more than that, but we’ll get into it!

Trevor: Yeah, exactly. It’s incredible. So, what I saw in TerraClear as I met the early team was just such a passionate team. A problem that is massive and has been completely underinvested in, and this recurrence of rocks that arise each year in farm fields.

Talk to any farmer and they will immediately smile and make a reference to how bad this job is, but that is such an opportunity to solve one of these problems that most farmers have honestly given up on. There’s a wide variety of solutions, none of which have really answered the call.

Now we’re at a point where some of the breakthroughs in robotics and machine learning technologies allow us to solve this problem in an elegant way. We can be the solution in a giant market. You combine that opportunity with a team that’s done it before and has, immense experience and talent focused on this problem. It’s really fun.

Elisa: I love hearing you talk about the parallels between your life in the military and your life now, and what you love the most, strong teams working on tough problems. How do I replicate that kind of an environment, but just pointed in a different direction? I would love to hear; how did you find TerraClear?

I’m talking to other veterans and soon to be veterans who are listening, what resources did you use, how did you use your network or what was most successful for you in finding what you wanted to do next?

Trevor:

Originally, I had lunch with Mark Mader, who’s the CEO of Smartsheet. I was really excited about the culture that I’d heard about at Smartsheet and him [Mark] as an inspirational leader. As I continued to talk about other folks, somebody said, ‘oh, you got to meet Brent Frei, who was one of the founders of Smartsheet’. So, I talked to Brent, and he said, in a very Brent way, ‘Smartsheet’s really cool, but you’ve got to come see what we’re doing now it’s even cooler’. That was TerraClear, and they were in those early days. So, I met with them early in TerraClear’s period, and got to know the team and grow with them as I was transitioning.

That was the experience there, I’d say, in terms of advice to veterans, there’s almost nobody that is going to be more of an advocate, for you when you come out. Because I think veterans who have been successful in different sectors, they really understand the upside there clearly. Right? So, they’re willing to invest in folks that they see that enthusiasm and humility and talent and say, I know that this, gal or guy can, can do something great, we just got to put them around the right kind of people and get them started on the right foot.

Spending time with those real advocates was incredibly valuable. Some of those came, into new networks that in Seattle were really valuable, like the Dartmouth network or the Harvard business school network, or the Madrona network. Where you meet one of these people, who’s an advocate and then they kind of spin you into a wide variety of different folks.

If I could just add one point to that, there’s two sorts of people. I think that you meet when, you’re transitioning from the military into, some other sector, and that is the ones who kind of shrug and say, “boy, this is really interesting. I’m not really sure what to do with you”. Then there’s the different, group that sort of says, “my God, you could have an incredible impact here. Like we could use somebody that has these skills”.

I think generally you get the people that have more experience and have seen the importance of team dynamics and energy and problem solving and operating within ambiguity. All of these, kind of cliche traits that you hear about. I think they really see those. They’ve seen them manifested and so they see the opportunity and the upside there. So, finding those people is important.

Elisa: It sounds like Brent was one of those people and you two immediately connected. One of the amazing things about your TerraClear journey, Trevor is you’ve like had this meteoric rise. You’re on the senior leadership team of the company in the span of a few years. One thing I would love to learn kind of in that first year of working at TerraClear, just a bit more about that transition.

How did you stretch your leadership capabilities or how did you really lean into the leadership capabilities you had already developed at the military? What served you well, versus what other areas were you trying to grow in most?

Trevor: That’s a good question. I think oftentimes one of the things you learn, or at least I learned in seal training. Is just how we ended up limiting ourselves more than almost any other external factor. That has a lot to do with, self doubt and negative talk and all these other psychological elements, but the ability to overcome those is actually really empowering and have the ability to say I don’t know everything.

I had come from a world where I was often. I was often, theoretically, in charge and responsible, but was not an expert in any piece of the equation. So, when we’re solving hard problems, there was somebody that knew the intelligence much better. There was somebody that knew the tactics much better, et cetera. So, I was pretty comfortable being honest with what I knew and didn’t know, which I think is really the first step in that quick growth period. Being around a team that was awesome, to put it in the simplest terms, that allowed me to grow really quickly in that area and allowed me to ask some pretty stupid questions that was really empowering.

It allowed me to take these really well-developed skills, like team organization, and goal setting and prioritization and all those things and account for some of the gaps, that you might encounter that you would expect and things like finance. Right? Areas that I did need to grow quickly. Having advocates on the team that understood my role was valuable and helpful.

Elisa: That’s amazing. So fast forward to TerraClear, you jumped into a company that has a really dynamic strategy. On the one hand we’re building, rock pickers, this is like metal and steel and, a real physical implement that you attach to, skid steers and different pieces of equipment on a farm. And then also there’s this amazing data and mapping component AI strategy would love to hear a little bit about the evolution of the company and what you think about, this world and ag tech and smart ag tech moving forward.

Trevor: The evolution of the company really started as a problem. Oftentimes in agriculture, what you’ve seen over the past decade is some of the lag on adoption has been the result of solutions looking for a problem. Fortunately, we really started with the hard problem.

I mean, physically in the field, picking rocks by hand, Brent had an epiphany that said, ‘good Lord, like there’s all this stuff that’s been automated. These huge elements of agriculture, harvesting and spraying and seeding and tillage, they’ve been really heavily automated. And then there’s these things that have been left behind that we all have to do as farmers’.

Solving those problems is really exciting. That’s where it started, and the solution really initially came in two areas. One is we’ve got to be able to identify this problem over large acreage. Farms are increasingly bigger and bigger with a smaller or equal labor pool. So, we need to identify the problem and then we have to solve it with a high degree of precision, which allows for really modernized farming, where you’re not digging through the ground each time, you’re just removing the rock. So that’s really where it started, and we had these kind of two parallel efforts to figure out what is the right solution for this, and we continue to iterate on those.

Elisa: I’ll give a fun plug. Earlier this year, at one of the board meetings, so TerraClear has offices in Bellevue, Washington, and out in Grangeville, Idaho. We had a board meeting out in Grangeville and a field trip day, and I had the distinct honor of driving a skid-steer that had the picker attachment on it.

As someone who didn’t grow up on a farm, never driven a skid steer in my life, I was able to get in by myself and I picked up what was it, Trevor? Like 15 or 20 large rocks in the span of two minutes. It was like driving this, Go-kart basically, which the skid steers are fun, but the beauty in what you and the team have created is this incredibly intuitive, very easy to use heavy duty system that is super fast and quite honestly like really fun.

Trevor: I think the important detail that you’re omitting is that you picked about twice as effectively as somebody had farmed for 40 years, right after you, so that was the really exciting part.

We’re really proud of the fact that it can be used by anybody on the farm.

So, a nine-year-old or an 85 year old can use this thing and really contribute effectively not to diminish your performance that day, but that’s really important for us is can we get this to be fun and easy because you take a job that was really the worst job on the farm, or certainly up there and make it the first job that somebody wants to do on the farm.

That’s a big transition.

Elisa: Right! I mean, because you think about some of these eight-inch rocks or 10-inch rocks, they are heavy. You can’t just manually pick those.

Trevor: It’s so fun obviously to get this in front of customers and, at different farm shows and all, but the face of farmers, when they see it just suck in a 300-pound rock, in an instant is pretty extraordinary. I mean, that’s, that’s a rock that is going to take a lot of time to figure out how to get out of there and potentially a lot of back pain as well. So, it is really, every single time we show this to somebody there’s this incredible reaction. That’s really fun.

We just sold this to a farmer, and he said, ‘unequivocally, the best thing that I’ve seen created in agriculture in my lifetime, just the most exciting kind of new thing’.

That is one of these, the ability to create something that didn’t exist that people didn’t think really was possible it’s not even a tweak on an existing product, it’s actually a fundamentally new approach to this problem. That’s something that we feed off of quite a bit.

Elisa: I also think, one of the unique aspects of building in ag tech is, your customers, farmers have these natural, really tight windows when they can be productive and do work on their fields in between all of the things that they do from prepping the field to seeding, across all of these stages over growing season.

I would love to hear a bit more from you on, what are you hearing from farmers in terms of top pain points that kind of surround their natural farming cycles and how does TerraClear fit into that?

Trevor: Those cycles are tight, and risk is really another way to think about that, and we think about it in terms of risks. Just to take a snapshot of, Brent’s family that, when he was a child, was farming under a thousand acres with the same number of people in the family fast forward to today and it’s almost five times that with the same group. So, they just don’t have the luxury of spending time on a field solving problems like this any more. Everybody is feeling that pressure. I mean, there it’s every sector of agriculture, similar to every sector, really across the economy. Really acute in agriculture is how do we then solve these problems with a higher degree of efficiency?

For us the answer is we can solve this problem in a way that reduces your risk during those critical periods. So, whether it’s planting or harvest, these are tight windows where missing a single day can cost you a percent in your overall revenue for the year and that’s considerable. Removing the rocks ahead of time, in a way that’s comprehensive, reduces that risk dramatically. It’s a relatively straightforward ROI for a farmer.

In terms of our actual solution, we’re accounting for that tight window by creating an autonomous tool that allows you to pick in a much wider window. Historically you turn over the soil, you go pick as many rocks as you can, and then you seed and you just kind of deal with them and you pick them by hand, if you can, after you seed. Well, having a tool that’s smart and has low ground pressure and low ground disturbance and meets the needs of the actual problem, widens that window, where we can solve it and transforms the way that, takes this from a problem that’s barely solvable to a problem that is no longer really a thing.

Elisa: Let’s talk about some of the challenges the company has faced. It’s been this wild world over the past year, especially I know as it relates to supply chain and some other issues when it comes to manufacturing a real physical product. What are some of the challenges that you’re seeing in your sector and for TerraClear specifically?

Trevor: In the sector in general, I think there’s so much promise with digital solutions in agriculture but in many cases, they’ve really met their match with the conditions in farming. I mean, you’re talking about low bandwidth areas, relatively, generally very remote areas, very large areas and so often these digital solutions provide that, they’re challenging. How do you transfer high amounts of data to be effective with machine learning tools and computer vision tools? So that’s one of them is how do we figure out how to operate in these remote environments very effectively? I think we’re making the right steps there.

On the supply chain and being optimistic here, but really look at COVID and the supply chains, two big challenges for every company that deals with any hardware over the past year, and we’re just, I think in both cases we’re better for them as a company.

COVID was challenging at first, but farmers are naturally socially distanced and so it allowed us to figure out other ways to reach them and be more effective and really get closer as a company. On the supply chain side, it’s interesting how it’s affected our engineering.

We wanted to build, twice as many units in this fall, as we were able to because of some supply chain constraints. Well, that forces us to look at, okay, what are the items that are holding us back and maybe make some engineering adjustments to get those to be items that are more mass produced, which oh, by the way, reduces your costs. On the supply chain stuff, I think the silver lining is that it has made us more conscious of some of these engineering decisions and frankly, a little bit more flexible as a company.

Elisa: I know you have a really neat program that you’re working with at TerraClear to help with employing veterans who are looking to move into civilian life and work in tech and startups. You’ve been an incredible resource to your network. We’ve talked about potential candidates who are looking into joining VC or joining an early-stage tech company, or even you’ve talked with your friends who are founding companies and being a part of that broader discussion when you’re thinking about hiring, I think TerraClear is hiring veterans too. Is that right?

Trevor: Yes, and just a quick plug and a thanks, from you who have also been a part of a lot of those conversations and Matt McIlwain, who’s on our board, both really active in that world of, helping folks find the right situation.

There’s no shortage of programs out there that help with transition. We had an incredible army captain that came out of Fort Lewis and spent a few months with us and was able to really make a big impact in just three or four months. There’s no shortage of things to do at a startup as everybody knows.

The program that I think is maybe worth highlighting is one called SkillBridge which we’re entering into now, which is an up to six months internship for a transitioning veteran. Their salary is actually paid by the department of defense. The company is not allowed to pay their salary in any way. As long as there is a path to a potential opportunity on the backend, and there’s a good faith effort there, you essentially get this incredibly talented, often times, veteran who can come in and work for free for six months and they get exposure to, figuring out what they want to do and being able to contribute to a company in an exciting way. We’ve got a rockstar coming in in January to do that program. That’s one that I think is available for anybody that wants to look into it. Again, it’s called SkillBridge.

Elisa: Great! The process for startups to reach out, to SkillBridge, it sounds like it’s fairly direct and easy to post a job description and get referrals that way.

Trevor: Nothing’s too easy with the government, but it is relatively easy if you go to the website and that is an area that there’s a little bit of a backlog right now, but it’s all there. It’s all spelled out clearly and it actually is a fairly seamless process.

Elisa: Trevor, as a leader at TerraClear, you have some incredible background and lessons you’re bringing from your experience as a Navy seal over into the startup. What are some things that you’ve directly taken from that experience and applied to the TerraClear team to help with team building, cohesion, getting people on the same page, and things like that?

Trevor: One of the things that is a hallmark of special operations is how close the teams are. That allows you to be resilient and flexible and deal with missteps much more effectively. The why behind that, I think, has a lot to do with how you’re just presented with challenging situations.

Training is artificial challenge and controlled environment that makes things very difficult and what you see time and time again, it’s very evident that when you go through hard things with people, you get much closer with them and you learn about much more.

Figuring out ways, without doing morning PT every day at TerraClear, figuring out ways that we can push through some of these challenging periods and spend a lot of time and really immerse ourselves in this environment amidst some, significant business challenges has really, I think, brought our team closer and that’s nothing that I’ve done. That’s something that was already part of the team, was finding people who are willing to be really pushed and challenged. If folks are looking at a relatively easy, nice little lifestyle job, it’s not the right company because we’re always pushing ourselves. We’re always challenging and asking hard questions to see ways that we can grow.

In training, I guess early on, I learned the value of leadership, which sounds extraordinarily cliche, so let me unpack it a little bit. Everybody kind of believes in this, but everybody has a different definition of what it is. It really materialized for me in a way when we were in basic seal training, you just do a lot of races and challenging group things with the same sized groups.

One example is you’re physically racing with boats on your head. It’s this a perfect team game, because if you pull your head down, the weight increases for everybody else on their team, whereas everybody, stands up tall, then it actually evens out the weight and reduces it. That one weak link affects the other five people on the boat. You just do these for hours and hours and days and days, and things like that, that are really challenging a group.

They do this thing where they’ll take the groups, maybe one group is getting first place every time and another is getting fifth place every time. The only thing they’ll do is they’ll swap the two leaders. So, the boats stay exactly the same with leader swapped. Shockingly time and time again, is that the poor performing boat, all of a sudden is winning races or coming close to it and the other boat drops off. So what is that, right? What are those traits that define that?

I spent a long time thinking through it, and boy, I have evidence that, that exists now, what are those things and how do you then replicate them moving forward? I think there are a couple of things, it’s a leader who is trying to celebrate and identify the strengths of the group as opposed to elevate herself or himself.

The ability to actually just think hard about what does this person want and how can I help them be more successful? That framework I think is what really has, I think, unlocked the good leaders that I’ve seen in the past. It’s a little bit liberating because you don’t have to have all the answers.

You don’t have to tell everybody exactly what they need to do. You just need to identify the things that they’re great at and really help celebrate those things and put them in the right positions to succeed.

An example is when I came in, I think Brent chose to see the upside of what I could bring to a company rather than the downside of what I didn’t know. It’s a great example of that as somebody who’s an enabler and an empower and I think that’s an important lesson.

Elisa: Wow. That’s incredible and then you do the same thing with your teams. That’s an incredible way to think about how do you succeed together? How do you recognize other’s strengths and set them up to be in a position of success to leverage those strengths, knowing that the rest of your team is thinking of you that way?

Trevor: Another exercise that we used to do that I think is a hallmark of a good company and you see it a lot is, the ability to be really harshly, honest with yourself, both at a personal level and at a company level. And so, we used to do, you had a training mission, or you do a real world mission. If something good happened or bad happened, the first thing generally after everybody got a glass of water, was to come back and do what’s called an after-action review. This is a breakdown of every part of it with an eye towards what you can improve. So shockingly little is celebratory, ‘how cool was it when we did this’? Like, there’s not much of that. It’s more ‘hey, it took us 10 extra minutes to get in. Why did that happen? Why did we judge that incorrectly’? What it does is it just kind of breaks down the ego pretty quickly when you’re just used to always talking about what you could have done better.

That’s something that I came into this company and really was looking for was a company that was honest with its own shortcomings and honest with its own degree of performance. I think that creates a culture where you can really get to rapid growth, both personal growth, and also, company growth is we’re just constantly asking how can we be better and trying to look at ourselves as honestly as possible.

It’s hard, right? I mean, we all have ego and it’s sometimes hard to address those things, but at least talking about them regularly and finding people that want to, aspire to that value has really been important for us.

Elisa: Right, and people who want to join that environment and learn how to do that from you and then contribute. That’s exciting.

Team TerraClear is this incredibly dynamic group of people. You have software engineers who have a background in coding and computer development and AI. You have folks with farming backgrounds, yourself as a veteran, all coming together in this world of ag tech and selling to farmers.

What is it like selling to the farmer customer and how do you galvanize the rest of your team to understand the problem sets of the farmer and, and work with them?

Trevor: The best solutions at TerraClear come when you combine, we think about it in three areas, business leaders, farmers, people in farming and agriculture and incredible engineers. The ability to blend those worlds is probably our best attribute as a company, as we’ve got people that have never even been on a farm who just want to solve a problem that affects a lot of people. Then other folks that have never don’t even know what deep learning is. We’ve actually got two glossaries that we have in our onboarding process. There’s the Grangeville, Idaho glossary, and there’s the Seattle Bellevue glossary. Oftentimes people have never heard of a combine or a header or, tillage. That’s totally fine, because as long as there’s enthusiasm and passion for the problem we’re solving that’s great.

On the other side, these are people who have been dealing with dirt and rocks and seed and crops for their entire lives, and don’t have a familiarization with the technologies and so constantly putting people in different environments. It’s the thing that I just love about the company, I mean, even culturally, there’s not a lot of companies out there that have that type of diversity, where you’ve got people from central Idaho and people from Seattle who are constantly interacting and we’re going back and forth all the time. So that’s really fun and it allows us to, I think really have an edge against a lot of other agriculture companies, because we can recruit such incredible engineers out of this region.

On the farmer side, working with farmers, farmers are really multifaceted and what they’re asked to do. They’re managing, budgets and then they’re fixing equipment and then they’re designing new solutions, with steel and welding. Then they’re really CEOs of a larger organization with a lot of employees sometimes. You’re asking so much of them that they can’t really live in the theoretical world. It’s very practical and often very physical.

This is why I said earlier, digital solutions often meet their match in agriculture is because, the idea of an insight for a farmer isn’t that helpful because they just don’t have time. You’ve got to give them an answer. A real practical solution that’s going to affect their bottom line this year. Sometimes, there are things that lag in agriculture because they’re not able to forecast out 10 years because the risk is too high. They need to focus on the immediacy.

The way that’s manifested for us is getting into fields and really understanding the problem firsthand but also understanding that we’ve got to provide real value from day one. That’s how we’re going to really grow as a company.

The rocks as a problem and as an entry point into ag automation, it just think is right on because it’s something that’s acute and visceral and nobody wants to do it and it’s the first thing they would love to outsource. If we can solve this problem for the vast majority of acreage globally, there’s just so much more that we can do in terms of bringing automation that’s practical to farmers.

Elisa: Thank you, Trevor. Thank you so much for joining us. It’s amazing to have this chat and to have you on the Founded and Funded podcast. Thanks again.

Trevor: Really a pleasure. Thanks for being interested in taking the time and for everything that you guys do at Madrona, you’re incredible and a great partner. So, thanks.

Meet the Investor: Aseem Datar

We are trying something a little different this week. I sat down with our new Partner, Aseem Datar, to talk to him about his journey to being a venture investor at Madrona. Aseem worked at Microsoft for 17 years in a wide variety of roles from developer to global sales to helping to build Azure into an over $20B ARR business. We talked about growing up in Mumbai surrounded by Jugaar – the Hindi word that means Hustle plus a lot more, how he got to Seattle, to Microsoft and to Madrona and what he looks for in a company.

Aseem also didn’t waste any time and led our seed funding of SpiceAI which is innovating in the Low Code AI space, helping developers integrate AI into their applications and he talks about that team and problem space too. You can listen here to the 20 minute podcast or find it on all of the major platforms! Aseem’s bio (and contact info!) is here.

Founded and Funded: Building a Company at the Intersection of Innovation with Dr. Ali Ansary of Ozette

In this episode of Founded and Funded, Madrona Partner, Chris Picardo, sits down with Dr. Ali Ansary, founder & CEO of Ozette. Chris and Ali talk about Ozette’s mission to uncover hidden information about the immune system to help with the efficacy of cancer treatments. Ali also speaks about the ability of biotech companies to attract traditional tech talent.

 

 

Transcript

In this week’s founded and funded Madrona partner. Chris Picardo speaks with founder, Ali Ansary about Ozette, Ozette is what we call an intersection of innovation company. Blending innovation in life sciences with machine learning and AI to uncover data not available through conventional means.

Ozette is focusing on the immune system and specifically how various cancer treatments interact with the immune system. As therapies for treatment, get more complex and doctors are evaluating how to combine various treatments, especially in the case of cancer treatments. Data like this. Derive from Ozette can have a direct bearing on a patient’s experience.

Ozette spun out of work and an open source project. Developed at the fred Hutchinson cancer research center. [00:01:00] Combined with incubation at the Allen Institute for artificial intelligence. Chris and Ali talk about building a multidisciplinary team. And the unique. Attraction that a life sciences based.

Company has for traditional technical talent.

Is a great conversation. Listen on.

[00:01:23] Chris Picardo: Ali super excited to have you here on the Madrona podcast. And it’s always fun to have these conversations, especially with entrepreneurs who are early in the journey and learning new things every day. So excited to have you join us. Ali is the CEO of Ozette which is a recent investment that Madrona made and was spun out of both the Fred Hutch and the Allen Institute incubator here in Seattle and we’re incredibly excited to partner on the journey. One thing that’s so interesting about Ozette is that this is another investment that Madrona has made and what we’re calling the intersections of [00:02:00] innovation, which is companies that are operating at sort of this intersection point between cutting a wet lab, life science techniques and machine learning and software. We are super optimistic about the future of companies who are working there and Ali will certainly share more of the reasons why we’re so optimistic. And, you know, we’re excited to have this discussion.

So without further ado, I’ll introduce Ali he’s the CEO of Ozette. Ozette is a immune intelligence company that combines the best of single cell analytics with cutting edge machine learning. When we say single cell analysis, we’re talking about the analysis of individual cells in a patient’s sample. It’s often used to diagnose conditions like leukemia, and there are many other emerging use cases and Ali will certainly talk about some of those.

Ali, that’s a lot of me talking. I think it would be great for you to spend a little bit of time on the background of Ozette and how it was founded, how you originally got [00:03:00] involved and where you guys are now.

[00:03:02] Ali Ansary: Well, I appreciate, Chris, you’re having me. I’ve been looking forward to spending a little time, I know you and I speak on a weekly basis, so I think it was a natural time for us to put this down into recording. I appreciate it the Madrona team has been absolutely supportive and like you had mentioned, you know, we we’ve been fortunate that, Ozette’s being built in a, what I would probably say the capital of humanology. A lot of it actually predates, Ozette and the work that had been pioneered at the Fred Hutch, with E. Donnall Thomas who had received his Nobel prize in pioneering work in bone marrow transplantation in the early nineties.

That basically put a springboard for the Hutch becoming a pioneer in cancer research, infectious disease. You had Immunex who was known for their therapy for Enbrel which Amgen had acquired. So, naturally what has been being set up for the last two to three decades, Ozette has been able to capitalize on.

I had the [00:04:00] opportunity to meet my co-founding team out of Raphael Gottardo’s lab, as you had mentioned, who was the Director for Translational Data Science Integrated Research here at the Fred Hutch. It was a whole new place where you’re integrating across data sets the science meeting computational biology. My two other Co-Founders Greg Finak and Evan Greene were all part of Raphael’s team, they were senior staff scientists at the Hutch as well, who joined as my CTO and VP of Data Science.

A lot of this actually spun out of this need to look at really high dimensional single cell data, as you had mentioned. I think the last few years we’ve seen advances in instrumentation that has been able to generate large volumes of data in a quick amount of time.

So I met my, I met my co-founding team and we sat down, as an opportunity to look at the work that they had pioneered in the field of single cell analysis. [00:05:00] Now, again, there’s a lot of background context here that I think is important to point out in the sense that, you know, biology had never had a large amount of data until just recently. Biologists, never had access to this large amount of data and the tools to analyze it. Now we’re creating such a large volume of data that some of our partners will tell you that they’re only looking at 10% of the data. In fact, they’re leaving 90% of the table and the fact that, Greg, Rafael, and Evan had pioneered a lot of the tooling to be able to do the analysis of single cell work allowed us to be in a unique position.

When we’re talking about single cell analysis, what we’re talking about is that immune system. Coming back to why the Hutch was a unique player in all this because of the resources around and uncoupling with the immune system has been able to do, we’re able to use our technology to really measure individual cells [00:06:00] as it’s coming off an instrument. That allowed us to not only just resolve what the immune system is doing.

As you know, I’m a physician by training and I still spend part of my time at the hospital taking care of hospitalized cancer patients. There’s this frustration of not knowing how patients are responding to treatment and understanding better how patients are optimized for the right treatment is super important in today’s environment. So the right treatment for the right patient, what does that mean? How do we find that? What are the instruments that are necessary? What are the platforms doing? So what we’ve essentially been able to do was, build a platform that’s automated the workflow for scientists in order to unlock the power of the immune system. That platform has also allowed us to use power of machine learning in order to unlock the power of the immune system.

[00:06:53] Chris Picardo: So, Ali, I think it’s really interesting, I’ll pick up on a thread that you just mentioned, which is that over the [00:07:00] last four years, five years, it doesn’t really matter, there’s been an explosion in the volume of data, right? The instrumentation for collecting and putting more kind of granular detail on this single cell data is really catalyzing that volume, how, without Ozette, would people analyze that data?

[00:07:23] Ali Ansary: They’re all analyzing it manually. This is the other part that gets us absolutely excited. The field of science is ripe for innovation to automate that workflow of data. So traditionally we have scientists, computational biologists, analyzing high volumes of data, but the dimensionality only recently has become very high. Before we’re looking at maybe only a handful of different parameters.

What I mean by that is, a computational challenge brings you back to your old math days. So two to the nth power, “n” being the number of proteins you’re measuring, or parameters, and two, whether it’s on or off, or there or not. [00:08:00] So in the past, we’re only measuring six or eight different components, so two to the eighth power means the search space is pretty feasible manually, but now that we’re measuring 30, 40 hundreds of different parameters, that search space is too large to do manually.

This is where the platform that we’ve developed allows you to do not only the analysis in real time of this high dimensional data, but allows you to explore that data and understand the visualization of that data and the impact of response rate to therapy. So,to bring it back, what you were saying is that there’s a large volume of data that’s being produced that was just being done manually.

It’s funny becauseI think that the bar for innovation is actually very low right now. That’s because we are only now starting to begin to see the opportunities that exist.

[00:08:56] Chris Picardo: Just put an example on the last thing you just [00:09:00] said, Ali, you know, give some color around the type of insight that you can derive if you can look at the data in higher dimension, versus when we used to only be able to look at four or five parameters.

[00:09:13] Ali Ansary: That’s right. So this is the part that gets me most excited as a physician because now I can determine response rate. I can now determine whether or not my patient is going to have Cytokine Release Syndrome or Tumor Lysis Syndrome, it’s that anticipation of treatments. When you look at these immunotherapies, these checkpoint inhibitors, for example, you’re unlocking the brakes of the immune system, right?

Now all of a sudden it’s going at a hundred miles an hour and, you know, Usain Bolt ultimately runs out of energy as well. With our platform you have, now, this ability to predict when the immune system is going to shut down and then you can augment that system as well.

Not to be too heavy in the analogies and I’ll have to give credit to my mentors for these analogies, it’s not something that I’ve come up with my own, but what we’re seeing is [00:10:00] that we can’t just be treating patients with single therapies any longer It’s going to be a combination of different therapies in order to treat an individual. It’s much like playing Beethoven’s fifth, it’s not just with one violin and you have to know when the various strings are coming in, in order to be able to have a beautiful symphony, and that’s what we’re seeing in immunotherapy today.

[00:10:22] Chris Picardo: Is it fair to say then Ali, that, Ozette sort of gives you that lens and that insight generating ability to be able to do some of the things you just said?

[00:10:34] Ali Ansary: Yes, so the opportunity here is not only in just automation of the data that’s coming off the instrument, but it’s also to learn from that data. It’s to be able to build a corpus of data against different disease processes, and then to be able to integrate across different data sets. You can use NLP to query against existing data against the publications, against publicly available data. There’s a large component of computer [00:11:00] vision with actual visualization of the data that’s being generated. The machine learning itself allows you to optimize that data generation. The insights that you’re now providing are just as valuable as the instrument that’s being produced on. Your Porsche is only so great as the driver behind it, otherwise it’s just a car that takes you from point A to point B. So, we’re positioned really uniquely to take advantage of single cell data that’s being generated in high volumes.

What we’re talking about here is at that protein level. We know that we are still developing therapies that target proteins, the FDA recognizes that it’s the proteomic data that’s the most valuable. You don’t necessarily submit transcript or you don’t make data for the FDA to approve, and a lot of the instruments that have really catalyzed the science, everything from genomics and transcriptomics and spatial omics, still are really early R&D discovery instruments, and [00:12:00] they will continue to increase in throughput. We’re seeing this, and that’s why the platform that we’re developing has a multi omics approach, but our primary focus has really been at the single cell proteomics level to really resolve each individual cell type and building these corpuses of data in order to be able to drive.

The one last part to not discredit is that, the instruments that measure the single cell proteome plays a role in every single part of the drug discovery pipeline from discovering and R&D through early and late phase clinical trials, all the way post FDA approval. These instruments have been around for the last 3-4 decades. So we really are primed to be in a place where there’s an accepted methodology and instrumentation for generating data, for us to be able to take advantage. There’s so much information and data for us to utilize and build upon that. We’re really primed uniquely right now [00:13:00] for this.

[00:13:03] Chris Picardo: One way, now that you mentioned, that I like to think about how to frame our areas of interest when we invest in intersections of innovation, is to think about sort of two broad buckets. One is, companies that have a method to generate totally novel data. A way that you wouldn’t have been able to see this before and then be able to apply machine learning or some sort of software to that.

The second is companies that are saying like, “hey, there is an explosion of data, but the tools and the ways that we’ve been looking at the data is not keeping up with the volume and where it’s going, and that we actually have to have a lot of insight generation mechanism to take advantage of what’s going on there”.

I think in some ways, those that sit in both of those buckets, but certainly there’s such an interesting thing to do in the second bucket where, like you said, there’s so much of this data and the lens has been manual, and now we’re switching it to machine [00:14:00] learning and insight generation.

So, given all of that, I thought it would be interesting to talk a little bit about the founding of Ozette. I think one thing that, that you guys did that’s fascinating and I just love your learnings on is, this company was formed in a trifecta process where Rafael, Evan, and Greg had been building some of the core software that underlies Ozette, at the Hutch for years. You were at AI to, trying to understand where are the interesting places that I can engage in this intersection and you guys came together and you built a company that has really deep academic roots.

I’d like to just have you add some color on how you think about building a company and bridging it out of the academic world and having to bring it into the more commercial use case and pharma or [00:15:00] customer facing world.

[00:15:01] Ali Ansary: I love that you asked that question, because in the life sciences, that academic affiliation, that academic validation is absolutely important. It’s a field where you cannot just sell vapeware, that your science has to be validated by your peers. You have to be able to replicate it and over validate it, based on publications in the science itself.

So to have an academic foundation has been crucial to what we’re doing. In fact, I think it has given us a strong platform to build, so we already had, I think, the back of the envelope was nearly $6 to $8 million in grant funding to be able to build the tooling that’s necessary. That gave us significant advantage versus anyone else who’s trying to build any kind [00:16:00] of competing platform to what we have.

It also allows us to actually be more resourceful too, because we know that with grant funding, academic institutions, you have to be nimble, you have to be fast, you have to be resourceful, because you only have only a finite amount of time and money to be able to build a technology.

The academic spin-outs have been advantageous to us. It allowed us to partner very quickly because of the reputation that Rafael, Greg, and Evan had built over the course of a decade. It allowed us to take advantage of an open source community that we’ve been continuing to support, and building that reputation saying, “hey, we’ll continue to support the open source, which is very critical to part of our mission [00:17:00] and business, but at the same time, we can build a significantly better version and automated version of what our open source tooling provides”.

We were positioned very uniquely, but I think in the life sciences as a whole, that academic affiliation is really important. It allows you to have a place of creativity, a place of research, a place of being able to build out, iterate quickly, experiment, and then bring alive. So, for us again like I had said earlier, I think it really positioned us in a unique place. I think in the field of life sciences you do need that those academic partners. Many of our early studies that we’ve been partnering on are through academic cancer centers, some are industry sponsored, some are not, but it allows people to become more aware of what you’re working on.

[00:17:54] Chris Picardo: How do you think about the team building when it comes to that? You’ve got a couple of core [00:18:00] team members who are at the company and you have a couple of core team members who will stay in academia and so how does that, as CEO, inform how you think about building a team around that kind of core academic group who really got the core product where it is today?

[00:18:23] Ali Ansary: Chris, I love that you asked that question. What we’ve been able to do at Ozette is position ourselves, not just as a life science company, but as a company that is bringing core values and missions that I think resonate really well with traditional engineers that have been at companies that are just making more money off advertisements and clicks. What you’re seeing is that engineers are tired of this and want to be able to have an opportunity to contribute [00:19:00] to something to a vision that’s beyond them.

At Ozette, it’s really creating an ecosystem and a dynamic where you have engineers, not necessarily executing a scientist’s idea or vision, rather creating an environment where the two can learn from each other. So you have these “aha” moments and you have this true curiosity and collaboration to be able to push a vision even forward. We’re lucky again, there’s a foundation technology that we’ve developed, but that’s version one. We’re planning for version two, version three, but the version 100 is going to come from these moments where you have talented engineers working across disciplines. This is where we have a lot of different opportunities to be able to educate whether it’s active learning or passive learning.

[00:19:49] Chris Picardo: I think that’s awesome. One thing I’m curious about is Ozette’s in a pretty specific subsection of life science, [00:20:00] right? Single cell data is its own world and field of study and we’ve seen that in a lot of ways. We’re bringing engineers with no background into something that’s really deep.

Just talk a little bit about the interaction between the engineers that you have on the team and the scientists and how they work with each other and what you sense is going on there.

[00:20:28] Ali Ansary: The interaction is something I have witnessed only a few times. What it is, is creating an environment of free flow of thoughts and questioning. There’s this culture of authenticity that we’ve been able to create at Ozette. I have no idea how it came about, but it’s been very unique in the sense that there is no such thing as a silly question.

It’s an [00:21:00] opportunity to truly bring in world’s experts who have developed everything from a front end to a backend with computational biologists to ask questions. As long as we’re asking questions, we start focusing on what are the right questions we need to ask and having that opportunity to have candor and challenge, and then come to a resolution quickly and then going and execute an idea. If it fails, you come back and iterate, understand why you failed in order to build forward.

Every component of any startup is risk and how do we mitigate risks? How do we create alignment? Being aligned that it’s okay to fail and coming back again to iterate on those processes. What we’ve also done is making sure we’re aligned on our vision and our vision is very much finding the right treatment for the right patient.

We’re in such a unique place to be able to help catalyze, [00:22:00] and it sounds scary, but the cure to cancer. It’s really a unique opportunity for someone to join and say, “yeah. I can get with that”. It sounds surreal for me to even say that, but the partners we’re working on are developing some of the most cutting edge therapies. so much talent that we’ve been able to bring together that it’d be a waste to not truly have a strong vision that we can try to execute here.

[00:22:31] Chris Picardo: Yeah, no, that’s awesome. I love to, that you mentioned “stupid questions”. I feel like we talk once a week and I asked you lots of stupid questions about science and it’s clarifying for me. Hopefully, sometimes it’s clarifying for you too. I do wonder that now that, teams are becoming really cross-functional in this space, especially if that’s a little bit liberating for both the engineers, the product people and the scientists where someone’s like, “hey, you spent a ton of time in [00:23:00] PhD, which is great. You know way more than anybody else, but how many people ask you the dumb question anymore?” I wonder, and this is probably more of an open question, but if we’ll see that being clarifying and freeing as you guys move down and continue to create what you’re building,

[00:23:19] Ali Ansary: I think it is, and more than ever, we have to just remain intentional about it. We have to be intentional about even a job description, so we’re not excluding a particular individual for them to say, “oh, I don’t know if that place is for me”. We have so much to grow and develop. If you were going to ask us if we needed a designer 18 months ago, I would have said, “yeah maybe”. But it was probably one of the best decisions we made because as soon as we put Calvin in the room, you have these aha moments that just come within the first 15-20 minutes, and everyone leaves aligned and [00:24:00] energized with who has been able to deliver really strong products in the past.

There’s a lot of skills and expertise that I think we tend to overlook that are not always in the life sciences. That’s, what’s been really important is how do you bring those in even more now than ever before?

[00:24:20] Chris Picardo: That Yeah, that brings me to my next question. We’ve got all these cross-functional team members. It’s been awesome and we’re building, what’s largely a software company, or at least on the UX side looks like a software company to a world that hadn’t had a lot of software companies that operate like this.

What are you finding challenging or liberating, or what are you learning about trying to build a software product with this type of data, in this world where the end user is at the end of the day, aren’t often people who have been sold or used 50 software [00:25:00] products every week?

[00:25:01] Ali Ansary: This is a good question. The reason it’s a good question is that what we’re learning is the end user and the decision maker about adopting a technology, are often different people. Sometimes you’ll have a scientist who will climb the ranks because they’re on maybe a scientist management track and they’ll grow into a director, senior director or VP, but when you become a senior executive at a big biopharmaceutical company, you want to know whether or not your billion dollar investment in a therapy is going to be successful in successfully to be able to treat patients with a disease. You don’t want to see that therapy fail because [00:26:00] it’s a heavy investment, but the steps needed to bring that therapy to market, the early R&D and discovery, and every component of those clinical early and late clinical trials have different users involved with that.

I think one of the biggest challenges is your end user is not oftentimes the person who you’re selling to. You have to find your internal champions who have these aha moments. We’ve had a handful of different times where we’re presenting to a team of 40 or 50 scientists in a room and it’s one person who says, “oh, I get this. This is incredible. This is so far ahead of where we’re at”, and I’ll get an email right after saying, “this is incredible”. I’ll say, “yeah, absolutely! This is why we all left our full-time jobs to do this”. end user is not always going to be that champion.

[00:27:00] Navigating industry is really important. Industry is siloed. There’s a lot of turnover. There’s a lot of old data that’s sitting on the table. There’s a lot of different competing priorities. And only now we’re beginning to see a lot of this data becoming digitized and that allows us to have a lot of freedom to explore through different avenues.

[00:27:26] Chris Picardo: I’m lucky. I get to spend a lot of time with Ozette every week so I’m very close to the product roadmap and what we’re thinking about on a daily basis, but I am curious when you think about it from a user facing perspective. You’re building software for, at the end of the day, for scientists and drug development and discovery teams who are trying to find new therapies or understand how patients respond to different treatments.

That’s a lot different than building software for managing your workflow or optimizing your ad spending or any of these other things. [00:28:00] So I wonder, when you think about, what are the implications for design and visualization facing them? What have you had to rethink, or is it really just a blank slate where you were saying, “hey, there’s a lot of stuff we can do here and our partners are so eager to work with this software that we can experiment and some new modalities”?

[00:28:21] Ali Ansary: I think that we’ve struggled a little bit about this. We’ve been building out this partner advisory committee where we have scientists helping to shape and give us feedback. I will say that the talent on our computational biology team or data science team has allowed us to really say, we’re actually building this for ourselves, which is a pretty high standard. As long as we know that we’re building a product that we want to use, we will see it widely adopted. There are different components that a scientist will want to see or do because scientists are creatures of [00:29:00] habit and they want to still be able to maybe export the data and interacted on a legacy system, which is great and we’ll create that for them. But at the end of the day, scientists want to be able to see their data, interact with it and the first thing, anytime a publication is going to be a RIN, is the visualizations. You have to have the graphs that are available to be able to then write the story around it.

That’s really what we want to be able to deliver, is that ability to understand that complex data. I think it alleviates a lot of the time that the scientists are spending to do the analysis of data. We go straight to insight generation and these insights help drive really important decisions that again, determines whether or not a therapy will come to market or not, because we can help find the right patient for the right treatment.

[00:29:54] Chris Picardo: I think it’s so cool when you think about the visualization side. [00:30:00] One way to talk about what Ozette has already achieved is moving from looking at graphs and drawing circles by hand on a piece of paper to generate an insight because you’re using machine learning to identify factors and dimensions that you physically could not see.

So you couldn’t have drawn a circle around it anyways, because you didn’t know it was there. I think it’s interesting. I think this optionality and the ways that that will end up being translated through software, it will be an interesting paradigm for us to help create.

I’ve got a couple of last questions to wrap this back to the beginning. I’ve talked in the beginning about the power of what you can do with single cell data and Ozette is really facilitating, generating tons of new insights out of that. If you think about, call it the short to midterm, not the super long-term, but the next three to five years, where do you see [00:31:00] this world of single cell analysis and immune profile, and is this powered by Ozette, going and what are the interesting things that you are super excited to see happen?

[00:31:12] Ali Ansary: Another way to probably ask me that same question, Chris is what keeps me up at night? In the short term, we make it very clear that we’re here for long-term partnerships. We’re here to help uncover the large amount of data that has been otherwise left on the table and to provide novel insights that we actually don’t even know how to value because you’re getting so much information.

In the next half decade we’re going to be at a place where we’re actively monitoring every individual on clinical trials with high dimensional data and that data is not only helping [00:32:00] with pharmacodynamics, pharmical kinetic information, it’s determining response rate. It’s ensuring that the right treatment is getting to the right patients and Ozette will be the default platform all the way through for any single cell data. We’ll continue to build in our transcript omics and in spatial omics because we know this is the way the field is moving towards. What makes our platform and machine learning very unique is that, it’s unsupervised and it allows us to continue to be agnostic of instrumentation.

As a physician, my biggest frustration has been looking at a complete blood count or a complete metabolic panel, spend only a couple of seconds looking at it, and then I look at my patient and say, “all right, they’re healthy enough to get treatment or not”. We’re going to fundamentally change that because the insights generated from someone’s immune system is going to allow us to [00:33:00] determine that response rate in real time. We won’t need to wait six to eight weeks any longer to determine if you need a pet CT scan, to determine response rate. We won’t need to go back and rebiopsy a solid tumor because we have these immune markers that we’re able to extract. That’s in the short term and I know the short term is right around the corner, but in five years, we’ll have a lot of opportunity to mature with a lot of therapies in the field of immuno oncology.

[00:33:34] Chris Picardo: That’s a good vision. I think that if we accomplish that in this short term, that would be pretty incredible and not just for Ozette, but for patients and I think that’s, at the end of the day, what this is all about. That feels like a really good place to end because I’m not sure you could say it any better and so Ali I want to thank you a ton for coming on the podcast.

[00:33:55] Ali Ansary: you, Chris. I appreciate it. I always have fun doing these.

[00:33:57] Chris Picardo: We Yeah, do this and we [00:34:00] just don’t record it on a weekly basis so it’s fun to put it down and make something for other people to listen to, but really appreciate you taking the time Ali, and thanks for joining us.

Thanks for joining us for founded and funded. I’m Erika Shaffer from madrona venture group and i’ll be talking to you next time

Founded and Funded: Conversation with Entrepreneur and Author, Shirish Nadkarni

Are you a founder or would-be founder? Madrona Investor, Ishani Ummat, sits down with Shirish Nadkarni, serial entrepreneur, now angel investor and author of FROM STARTUP TO EXIT, released by from Harper Collins in August of 2021. Ishani and Shirish talk about starting a company, finding your co-founder, product market fit and how to choose your investors.

Transcript (this is machine driven transcription so expect some typos)

Erika Shaffer:Welcome to founded and funded. I’m Erika Shaffer from Madrona venture group. Today, we hear from two new voices. Ishani Ummat, an investor at Madrona who came to us in early 2020, from Bain & Company and who has worked on numerous investments and initiatives at Madrona since. In conversation with Shirish Nadkarni.

Shirish is the author of the newly released From Startup to Exit book. Shirish has a special relationship to Madrona, which backed his first startup called TeamOn in 1999.

In this conversation. Ishani and Shirish talk about his road to entrepreneurship from Microsoft, how to choose an investor, and his 40, 20 10 rule. From Startup to Exit is on sale now, which is August, 2021. And it is a great how to guide for first time entrepreneurs. Listen on.

Ishani Ummat: Shirish, thank you so much for coming in today, it’s so nice to be with you in person.

Shirish Nadkarni: Hi Ishani, nice to be here.

Ishani Ummat: Congratulations on your book. So exciting to see you publish a book from this sort of illustrious career that you’ve had, it’s called [From] Startup to Exit. Is that right?

Shirish Nadkarni: That’s correct, yes. [From] Startup to Exit an insider’s guide to launching and scaling your business.

Ishani Ummat: That’s so awesome. I’m excited to get into some of the journey that you’ve had some of the anecdotes around that today. First of all, though, where can, when and where can we find your book?

Shirish Nadkarni: So we launch on August 24th you can buy it from Amazon, Barnes & Noble or really any bookstore. If you’re here based in Seattle, we have a great bookstore called Elliot Bay bookstores that you can purchase it from as well.

Ishani Ummat: We’re big advocates of our local bookstores, so certainly make sure to check that out for all of our listeners. Let’s start with back to the beginning. Like so many others here in Seattle, you started your career at Microsoft and, perhaps fewer of those people who started have ended up on this journey through many different companies, starting many ones and ending up as this, an angel investor, and then publishing a book about it.

I’d love to just go back to those original days. Microsoft is such an interesting and dynamic place. We’ve come to know and love the company here in Seattle. But making the transition from a big tech company into entrepreneurship and starting your own business can be pretty daunting for folks today.

What about working at Microsoft made you want to be an entrepreneur? Was there a moment where that catalyzed this; hey, I want to have this entrepreneurial startup experience rather than staying at a bigger company?

Shirish Nadkarni: Yeah, first of all, I was very fortunate to have joined Microsoft in it’s very early days. This was in 1987, when people were actually using MS-DOS. I don’t know how many people know about MS-DOS versus windows. Microsoft was really a startup a t that point. So I got great kind of experience working at Microsoft, launching email software on the PC and the Macintosh. And then I got to work on MSN.

I drove the strategy for msn.com and one of the things that we felt was really important for us to have was a web-based email offering. And at that time, I noticed that Hotmail which was founded a few years ago at that point was really successful and gaining a lot of traction.

And so I met with Sabeer Bhatia the founder of Hotmail and then quickly decided that we needed to acquire the company. But really what inspired me to become an entrepreneur was the fact that here what you know, two young adults 26 years of age who had built this amazing piece of web-based email, that you could access your email from any location. And that was really inspiring for me.

And I realized that the internet really had changed the model for startups. In the old days you had to not only develop your software, but you had to then, publish it on floppy disks and find distribution from egghead and so forth. It was not really easy for a startup to get going.

Whereas the internet really changed all of that and made it possible for a young entrepreneurs to build a piece of, SAS software and make it available through the cloud on the internet. So it was a lot easier to get started. And so that inspired me to, Dig that vision and really see if I could, provide a business email solution that would provide enterprise grade email and calendaring functionality for small to medium businesses. And that was the Genesis of TeamOn.

Ishani Ummat: Yeah, that, so precious, right? The vision for being able to access your email anywhere, anytime. But at the enterprise level, right?

Pretty different from the Hotmail product in its end user. But actually the underpinnings of that are quite similar. At Madrona and many of the other, large VC firms we think about these technological shifts, these major technological shifts, a step function changes, right?

What underpins what these technologies create, can be the underpinnings of massive new businesses and a pretty significant rise in startups. And okay, you have this passion for email, right? You work on the Hotmail acquisition. You take a little sabbatical, take some time off, reflect on things and come back energized and see an opening in the market, for sort of enterprise email. And the product, really great. We’ve talked about in early days, I can totally imagine who would use email every day. And who would think about using email even multiple times a day? Seems like it could have been, that could have been dissonance around; okay is this a weekly product? Is it a monthly product? But everyone was on the phone. People would re record rerecord voicemails. Finally get it right. And leave a voicemail. But no one was really using email all that often. So of course, we’re looking around that corner to the next thing you came up with this idea, I saw a market opening, built a great product and raised some VC funding and including from Madrona. ‘

Shirish Nadkarni: That’s right. This was in the heavy days of the internet.-boom, the .com-boom. I raised $15 million , a number of VCs, including [00:06:00] Madrona ventures here locally. And did that, with just a beta product. It was quite amazing. And I was lucky to have raised lot of funding at that time.

Ishani Ummat: Yeah and even in today’s world of massive rounds, $15 million is a pretty hefty amount. And thinking back to, that era of the .com-boom, you, must’ve done such a great job of conveying the vision for the company and Hotmail paving the way in terms of understanding the product at a conceptual level.

But I’d love to talk a little bit about some of the lessons you would share and you learned from that experience. We live in a world of product led growth now. And there’s these big terms, “product market fit”, “customer validation” they’re tossed around quite a bit. And there’s a lot of lengthy theories out there on what exactly it means to have “product market fit”. How do you measure that? What markers suggest that you might have it? Folks might be familiar with Rahul Vohra’s Superhuman’s Playbook, that’s really gotten a lot of traction lately, which is just around this idea of how would you feel if you could no longer use the product. And when customers say that they’re very disappointed or disappointed, maybe you have something that people might be interested in and would be upset if they couldn’t use.

So there’s a host of other ideologies that become popular in the product market fit front. And how to think about and measure it. But thinking back to those early TeamOn days, what do you wish on this front measuring product market fit, thinking about it that you had done differently?

Shirish Nadkarni: Yeah. When I, you know, thought of the idea of TeamOn and the notion of web-based enterprise grade email. I was convinced that this is going to change the world. And so I did really no virtually no market research. And in a sense, I was taking a bet that as you said, the technology shift.

That’s really what enables new startups to come out and change the world. And so I was making a similar bet that email would become prevalent in a kind of cloud-based environment. But I wish I had conducted, customer interviews to find out if the market was ready for our product. And it took a long time for cloud-based offerings to really gain acceptance because companies were not really willing to keep that data in the cloud. They were, they had concerns about security cloud based offerings. And I think that’s what ended up for us making it difficult for us to be successful with the original vision for TeamOn was that email is really sensitive data. You have sensitive communication, sensitive documents being shared across, individuals in a company. And I think at the end of the day, at that point the industry had not really migrated to a point where they felt comfortable with, cloud based storage of sensitive information.

And so we had to pivot and ultimately we pivoted to a mobile version of a TeamOn the idea was that you could access your email, your existing email from any internet enabled phone.

Ishani Ummat: Which is such an important part of the startup journey, but, hearkening back to the original vision, you were just too early. And I think sometimes when we are on the cutting edge of what’s going on and looking at these broad technological shifts and specific applications, sometimes we forget that we have to bring the rest of the market along with us. So what a good journey and what a good learning set of learnings for you in in the startup journey and how to, respond to a market need, but then also where exactly it’s taking you and how exactly it’s playing out, maybe a little different than you would have anticipated early on. It’s a good learning that most of our founders go through at many given points in time.

Before we talk about the next journey that you had, I wanted to talk about briefly, early in your book, you mentioned that recruiting your technical co-founder took you several months. It’s one of the biggest challenges. LinkedIn didn’t exist back then, there was no teal fellowship, no on-deck fellowship, none of these Twitter, different types of ways to build relationships and find people that might be interested in building the same products or same types of technology that you are.

Given all those things exist today, it’s still a big topic and it’s still a massive challenge. I talk to founders about all the time. How talk us through how you found a co-founder, how did you approach the process and what parts are still relevant for entrepreneurs today?

Shirish Nadkarni: A tough time to recruit people, even though, as I said, the.com- boom was happening and a lot of people were leaving established companies to join startups or start companies. I first obviously went after people I knew at Microsoft and many of them were excited about what I was applying to build. But they just couldn’t get themselves ready to leave Microsoft, where they were getting a nice comfortable, you know, paycheck and healthcare and all that. In my case, finally, what happened was I was introduced to my co-founder Shaibal Roy through a common acquaintance. He had a lot of expertise around email but unfortunately he was based out of the bay area and he was working at Netscape at that point and still was also hesitant to leave the company.

So we arrived at the arrangement where I would work with an outsourcing company to get the software developed and he would work part-time in the bay area and guide the outsource development shop in developing software. And that he joined the company. Once we raised the Series A and that’s what happened we raised $15 million and obviously that made him comfortable enough to move from the bay area and come get to Seattle.

Ishani Ummat: That’s great. Fortunately for a lot of folks today, we live in a world where remote work is possible. Folks are building remote first companies and instead of having off-sites, having on-sites for the first time. But I think that problem and challenge of leaving a comfortable job in a position, whether it’s at a big tech company or even a later stage startup to go start your own venture can still be so daunting and still be a big decision for folks to make. So I would say that’s part of, one of the challenges that still remains for a lot of entrepreneurs looking for co-founders to come and join them.

Shirish Nadkarni: Yeah, and it’s difficult these days because especially here in Seattle where you have all the big companies, whether it’s Microsoft, Amazon, Facebook, Google. And the amount of compensation that they’re providing is amazing. So you really have to, one of the things I emphasize in my book is the fact that the founder has to be really a visionary and a great sales person, not in a traditional sales person sense, but somebody who can really excite people about their vision. I think that’s an essential skill that a founder has to have to successfully recruit folks to join the company.

Ishani Ummat: Absolutely! And I think that’s part of the skill set of pitching to investors too, is having the conviction and then being able to convey that conviction to a broader group of folks, whether that’s someone who’s going to join your team and having that recruiting capability is so important. Backing that recruiting capability is the venture funding. And so that’s something, absolutely, we all look for and hope to see in many of the entrepreneurs coming out of Microsoft, Facebook, Google, etc.

Okay. You start TeamOn, you have a great exit there from the email company, and then you go on to start a new company, right?

So this started your serial entrepreneur journey, a company called Livemocha, both inspired by and then acquired by. So you mentioned that, a year and a half into Livemocha Series A, one of your VCs instructed you to work with an investment bank and sell the company actually at a valuation of $100 million, even though you had a little proof of monetization and your acquire, wasn’t interested in paying that price. That’s the canonical example of don’t work with venture capitalists. Right, like, that’s what everyone’s terrified of. Then they weren’t happy with the proposed price and then to me, that seems so absurd, you know, coming from an objective point of view, but it’s true that I talk often with entrepreneurs who are nervous about giving up control of the company for fear of this type of situation playing out.

Inherently, and always there are going to be some bad actors out there, and so that’s a nature of the deal. Largely, in my perception of the world this often comes down to misalignment. A fundamental misalignment between an investor and an entrepreneur, or the, a mismatch, if you will.

How would you advise founders that, you work with now on the angel side of things to avoid this conflict with their own VCs or folks that they might be thinking about taking money from?

Shirish Nadkarni: So that’s one of the things that I really talk about. My book is you have to be really careful about who you pick as your partner in terms of the VC firm. So not only do you need to do due diligence about the VC firm that you want to partner with, but specifically who is going to join your board.

Unfortunately in my case while the individuals who joined my board were really smart individuals, they were fairly inexperienced as venture capitalists and they didn’t really have good, they had good operational experience, not really in the startup world.

And I didn’t really get good guidance, good advice from my board members. So it’s really important for you to, have a discussion with your VC firm, understand who is joining your board, do the due diligence, just as much as they are doing due diligence on you to really make sure that there’s a good fit and they have the world of experience that you can count on to make important strategic decisions in the future.

And then if you receive acquisition interest you really have to, as a board figure out, you know, how you want to respond to that interest. How’s the company doing? Is the company really doing well? In which case you may not want to sell the company or sell the company only at an astronomical price that makes it compelling for you to consider.

It’s very important that you don’t waste, the time, the precious time, each founder has, can only focus on a few things and, we want to make sure that as a board, that the founders are really focused on making the company successful and that you don’t waste their time on unnecessary pursuits that may end up not being very successful.

Ishani Ummat: Yeah, it’s a really good point that M & A is a whole separate topic that we could talk for hours about as well and that process gets really complicated quickly and we’re seeing more of that with the rise of SPACs and that whole advent, but coming back to this mismatch point and being, having alignment on your board.

Such a critical part of building a company is prioritizing the right things collectively. And I think first time founders, serial entrepreneurs in general have so much to learn from, about creating a board and their board members and putting the right people in that room together to help drive the business forward, create alignment, and make collective decisions. But it’s hard. It’s a really hard process to understand who the right partner is for the long journey are going to be.

One of the things I’ve seen more recently, is founders actually, while they’re doing the fundraising process. And in those sort of third or fourth conversation with investors actually hold a mock board meeting. And I really liked that because it you’re right. It is such a two-way street where you have to figure out, hey, is this the right fit for the investor? And is the investor the right fit for the entrepreneur? And the mock board meeting is such a good way to test that because saying, hey Shirish, how are you going to be, if you’re on my board, what is the type of interaction? What are the questions you’re going to ask me? What rapport can we establish? What are the directions you’re going to push on? Where might there be tension? Can be sussed out so nicely in a board meeting or in a mock board meeting versus just a formal one-on-one pitch, right?

Shirish Nadkarni: Yeah. I think that’s a great idea to test out if there’s compatibility between you and the board members. The other thing that I would emphasize is that really the board meetings while, there’ll obviously be discussion around operations, situations and how you making progress and all of that, most of the board discussions should really focus on strategy.

What are the strategic decisions, important, strategic decisions that the company is making and are they making the right decisions and investments? And you’ve got to do that on a quarterly basis so that you make sure that you’re all in. But your board and you making the right decisions moving forward, that’s really the level at which the VC should really be or the board members should really be operating, not getting into the nitty gritty details of the operational performance of the company.

Ishani Ummat: Yeah, totally. And I think, there’s certainly both sides of that argument. I, 100% having strategic alignment in the board meetings themselves and with the board members and when you have to have those quarterly meetings that making sure you’re focused on the strategic aspects of the goal.

As a junior investor, we also try to spend a lot of time in those details, those operational details outside of the context of a board meeting. And I think that’s also where folks maybe don’t quite utilize their investors, as much as they could. Having a board observer or someone who has been in those meetings, but also can get into the details with you and say, hey, let’s test this operating model, or what might pricing look like and how can we go figure out a bunch of different pricing options? And what have I learned from pattern recognition around seeing the companies that I work with and how can I bring that to you? Is another really good way to take advantage of the fact that, hey, you have this group of people that are eager and willing to help beyond just writing a check.

Shirish Nadkarni: And I was fortunate that at least one of my company that I had the opportunity to work with other members of the VC firm who are willing to roll up their sleeves and really get into some operational issues and provide their expertise.

That was a really valuable resource. So you should, as a founder, really understand. What resources is the VC firm providing to help you with operational issues, with recruiting, with business partnerships and leverage the hell out of that relationship for your business.

Ishani Ummat: Totally! And it’s something that we at Madrona and many of our peers always try to make really clear when we work with companies where we start the journey together is that it’s more than capital.

Shirish Nadkarni: Yes, I remember actually, when TeamOn working with Matt McIlwain when he was, an early partner at Madrona back in 2000, it was, we had some pricing discussions and I remember, to this day he offered some really good advice to help me think through my pricing challenges.

Ishani Ummat: That’s so great to hear, and I’m sure that advice has been amplified by many more years of experience since then. So for folks that you know, are looking for, to work with hands-on investors, that is an awesome way to be able to utilize them. So let’s talk about what happened after Livemocha.

Shirish Nadkarni: So after my mocha I launched a third company called Zoomingo, this was in the mobile shop space and the idea was to take all the information that you would typically find on your Sunday flyers. Of course these days nobody gets a newspaper, but in the old days, people would get the Sunday newspaper just so that they could get all the flyers from your, Macy’s or Nordstrom’s telling you about all the great deals that are happening.

What we did was built a mobile solution, which allowed you to access all the great deal information by zip code. So based on where you’re located, tell you, Pierce, Bellevue square mall next to you and hear all the great deals being offered by Macy’s or Nordstrom’s around you.

We did pretty well initially. We got to number 15 in the shopping category as an app, we had over two half million downloads but the space got super competitive with big, much bigger players entering the market with coupons.com and others. And so our growth flattened out and that’s the death nail for any startup it’s you have to show hockey stick growth otherwise it’s very difficult to raise funding. So unfortunately that was one where we didn’t really have a successful outcome.

Ishani Ummat: Yeah, but so much learning along the way. And again, this kind of precious product motion where you identify, you have a life experience that informs you starting a company because it’s such a big pinpoint, where’s there going to be a sale? Why do I always get this paper in the mail? And then turning that into a new technological shift has created an opportunity for us to build a company around it. So again, those, thematic learnings really shining through and every time I’m sure you got so much better, learned so much from the last process.

Shirish Nadkarni: Yeah, absolutely. One of the things that we were highly focused on with Zoomingo was in terms of achieving product market fit was really tracking our retention. And the way I talk about it in my book is to crack cohorts of users and track the usage from day zero to day 30 and beyond.

And there is a magic rule that I talk about in my book, the 40, 20 10 rule. So you want to see 40% coming back on day one, 20% on day seven and 10% on day 30. And if you achieve that level of retention, then you can get to becoming a top 5,000 app. We got very close to it, but we didn’t quite hit that mark and then that’s one of the reasons why we didn’t see the hockey stick growth that we wanted to see.

Ishani Ummat: It’s such a good early building early hygiene around being able to collect, track, and then report those metrics is such an important part of company building that I think people sometimes under appreciate that, oh, in this era, of product lift growth, then you have to understand how that product is interacting in the ecosystem. And so that’s such a well-taken and a good point. And obviously from the investor side of things, I’m always looking at metrics. And that level of hockey stick growth. And obviously there are deviations to that model and to that narrative of continually growing so fast and outsize growth, but I think it’s this responding to what you’re seeing in the market, being able to track those things, lets you say, hey, let’s make this adjustment and then you get back on track.

So now fast forward you are, you’ve had this sort of incredible foundational learning and career at Microsoft. Now started three companies and had various outcomes and exits from them. But again, so much learning along that journey. And today you sit as an angel investor through one of the local organizations, TiE. You’re giving back to that community and those, the serial, and set of entrepreneurs that are in their local here in the Pacific Northwest, which we love with our sort of vision of giving back and building the Pacific Northwest tech ecosystem.

We’ve also done a lot of work in build and helping build that angel community through meetups over the years, which I’m sure you’ve attended. And our pioneer fund most recently, we ran a survey for an angel investors locally in Seattle. And then in your book, you did talk about this idea of these technological shifts and whether that is from the entrepreneur or investor side, I think an incredibly important component of what you have to believe for starting or investing in a company.

Shirish Nadkarni: Absolutely. I’m a big believer in the opportunity that technology shifts or platform shifts enable and how you can use that, disrupt existing incumbents as well as build totally new solutions that can leapfrog what incumbents are providing in the marketplace. So that’s where I look for at now as an investor is, are you taking advantage of some technological shift that you are the first to really adopt and use to disrupt the existing players in the market?

Ishani Ummat: Tell us a little bit more about that, what are the technological shifts that you’re excited about? Who are the types of entrepreneurs and what are they taking advantage of in Seattle today that you are getting most excited about and seeing a lot of energy around?

Shirish Nadkarni: Yeah. So I invested in a number of companies here locally that I’m really excited about. There’s a company that I was an early investor in called Ally which is it also received funding from Madrona ventures. And they are a SAS solution to manage OKRs or Objectives and Key Results, the company’s doing phenomenally well. And I see them applying AIML to provide more insights and actionable actions. Individuals and so forth.

There’s another company called Bloomz which is an educational space. It’s a communication platform for teachers to communicate with parents. They are in over 25,000 schools across the US. They recently won an RFP for the state of Texas to be the sole communication platform for schools in the state of Texas. So I’m really excited about them.

Then I was excited to see I was an early investor in Safari, they announced the acquisition by Microsoft. And again, they’re applying AIML, which is again, the technology that I’m a big believer in to provide actionable insights on spend data within corporations.

Essentially I’m looking for companies that are either taking advantage of AIML or moving legacy software to the cloud. Those are some of the types of technology platform shifts I’m looking for.

Ishani Ummat: So nicely dovetails with many of our investment themes here at Madrona. We’ve focused so much on infrastructure, intelligent applications, cloud, native applications, and now this sort of next generation of artificial intelligence machine learning (AIML), natural language processing, unlocking new use cases in different verticals that we may not have thought of before. One, we’ve spent a lot of time on recently is in the life sciences, for example there are countless examples that we could go on and highlight.

It’s been so nice to hear your story Shirish and congratulations again on launching your book.

And we’re so excited for it to come out in a more public way.

Shirish Nadkarni: Thank you very much. Great to be here.

Erika Shaffer: Thanks for joining us for Founded and Funded. If you’re interested in checking out Shirish’s book From Startup to Exit, you can look in the show notes and there will be a link to the Amazon page.

Till next time.

Founded and Funded: Linda Lian of Common Room on Building a Team of Co-founders

Starting a company is a lonely business. Finding co-founders can be the solution to this – but what if you don’t know anyone who fits the bill? Linda Lian of Common Room set out to build a company and recruited her co-founders one by one. Hear her story and theirs in the latest Founded and Funded podcast. Linda sat down with Madrona’s Shannon Anderson and then we checked in with co-founders Viraj Mody and Francis Luu.

Madrona works with founders from the earliest stages and has helped founders identify possible co-founders and those crucial early employees. Listen to this conversation to hear Linda’s approach and how the future co-founders at first ignored Linda and then dove in to the challenge due to her persistence and vision.

Transcript

Erika: Welcome to Founded and Funded, I’m Erika Shaffer from Madrona Venture Group. Today on the podcast, we talked to Linda Lian, Co-Founder and CEO of Common Room, a company that as Linda mentions in here, Madrona has been working with in funding since the negative day one. Common Room is working to build a platform that enables brands to more easily connect with their users. The company came out of Stealth in the spring of 2021 with $52 million in funding from Greylock Index, Madrona and others.

We have a deep relationship with Linda in part because she used to work at Madrona. She was an associate working with entrepreneurs on new investments and our existing portfolio companies. From there, she went to Amazon’s AWS group and then she left to build Common Room. In this conversation, Shannon Anderson, our Director of Talent, talks to Linda about one of the most important elements of building a company, finding the right co-founders. Linda went about this in a slightly different way than we see with most startups. We also talked to two of those co-founders about how Linda approached them and their first responses, which was to ignore her for various reasons, and their decision to join her in founding Common Room. The conversation with Shannon and Linda is interspersed with Shannon’s conversations with Francis Luu and Viraj Mody, two of the co-founders that Linda recruited.

There’s a little bit of musical interlude to indicate when we are making a switch, we’re going to start off here with Shannon and Linda speaking. Enjoy!

Shannon: I am so glad you are here. We’re having so much fun working with you. I want to start off here with you. I just want to get a baseline for who you are and understand your journey. My question is, what is your why? In other words, Linda what kind of problems do you tend to find yourself solving? Another way to think about that it is, what are you known for?

Linda: Hey Shannon. It’s really awesome to be here with you today, talking about the Common Room journey which, Soma and Madrona has been part of since day negative one. But Shannon, to answer your question, I wish I knew myself better. It’s a big question, but I think that what really drives me, and it has from an early age, is to build something of value to prove that I can do it. I think that a lot of entrepreneurs might have a certain chip on their shoulder where the more that someone tells them that something can’t become a reality, the more you want to make it real. So I would say it’s been a combination of, just wanting to build something of value and the desire to prove anyone wrong who says that, that can’t happen.

Shannon: Yeah, I get it. Wanting to prove yourself is such a motivator. It’s an intrinsic motivator, right? It’s not, it’s a little bit external, but it’s really inside of you proving to yourself and to others that you can do it. What I’d love to understand is how your career has reflected these motivations, right? So, as you think about, why you chose the school you chose and the program that you chose, how you ended up from, job A to B, you ended up at Madrona, as an investor, and then you went to Amazon to be a product manager, and now you’re founding your company. I’m curious what, in your mind, as you look back, are those common threads.

Linda: So I think for me, I’ve always had this like insatiable appetite to look at things from a 360 perspective. By that I mean, I’ve had a nontraditional career in that, I have done a lot of different things. Sometimes I call myself like a ‘jack of all trades’ master of probably nothing.

But as you mentioned, I started my career in investment banking doing really traditional mergers and acquisitions and really large, cross border multi-billion dollar deals in very stable industries. And having had that experience, I think it was incredibly valuable to be able to strategically understand the value of a company from simply looking at its financials.

But what it made me realize was, I had this hunger to see the other end of the spectrum, which was how can I work my way from like this late stage, massive corporate clashing up against each other kind of world to go upstream continually to where, the source of where ideas become real.

I’ve mostly spent my whole career I think, working backwards and trying to get to that source going earlier, earlier stage, after my time at Morgan Stanley and investment banking, I went to a late-stage startup called Lookout Mobile Security. and still at that point, the company was a couple of hundred people.

I felt like that was still feeling like a company that had already figured out a lot of things. And of course, we now know that companies are never fully figured out, but I think at that time I just had another sort of push and urgency to go earlier and I never really tried to stay in the same role.

I think I always tried to maximize for learning and to me after a time in finance, I felt like I didn’t necessarily have the skillset or the experiences that I wanted more on the outward facing thought leadership, business development, content marketing side of things.

I felt like that was just an area where I was intrinsically uncomfortable and I think early-stage investing enabled me to leverage my sort of finance assets and experiences, but also couple that with, the day-to-day work of being an investor, which I don’t know if many people know this, but is incredibly, outward facing.

It has a lot of like mappings to what I would consider in a more traditional company to be almost like business development or, more external facing type functions. And then again, it’s after a couple of years working with Soma and the rest of the Madrona team I just felt like I wanted to get back into being where the action was, rolling up my sleeves, building within the context of a company. So when AWS offered me the opportunity to join them and lead product marketing for Serverless, which was at that time growing extremely quickly and was in this completely new category that was still being created, I jumped at the chance to do that. I think it’s really that that ability to take a risk and not worry about having this traditional more linear career path that I think has enabled me to be a better founder and to be a more empathetic leader and I’m still figuring out all those things. I think having that diverse background and perspective has been really helpful.

Shannon: Yeah, that makes a ton of sense to me as you walked through it and this whole working backwards concept of trying to get closer and closer to the source of where our company originates, or at least where our product originates.

So, at AWS you’re building the VM1 and now you’re at Common Room and you couldn’t get any closer to the metal than Common Room, because that was an idea that you had and nothing more at the time.

Linda: Yeah, exactly.

Shannon: Yeah. So that’s great. So, let’s talk about Common Room.

When you started Common Room and you had decided that you discovered a problem that you were passionate about solving in terms of a customer focus, did you start off thinking that you were going to be a solo entrepreneur founder, or did you have other ideas for what your early team might look like?

Linda: Yeah so I think despite having been an early stage investor and having seen this from the other side of the table, it’s never as real as when you’re trying to get something off the ground and you’re asking yourself, I have a problem that I want to solve. I understand and have empathy for a specific customer set, but I may not have the necessary skills to make this a reality or if I were to try, it would be a sub-optimal experience because I am not an engineer, I’m not a product designer, and I think it’s hard to believe that anyone wants to start a company as a solo founder.

Starting a company is a scary experience. It’s a leap into the unknown. It always feels better to do it with somebody at your side, but oftentimes, for one reason or another, you do end up being alone at various stages in the early company building journey.

I think for me there’s two paths that every founder or founding team can take, they can choose philosophically to build everything themselves and do what it takes to, learn new skills. And like the example here would be, I would design the product using pen and paper, even though I’m not a product designer or they can philosophically decide I’m going to identify what I’m good at.

I’m going to spend time doing what I’m good at on behalf of the company. Because I believe that if I can leverage my super power for the company, that’s going to be best for the company. And I’m really going to take a lot of time and effort to build a team around the things that I don’t have as much strengths and capabilities in.

I was philosophically very much in the latter camp and I think one of the first things that I did after we closed our C round was I set out to find the right co-founders on and I decided early on that the first co-founder I needed was in product design. I think this isn’t obvious, but with our product, Common Room, which is a new customer journey platform for community in order to enable companies to build and nurture and engage their thriving communities of end users, it was very important that we had not only at delightful product experience, but one that required a rich set of workflows and interactions and a highly social kind of way to represent community because community is all about people, content, and communication. And so with that in mind I set out to find my design co-founder, which it took months, and it took a lot of work and it took networking and pounding the pavement and cold outreaches and having lots of conversations that went nowhere.

But when I found Francis who is my Design, Co-Founder it almost was like an instant fit in terms of our working styles, the thought partnership that we had and his experience and background having been at Facebook for over a decade recently, leading design for groups and communities and also yeah, chill out there.

Shannon: That’s amazing. Like when the first time, the most recent time I spoke with you about your team and I had seen how much progress you made. The first question I had was so you’ve got three co-founders at this point, you’ve got Francis, who’s your designer co-founder, you’ve got Viraj Mody, who’s your Engineering Leader and Tom Kleinpeter, he’s also Engineering. And so you’ve got like a very, like an all-star team with incredible pedigrees. And if I remember correctly, you did not know any of these folks until you reached out to them? All three of them, if I remember correctly, were cold calls, can you talk about, let’s start with Francis. How did you know what you were looking for so that when you met him, you knew he was it? And then how did you do it? How did you go about it? Like literally, like how many emails?

Linda: I think that I knew I wanted to work with somebody who had a, like an intuitive understanding of community. That was the thing that I felt was the irreplicable or incredibly special quality that, like you could go one of two ways with product design for Common Room. You could think about it okay, we’re building an enterprise SAS product and platform that is meant to cater to companies and organizations.

And so I’m going to, bias towards finding someone with that type of background, or you could say, because we’re building a community platform that is meant to enable other organizations and enterprises to better engage and nurture their communities. I’m going to be biased towards, someone who understands community.

And so for me, it was a no brainer in that. I believe that there are many people who understand the B2B SAS motion, but there are very few who have a deep empathy and appreciation for community, which is an incredibly amorphous and highly fuzzy word, but it combines things like social communication, content consumption, content exploration this concept of knowing who people are, hearing what people say enabling everybody to feel supported and heard and connected.

And that, that to me was like a special skillset that was really hard to find. And so I tried to find people that, might have that. And it was really hard. I don’t think I found really anybody except for when I met Francis. So the process by which, I was able to team up with Francis was I messaged him on LinkedIn in a cold outreach message and he didn’t respond. And I continued to make progress on my own. And a couple of months later, circling back, I messaged him again and I said, “Hey I messaged you a couple months ago. I’m reaching out again, would really love to chat more about this if you’re interested”. And to his credit, he just had his first child, Ben with his wife, Lisa. And so it wasn’t that he was ignoring me, he was just doing a much more important thing of being a father.

But he eventually did pick up my call. We went and grabbed coffee, I think, the week before the pandemic happened. So I did get to meet Francis in person, which I think, we just started jamming and the thought partnership was super natural. And he instantly got what we were trying to do, and it just worked out and it was always very frictionless, and I think we align on values.

We talked about what it meant to build the business, all the downside and upside scenarios. And that’s one of the things that I always value with all of my co-founders of frankly, our entire team is that we can speak very transparently about all the things, and I think that level of trust is just super important.

Shannon: I’m really curious to understand the experience that Francis Luu had, not only being recruited by Linda, but some of the reasons that he found this opportunity so compelling. Francis is the Co-Founder and Designer at Common Room and he was the first person that joined the team.

Francis, welcome to our podcast. How are you?

Francis Luu: I’m doing well. How are you?

Shannon: I’m Great. I really wanted to ask you about your recruitment journey coming to common room. It’s actually pretty unusual. And what I’d love to do is ask you about your first interaction with Linda, that, this story goes both you and Viraj have the same story. She reached out to you and initially I think you, you did not speak with her, but at some point you finally, somehow she converted you into a conversation, a coffee chat, and then, and then the rest is history. So I’m curious, what changed your mind to talk to her? And what were your first impressions once you finally did make that step?

Francis Luu: Yeah, absolutely. And just to, as a bit of context I think this will definitely shed some light on Linda’s claim of basically us ghosting her. So yeah, let’s take it back a little bit. So June of 2019 my wife and I actually had our first kid and I promptly went on parental leave and around that time, I’d already then wondering if I was ready to take the next step. So I wanted to really, in a way, live that, and I think the parental leave and the very gracious benefits allowed me to really just live that without making a big leap or guessing.

So I did the stay at home dad thing for a bit ended up actually officially leaving Facebook in November and then, just continued on and I’m like, this is great. This feels like a next, a good sort of way to evaluate next steps for myself. And yeah, it was having a good time learning how to be a dad and. Understanding that it definitely isn’t a break at all. It’s a ton of work and a ton of different work. I’m just so grateful for my parents. I unfortunately have to go through it myself in order to learn these sorts of things, but better late than never.

So I think it was around February that’s I just randomly decided to log back into LinkedIn. I haven’t really checked in on anyone, when it came when it came to work and I saw it obviously a million messages I think people had seen that I’d left and we’re curious to reach out and everything. And right near the top of the inbox list was someone named Linda that had reached out and that hadn’t just reached out, this was her second time reaching out. And I actually completely missed her first message.

That was, I think back in November, December, she had mentioned that she was going to be leaving AWS, had an idea and really wanted to get some of my thoughts around it, given that the last two or three years for me at Facebook was actually working on the grips of Kennedy’s product. And I’m like, “Oh My God, I’m so sorry. I totally ignored your first message. I wasn’t aware of it. My deepest apologies”.

What was actually funny is that you can tell there’s a difference between message number one and message number two. Message number one was like, I think I’m going to leave. I have this idea. And then the most recent message right around the February timeframe was like, I started a company. I’d love your feedback on what we’re working on right now. So there was clearly this sense of progression and I’m like, oh, okay. If she just wants some feedback and some ideas more than happy to help out, I guess it’d be nice to use my brain again for a little bit and not just be completely to a completely in the dad thing, even though that was, that’s been a lot of fun up to that point.

So yeah, I, I reached out, reached back out, apologized profusely and we figured out a time and a place to meet, and it really was as simple as that. And then we saw each other in person and shared a coffee for about, I think it was a good hour and a half, two hours that first time.

Shannon: Francis it’s interesting. Linda used the ‘I’d love your feedback’ tactic. So tell me about that tactic versus maybe another tactic she could have used, which is, I want to recruit you. Would you have responded differently?

Francis Luu: I think so, especially at that point, I had been tinkering around with the idea of perhaps going back to work, but I wasn’t ready because I was really enjoying just staying at home, being with the kid. And I think the barrier to entry, hearing something like, oh, ‘just wanted to get your thoughts on something I’m working on’, I think made it quite a bit easier to say yes. Yeah, of course, ideas and feedback can be a very casual thing. When it comes to recruiting, that could be a bit more of a commitment even just saying yes to a conversation.

Shannon: The interesting thing here is every solo or, co-founding team that I’ve ever talked to says in some way, shape or form, we want to go hire the best XYZ out of you name any, big company, Google, Facebook, Amazon, Convoy and in through more local companies. And, but you did it. And it’s, I always discouraged okay, listen, it’s not about the pedigree. It’s not about the fact that they work at Facebook, that’s a safety net. It’s almost a lazy way of specking out the wall saying if they’re good enough for Google, they’re good enough for me. You have a napkin with an idea on it and a little bit change in your pocket, not to underplay that, but, what, how did you do this? What is your secret?

Linda: Yes. So, when we teamed up with Viraj, he was still at his last role. And I think with anybody that you’re trying to, attract, whether they’re, a new father or they’re in a really busy job as the technical advisor to the CEO during a pandemic. It’s all about building that relationship, aligning on values and if they’re, that person’s not ready to take the leap, then showing them continued progress over time.

So, with Viraj I reached out to him, he might have not responded, but I did reach out again and he picked up the call and we talked about the idea, and he felt like it was really interesting. I knew that he would potentially find it interesting because, he had experience as the co-founder of a startup which was built around the music community. So I knew that this was a topic that he had thought about before and had lived. And I think instantly when we were chatting about Common Room, what I recognized was that, like Francis he had an intuitive and deep and instant connection to the problem that we were solving.

Not only had he built, Audiogalaxy with Tom Kleinpeter, who is now my other Engineering Co-Founder in the kind of music community space, but like specifically Viraj and Tom had also lived the journey at Dropbox of product led growth and what a user communities could mean for a company a modern SAS company. And so again, it was where, Viraj was really interested in the idea. We had amazing thought partnership. He was bringing new ideas that I hadn’t thought of to the table and when you recognize that kind of energy in a conversation, it sticks with you because you’re pounding the pavement, as you mentioned with just a little change in your pocket and you meet a lot of people and have a lot of conversations where that energy isn’t there.

And so if you feel that spark that’s worth fighting for. And so Viraj, Francis and I were chugging along and we were making a lot of progress on our own with respect to customer discovery and really honing in on the problem. And just talking to a lot of potential customers, many of whom we’re partnering with still today. And I think with Viraj, it was just going back to him, a couple months later and saying, hey, we’d love to catch up and share our learnings because we’ve learned a lot. And I think, with a rush, I think he was positively surprised by just how much progress we made.

And it’s always that it’s the concept of hey, come on board because this bus is leaving the station and we’re going to continue to drive this forward so you can’t ever have the mindset that you need anybody or anything to move forward and continue to build. You just have to keep going. And the right people will usually end up coming along, even if you have to play the long game and we still play the long game today, right? Like we’re always playing the long game, whether it’s with team building or earning the trust of our customers.

Shannon: You hit on something earlier that I really wanted to dig in on just for a moment. The idea that I know that Viraj, in looking at his profile on paper, I know he looked like he might have some of the same interests that you’d have in community. And that’s why he just, a little plug for Madrona, I went into the things that we do for our founders and try to help you with recruiting. And so we gave you a short list of people that we thought might look a little bit like what you had described as the kind of people that could help you build this thing. So his name showed up on that list, but that’s, identifying what somebody might be interested in.

It’s different than really discovering the truth of that. And I always think of everybody, including everybody here, listening. Everybody has a career problem all the time. And the career problem is that delta between where you are right now and where you want to be like current state versus future state. And we’re always growing and we’re always trying to get to that future state. So there’s always a problem we’re trying to overcome where whatever we’re working on, we want to learn something and then move onto the next thing.

And so all of these things lining up is almost a little bit like you think of it as magic, but it’s not, you’ve got, Viraj and you’ve got Tom and other than that they both know how to solve or a lot have thought a lot about how to solve these community problems. It’s, there had to be some other things that they were hoping would be present in working with you at Common Room, that wasn’t happening for them in their current role. How did you discover that? How did that conversation happen, in real time, when you were getting to know each other?

Linda: That one’s tough. I don’t know Shannon, if I have the same, like jujitsu as you it was probably yeah, it was probably unconscious on my part. Like maybe I was listening for the desire to build or the desire to start a company or the excitement around the actual work that company building is, which is team building and customers and I don’t know that’s, when you’ll definitely have to ask them.

 

Shannon: So Viraj thank you so much for joining me. I’m excited to talk to you about this topic. We talked about it in the past, but without the recording button on. So I really wanted to get your story. I had a chance to speak with Linda about her impression of the, the recruitment process with you. Tell me about your first interaction with Linda of course, the story goes that she reached out to you, maybe you weren’t necessarily responsive and so I’d love to hear what changed your mind about talking with her and, what were those first conversations and what were your impressions?

Viraj: Yeah, for sure. She emailed me just before the world locked down. And when I first got the email, it was definitely interesting but also one of many that I usually receive. And so I was like, hey, I’m just gonna ignore this for a bit, but I did respond to her saying, hey, this sounds pretty cool, I’d love to get to know you, but also like it’s unlikely that I’m going to do anything now. And it took us a while to get it scheduled. I was dragging my feet because honestly there was no urgency on my end to do this, but also the COVID rumors had started and people were starting to see the world going to lockdown. So like work had gotten really busy, too.

It took maybe 20, 25 days since she emailed me to actually get on a call with her. I really enjoyed that conversation. I could tell pretty quickly that, she knew what she was doing. If you know, if you know, Linda, you know, all her strengths, you can pick up pretty quickly. And so I left the conversation feeling pretty impressed by Linda, but also I was like, Hey, look, this is too early. I am really not thinking about doing a startup thing just yet, because I got a day job and it gets pretty busy. So I filed it away as something that was more interesting than the average email I get which I mostly don’t even respond to. And then just, things went to 11 at work. The world’s shut down for real.

The company I was at, obviously like every other company during the time, we were trying to figure out how to cope with everything because everything was up in the air and unknown. So things got really busy. I basically ignored reaching back out to her. I would have been busy, but then a couple of months in, she emailed me with a pretty solid update on what she’s been up to. Some of the things she’s learned about the community space, some of the customers she’s been talking to. And that was the first time, and I was like, okay, look, I probably want to take this call and reconnect with her because clearly she’s going to get this done and it lined up in some ways with what I was excited about. So it wasn’t like a complete, Bitcoin or AR VR thing that may have been interesting in its own , but I had no interest into like this was definitely something I had interest and experience with. And so the, hey, look, it’s worth getting in touch with her again and then the ball started to roll pretty quickly after that.

Shannon: That’s really interesting Viraj, Linda told me the same thing. She said she, her secret sauce here was really persistence, but not an empty persistence. It was one of providing something to you in the terms of an update. How does a founder get the attention and I’m not trying to be too flattering, but you’re a force, you have a, you are an accomplished highly pedigreed guy and you’re no lightweight. And Linda is no, she’s wonderful, but she’s no more special than every other, brilliant founder. What was the transition for you from ignoring her emails to, I gotta get in on this?

Viraj: I think for me, particularly the timing lined up with what I had wanted to do eventually anyways, so I’m pretty entrepreneurial. It was mostly a question of when not if I was going to do my own next thing or, join like a really early-stage company of some sort. So, I had clearly been like in the headspace of wanting to go back into entrepreneurship and then meeting with Linda and keeping up to date with what’s going on with her helped me see that, okay, this is a person who’s similarly motivated and who’s similarly diligent.

I would do what she did. Like just because somebody says no one to blows you off once doesn’t mean they’re not interested, doesn’t mean you walk away. So I saw a lot of what I would do in what she was doing, but also very complimentary, I come from a product and engineering background, her background is very different than mine. And so the thing that connected the dots for me was, hey, look, I am in this head space where I know I want to do this eventually. And in fact, until recently I was talking to Tom, who I was almost certain I want to do something with again, and from a space perspective, from a business opportunity perspective this stuff seems pretty legit, she was able to describe what she was doing, talk precisely about the progress she had made versus, I get emails from people that are either just like name dropping, like nobody’s business or using 300 words and I still don’t know what they were trying to tell me.

Linda’s like that, it’s very precise. So yeah, it just. It was the right thing to get me to start talking to her. And then obviously once you start talking to somebody and get to know them, then the equation is completely different than now.

Shannon: Yeah. That’s great. That’s perfect. So you referenced Tom Kleinpeter, and he is, was actually your co-founder at your previous company that you did together, which was Audiogalaxy. And it’s interesting because I want to move onto another topic, but I want to ask you, did you come together? Was it a condition of you coming that Tom would come with?

Viraj: It was not a condition of any sort. It was one of those where if you can get Tom and me together, you’d be a fool to pass on that opportunity, no matter who you are. This is like plainly speaking. Both of us have very different strands. Both of us complement each other really well and you increase your odds of success exponentially by having the, both of us on the team. And from my perspective, obviously I wanted to work with Tom again.

And if I was going to do this with Linda, I would want Tom to be on that team. Cause why not? A team is successful because of the various skills that people bring to the table and the complementary skills they bring to the table, it was a no-brainer from my perspective, I remember talking to Linda instead of breaking out of character for a second, hey, I’m just going to objectively tell you that if you could get the, both of us, you’d be a fool to pass on this really is the right thing to do. And to her credit, like she got it, we chatted about it and she had some questions about how we’d work. Cause it’s scary, if, bringing in one co-founder’s scary and bringing it in two at a time is even scarier. So I could totally see her perspective, but it was such a great conversation, walking her through my thought process, having her get to meet Tom, get to know him. I think it all worked out at fabulously.

Shannon: That’s awesome. It worked out great so far, so good. And it’s interesting because Linda recruited you out of Convoy, she recruited Tom out of Dropbox. Both of you have worked in enterprise as well as startup situations. What’s the difference, like how would you compare and contrast for somebody for first time co-founder coming out of a Microsoft, maybe not having done a startup before?

Viraj: The thing that’s common is you need to know how to build. At a Microsoft, you probably can’t get by and get too successful without actually being able to deliver. And that’s the same thing with a startup. You have to ultimately deliver. Talk takes you on so far, even at Microsoft, even at a startup. But other than that, I think it’s developing completely new muscle.

So it’s I’m probably, I could probably come up with an analogy, but I think the bottom line really is. You have to be willing to understand how the rules are different or how the needs are different and be able to adapt. And if you can get your head around that, I think the context and the experience you have working at large companies can be modified and reapplied to having really strong impact at small companies where almost certainly will not work is expecting that you would work the same way you did at a large company, and then expect to have success at a startup. I’m not saying it cannot happen, but I’d be surprised if it happens.

Shannon: So Viraj also, I want to just give you a plug. You are in the co-author of a book called Technical Recruiting and Hiring. Ozzie Osman is actually like the main writer and then you are one of the co-writers and this is published by Holloway. And it is a phenomenal book. It is my Bible. I send it to every founder that we invest in and I use it as our textbook, as we walk through various things that they’re learning and you wrote the campus and university recruiting piece of it, but I know you have expertise all along the way.

So I just wanted to say I think you really know, how to put your money where your mouth is when it comes to this topic. And so finally, I want to ask you about the future of Common Room and you guys are a little over a year into it. You’ve just come out of stealth mode. You raised your B round. What keeps you coming to work every day? And what are you most excited about in terms of the mission itself?

Viraj: When I was a kid, I used to love Cadbury chocolates. They were pretty big in India. And I was so passionate about it, that I sent a letter to the MD of Cadbury, asking them to invent. It was something with sprinkles and cashews and something. I don’t know the details, but I know I distinctly remember writing to them. And what was the most amazing part of this as I got a response back from them and they invited me to their factory and I toured it and it was. It was just so phenomenal. Even today, when I walk into a store, I will instinctively just pick up a Cadbury bar. I don’t like the American version as much as I like the British or the Indian version, but still that won’t stop me from doing it.

And so that little act of kindness or customer relationship building that happened when I was a kid, left such an impression on me that I’m essentially, I feel like an extension of the company for no logical reason other than I got to visit the factory and I got a letter from somebody high up there. But if you step back and think about that motion they made a lifelong evangelist or champion for their chocolate bar through a tiny personal interaction.

How do we build software to scale this so that everybody can have their customers become an extension of their company? You call it community motion, you call it bottom-up motion, you call it product led growth, it doesn’t matter what you call it, the dynamic I cared about really is that look; treating our customers as like a revenue machine on a transactional interaction paradigm where it’s you have a problem, I haven’t answered and let’s not talk to each other ever again, like that just feels so old.

And so that’s the thing that I connect the dots with where I’m like, if I can do a little thing, everybody intellectually understands, having our customers be your champions is great. How do we actually make that happen? How do we teach the world? How do we build software? To make that happen there, wasn’t the kind of things that excite me. So from a mission perspective, obviously that’s what brings me to work every day. Part of it also is the team, when you have fun working on stuff with people, it doesn’t have to be easy. It doesn’t have to be hard. It just has to be fun.

With startups, a new curveball shows up every day, multiple times a day. That’s part of the fun for me . Look if I can deal with this with a group of people who are similarly motivated and passionate. That’s perfect. What else could I ask for?

Shannon: That’s great. We are really excited to watch you all on this journey. I have to tell you before we go, I do want to ask you, did they make the candy bar that you suggested?

Viraj: No, they did not. My ideas were not that great back then or now, but at least I had ideas.

Shannon: That’s right. I just wonder, because whenever anything with chocolate and nuts, it sounds great to me, so

Viraj: Yeah, no, pretty sure they had professionals making decisions for them, but

Shannon: Viraj, I’ll talk to you again in a year or so when you’re down the line and maybe interview some of the rock stars that you haven’t even recruited yet and find out how this is all going, but in the meantime, I wish you all the best of luck and thanks so much for your time today.

 

Linda, a couple of things that I heard here today is that, you were pretty relentless. First you identified that basically, the skills and the motivators that you needed to put on your team to either fill the gap and what you were missing or round up the team. Then you iterated on that by having conversations with people and you were not just having conversations, but you were always in recruiting mode and earlier you refer to this thing called the ‘slow poach’. And I think that’s interesting because it’s, you don’t just go into recruiting mode for when you need somebody. You always need to be recruiting. And so when did I, when I wanted to ask is if you could give our listeners, two or three or four things that you consider to be your tenants or your operating principles, as you continue to move your company forward, as you probably have 20 people that you are sending emails to and pulling along, I’d love to know like, how you think about this just in a summary?

Linda: Yeah, I think for me, it’s just about two things. Building a relationship based on transparency and trust, having plain direct conversations about what it means to join an early-stage startup and the day-to-day work, like I’m always biased towards transparency. I don’t oversell anything. In fact, I undersell things. And the, secondly, if they’re not ready to leave, then continually keeping them updated on our progress. And demonstrating that rapid clip of, that acceleration of progress day after day, week after week, month after month. And hoping that at some point, those stars will align and we’re always, you know whether or not we’re a good fit for a good person today. We’re always going to be a place that welcomes great people at any stage. And so that’s what I bias towards.

Shannon: And thanks so much for sharing your story today.

Linda: Thank you so much, Shannon.

Shannon: You’re welcome.

 

It’s so interesting to talk to Linda Lian about her experience, recruiting Francis Luu, Viraj Mody, and Tom as well. And it’s interesting that the stories actually match up quite well, but one of the things that Linda wasn’t able to give insight to is what were the things that compelled each of these people to join her team?

And she, I think she knows instinctively, but like any great founder, any great recruiter. They may know it inside, but they haven’t really bubbled it to the surface. And one of the things I noticed was a real contrast in the reasons that Viraj and Francis joined Common Room. Viraj is really motivated by making great software and creating amazing customer experience. And he told this story about Cadbury as that’s the kind of product and kind of loyalty that he wants to build and doing that through great software is his mechanism for building that. And that’s a very compelling mission and it’s just as valid for what Common Room is doing.

Francis’ motivation, which is much more about his passion around community and building communities and groups, and some of the work that he’d done at Facebook and the markers for his motivations are really easy to see on his resume or his LinkedIn profile that he’s all about creating community with the software. Just working at Facebook is the tell. And when you look at Viraj, you can see the same mark different markers that actually indicate that his motivations are all about building great software building great teams.

So, in retrospect, after having this conversation, I can see very clearly that those two areas of motivation, the problems that they were trying to solve, I guess, in their career, like, what do you want to do next? What are you running toward? They each described them differently, but those are both compelling and interesting for them at Common Room and that’s what makes a great two-way fit.

So, for those founders out there listening to this, or for those folks thinking about becoming a co-founder with someone like Linda, the path that you get there, isn’t going to be straight, but it’s all about finding that two way fit and working together to solve problems that you all care about in a way, and doing it in a way that aligns with your values and your interests.

 

 

Erika: Thanks for joining us for Founded and Funded. If you were thinking of starting a company, reach out, as you could tell from this podcast, we really work for our founders. We worked with Linda early on, helped her identify possible co-founders, and then funded her company. It doesn’t always work that way, but we are very invested in the success of the Seattle tech ecosystem and that means making a lot of connections possibly for you.

Reach out to [email protected] or to [email protected] to learn more and thanks for listening and please share this podcast and like it on all the different platforms, thank you.

Rajeev Singh of Accolade on Resilience and the Expectations of Leaders

In this week’s episode, investor Matt McIlwain speaks with CEO of Accolade, Raj Singh. Raj & Steve Singh (now a Madrona investor) along with Mike Hilton started Concur in the early 1990s and over more than 20 years weathered economic and product challenges to build the company into the leader in corporate expense and travel. In 2014 they sold Concur to SAP for over $8 billion. Two years later Raj and Mike joined Accolade, a personalized medicine and health advocacy company that went public in July of 2020. Matt and Raj talk about the need for resilience in leadership, lessons learned, how the board room is changing for good and what the big tech companies getting into healthcare means for consumers.

Matt McIlwain: [00:00:00] I’m excited to welcome Raj Singh to our podcast series today. Raj is both a great friend and an incredibly accomplished entrepreneur and innovator, having both founded and built Concur Software. And eventually, after 20 years of building that company and transforming that company a couple of times, selling it to SAP in 2014 for about $8 billion. And then, as you’re going to hear, he spent some time thinking about what was next and eventually decided to join a company called Accolade, but we’ll let him tell that story. Welcome, Raj.

Rajeev Singh: [00:00:35] Thank you, Matt. It’s great to be here. Appreciate you having me.

Matt McIlwain: [00:00:38] Let’s go back a little bit first to, to Concur. This is a company that you co-founded back in, in the mid-nineties and tell us a little bit about that journey and both the founding of it and maybe one or two of the big moments of transformation in that journey.

Rajeev Singh: [00:00:56] Sure the founding is actually a, boy it feels like a thousand years ago now. It was 1993 which is a thousand years ago for those listening. And I was lucky. I was really lucky. My brother Steve who has some tie-ins to Madrona, as I understand, and a gentleman by the name of Mike Hilton and who’s now one of my dearest friends, we’re starting a company and I was a college kid looking for a purpose. And so, they gave me a ring and said hey we’re starting a company. And I thought that’s exciting, maybe I should jump in. And then they told me it was working on expense reports and I thought maybe I shouldn’t jump in.

That doesn’t sound exciting and next thing you know it’s 21 years later and we were really lucky to have found both a category that was that was missing a leader, number one. And number two a group of individuals who founded the company to share a thought on what leadership looked like and how to build culture and mission and a business. The story of the company is, I think, the story of any company that goes through 20 years of creation and transformation which means you’re no matter what business you’re building whether it’s a dry cleaner the last for 20 years or it’s a travel and expense reporting SAS business that last for 20 years there’ll be moments during that journey where you have to fundamentally rethink the founding principles of your business. For us we lived through 1999 and the.com crash. We made a fundamental pivot of our business from the licensed software business, which probably no one remembers anymore, to the SAAS business that was somewhat controversial when we made that choice in 2000-2001. And then we started to add on capabilities and really start to think about how we could transform the travel supply chain later in our life. And each of those were transformational moments where we had to make a choice. Were we in this for the long-term, to build a great and enduring business or were we in it to make to maximize the sort of short-term returns? And every choice we made, and this I attribute to my co-founders as much as anything I was a part of, was about the long-term value of the business and the ultimate, ultimate highest purpose of what concur could be.

Matt McIlwain: [00:03:07] Oh that’s fantastic. And, yeah, it’s notable that you and Mike and Steve were with the business all 21 years, all through the acquisition of SAP. And you mentioned this point about leadership and culture. When you face that really tough economic downturn, and even more importantly the.com crash, and then made this decision to move from being licensed software to one of the very first software as a service companies. How did you all bring the culture and the company along in those decisions?

Rajeev Singh: [00:03:45] It’s such an important question because sometimes people think you just make a strategy choice, and you tell people okay we’re going this way, and everyone just comes along. And anyone who’s led and knows you don’t really get to tell people to do anything. You are constantly selling your vision and where you’re going. And the mission of a leader is ultimately to get everyone to understand why we’re going in this direction and a big part of that why is culture. What are we trying to build? We’re trying to build something long-term and sustainable. We’re trying to build something that we can be proud of in terms of the way we built it. And so, when we said, hey we’re making this shift to the SAAS business, a part of our story to our team was, one, the long-term sustainability of this company is tied to this new business model. It’s going to open up new markets and give us a new opportunity to serve the middle market, smaller companies around the world, and it’s going to allow us to stay together as a team and stay true to the values of the business that we built. Meaning the choice in 2000, Matt, candidly, for Concur was, were we going to sell our company or were we going to buckle down and recommit to the promise that we’ve made to our shareholders and to ourselves? And that was as much a part of transitioning to the SAAS business as the business model shift. And I think that was what we were selling our team. Do we believe what we said five years ago when we were trying to build this company or was that all talk? Because if it was all talk, we should sell it, and if it wasn’t, let’s hunker down and get this done and this is how we’re going to get it done.

Matt McIlwain: [00:05:22] I love that thought about this idea of when we had this decision asking people to recommit and double down on the vision and know that there’s hard work ahead and it if you want to be a part of that you know let’s, let’s recommit as a team. I really like that.

Rajeev Singh: [00:05:38] Not everyone does recommit but think when you have that honest conversation you find out who doesn’t want to. And that’s okay. There’s nothing wrong with those people, they made a choice and they’ve had successful careers. But those who did recommit knew what they were in for, and I would argue 10 years later could look back and say that’s one of the things I’m most proud of in my career.

Matt McIlwain: [00:06:00] Now let’s fast forward to 2015 ish and SAP has acquired Concur, and you have decided to move on from that and are thinking about things and ultimately land on this opportunity with Accolade. It was an existing business; it was on the East coast. You know what was it that inspired you and Mike, who joined you in that, to come on board at Accolade? And then I’ll probably follow up from there.

Rajeev Singh: [00:06:25] So I think you have a choice, like we all do. And we’re lucky, actually, let me start there, we’re lucky when we have choices because it means the world is smiling at us and saying here’s some choices you get to make. And for us we had some choices to make around were we going to go start another business, which was our inclination, but where were we going to start that business. And the choice that we really committed to, almost immediately upon leaving Concur, was that we wanted to make the next business we were a part of way closer to the human condition. Meaning we wanted the end of every workday to align around the idea that we helped the human being, or we helped people. And so, healthcare was a natural thought with a couple of notable exceptions. We knew nothing about healthcare, and it was, and it looked to be maybe the single hardest category on the planet to build and build sustainable long-term value. There aren’t a lot of success stories of tech entrepreneurs getting into healthcare and building successful businesses. And so, with those two-notable sort of question marks we thought we’re still going to give it a shot. Because that’s what entrepreneurs do, they say wow everybody else failed we’ll give it a spin. No doubt it will be fine. We were lucky to bump into Accolade. And the reason I say that is they were building something that we thought was extraordinarily unique and so when we found them, we abandoned our ideas around building our own from scratch. In part, Matt, I think, in part because we loved what they were doing, and in part because we were a little older. I wasn’t 23 anymore.

Matt McIlwain: [00:07:59] It’s interesting, you know, having gotten to share the Accolade journey with you and the team, is that you had this vision for, first of all, individual employees and their families deserve better access to information and ultimately healthcare, and you can find ways to align that with their employer. And Accolade already had that vision, had that passion, and yet there were opportunities to then deploy modern technologies into making that whole experience even better, was that kind of the core of the thesis for you and how have you pursued that?

Rajeev Singh: [00:08:34] A thousand percent and we were quite thrilled when Madrona decided to jump into that journey with us. And so, the core idea, which is so sensible to anyone who’s experienced the U S health healthcare system in any way shape or form, is that most people who enter the US healthcare system are confused by the by the incredible complexity, by the opacity and by the disconnectedness or the chasms between each of the components of the us healthcare system. And so, people needed help and the help they needed is often the information they needed to make a good decision. Accolade, it built that out, building a human relationship, which people laughed at, Matt. When we first started, people said that’s not a scalable model. How can you build human relationships at scale with millions of people? You know of course. What do you need technology, you need to be able to leverage data to, in turn, personalize every one of those experiences, and deliver them at scale? And we thought we could help there. Along with the idea that building that technology stack, building that data set that you know the idea of reaching HR buyers, and building a B2B commercial motion to acquire corporations as customers was something we knew how to do. And so, we thought that two plus two might equal more than four equation did work here and with a few bumps and bruises along the way so far so good.

Matt McIlwain: [00:09:51] You know you had a very successful IPO last year, originally planned for right about when COVID hit its initial very hard point, and you guys made some really good decisions around that and have done quite a bit since then. We might get back to that, but I’d love to, you know, this was your opportunity to be the CEO, too. As I believe you were president at Concur, if I remember that correctly, and, you know, maybe a reflection on resilience as a CEO and what you’ve learned over the last six years in that regard.

Rajeev Singh: [00:10:27] I think it’s such an interesting question, Matt, because there’s been no matter where you are in a business you have these moments where you have to reassess where you are and what you’re dealing with and what you’re going through. And that’s true in life. And it’s true in business. And I think what might be unique in the CEO role around resilience is, is that the ultimate decision does rest with you. And there are big choices you make that have an impact on many, in my case now at Accolade 1900 people’s lives, and the and those decisions are compounded by the fact that you were the one who recruited those 1900 people. You were the one who said, hey, believe in this dream and go make it, go make. So, I think with each component of, or with each setback, or with each challenge, we have a choice to make about how we’re going to respond to those setbacks and challenges. You’ll recall, Matt, when we started at Accolade the first thing that happened is our biggest customer canceled. So, three months in we lost our biggest customer and we thought this is going awesome. And then we filed to go public in February of 2020, that seemed like a really good idea until the market went down by 30% in March. And with each one of those moments, you have choices. And here’s what I’ve learned in that process that there are things we have to recommit ourselves to in order to create that resilience. And I think it applies whether you’re a CEO or wherever you are and those are, in difficult times you recommit to the fundamental principles that you run your life by, that’s number one. And for me that meant family, that meant core values, that meant physical health and mental wellbeing. There is a, there’s an interesting dynamic that says when things go wrong, we get pulled away from our routines. We pulled away from the things that matter the most because we think we have to do unnatural things to change or to fix them. And what I’ve learned now, because I feel like I’m a thousand years old, but I’ve learned now is in those moments when things are going wrong, you double down on what you know, and you double down on all the things that got you here and you just go one step in front of the other. There’s an interesting story, and I know I’m rambling on too long, but it’s a, it’s a story I repeat all the time. I was at dinner one night with a group of business leaders and a gentleman by the name of Randy Hetrick. Randy’s a former Navy seal who founded a company called TRX in the fitness world. And somebody asked Randy who had been shot multiple times in combat, what’s it like to get shot? And he talked about a time in the field where he got shot. So, you want to talk about resilience. And he said, you know, he told the story, he said the first reaction you have is you’re mad, shot you and you want to go find that guy and shoot him. And the second reaction you have is, I’m bleeding in the middle of a field in Afghanistan and I need to get home. And then you focus on the five feet directly in front of you and every piece of training you’ve ever had in your life. Take the five feet in front of you and then you take the next five feet. And I’ve probably given that speech a thousand times to people who are wrestling with either different difficult moments in their personal lives or difficult moments in their professional lives. Sometimes you’ve got to break it down. Don’t look at the mountain look at the five feet in front of you and keep taking the five feet and eventually you get through. And my experience is you do get through it.

Matt McIlwain: [00:13:57] I love that story. And it does remind me of, hard to believe it is 13 months ago last March, and I remember two conversations we had then. And one was the conversation about, you know, should we go forward with this IPO in this very difficult environment, and you were being super thoughtful and grounded about that. The one that I’m going to remember more, all my life, was the one a couple of days later when you called me up and said, hey, we’ve got real needs in our community that are emerging with this COVID and you know what are we all going to do about it? And I’m here to want to try to do something about it. And so, in the midst of this, you were there trying to lead on starting something that came to be known as All in Seattle. And I just, you know, to have that kind of grounding, in that time, what was going through your head to be able to keep those two different, important issues and to lead on this issue of All in Seattle?

Rajeev Singh: [00:14:59] It’s very sweet of you to say, Matt, and I can’t tell you how much it meant when I called you, that you said I’m all in what do we do? What are we going to do? I think we do have at some level, a capacity in our lives to look at our lives and then look at the broader picture of the universe and say our particular travails and foibles aren’t really all that significant in the broader scheme of what people were wrestling with. And in many respects, Matt, the capacity to just focus and it was in, you remember, was every night. It was all night every night making phone calls, while the day-job was happening, was an opportunity for me to put in context that, yes, Accolade couldn’t go public when we thought and maybe we weren’t going to be able to go public at all, maybe who knows what was going to happen? But in the broader context of people not having work, not potentially getting kicked out of their apartments, potentially not being able to eat, being food shortages happening in the city already, that it was not the biggest problem in the world. It wasn’t even close. It wasn’t on the top 10 list. And I think that context is helpful in how you think about your business. I really do. I think, look I’m obsessed with my business, like you’re obsessed with Madrona. I think about it constantly. But it’s not the most important thing in the world and we have to keep it in context in order to make sure we’re making grounded decisions within our business and outside it. That’s the best way I can describe it, Matt. It was the best thing that could’ve happened to me, to be able to throw my heart and soul into something with my wife.

Matt McIlwain: [00:16:27] Yeah, I was going to say Jill did an amazing job too. Yes. As did many others our community, as did many others.

Rajeev Singh: [00:16:34] Exactly. You and Carol, Kabir and Noreen. There were so many people who jumped in. Heather Redmond, you know so many people who jumped in and really made a commitment to this. That was inspiration in a moment in time where the world needed inspiration. It was inspiration for me as much as it was for anyone else.

Matt McIlwain: [00:16:50] It’s great that you mentioned Kabir, cause that’s, I think that’s the place I wanted to go next. In that another way to both continue to learn and also to give back is being on boards of other companies. And you I have had the, really, the pleasure of being on the board of two companies together in Apptio, with their founder and CEO Sunny Gupta, and then Amperity with, with the founder and CEO Kabir Shahani. Curious, you know, what draws you to other talented entrepreneurs and CEOs that would say gosh that could be a real fit a good fit and it’d be something fun to work with them. What are some of the attributes of those other CEOs that you’ve had a chance to work with over time?

Rajeev Singh: [00:17:35] With those two guys for sure, off the top, integrity right off the bat. Life is too short to work with people who you don’t enjoy and who you don’t trust and know who are waking up every morning to do the right thing and to take care of their people to build a real business the right way. And Sunny and Kabir hit that off the top. The other thing you talked about resilience, Matt. You know, if there was one word you would use to describe both Kabir and Sunny, would be tenacity, relentlessness. Like those guys are never stopping, in fact, I get a ton of energy, I go to Kabir’s board meetings and I won’t lie to you I come by walk out of there not only fired up about his business but also fired up about mine, for some reason. And, and that tenacity just indicates someone who’s not going to fall down at the first setback because we know building businesses is all about setbacks. And here’s the other thing that I love about those two guys and this will sound weird, I think, as it relates to how I make my choices. They have fun. They love their work. They’re not complaining about the bad, you know the hard parts of the job, they’re relishing the fact that they get a chance to do it. And I just love that mentality. That this is supposed to be fun. Like you’re supposed to enjoy this. And I’d rather do that at whatever scale I’d rather do that with people that I like. High integrity people with this kind of character who are having fun. I’ll take that any day. It doesn’t matter to me the size of the business, it, those are the attributes that probably really appeal to my heart.

Matt McIlwain: [00:19:02] No that’s fantastic. And I just would chip in on you know that they’re both such curious and humbly curious learners and they’re really good at something I, you know, I like to call triangulation. Taking all the different data points and trying to bring those altogether. And, as you were saying earlier, you know, sometimes as the CEO, you do have to make ultimate calls on things and being able to be good triangulators, good listeners, and then make those calls and then help the team, you know, follow around those decisions, is both things that Sunny has done many years and now Kabir as Amperity’s growing. You know one of the decisions that both Kabir and you made last summer was in thinking about your boards. And you guys both had you know a lot of diversity in different respects on your boards, but you know wanted to be intentional about ethnic diversity, in particular, having a member of your board who is black who came from a BIPOC background. And you took on this board challenge. Tell us a little bit about that from your perspective.

Rajeev Singh: [00:20:04] As the world evolves, we take on new responsibilities as business leaders, Matt, that weren’t necessarily presumed responsibilities of business leaders 25 years ago. Meaning that I think in 2021 we do, increasingly as business leaders, have a responsibility to speak on topics that matter to our employee base. Because our employee base very much is expecting us to not do more than make a profit, but to make a profit consciously, that the idea of conscious capitalism and building businesses the right way matters. And I love that by the way. I think that’s fantastic. And so, the idea of creating diversity, but ensuring that diversity isn’t just at the lower levels of the business, but it’s at the very tip top of the business at a board level and then a senior management level is something that I think every business gains from if they’re willing to make that commitment. And so, when Brad Gerstner and crew came out with the board challenge, and I know you were you were instrumental in kicking that, in getting that thing kicked off, when they came out with that board challenge, Matt, I remember talking to Brad. He said about three sentences and I said yeah, I’m told this makes so much sense. And it was a great impetus for us to commit to the principles that we already believed in. And we were lucky enough to bring on a woman by the name of Cindy Kent, who’s the president of Brookdale, senior living.

And she’s been spectacular. And she comes from a different background than many of our other board members, and yet brings the healthcare expertise coupled with that different background that has already really shed extraordinary light on our boardroom. And so, I think there are moments like these that are going to continue to face business leaders in our, in the United States over the course of the next three to four years.

And I just encourage them to wade in and make these conscious choices and make sure that they’re consistent with your belief system. And I think your employees are going to embrace that belief.

Matt McIlwain: [00:22:05] No that’s, that’s really well said. And I do think that there is a kind of this embedded word of kind of intentionality, too, that, you know, you had your core values, you were living them out in many respects, but in some areas, there was an opportunity to be more specific and more intentional and you followed through on that, which is just fantastic.

Rajeev Singh: [00:22:24] Don’t you think, Matt, a part of this is, if we have the platform and we can give other people the example of, hey, you can do this in your business and the outcome is going to be positive. That it’s one thing to do it’s another thing to commit to something like the board challenge publicly. And in some ways, give others who might not have the same situation we do the cover to go commit the same way. And that’s that is that point of intentionality. It’s not just doing it’s saying I’m going to; I’m going to say out loud that I’m going to do it. And in, so doing, give other people some room to follow suit.

Matt McIlwain: [00:23:05] I just, I definitely think there are our roles in situations for that help. And this was certainly one of them and it just it meant a lot to me and to Madrona, as well, that you and your team decided to accept that challenge.

Rajeev Singh: [00:23:18] And here’s the best news of the whole thing. Not only did you do all that, but your business also got better and there’s a way to build a business that continues to improve, and it continues to improve the society around it at the same time. That’s possible.

In fact, like, you know, I worry sometimes that there are indictments of capitalism out there, and yet I’m such a huge believer in the system and a believer in the idea that capitalism done well for our communities for our society is the future.

And I think it’s what this, you know, you’ve got a 25-year-old. It’s what this next generation of people coming out of school wants. They want to know that they can go build something, go build their lives, go build their careers, but do it in a way that makes the world better. And I just, I love the push that we’re getting from that generation.

Matt McIlwain: [00:24:05] I think that’s a said. And it brings us back to why you and Mike decided to help lead Accolade. And that, you know, you were caring about how do we make people’s lives better in a very tangible way. And make a difference through business, through capitalism, as you say, tell us a little bit more about how the technologies you’ve been deploying over the last five six years, whether that’s, you know, the mobile interfaces or the early applications of machine learning are actually leading to, better patient experiences, better alignment with the health service providers that you all employ and ultimately better outcomes.

Rajeev Singh: [00:24:47] I think if there’s one word that I probably wouldn’t have described it this way, six years ago, Matt, of as I really started studying healthcare, but that I think is the, or the most important word, in how healthcare will evolve over the course of the next 10 years, it’s personalization. That we have a system today that kind of churns people out transactionally, deals with their condition or deals with their particular transactional need in that moment, and yet we have enormous amount of data that’s available to us about all of their contextual needs. And so, you know the unfortunate reality in our country is you know, some number like 30, I think at the numbers, 35% of the people who are wrestling with one chronic condition are actually wrestling with two or three, two or three.

And so, managing their diabetes isn’t necessarily good enough, if you don’t know that they’re also wrestling with hypertension and depression. And so, the capacity to collect the data set required, which is something we’ve worked enormously hard on at Accolade, and then the leverage that data set using AI so that we can make recommendations.

But today we have frontline care teams or claims and benefits specialists, nurses, and pharmacists, and we just added primary care positions to our service delivery engine, to be able to use that data to put and use AI to put recommendations in front of our care delivery teams, that say, this is exactly what Matt McIlwain needs in this moment, or at least this is a really good recommendation for you to take up, that you don’t have to search through all of his medical records to figure out. We’re going to use computers in the way that they’re supposed to be used to give you the data you need to get you to the right outcome faster and in a highly personalized way. And I think that same concept exists in all the gene coding work you’re seeing. The same concept exists in all the blood work that we’re seeing. Like there’s so much work happening that says I can know more about this individual and stop treating their condition. They came in and told me their shoulder hurt, and I treat that shoulder. I know so much more about that person. How can I help really get that to the exact right spot?

Matt McIlwain: [00:27:02] Yeah, no, that’s really well said. And in a lot of respects, you all are trying to create a personalized experience for sort of the whole person, you know, for the macro biology, if you want to say it. And of course, it’s not just the biological makeup it’s environmental, there’s so much more. And yet, as you hint at there, you know, one of the things we’re excited about is the microbiology and the micro and in the core chemistry level, what we can are only beginning to understand and see around single cell sequencing and the leveraging of DNA. Seems it’s that personalization theme is going to play out over the next set of decades.

I mean, we really truly are only in the beginning days here.

Rajeev Singh: [00:27:44] And this is the macro hypothesis that ultimately you have to take all that information and to get human beings to act on it. You must have a relationship with that human being that engenders trust. Because once we know all these things, can we leverage the human relationship or the relationship that we’ve built with them in order to get them to act on their health and their needs?

And this is one of the most confounding parts of health care in any country, not just the United States, which is oftentimes people understand what’s best for them, but don’t act in that manner. Because of the complexity of getting to that outcome. But if our hypothesis is let’s gather all that information, let’s understand where they need to go and then let’s hold their hand and get them there.

And today it’s with one set of data, but tomorrow to your point, I think the data is going to be dramatically larger.

Matt McIlwain: [00:28:40] And that kind of leads me to one last topic, I think that our audience would be interested in your perspective on which is, this set of opportunities in healthcare have not gone unnoticed by the big tech companies. And it’d be interesting to hear, you know, especially with, Microsoft in light of their recent $20 billion, you know, announced acquisition of Nuance, or Amazon with things like Amazon Care and PillPack, or Google with Verily. Just a little bit your perspective on how those different players is approaching the healthcare market and, you know, how they might compliment some of the things that you all are doing.

Rajeev Singh: [00:29:19] Yeah. I get this question often. There’s a, there’s a question as you know, which of these guys are competitors or future competitors and which of these guys are partners? Here’s the way I think about it. First of all, it certainly has not, it’s not gone unnoticed even in the past, Matt.

I mean, it’s 20% of GDP in the United States and is 10% of GDP around the world. And so, if you’re going to be a company at scale like Amazon, Microsoft, and Google, you have to play in healthcare and it’s, it is a vertical that you have to pay attention to specifically. Meaning you can’t build generic solutions for the vertical.

I think Amazon is approaching the space in much the same, brilliant way that they approach everything that they do cost, utility, and availability. And so, and with an obsession around the customer experience around the individual transaction. And so, to me, Amazon Care, PillPack and the wide variety of things that they may do are going to be a focused-on cost availability and transactional customer experience. We think that’s really smart. And to the degree you can reinvent individual components of the experience, those will be valuable components of the experience for individuals. We do think we believe differently that healthcare is longitudinal and that the individual transaction is important.

But unfortunately, unless you understand the breadth of that individual’s needs, you’ll struggle to really have an impact on trend line. You can improve the consumer experience and you can lower the cost of the transaction, but healthcare is a long-term journey, and the long-term cost of that individual won’t necessarily alter, unless you really understand that context.

I think Microsoft and Google are playing more of a data game. And enabling this personalization capacity via data. Now, I think Google’s playing in a number of investments as well, but fundamentally I think that both companies are taking a platform story that will enable companies like Accolade, or others, to leverage a broader data set at scale and less expensively, to go deliver their personalized service.

And I think that’s a super smart strategy that will yield value on a broad basis, particularly for the larger players in the space who aren’t necessarily technically adept enough at getting that data themselves.

Matt McIlwain: [00:31:36] That’s a great framing. And I agree with you that, you know, both on the kind of the operational initiatives, as well as on the investment side, I would imagine that all three of those companies will continue to increase their presence in healthcare more broadly.

Well, Raj it’s just been a delight to spend some time with you here and it to hear a little bit about your journey and your perspectives on a variety of topics. Really want to thank you for spending some time with me today and look forward to seeing you both in the boardroom, hopefully in person soon, as well as at the Seahawks games in person when the fall turns come around.

Rajeev Singh: [00:32:17] Oh man. Can you imagine? I can’t wait. Matt, thank you so much for having me. It’s always a pleasure. We could do this without the recordings and the video, anytime.

Matt McIlwain: [00:32:27] Okay. Thanks Raj. Appreciate it.

 

Building a Healthy Open Source Community with Jeremiah Lowin, Founder and CEO of Prefect

In this episode of Founded and Funded, Anu Sharma continues her deep dive into commercial open source projects and talks to Jeremiah Lowin, the founder and CEO of Prefect, a dataflow automation platform that is trusted to build, run, and monitor millions of data workflows and pipelines. Jeremiah talks about how he and his team built this open source community from zero to 5,000, and how the community helps the team at Prefect reach their users and intentionally break out of internal echo chambers that often trap early stage products.

To hear the full interview which goes in depth on data workflows, airflow and Prefect – download here.

Transcript (this is machine driven transcription so expect some typos)

Anu: Hi, I’m Anu Sharma with the Madrona Venture Group. I recently spoke with Jeremiah Lowin, who’s the founder and CEO of Prefect. IO. Prefect is an open-source software company that helps customers manage their data workflows. Data workflows help transform data through a series of steps and are often used by data engineers, across companies. Jeremiah came up with Prefect while he used to still work in risk management. As he built Prefect, he discovered others wanted to use it too. Now the team has an outstanding customer list and recently landed a CDC as well as a partnership with Microsoft.

In a previous episode we spoke with Joe Beda from Heptio about how open-source software can help create a thriving ecosystem around a core project. In this episode, Jeremiah speaks about how Prefect has focused on building a rich community around an open-source project. This community helps them build a far deeper understanding of their users and customers. This episode is a part of a longer conversation you can download from Madrona’s website, just search for prefect. That’s P R E F E C T.

In this shorter version, we dive right into how open-source communities help break out of our echo chambers that might trap us as we iterate on the product. Enjoy the show.

And you were just beginning to get into why it was important to not speak to yourself and get into an echo chamber. Can you say more about that?

Jeremiah: Absolutely. This is a complicated thing because I believe that open source has become very similar to how social networks would be pitched or described 10 years ago. Where you would hear these ridiculous business models like, oh, we’re going to start a social network.

And if only a million people sign up, then we’ll have a great business. And it’s like, well, yeah, obviously that’s how business works. The question is how you get the million people, not what happens after their there. Open-source pitches today have very much the same tenor when I hear them. It’s well, after we get the community, then, then this will take over.

After we do this, we’ll hire the, the dev advocates. And it just doesn’t, this is the hard part, which is you have to build that community. You have to give that community a reason to exist, and you have to do it while giving away something for free, in the open, which is a relaxation of the control that a startup with otherwise enjoy, the editorial control.

There’s a list of reasons that building in the open are strictly worse. I think that that’s an important, maybe a controversial thing to say, but from the point of view of a startup aiming to build a successful product, you would typically want to do that with a very strong product vision editorial hand on the rudder.

Not in the open where you’re in progress designs, that you don’t have time to explain context for, can be viewed and adjusted and critiqued. So why do we believe so strongly that this is a good thing, therefore? Well, it’s because you can tap into this diversity of opinions and use cases and problems. If only you can find the spark to get this thing started.

And that is, that I think is the big challenge is how do you start a community? Forget that it’s open source. How do you start a community from nothing? How do you get people together to care at all about this? And I think that there’s a unique opportunity for companies, for commercial open-source entities to do so.

Now there’s an easy answer there, which is sure, just dedicate resources to it. And we see that in the largest open-source communities. We see that in the TensorFlow ecosystem, for example, which is an open-source ecosystem, but of course, with millions of dollars being pumped into it by various stakeholders and it’s very much taken off and it’s self-perpetuating.

But on day one, what does that look like? How do you, how do you get people to buy into this? And there’s a line that Danny Meyer actually says, the restaurateur, and he was talking about the hospitality business. And he’s talking about how do you elevate an interaction away from being a transaction and into being a hallmark of an experience of, you know, the start of, of a longer relationship. And he has this line, which I, which I just love. And I think it’s absolutely true. He says, people will take as much interest in you as you show in them. And that is something that we see born out every day in our open-source community.

It’s a, it’s a value that we try very much to hold on to. If we do not show deep interest and to us, just to be clear, that means in bringing the use cases and us delivering a solution. If we do not show that interest, what right do we have to expect anyone will show interest in us?

The only way that we can do that is through a misguided belief that tech is a pure meritocracy and we’ve built the best product possible just in a vacuum. We don’t want to believe that we don’t want to rely on that sort of hubris. So instead, we want to engage our users. And what I think is very interesting is we view our open-source product.

Well, as a product, we view our product as a product is what I was about to say. We view it as a product in the same way that a company would view any commercial effort as a product. We treat it as a business, we treat it as if it has revenue, we treat it as if it should have resources allocated to it. This turns out to be a bit of a contrarian, maybe even controversial approach, but it means that we are able to make commitments to it in the same way that every startup makes commitments to its commercial product. And so, what I mean by that is if you look at many commercial open-source companies, you’ll see this intense focus on the commercial product.

And then you’ll see this effectively side project, the open-source side project with a hope that it becomes huge, but projects don’t become huge, except by accident. Products become huge. And so, whereas every entrepreneur can probably recite do things that don’t scale and go off and do that in how they make phone calls to their customers.

You see very few of the same people doing the same in an open-source context where you also need to do things that don’t scale. And an early thing that we did that doesn’t scale at Prefect is we invited our first hundred users of our open-source community into the community. We gave them reasons to come in.

We formed user councils. We held, oh, gosh, I think we had a happy hour as we flew around the country and we met with them in their offices to learn about their use cases. We made this unbelievable effort to get to know these people who we had no commercial relationship with. We just thought that they were the bedrock of the type of open-source community we wanted to start. And we wanted to get to know them, and we’d made this commitment and this effort. The next thing we did that doesn’t scale is as the community grew beyond our ability to go meet every single person, we made a commitment to answer their questions very, very quickly. I think originally, we said 15 minutes is the maximum time a question can sit. I think now, just because of the realities of a 5,000-person Slack community, growing a thousand people a month, I think we’ve, we’ve relaxed that down to 30 minutes now, but the idea is the same. We make this commitment to a completely free community. If you don’t decide to purchase an escalated support contract from Prefect technologies, you get what we would call community support. And we caveat that, we say, but it’s a really good experience because it’s still our entire engineering team, our dedicated support team, in the open, doing their best to deliver solutions. It’s, it’s a good product, but it’s a good product because it doesn’t scale.

And, and our effort therefore is figured out how do we scale it? How do we take it from that first hundred users? I remember speaking with, with Chris White, our, our CTO, as we started to cross, I think it was around 700 or 800 users. And just saying, I don’t know how we’re going to be able to keep this up.

And then here we are, you know, getting closer to 5,000 and we’re still doing the same thing. And it’s, I won’t say it’s easy. I have people on my team would murder me if I suggested it was easy, but it is rewarding, it is time well spent. So, this cycle is a difficult one. This is our path through it.

And it’s worked well.

Anu: Open-source projects and communities optimize for sometimes users and sometimes for contributors. Do you have a sense of what you want to optimize for, or maybe both? How do you organize the community to productively contribute and maybe even co-own what you’re developing as a product?

Jeremiah: It’s very challenging. We do not ever assume we will get a single contribution. And contributions are not necessarily the metric we optimize for. I think that there’s a meme that you’ll hear sometimes about open-source commercial open source, which is, oh, you’re doing that because it’s free R and D or it’s free engineering.

And this couldn’t be farther from the truth. You sometimes get very high-quality submissions and extraordinary functionalities, yes, from someone in the community. But you can’t bank on that. And you really can’t bank on that aligning with your product objectives, that it’s necessarily going to align with the objectives of someone in your community, which may or may not be your product objectives. It’s a horrible thing to bank on. Uh, and we don’t. And so, while we have, of course, it’s, it’s an open-source product, so the opportunity is there to collect these use cases. We focus much more on the network effect of discovering best practices for our own products. Funny thing to say, but because we meet people where their tools are and because we’re a framework and because in our commercial product, we, we by design never receive our customers code or data.

So, we actually can’t find out what people are doing with our tool, unless we have a good relationship with them. So, we focus very much on this network effect and the metric that I am most interested in, in our community, therefore is, the number of times someone who doesn’t work for Prefect helps someone in the community.

That to me is the, is the sure sign that people care sufficiently to assist someone with a tool that delivers a common, a common purpose, a common benefit. As we see contributors, and we do, it’s wonderful to see the growth of contributors, don’t get me wrong, but we are a commercial open-source company, we are paid to produce this product, we don’t try to extract that from our community. And I think it’s a bit of a warning sign when folks do. When people use it, when people open issues and yes, including bug reports, including their frustrations, including those problems, those are the best things that can happen to us, because those are the moments that we actually advance our understanding of our product, of its usage, of, of its shortcomings of its frustrations.

I could tell you right now, probably 200 different ways that people say Prefect created a friction for me on the way to delivering some solutions. Great. I have this list now where we can go through and check it off and make sure that our process is as smooth as possible. Whereas if we, you know, this is the flip side of the distribution model of the open-source distribution, while we can get our software to people in a certain way, we can also solicit their feedback in a very specific way, in a very public way.

And one of the things that we do the most important thing in the community is to make sure it doesn’t evolve into toxicity, and it doesn’t evolve into one of these horrible situations of, you know, one person’s unthanked and this person’s ungrateful. And we have this rule, sort of, above our code of conduct, if you will, that we assume positive intent on the behalf of all participants in our community. If you want to come into, into the community and complain and say, everything is terrible, you’re just, it’s not a great way to get help. If you come to us and say, I’m trying to do X and Prefect, doesn’t do it, and I’m trying to understand why. That’s a great way to get help because we are desperately invested in making sure that our product does everything that it should. And that positivity is contagious. And I think it’s when you don’t actively seek it the community devolves, because it is a network effect.

It is bigger than any person in it and it compounds at the, at the worst rate. So, keeping that as high as possible is just a critical part of this.

Anu: Outside of building a community, you’re running a company and growing at, I don’t know a breakneck speed, seems like. How do you make sure you’re staying on top of the decisions, both in terms of speed and quality for the company, but also for the community? Maybe, I don’t know if you tie them together?

Jeremiah: I wouldn’t say we tie them together explicitly, but we apply very similar frameworks to both. We were very fortunate when we started Prefect. We started the company because people tried to buy a prototype, which meant that the normal goal of a very young company, of can we determine product market fit, in many ways was satisfied.

Now the products that we had at the time, remember it’s a prototype, so we still had to develop that product and assure that it continued to meet that objective, but just this enormous de-risking that just took place at the company’s birth, which is just incredible. And so, what a luxury, so instead we focused on building our company side by side with building this product. And this is where, you know, for, just for example, we have this advisory board, which is very large, and this is a model that we learned about from Keith Krach and Marc Carlson, who are the CEO and CCO of DocuSign most recently, and this is a model they successfully deployed there to scale DocuSign to, you know, the height it is at today and at Ariba before that.

And it’s, and it’s all premised in this idea of building frameworks and avoiding what, in my finance days, we would’ve called pin risk, which is the idea, you know, as an option approaches expiration, especially, you know, just for example, if it’s a binary option, but even if it’s an option that’s near its strike price, you have to really worry.

If it goes a little bit up, you’re going to be in the money and it’s going to convert. And if it goes a little bit down, you’re going to have nothing. And so that’s called pin risk cause you’re getting close to the pin. So, we seek to avoid pin risk in decisions and in people. And I find it insane when startups spend a lot of money to hire a very small number of advisers because the pin risk that they’re taking, the belief that they must have that their problems will align exactly with their advisor’s experience, as well as their advisor’s willingness to help them in a necessarily difficult time, it’s not a very favorable position to put oneself and it’s certainly not a position you would pay to put yourself in.

And so instead, what we’ve done is we’ve tried to build this incredible diversity of opinions. This like constellation of people, some of whom are very obviously related to our business. They have experience in open source and technology and finance and healthcare. And some of whom on the surface looks like they have nothing to do with our business. They work in completely tangential fields or in sports or places that don’t look like they’re exactly the same, but they have deep experience in communication, in product design, in marketing, in outreach and communications, and in this host of other things. And everyone’s sort of joined by some interest in decision-making through data. That’s sort of the common denominator. It’s how we bring everyone together. And I think we have, I think we’re approaching 50 advisors now and we intend to keep growing that and we have these phenomenally incredible dinners, and we haven’t because of COVID, but pre COVID, we have these incredible dinners and just this vibrant conversation. When COVID happened, I got on the phone with 40 different people. I got this constellation of opinions and the important thing is we never need anybody to be right. We only need that opinion to fuel this framework. And then we as a company take on the challenge of running that framework.

And again, this is me talking my risk manager book just for a second, but our objective as a company is never to make the best decision we can. Our objective as a company is to never make a bad decision. And so, the way we think about that is given a hundred options, our framework is designed to eliminate 90 of them not to pick one.

So, we leave 10 options and then we pick one of those 10. And the reason we do that is we have this very sort of iterative fail fast philosophy. So, we’re going to pick one of those 10. It’s almost certainly not going to be exactly what we need, but when we do discover where it falls down, we’re going to come back to the starting line and we’re already going to have only nine options left, instead of having to come back and see all hundred. And obviously I’m sort of oversimplifying, but the result of this is that we can move very quickly, with very high confidence under extremely limited information sets because instead of focusing on picking the best outcome, we just focused on getting rid of the ones that are obviously bad. This can be a little bit of a confusing thing for people to get used to, especially in a startup culture that’s usually characterized by outliers and best decisions. In a very funny way, I think we could joke that it is probable that if you look at Prefect’s history at any given moment, in retrospect, it will always look like we made a slightly suboptimal decision.

And I view that as a win. And that is crazy to me because it means that long-term, we maximize the chance of survival, even if at any one moment we didn’t spend the extra, whatever it would have been to be exactly optimal in that moment. And that’s something that we are not only comfortable with, but that’s also a known consequence of the approach that we are taking. Is this guaranteed to work? Absolutely not. And it takes a lot of effort. It takes a lot of effort. We have to put some rules in place around how this, how this becomes possible. One of them, one of the earliest ones is a rule against something called inertial thinking, which is the idea that no idea can be justified simply by the fact that we are doing it already.

Everything must be constantly reevaluated and that helps us again, avoid bad decisions. Because whatever was the right decision at any given moment, if we could live in a world where we magically pick that, it would be insane for a company changing and growing as fast as us in a world that’s growing and changing, it would be insane to claim that that decision was optimal in the next timeframe as well.

This has been such a core part of how we evolve the company and how we move with confidence even when we don’t really know very much about the world.

Anu: Fascinating. In fact, in my previous role, I used to admire a leader and the worst answer I could give him was, when he asked a question, was this is how always been done.

Could you share an example where you converted or used this framework to make a decision? Just kind great example of how.

Jeremiah: We use this, I mean, we use this for almost everything. It almost seems silly like that I can’t even think of like a major example. One of the goals of this framework is actually never to have to make a major decision.

One of the goals is always to make a series of very small decisions so that we can fail as quickly as possible. So, it’s funny on the one hand, almost everything we’ve ever done falls into this framework. And on the other hand, it’s hard to think of like a single big bang example, but going through COVID actually would be, would be such an example.

I don’t have to tell everybody what an extraordinary period of time that was. I think it’s very easy to say that no business could claim that business was the same as it was 52 weeks ago, as we record this, right? As we went through mid-March and the realities of the pandemic set in you were insane if you just tried to continue with whatever strategy you had in place. It didn’t matter if you were a giant company and changing was hard, or you were a tiny company and resources were scarce.

You could not claim credibly that you were going to operate the same strategy to the same efficacy. Maybe you would do better, maybe you do worse, but it was not going to be the same. And so, this was a moment where certainly nobody knew anything. The future was impossible to predict. And so, we decided to adopt a framework that was kind of terrifyingly draconian.

We made a series of assumptions, almost all of which were wrong. Just to show you how effective this framework is, we decided that we had no customers, nobody was going to spend money on anything. We decided capital markets would be closed for at least 12 months. I’m trying to remember what else, what else we, what else we came up with.

There were six rules. I don’t remember them off the top of my head. Those are that those were the two scariest ones and we prepared for that world and we prepared for it in a way where we would be excited to be wrong, obviously. And of course, we were very wrong, but. But this was a case where I think fundamentally the framework that I’m describing is about the preservation of optionality and reducing the cost of failure.

And this was a case where we didn’t know anything. So, we made, we grounded ourselves in a way of thinking where the more wrong we were, the better the outcome would be. So that again, we weren’t pinned to our own beliefs. We had what I would call right-way risk and, and we also set up frameworks in which we would experiment rapidly to move forward so that we would speak with, you know. That was the point where we open-sourced a big chunk of our stack actually, at the end of March of 2020, we open-sourced a big part of our stack or that had previously been proprietary.

That was one of those decisions was like, whoa, we should have done this from the beginning. But it’s a very, very, very weighty, and difficult decision to make. We made it in that moment because it complied with the new reality that we observed. It was the right way to get our software in the hands of people who were not going to pay for it, in our assumption, but who would be benefited by having it, in our assumption.

And that was the beginning of a really incredible run for our open-source product. But again, it was rooted in a decision framework that was optimized around this objective of reduce the cost of failure, maximize the probability of survival and to iterate as quickly as you can.

Anu: That was a one-way door. Open sourcing the product at the end of March, obviously a tough one to make, and we, coming from Amazon take one-way doors pretty seriously. Do you ever fear walking into a one-way door unintentionally through a series of small decisions?

Jeremiah: That’s a fabulous question. No, I think that generally speaking, one-way doors are well enough marked. When, when you really get to a point that something’s irreversible you, you generally know you may find yourself there slightly by surprise, but, but you rarely cross that threshold by surprise.

You need to, you need to commit to that. And I think the interesting thing there is the scary thing is not so much the door, but obviously the, the one-wayness of it, right? It goes without saying. Open sourcing our product was something, you know, we, we had all these very frustrating, at the time, pushback where people would say things to the effect of, well, I know you have to run a business and that’s why you do this, but we really wish it was open source.

And what we want it to say at the time, for, at the time we had no commercial product, we had no revenue, we were just building this thing. We said, no, no, no, it’s actually not that, there’s nothing to do with a business decision right now, it has to do with, we don’t yet understand whether or not this is a good thing to do, whether or not this is a good decision in line with our product vision, and it is irreversible. And those two things coupled together, led us to take the more conservative approach. To give some context for that, I think that the strategy of open sourcing a product and then hoping your community doesn’t notice as you monetize them is a disaster from a sort of just an antagonistic business kind of standpoint.

We strive to never have antagonistic business models, and that means monetizing our community is sort of contrary to our philosophy. It also means that we can’t release a product and then try to convince people to, you know, upgrade I guess, or I don’t really know how people justify that. The other business model that we hate is releasing an open-source product and then just hosting it because we don’t think our, we don’t think our insight is knowing how to host things, right. Amazon knows how to host things. So, if you want to host something, take our product, take it to Amazon, ask them to host it, pay them to host it. Don’t pay us, pay them. Our job as a startup and as a company is to figure out what our unique insight is, what our edge is, and then turn that into a commercial product.

And so, if our unique insight was just building workflow engines, then to be honest, we might not open source it. Fortunately, that’s not our unique insight. We happen to be really good at it. But our unique insight is that we understand how to use the metadata of workflow engines, or rather of workflows, to deliver a meaningful analytic and insurance product over an entire organization’s workflows.

And so, our commercial offering is that. It’s the manifestation of this insight we have into what you can do with workflow metadata. Whereas our open-source product is this most full-featured workflow engine you’ll ever see. Because that’s at the end of the day, not something we charge for, we don’t extract a value for the fact that we’re good at that. We empower people through that.

Anu: Thank you so much. This has been a fabulous conversation. Any closing words?

Jeremiah: No, just thank you so much for having me on. I enjoy we’re recording this late on a Friday afternoon and you get me at my most rambling, but it’s a very fun space to explore. And we have a lot of hard-won opinions here. Some of which are we acknowledge are a little bit, a little bit contrarian, but have proven their efficacy over the last few years.

Anu: Love it the best way to close a Friday afternoon. Thank you so much.

Jeremiah: Absolutely. Thank you very much.

 

Hope Cochran on the Entrepreneurial Journey – Hers! (Encore)

Going back to the archives to bring forward one of our most popular episodes which is a deep dive on Hope Cochran’s journey to investor, public board member and colleague. She tells the story of being overlooked at her first job which spurred her to take a post in a small European country in her early 20s to take on a huge challenge. That spirit of adventure and ambition set her on the road to entrepreneur, CFO, and founder advocate. Dan Li, who is now a CEO of a new stealth company, Plus, sat down with her to learn her story.

If you like this episode, check out Founded and Funded on the podcast platform of your choice! (Apple, Google, Spotify, Stitcher, Amazon)

Transcript (this is machine driven transcription so expect some typos)

Dan Li: I’m really excited for our interview today to get the inside scoop on one of my mentors here at Madrona, who is an amazingly accomplished operator now turned VC.

Running through a quick bio, Hope Cochran joined the team at Madrona in 2017, after moving back to Seattle from London, where she was CFO of King Digital.

Hope was brought on as CFO of King to help the company go public. And then she ushered the company through their $5.9 billion acquisition by Activision. Before that Hope was also the CFO of Clearwire, Evant and the founder of SkillsVillage. She’s on the board of some public companies as well, like New Relic, MongoDB, and Hasbro.

So basically, she is pretty awesome. But today, we’re not going to spend time talking about awesomeness. We’re going to try to spend some time discussing those moments of truth that got you from here to there.

Recently, Hope and I were on a little field trip to visit a company and we were asked, so what really gets you up in the morning? This is particularly topical today because we’re talking about Hope enjoying getting 4:00 AM calls, because those are the ones that you really need to answer. So, while I was thinking about my answer to this company and about how cool it is to meet with new startups and inspiring founders, Hope cheekily answered something along the lines of, there’s an enormous constellation of people all around me that depend on me every single day.

So that’s definitely how I feel working with you now as well. And specifically, I feel like your ability to deal with rough times while remaining calm is a skill that’s probably been developed over a pretty long time. So today for this interview, given all of the success you’ve had in your career, I thought it’d be really fun to go back in time and talk about some of those moments where everything went wrong and how you went from chaos to success.

Hopefully, that works with you.

Hope Cochran: That would be great. I have a lot of content in that area.

Dan Li: Great.

Okay. One of the things that I think is great these days that you can go up and look up senior executives, LinkedIn profiles, and they’ll just say stuff like CEO, 2015 to 2019. It’s great. It’s like their whole career began when they became CEO a few years ago.

And it’s that’s not how LinkedIn works. And if you check out the CEO of Microsoft, it might look something like that. Anyway, I love that your profile really shows each of these transitions between different experiences and your career beginning at Deloitte and a few years later, starting a company. It’s really great for those of us coming from a professional services background, as well, and seeing that we can one day do something useful. Can you take us back in time a little bit and talk about how an opera singer and music major ended up joining an audit firm?

Hope Cochran: Absolutely. Yeah, that was an interesting choice in my college career was to choose to do a double major both in econ and opera.

And I laugh back to that decision because as I think about that, I really did it because I am by nature cheap. As I embarked on taking music lessons, I could not imagine, not taking music lessons. And if you joined on as a major, you got to take them for free. So, I signed up as a music major and took all of my music classes for free.

And then felt guilty a couple of years in and realized I actually better complete the major. So, I ended up graduating with the econ and the music major. And the only reason why I think this is pertinent is because as I think about my career, I do think the econ major got me interviews and therefore it was impactful in getting my first job. But as I think about my career, it’s those skills that I developed singing that I really feel like I utilize every day. You mentioned that I’m decently good at being calm in chaos, and I’ve been through a lot of chaos. So, I think I’ve developed that skill over time.

But I actually think I learned the basics and fundamentals of that by being on stage, because you have to learn to handle every crazy thing that’s thrown at you. Like it’s just part of the process or it’s part of the plan. So, when I think about the music degree, practice makes perfect, making sure you’re prepared for everything that you do.

Also, when things do go wrong, handling it calmly and working through it, like nothing was wrong. And so those are some of the skills that I really take with me throughout my entire career. And so that was a pivotal part of my journey. And you’re right to point out. I started at an audit firm which, that sounds boring, but you can learn great skills in an audit firm.

You learn how to manage your time. You learn how to manage your career. You learn how to be in lots of different situations. I saw a lot of problems. I got to figure out how to fix them and you get a lot of responsibility at a young age. So, it was actually a great place to start out. One of the things that was unique, in that, is I went to Ljubljana, which is in Slovenia, for a year and took on that challenge to help that country get their accounting principles in place and work with them. And that was a great learning step in my journey to then take back to the United States. One of the things we think in the United States is that the accounting laws are complex and overly thought through. And when you’re in a country where there actually, just at nascent stages and not thought through, you realize how quick they are to be ineffective. And so, I appreciated the complexity of the environment that we’ve created here in the United States.

Dan Li: That’s funny. So, I think a lot of people wonder when’s the right time to make that leap, or they’re already on the other side and they’re wondering if they made the right choice. You’re working in Lithuania and doing, I think some professional opera performance on the side, as well at that time. How does that turn into I’m going to start a company?

Hope Cochran: Yeah. I tend to be a person that tends to run towards a new adventure.

That’s just part of my DNA, so I don’t do things twice very well. And as, I looked at every step of my career, it’s always been something I haven’t done before. And when I started my company Skills Village, I was actually with PeopleSoft at the time. And I had a friend who had a great vision, and I was excited about that vision and leapt into it.

And quite frankly, leapt into it without a lot of forethought. Like we didn’t do a ton of research. We just trusted our gut that we knew that this was an opportunity that no one had filled and that we had the technical and business skills to tackle it. I look back on that with such amazement because we had such naivete, like we just thought we could get it done, which I think is a really important trait to an entrepreneur and that they think they believe in themselves and they believe they can climb every wall.

But I remember raising that first $3 million from a venture capitalist with an ID on a PowerPoint. And I look back on that moment, like, why did he give me that money? Like I didn’t really have much in terms of my background, but somehow, he believed in me as well. One of the moments I think through in starting that company is when you’re negotiating a term sheet, there are a lot of technical terms that you just don’t know unless you’ve learned them.

And I remember having to negotiate real time with him. And I had no idea what preferences were or what different terminologies were in the term sheet. So, I pretended I had to go to the bathroom, and I ran into the restroom and I called my lawyer, and I took copious notes really quickly.

And I went back in there, from the bathroom, and I went in there with all the confidence in the world that I knew exactly how to negotiate this term sheet for the first time. And he was very kind. So, I look back on that moment as I thought I was great, but really the person across the table was fully aware that I didn’t know what I was doing and helped me through that process.

Dan Li: Cool. So, it sounds like you had a great co-founder, you were able to raise some venture money. A couple of quarters after raising the $3 million, were you thinking, oh, this is great, or was it more of a, oh no, what have I done?

Hope Cochran: I remember, um, right after we raised the money, we, the first thing we needed was offices and I had to go figure out how to get an office and how to get desks and how to get chairs.

And so, we went to Costco and Home Depot. And I just remember that moment of, oh my gosh, what am I doing? I am spending someone else’s money, so we can pursue this idea and it is a moment of truth and a moment of fear, but we did believe in our ideas. So, we grew that company from the two of us to a hundred employees.

It was eventually bought by PeopleSoft. And as I think back to that. From the outside, looking in, it all looked like a success and yes, the investors are happy and all of that. There were so many moments in that journey where it should have all fallen apart and fallen apart because of decisions and things I did.

And so that’s an, and I do think that part of your journey is luck. And part of your journey is fortitude and courage of which I think I had both, I think I had luck and I had perseverance and fortitude. I think about things like I had a marketing manager who went to the local ball game and he committed $250,000 of marketing money.

To market Skills Village at that ballpark. And we didn’t have 250,000. I mean we did, but like I had every single dollar planned out and he came back so proud of himself and I was just panicked. And somehow, we had to rework the budget, we had to rework everything because I couldn’t get out of that contract.

He signed it; it was legal. And I had to tell my board, I was embarrassed. I remember another moment where we needed a new office space, and it was the Bay area. And I signed a seven-year lease at astronomical rates, and I didn’t think twice about it. But when it came time to be acquired, it was that lease that was the noose around our neck. Meaning the amount of money that was committed and the company buying us didn’t need that space. That became a material issue in the acquisition that made the acquisition almost fall apart. And so now I look at those leases differently. How did I get out of that mess?

I went to that landlord on my knees. And I begged for him to give me forgiveness and he was kind, and he did, and I don’t know why he did. He had no reason to do that. Wow. But he saved that acquisition. And again, looking from the outside in that acquisition looked positive and everything was fine, but there were so many moments that it shouldn’t have happened.

It also was in 2001, when everything had crashed and the company had asked that was acquiring us, that we pay all of our payables right before the acquisition happened. And then the market crashed, and I was left with no cash. Like why did I agree to pay all my payables before the acquisition happened and leave myself with no cash? I did because I was naive.

And once again, someone was helpful to me and I was lucky, and it all went through. But, I know, and I would say it went through because we did create a great product with great IB. Like ultimately the company had value and that saved at all. But I think of so many moments in time that I made personal mistakes, that really could’ve killed the whole thing.

Dan Li: So, what’s it like that day you wake up and you get the message from PeopleSoft saying that because of this, lease this, we don’t think we can do this deal. Do you call someone, do you make a checklist of things to do next? What’s the process?

Hope Cochran: My method has always been to pursue five avenues at once.

So, I become a bit of a whirling dervish. And I deploy all my resources in all different directions. And I would say that I’ve had to do this on lots of different occasions, whether I’m pursuing raising debt for a large company, I’m going to pursue lots of different avenues. I’m never single thread, anything.

I always have lots of different ways to approach it with the hope that one will come through. The moment of that day, when that happened, I won’t forget it. It’s, we have these moments in our lives that are very memorable, for some people it might be an earthquake or something for me, it’s the day that the lease almost killed my deal.

And yes, I do remember that in all panic. I remember calling lots of advisers reading the legal documents itself. Was there any out I could find? And then ultimately like writing down a message that I could give to my landlord and really going and talking to them and crafting that message really carefully and just hoping I would catch him on a good day. And that’s ultimately what won.

Dan Li: That’s amazing.

Hope Cochran: Yeah.

Dan Li: So, after the startup got acquired by PeopleSoft, instead of sitting back, you went and took another CFO role, cause you wanted to do it again with a company called Evant. How’d you get connected to them. Did you know the team already?

Hope Cochran: I didn’t know the team already. That was a venture capitalist at Kleiner Perkins who reached out to me to come in. And he was really frank about why he was changing out the management team. They had just replaced the CEO and they needed a new CFO. And the company was a ten-year-old startup, meaning that it had been through lots and lots of rounds and recapitalizations, and it had to be reborn.

Basically. And so that’s a very different journey. If you look at my journey and I always say the only consistent theme is a lot of change and a lot of chaos, and that goes in growing and downsizing them. So, I’ve done both sides and that’s what Evant was, and I went into it, eyes open that’s what I would have to do, but I had not done that before.

And when you get in there and you start meeting people and you like them, and you understand how it got to where it is, you gain a lot of sympathy for the process. And I had to look at even the GNA team and realize I had to reduce it by half. I like to be liked. I think we all like to be liked, but that was my job and that was painful.

And it also gave me a different lens on how to grow a company. Meaning growth is fun and good, and you have resources and want to spend it. But if you hire too many people, if your space that you get is too big, it does not lead you down a good path. I tend to know, as a CFO, like crowded offices where everyone’s too busy. Because when you have a crowded office there’s great buzz, people are excited, there’s great energy. And when people are too busy, they don’t have time for politics. So, they don’t worry about their title, or if someone’s doing part of their job. They’re happy for the help. And so, I tend to now approach growth with a different mindset because of the Evant experience.

And yes, I had to make really difficult choices. I think when you have to make those difficult choices about who to keep and who to let go and how to reshape the business, you have to keep in mind that you’re actually helping people’s career. So, look at the talent you have in the organization. They are not being helped by the fact that there’s too many people or that you need to prop up those people that are trying and have talent. And that’s ultimately the benefit of what you’re doing. And just to go back to Skills Village for a moment, one of the things that I did wrong as a young CFO was trying to keep people along for too long. I can coach them; I can train them. When ultimately, if I have a population of 10 people and I have one person that’s not carrying their weight, I’m actually hurting the nine.

So, while I’m avoiding a difficult situation with the one, I’m creating a difficult situation for the nine. So, I have learned in my career to act much faster than I did in those years. And Evant really brought that home to me because I had to make the choices quickly. And when I did, I saw how much healthier the organization was almost right away.

And it was a very painful process, and I would hope to avoid the painful process. But if you have to do it, you are actually benefiting the rest of the organization and yes, you might not be popular, but ultimately, they’re usually grateful.

Dan Li: So, were a lot of the decisions that you had to make at Evant relatively obvious on the key areas, or you had to downsize, or how did you end up coming to all the different decisions that you made there?

Hope Cochran: Yeah, you always think they’re obvious until you start getting to know the situation and then things get complicated because you look, and I guess it is nice to have a little bit of a third-party perspective, because I do think it’s more obvious then, but you can’t then make the changes without really understanding how it came to be.

And, once you understand that you say, oh, this person has this history and this person understands this nuance and that nuance, and it all becomes mucky and hard. And that was clearly the case and you want to be respectful and kind to people as well, so it’s always a very hard process. We did understand that we needed to take the product a different direction, and so that led a lot of the changes, which is always helpful. If you can think in your business, I’m not just downsizing it, but I’m actually refocusing it. I want to get this business objective done, like start with the strategy and figure out how you’re going to get there versus just say, oh, we have to cut costs.

I don’t think that any CFO is ever going to be successful in a, oh, we just have to cut costs, mentality. They really need to think about let’s identify the three or four big objectives this company needs to accomplish. Let’s protect those and make sure that those are shored up and anything that doesn’t directly align with that is what we then need to address in the downsizing.

And that also just enables the message to be a lot better and sets up the company for success.

Dan Li: Makes sense. So then after a lot of that turnaround work was done, what eventually happened to that company?

Hope Cochran: Went through a sales process, which was the intention, and we sold it to another ERP company.

And, in that one, we were just happy that the investors recouped their money because it had been a 10-year journey. But I think, everyone was happy with where it landed.

Dan Li: So now we’re going to get to the really good stuff, billions, and billions of dollars. Apparently Clearwire raised about $9 billion during your tenure.

That’s a lot of money. How do you spend $9 billion?

Hope Cochran: Yeah. So Clearwire was a company that was born out of the premise that someday people would actually use more data over a wireless network than voice. And so that seems to be true today, right? So that was in 2005. And as we look at our usage on our mobile devices, very few of us actually talk on them.

We actually use data. It was a very valid premise. The intention was to take some spectrum that the company owned and make it valuable because it was perfect spectrum for data. Now telecom is an industry that just requires a lot of money. So, in order to make the spectrum valuable, the path to doing that was get it used.

So, in order to get it used, we had to build a network. Building networks are expensive. There’s a reason why there’s only so many big cellular networks in this country today. It’s because it costs billions and billions of dollars to build them. And data networks were even more complex because the towers need to be closer together, so you need more of them. We went back and forth between raising money to build the network, then also raising money to buy more spectrum. So, we basically pulled spectrum together, made it valuable and then built networks on top of it to show its usefulness. And ultimately that company was bought by Sprint for $14 billion.

And is the primary reason, why, or I shouldn’t say the primary reason, but one of the key reasons why the T-Mobile Sprint potential acquisition is being discussed today. Because that particular spectrum is so valuable in regard to being able to roll out these new data networks, specifically 5G.

Dan Li: Got it. And was it quote, unquote obvious in this scenario again, that this would be a bet that played out?

I don’t think that people always had a lot of optimistic views on data versus voice and whether data over the networks was going to be a big thing.

Hope Cochran: I wish more things in business were obvious. I can’t think of anything that’s been obvious. You have to take a leap if it fits all of the right decision criteria.

And I think that is something that we have to think about is we take bets and now on the VC side of the table. How do you decide to invest in a company? You have to be grounded in your own decision process, and remember why you made the decision because we, we try and be analytical, but there’s always two sides to every equation and it’s never obvious.

So no, it wasn’t obvious, but yet all the proof points seem to make sense and seem to indicate that’s where it would lead.

Dan Li: And was there some point, I don’t know, after a billion dollars or $3 billion, where you have a ton of money in the bank, you’ve got customers and contracts, a great team, you think maybe it’s going to be smooth sailing from here?

Hope Cochran: No.

So, we never had billions in the bank. I guess there was like little moments in time when we did, but we would raise several billion every year. And then we would spend that money rolling out a network and we would be getting down to the dribs and drabs and raise another couple billion so we could do it again.

So, it was a constant cycle and that was an eight-year process. And by the end of it, we really were in a situation where we were in the throes of being acquired by multiple different entities. And we had a lot of debt on the balance sheet and if we weren’t acquired, we probably would’ve had to default on that debt.

So, it was a definitely a nail-biting experience, and that’s not uncommon in telecom, I have to say. Telecom is a big game of poker. You have a lot of debt and you basically have to be able to create revenue to then pay off the debt. And in order to do that, build the network. So, it is a high stakes game.

But I had such an amazing crew to work through that with, and I am ever grateful for that team. John Stanton was our leader of the board at that time. Brilliant strategic mind. And so, he led us through that process. So definitely that was such a learning experience for me. And I’ll just say that in all of these situations, whether it’s you’re an operator in a company or a board, the one thing I will say that I have done well is chosen the people around me. Your reputation is never your own. I would love to say that these successes have been mine, but they haven’t. They’ve been the people sitting at the table with me. You never make a decision in a vacuum. You are influenced by all those around you.

And in every situation, I’ve been in, there have been moments that have been very stressful, there have been moments where people’s personal issues have come out, whether it be financial or home life or whatnot. And you really get down to the core of who the individuals are and how they make decisions in that time influences how the company will move forward, how your career will move forward. And I have been so fortunate to be surrounded by high integrity, fabulous people, and all of these situations that I feel like as my failings came out, they were there to catch me. And as their failings came out, I caught them. And I really think that has been a key to my whole journey.

Dan Li: That’s awesome. So, at Clearwire what was that 4:00 AM phone call that corresponds to the landlord or the downsize, or the announcement?

Hope Cochran: There was many, but I remember one specifically and it’s quite technical, but it was the day SoftBank announced that they were buying Sprint.

And the reason why that was important is I was at a big conference and I was speaking all day. I think I had 14 investor calls lined up that day, as well as a big public speech. And the reason why SoftBank was buying Sprint is because, while I’m sure they were excited about the U S telecom, but they also wanted this asset that Clearwire held because Sprint owned a portion of that asset through an ownership percentage of Clearwire. And so, all of the sudden it was exactly 4:00 AM, my phone started ringing off the hook and everyone wanted my opinion on this particular acquisition and our stock I think tripled at the opening. Because everyone felt it had big implications for me and I was in a very public situation with every investor and all eyes on me.

Dan Li: So, you have a day of investor meetings lined up, and these 4:00 AM calls are asking you what’s going to happen.

Hope Cochran: And to be fair, I knew SoftBank, but I didn’t know them all that well. So, I basically spent an hour cramming on all SoftBank related items.

And knowing that any word I said would end up in lawsuits if it was incorrect, so I had to be incredibly accurate with my words. I was on the phone with lawyers all morning so that I wouldn’t miss step. And we went through about three hours’ worth of meetings in the morning and the stock continued to run and we, ultimately made the decisions, the lawyers made the decisions that I needed to leave the building. So, I did leave the building because I was too surrounded by investors and the liability of what was happening with the stock was too strong. So, we got up and walked out and it was like my little moment of rockstar in a little tiny world.

Like no one really cares but we cared. And we walked out and ultimately that was the beginning of what led to SoftBank buying Sprint, and Sprint then buying Clearwire, because SoftBank didn’t need the asset we had. Now that was another year and a half down the road because it took that long, but that was the thing that kickstarted the process.

Dan Li: What a cool story. How did the eventual acquisition play out and then what did you decide after that?

Hope Cochran: How the acquisition played out is a very long and complicated question of which I think we would bore the world with, but it was a very curvy road. It was on and off and there were other players that came in and tried to acquire the entity. Ultimately it was purchased in 2013 in the spring. And, as a CFO, especially when you’re a public company, CFO, it’s pretty common that that’s the end of the public company CFOs journey with that entity.

So that is when I then decided to take a role in London with King Digital, and we moved the family over to London and I was the CFO of King Digital for my next adventure. And, King Digital makes the game Candy Crush, for those who might not know. But many people know Candy Crush. In fact, 500 million people play Candy Crush every month.

Dan Li: And what level are you on?

Hope Cochran: I don’t even know, I’m basically right at the end. They come out with 15 levels every week. So, you have to really stay on it.

Dan Li: There’s like a huge proportion of the user base, that’s on that last level, right?

Hope Cochran: There is, yes. And one of the things that we love to talk about at King is that 50% get there without paying anything.

Dan Li: Wow.

Hope Cochran: I know. I don’t know how they do that. I admit that’s not me.

Dan Li: So, the way I understand the King story, it’s a company that’s doing really well for several years, making tens of millions of dollars and then one day, boom, Candy Crush. Huge phenomenon, like what we’re seeing today with a Fortnight, and just overnight success, everyone’s talking about it, everyone’s ecstatic, we read about it everywhere, everyone’s playing it. Is that what it felt like on the company side?

Hope Cochran: It did. It really did. So, for 10 years and it was the 10 years I wasn’t there, it was making about 60 million in revenue based on smaller games.

And then one of my favorite stories from them was that over Christmas break, they were getting in their daily reports from the network. And they basically didn’t believe the numbers because the numbers were too big. So, they just ignored them. And they came back in January to really do a deep dive, to understand what was happening with their analytics.

And they realized they were accurate, and Candy Crush had taken off. The company went from 60 million in revenue for a year to 2.4 billion in revenue the year after due to Candy Crush. And approximately 800 million of that was cash to the company. Huge cash generated. They basically saw that they had an opportunity here and they wanted to get the company public.

And that’s when I joined on, when I joined on, as the CFO, they had already filed their documents to go public. So, I was coming in when it was already underway and had to get the company ready in about three months to then enter the public markets.

Dan Li: So that’s probably like a slow lethargic process with lots of controls.

What were those three months like?

Hope Cochran: The thing, the first thing I learned and again, I’d put this in the failing’s category, because I probably should’ve learned this before I joined, was that hiring in Europe is not a quick process.

Dan Li: So, actually it wasn’t a quick process.

Hope Cochran: Yeah. It was not a quick process. And I had a very light finance team if we can call it that. So here I was about to take your company public. I really had no team. I had no staff and what I realized in Europe is anyone that takes a job has to give three months of notice to its prior job or six months. And I was taking this company public and three months, so that was not going to work. So, the good news is I had just sold a great company in Seattle, Washington, Clearwire to Sprint. And I basically called everyone that worked for me, and I said, please move to Europe tomorrow and do this with me again. And so, I was very fortunate to have fabulous, talented people who like jumped on planes and came over and together we joined hands and got this company ready for the public markets.

Dan Li: Wow. In those three months, what were some of the things that had like the longest skating times or the toughest to get across the line?

Hope Cochran: Yeah, there were everything from like building the company’s financial models, which they didn’t really, have to figuring out the data analytics because the data analytics had never had any structure to them before, so they had been pulled, differently for every month for the past few years, and I needed consistent data if you’re going to go out publicly. So, I had to rework the data analytics and then, too, we were incorporated in Malta and you can’t bring a Maltese company public in New York. That’s just not going to fly, so I had to reincorporate it into Ireland. And that just takes time.

Dan Li: That’s so cool. This sounds like one of these times we’ve talked about this acronym a few times, FTJ that you use with your kids, and that stands for finish the job. This sounds like one of those times you could have started making FTJ your motto but tell us about that. How’d that come into play?

Hope Cochran: So FTJ is something I learned as a high school camper. So, I’ve been very involved with Young Life, my whole life. And I worked at their camps over the summers, and you get exhausted and tired. And I remember one of my leaders always using this phrase FTJ, which was, you don’t get any credit for something if you do a really good job, but then you actually don’t finish it. And I think this pertains to so much in our careers. Meaning, you could do a ton of research on a topic, but if you don’t produce the document in a professional way, for someone to read, they discount the work that you did. So, you need to spend that extra energy at that moment when you’re tired to complete it in a professional way that you would be proud of.

And that’s where I say FTJ, last night my children were doing laundry and they washed and dried the clothes but didn’t fold them. I don’t give them any credit for doing the laundry. that’s not FTJ, right? Like it, it just pertains to every little moment in life. Yes. Taking King public was clearly a big FTJ moment, but that one was like really big.

I actually think it’s more pertinent on the little everyday things in life where you just get things done and you finish them, and you finish them. In a way that makes you proud that you produced a positive and professional outcome.

Dan Li: That makes sense. Speaking of kids, one of the topics I do want to bring up here is having kids and starting a family.

Fortunately, and unfortunately, a lot of career growth happens at the same time that people are thinking about having kids. How do you generally think about this balance of spending time with your companies, the management teams and the board members versus your kids and your family?

Hope Cochran: I always muse about this.

We have, what, 90 years on this earth, I don’t know what the average life expectancy is. And really 20 of them, are killer, meaning that they’re the 20, when your job is taking off and you’re having your kids, they all happen in your late twenties, thirties, forties, and there’s this crux of everything comes down at you at once.

And so how do you manage through those years? I think number one, recognizing that it doesn’t have to be a straight line, is important. And number two, having a few little rules that can help you get through there. Like I would say in general, yes. I have had a very busy career. I also have three children that I want to parent well and do all the right things by. Probably my social life has not flourished as a result of all of that, meaning I’m not going out at night.

And so, you just make choices, you make choices about where you spend your time. I’m also very big on, I don’t try and strive for this balanced life that people talk about being balanced. I think, I don’t know a single soul that would say, Oh, I feel so balanced today. Whether they have kids or don’t have kids, that’s, what does that even mean?

So, I really look for what I consider an integrated life. Meaning, what do I have to get done today and how am I going to get that done? And it might be that, yesterday I took my fifth grader to look at a new school. And so, from 11 to one, that’s where I was, and I cleared my calendar. So that could happen. That was the priority of that moment. So, as I look at each day, I look at it individually. And how do I prioritize my days such that it is in line with, I want to say my objectives, but the things that are important to me.

Dan Li: So, on this topic of the moments of truth and the 4:00 AM phone calls and the doubt, did you ever have doubts about how you were prioritizing time at work versus time with your family?

Hope Cochran: I think every parent has doubts. It never feels like you can give enough. And that’s just part of the journey. I wish there were a good answer to that. I think you’re always going to doubt. The one thing I will say though, is I do feel that for the times that I was away because I was on work trips or whatnot, my kids know that I am their mother and that I love them. And if there’s something they need, they call me, they don’t call a nanny. They don’t call my husband. They call me like that role as a mother is never removed. And that has been comforting to me over the years. Cause I think when they were little and I didn’t have that perspective, I worried that, they turned to someone else because I wasn’t there when they had a nightmare and, no, that’s never happened.

I am very close to all of my kids and, you never say your journey as a parent is over. So, I don’t know if I’ve done enough, but you have to give yourself a little forgiveness.

Dan Li: Yeah. So, let’s talk a little bit more about what you’re working on today. We spend a bunch of time together at Madrona looking at companies and sometime in the gaming world and the FinTech world. Obviously, you’ve done a lot of stuff in those industries, but these days you’re in the investor seat, advising lots of founders and early-stage companies and company building. And I think the thing that we hear a lot today, and people like to tell potential founders is this, yes, go start a company, dropout of school, leave that job at Microsoft. What’s the worst that can happen? It’ll be a great learning experience, no matter what. Do you agree with that advice?

Hope Cochran: That’s an excellent question. I’ll first say that I love working with young companies and I love joining the entrepreneurs on this journey. I feel like they’re so courageous.

It takes a lot of courage to jump on this train and try and build your own company. So, everyone that I meet with, I walk in with humility and humbleness, and just want to be helpful to them in terms of leaving colleges. I don’t know. I think everyone has to have their own journey, leaving schools or pursuing something.

I do think there is no cookie cutter approach. I think every journey is unique. If I were to have one word of advice for my children. So that’s always where it comes down to the rubber meets the road. I probably would like them to finish school.

Dan Li: And which school is college or high school?

Hope Cochran: I have ambitions for them for college. But would I be open to listening to why they want to take a different fork in the road? Of course. So, I do think that in today’s day and age, there’s lots of ways to approach this. Back to what we were saying earlier, where like the crux of busy-ness happens in these twenties, thirties, and forties. That road doesn’t need to be that straight either. There’s different paths and thing. We need to create a work life that fits different lifestyles and journeys. And this is in that vein.

Dan Li: And going back to FTJ and finishing the job, you’ve been at a bunch of companies where the job has been finished, whether it’s an IPO or an acquisition from this side of the table, what do you see as the most common reason that startups or entrepreneurs end up failing?

Hope Cochran: Clearly, assuming, they have gone on a journey where the product is a good fit. So, we’re going to put that aside cause we’re, you don’t start a company if you don’t think there’s a good place in the market for what you’re building. So, let’s assume that’s happened. The number one reason, I see things fail is people. And what I mean by that is relationships, dynamics. I think the founder dynamic, or the co-founder dynamic is so hard. And people should never underestimate that. I definitely felt that my co-founder and I did really well together, but when you are embarking on a journey to start a company, Life happens.

Meaning are you both at the same financial place where you can put in this, financial resources or take lower salaries? What are your needs at home? Do you need to be home more than your co-founder? All of these things become very stressful and very important to work through. I would also say that just having the ability to emotionally support each other.

So, starting a company is really hard. And I don’t think people understand that unless they’ve done it and being able to be support crew for each other when one is feeling down, and the other one can help each other. I think this relationship is so important as companies are getting off the ground.

Dan Li: Yeah. And you’ve talked about this, the support network and the people and advisors around you that are helping you make decisions, and you have a great network of CFOs that you rely on and organize events for. How do you go about building that if you’re still earlier on in your career or just getting started with your startup?

Hope Cochran: Yeah. I don’t know that I ever had any formula. Like I said, I didn’t have a lot of extra time, so I wasn’t good at going to events or networking. I think it was really just about making sure that the people I was choosing to partner with were people that I wouldn’t mind raising my children. Meaning, I had to really love them and make sure that our values aligned and that the level of integrity was there because you do end up in really difficult, stressful times with these people and you have to be able to ride that journey together.

Dan Li: What’s your least favorite part of the job at Madrona? And then we’ll do most favorite part afterwards.

Hope Cochran: Yes. My least favorite part is really clear. And that is, I always say I was really fortunate, I married my high school sweetheart, and that’s still working out, so I’m good.

Like I haven’t had to break up with people. It’s not a skill that I have or that I’m comfortable with. And I think that reality of venture capital is you meet so many companies. And as I was talking about before, like I find these entrepreneurs so brave and courageous, and I just love their desire to embark on this journey.

And I just hate how many no’s I have to say. And often I’m saying no, not because it’s a bad idea or because I don’t believe in them, but for whatever reason, it doesn’t fit the Madrona structure, or maybe it shouldn’t be backed by VC. It should be backed in a different way. And so, I always find myself like wanting to then help them.

And I get myself completely overscheduled because I ended up helping all these companies, but I’m really awful at breaking up.

Dan Li: And then what’s the, what’s your favorite part of the job? I’m guessing it’s going to be related.

Hope Cochran: My favorite part of the job is finding that company and digging in with them and helping them build something. That’s what I love doing.

Dan Li: Yeah, definitely the best part of this job.

Hope Cochran: Absolutely.

Dan Li: This has been such a fun interview. I love hearing all these stories. So, one last question for you. If you were someone five to 10 years out of school today, interested in the tech and startup world, asking for a friend, what would you do?

Hope Cochran: I would, I, one of the things that my career lent itself to, which I didn’t really contemplate at the beginning, but has really done me in good stead is I’ve gone from tiny companies to big companies, to tiny companies, to big companies. And that actually has been incredibly useful. So, I clearly love starting things and building them, but also seeing how that plays out in a healthy big environment helped me build things in a healthy way. And so, having that perspective of being in a big company, like a Deloitte and Touche, which sounds really boring, but actually I learned great skills and then going to a little startup, and then going into PeopleSoft where it was 5,000 people and it was led in a really effective way.

And then I went and started my own company and I thought, I really like how they did this and I’m going to build it to that. I had a vision of where I was going to go. So, I think getting those different experiences and seeing all different environments is really important. You can learn a lot from a company with a great culture, and you can learn a lot from a company with a bad culture.

You can learn a lot from a great manager, and you can learn even more from a bad manager. Your career is your own. It doesn’t matter if you have a good manager or a bad manager, you’re in a bad culture. A good culture is to take those learnings and then apply them to whatever you’re wanting to build.

Dan Li: That’s awesome. Thanks Hope. Really enjoyed this podcast.

Founded and Funded: Knock’s Fundraising Journey With Demetri Themelis

In this episode of Founded and Funded, Madrona Managing Director, Scott Jacobson, and co-founder and CEO of Knock, Demetri Themelis, team up to talk about Knock’s fundraising journey. Deciding when to raise and who to raise capital from is a big decision for any startup founder and company. Listen in as Demetri and Scott talk about Knock’s decision to wait to raise venture capital, their early days of establishing product and market fit and more. And, then Demetri turns the tables and asks Scott about his thoughts on how founders approach term sheets and fundraising.


Transcript (this is machine driven transcription so expect some typos)

Erika Shaffer: Welcome to Founded and Funded. My name is Erika Shaffer with Madrona Venture Group. Deciding when to raise and who you want to raise from is a big decision for founders. In this conversation with Demetri Themelis, the co-founder and CEO of Knock, and Scott Jacobson, Managing Director at Madrona, they talk about Knock’s decision to wait to raise venture capital.

Madrona led Knock’s first institutional round, which was their Series A in 2019. But this is well after the company had established their market and product, and Demetri talks about those early days.

Knock raised a Series B financing of 20 million in early 2021. Knock had originally planned to raise their B round early in 2020 and the company had a lot of interest and term sheets on the table. Scott and Demetri talk about navigating through 2020 and how the raise actually ended up coming together.

And then Demetri turns the tables, just a bit, and asks Scott about the approaches that founders take when looking for financing from venture investors and his thoughts on their approaches. Knock is a CRM for multifamily managers. In regular language, that means large apartment buildings that are often owned by ownership groups and professionally managed.

Knock, like many companies, scaled back right at the beginning of COVID 19. But as people were stuck in their apartments, the communication between tenant and manager became increasingly important. An area that Knock excelled. And Knock had their best year ever.

We pick it up with Scott and Demetri.

Scott Jacobson: All right, Demetri, great to see you. Thank you for spending time with us today. Yeah. I know we’ve got a lot of ground to cover. Why don’t we just start with the very beginning of the origin story. Tell us a little bit about how you and Tom got started with Knock.

Demetri Themelis: Good. Thanks for having me, Scott. Yeah, the origin story of Knock. Myself and co-founder, Tom Petri, we’re both graduates from University of Washington. We graduated with finance degrees in the middle of a financial crisis. So really prescient on our parts. I think that both of us, we’d been friends at University of Washington and colleagues at a big Swiss bank, UBS, and became really fast friends. And the kind of global economic conditions at the time, a career in banking didn’t seem like it had a lot of much of a future. And so, we’d constantly talk about striking out on our own and starting a business together. And five years into our careers we both felt comfortable taking the plunge and quit our jobs to found a company. The pain point that led to the idea, that led to the company, that is now Knock was started from our experience as renters. So, we had both been renters in really competitive markets around the country, in Seattle, in New York City, San Francisco, and our experiences as renters was like, like most people, rather painful.

We felt like the customer journey for a renter looking for a new apartment, communicating with landlords and property managers, moving in, and ultimately continuing that relationship with your landlord or property manager as a resident, there was really nothing about that entire customer journey that was modern or positive in any way. And so, we thought that there were many opportunities to modernize that customer experience. And that was really the pain point that got us started.

Scott Jacobson: [00:03:58] All right. Great. So, you decided you, you found a pain point, you started bringing on landlords as customers. You build some software to help them manage that process, started charging them money, and then ultimately decided to raise capital from what we would call, in the business, strategic investors, in this case, actually your customers. And the seed capital came from big multifamily owners. Tell us about how you made that decision. If you had it to do over again, would you make the same decision? Tell us about that journey.

Demetri Themelis: [00:04:30] Yeah very early on, when we started meeting with property management companies and showing them demos of software that we wanted to build, we hadn’t even written a line, lines of code yet, but we’d ask for meetings, ask for feedback and we’d show them mock-ups and design ideas. And after 20 or 30 or 40 of those meetings, our mock-ups were getting pretty well-developed and they were, they looked like real, fully developed products, even though we hadn’t written any code.

And so impressive that by like the 20th or 30th meeting, a lot of those property management companies asked us, hey, this is pretty cool, how much does it cost? Or, hey, this is pretty cool, who’s funding you guys? And so those conversations started pretty organically. And I don’t think it was with a whole lot of intention at the time, other than well, gee if you’re a potential customer and you want to invest in us that, that sounds like pretty good alignment.

And just so happens that real estate owners happen to be pretty deep pocketed and often times are involved in making angel investments themselves.

And so, I think it was a pretty good fit.

Scott Jacobson: And looking back on that, was it all goodness, was there anything you’d, hadn’t expected by having your customers or investors that, that if you know somebody who’s listening to this might want to think twice about?

Demetri Themelis: There’s some pretty funny stories about people who ignored me for my meeting requests like 13, 14 times until I finally showed up at their office with a six pack of beer. And I said, I’m not leaving until, you take a meeting and by the time we got halfway through the beers that you are asking if they could invest in the business.

But no, generally speaking, it’s been great. I think having customers as investors is a tremendous benefit and I think maybe the caveat is that we didn’t have one dominating investor who was totally funding our business.

And they also were our biggest customer and therefore con controlling our roadmap or trying to control our destiny. In this case, the customers that invested were, several individuals that were made up a portion of our investors. And so, they, collectively, they were, a big chunk of our seed capital, but none of them individually were, in a, in any position to try to, with intention or without, try to dominate our roadmap or how we were building the business.

They were really there to help.

Scott Jacobson Got it. So, you built a pretty compelling, call it single digit millions of dollars, ARR business, on the back of investments by strategics and customers and had a really good thing going. Why did you decide to raise venture? Why did you decide to veer on your financing strategy?

Demetri Themelis: Yeah, Tom and I were both very apprehensive to go to the venture capital community to raise money early on. I think we both, whether we’re right or wrong, this, it was our first time founding a business, but our preconceived notion at the time was that venture capitalists, they’re all about growth. And so, from the moment that you take their money, it’s going to be, are you making my money? How is my return looking? How’s my return profile looking? And I think we were pretty nervous early on that until we felt really comfortable that we had great product market fit, that we wanted to make sure that our investors were going to be patient with us while we figured out product market fit. And so, once we got to a point as a business where we felt that we had achieved product market fit, then our goal was to grow as fast as possible.

And so, we went to the source of capital where our idea of venture capital was that you would want us to grow as fast as possible. And so, we wanted to make sure that like our goals at the time we raised venture capital aligned with our ideas of what a venture capital investor would bring to the table.

And so that’s why we waited as long as we did to approach the venture community. But we were actively trying to stay off the radar of the venture community early on.

Scott Jacobson That’s a, that’s probably good counsel. Now that you’re on the other side of that, what preconceived notions did you have that or that have been born out? And what did you think that maybe you’d have a different opinion about sitting here today?

Demetri Themelis: While we work with Madrona and here, we are in Madrona’s founded in funded podcast, but not to blow too much smoke, but it’s been an awesome journey. And I feel like any horror stories or ideas that you have about venture, like kind of the greedy venture capital partner, coming in and changing the way you run your business. Like we’ve experienced nothing of the sorts, just like 110% support from everyone in the Madrona family. And I can’t really think of any facet of our business that hasn’t been positively impacted by Madrona’s participation in our business.

And when you guys led our Series A and joined our board, we didn’t know how to run a board meeting and we didn’t know how to behave as a portfolio company. And so, everything was new for us, but it’s really just been an awesome experience. So, I don’t know, maybe we just got like really spoiled and this is how it every Founder or portfolio company relationship is like with their venture partner. But I guess like any nervousness that we had, that was definitely, quickly removed and that preconceived notion that our interests wouldn’t be aligned, was quickly shattered, and replaced with, these guys are truly our partners and are wanting to help in every way, in any way they can.

Scott Jacobson: Yeah, that’s great to hear. I appreciate the that you feel that way. And we do the same, I think it’s interesting as an investor and, and maybe I’ll make it specific to Knock. I think it’s fair to say that we all are interested in building really fast growing and great businesses. And rolling up our sleeves and helping each other, figure out how to do that. And ultimately the way to have the biggest impact is to go build a really big business. And I know that you and Tom have that ambition and are well on your way to do that.

I remember when we sat down, a couple quarters in, the question I asked you is what are those limiters to growth? If we wanted to grow at 3X or 4X or whatever it is, like what are the, as an investor, you never understand the business nearly as well as the operators, the people in the seats do.

And what you’re really trying to understand is what are those things? And if there are natural limiters and those are just the, the pace at which a company’s going to grow, then that’s the answer. But if there’s roadblocks or things you can get out of the way that can enable that kind of growth, why wouldn’t we all want to do that? But to do it in a way where the wheels don’t come off. And I remember in some of the early conversations you and I had, that was really what I was trying to get my head around is, when you’ve got great product market fit, and I should mention, when we did diligence in the process of making an investment in Knock, customers love the products, it’s a great product, in fact, I’ve shared this with you. Several customers said they’d pay 2X or 3X, what you were charging them, which we love to hear as investors.

But when you have great product market fit, that is the question, right? Which is, what do we need to unlock as a business to get to a much broader segment of the market, not just to build enterprise value, but because you can have real impact on customers. And I think that’s been a fun journey for us and it’s something we continue to ask each other and try to figure out what are those impediments that we can remove and, or investments we can make to increase that philosophy.

Demetri Themelis: Now that we’re talking about it, one other story that I remember from the weeks leading up to Madrona’s investment in Knock was we were getting to know each other and I can’t remember if it was at your office or at a, at our office, but Tom and I had a question that we were debating whether or not we should ask you.

And the question that we were debating was how would Madrona feel if after six months we decided we wanted to sell the company? And, our debate was well, does that send a sign of like weak, weakness or that these guys aren’t committed to building a really big business and like taking a path, to some, big IPO someday.

And is that a signal that we want to share with a potential investor who’s considering investing in our business? And ultimately, we decided that we did want to ask the question because we wanted to see how you guys thought about that. And I don’t know if you remember Scott, but your answer to the question was like, we’ve invested in a lot of companies and sometimes the founders have decided to sell their businesses much earlier than we think they could or should have in order to maximize value. But ultimately, we would never want to get in the way and try to block a transaction because often times, even if we felt like they left money on the table, or there was growth that was, not realized. But a lot of times those founders, they start other businesses.

And then because we have such a positive relationship with them, or didn’t create contention, we’ve ended up invested in their second businesses and then those have become, the great success of the next fund or the next story. And I just remember that was something that was funny.

Like even, it’s funny thinking about it now that we were even nervous kind of asking those kinds of questions, because we weren’t sure what kind of signal that would send. And that, the answer was so like obviously supportive of us as founders in our business is just funny to think about.

Scott Jacobson: Yeah, I probably said it was okay to for six years, maybe would be okay, but not, to maybe not six months, but I definitely, I do think that is, the best entrepreneurs you ended up working with two, three, four times. And. Yeah, the first one might be a devil, but that gives everybody the opportunity to go for the home run the next time, for sure.

All right. Let’s get back to, let’s get back to business. So, you raised the venture round, the venture capitalists aren’t as evil as you thought they might be. I think you tripled the business or roughly that in, the sort of first go round that we had together, great product great market fit, and it was about time raise capital. And this was in see the early kind of I think you came in actually in and pitched Madrona the update December of 19, 2019. And then in January we set out to raise a B round and maybe just give us kind of the high level on that. Obviously, nobody knew we were three months from a global pandemic talk a little bit about the series B fundraise journey.

Demetri Themelis: yeah. It started out, fantastic. I think we had, we had a great year of growth behind us. Like a record year of growth behind us, was the first time we were raising a round a financing with a venture partner already invested and already on our side with a strong board member.

And starting the process we were in as strong of a position as I think a company could possibly be, all of our SAAS metrics were in great shape and we were getting great feedback on our deck and our story, so we were really excited, to, to raise money again and put together a, an awesome growth round.

I remember in the middle of the, in the middle of the process, we were taking our time and, meeting with lots of different firms and we were flying to Los Angeles and flying to San Francisco and meeting with all kinds of different companies and sharing our story and gathering feedback and ultimately, several term sheets. And coronavirus started to unfold, and it was really interesting. I was giving an update to one of our angel investors, who’s a really successful Seattle entrepreneur and angel investor, John Keister. And I remember it was, I remember I was in a phone booth and talking to him and he said get your round done quickly because you know, Corona virus and I, he goes election year and coronavirus. And I remember when I got off the phone with him laughing thinking, I said, Hey Tom, I just got off the phone with John. And he said, we should get this run done quickly because of coronavirus. And we had a laugh about it thinking like, okay.

Meanwhile we’re getting so much interest in our business and as it turned out, John was right. No, we, we certainly couldn’t have predicted the impact that COVID would have on, on the capital markets and, within a matter of weeks, the public markets totally deteriorated and shortly thereafter, the private markets totally deteriorated.

And we had to really alter strategy and instead of chasing a really big round, when the venture markets and the valuations just really weren’t as strong, we ended up totally changing tact and doing our B led by Madrona, an inside led round.

And we changed our operating plan to really use that capital to operate and, buy time and put as much space between where, where we could be in a, in the pandemic and approach the capital markets again, when things were more normal for a bigger growth round.

And so, it really was an interesting time to raise money. And I think the two big lessons for me are there’s that school of thought that says, raise money when you can, not when you have to, and I think that was definitely evidence for that school of thought being correct.

I think the second thing is just the importance of who’s on your cap table and the strength of the partner and their reputation. And in our case, just like you guys didn’t even hesitate, and you said, hey, like the markets are changing. No, we’re not sure about what path we want to take with fundraising.

And our business was doing fantastic. Like we were having a record quarter and ultimately, COVID, I think really validated our business. But it was awesome to just see the support that came through from you guys who have been through many ups and downs and it was just unwavering.

So those two old, old school adages are raising money when you cannot, when you have to and make sure the people that you’re investing, are going to ride out any storm with you. Like both of those were really validated last year.

Scott Jacobson: I think as an investor, just to, to take the other side, when you’re looking at a business from the outside and, there’s a shock to the system, and maybe you have a public portfolio, maybe that’s way down.

And even though you’re hoping that this is a counter cyclical business that should perform well, it’s never been tested. And I really liked these founders, but I don’t really know them. That’s that is, I can understand, how, sometimes fear overcomes greed in the context of that environment.

But as a board member, who’s, gets the opportunity to see the ins and outs of the business. Every day, you have an information asymmetry, you have an information advantage relative to the investor because you do know the founders, you do know the management team, you know how they handle adversity.

You have a trust-based relationship, and you understand the ins and outs of the business, or at least the best you can as an investor. And, I think that, at least in this case, that gave me and my partners a lot of confidence that we wanted to double down, independent of the capital markets, but also to help try to figure out how to navigate, right? Because on the one hand Knock is a product that helps multifamily with occupancy, and there’s nothing more important than occupancy in the context of potential vacancies that happened in, in dislocated markets, but also, it’s a CRM product that helps building owners talk to tenants.

And, when you’re locked in your, or you’re not going out much, that’s actually a really important product. And we had a lot of confidence in you, but also felt gosh, we have an information advantage sitting on the inside of here and it’s just the right thing to do.

I appreciate the, we were there for you, but I think we also have information asymmetry that made it an easy decision for us. So, let’s talk about, what it was like navigating not necessarily from a, so you raised a small round, then you get intended as you mentioned.

And, we had a growth plan as a business that was more aligned, the size of that raise versus a bigger raise. But why don’t you just talk a little bit about navigating the company in a completely remote environment, but the pandemic, navigating with customers, that w what’s the last 12 months been like in that sense?

Demetri Themelis: Yeah, I think talk about looking at it from two perspective. One from like the company’s perspective and operating a business in the pandemic. And then the second from our customers and our product and how we managed things that way, in the market that we serve. To the first, coronavirus it was a big curve ball, of course, for everybody, I think, for us, I think it was the first real adversity that we’d faced as a company, not to say that we hadn’t been through all kinds of growing pains and challenges and, all the usual things that I think a company struggles to find product market fit and start to achieve early scale.

But it was really the first true adversity. And as we did the prudent thing of changing our operating plan from totally growth oriented to more of an efficiency-oriented path, and operating like, optimizing for operating efficiencies, one thing that was really interesting to me, and I’m still thinking a lot about is the, the cultural change that, that, had to the organization. Where when you hire a group of people that are joining a company and all you’re talking about is, growth, and now, you’re in a pandemic and you’re telling everybody, man, your battle stations, we’re very fortunate, things are going well for us and all the signals are positive, but we don’t know what the future looks like.

So, we’re going to be more cautious in how we invest and what kind of culture that is to work for and recruit in, what that kind of feels like in an organization. And so, I think overall, our team responded really well and that’s probably one of the things I’m most proud of over the last 12 months is that we were able to shift our culture from, myopically focused on growth to total focus on efficiency and not to say that those wheels didn’t come with challenges, but we responded really well.

And ultimately, put up a best year ever for us. So, I’m super proud of our team the way we changed, but I think it really was a reminder of how the culture and how you describe what your company is focused on and what your goals are impacts the overall working environment.

And when that changes, not every one of your employees is going to be up for that kind of that switch. And so that’s something that was really interesting.

Scott Jacobson: I was going to just chime in about the growth versus efficiency and it’s I think there’s a lot of companies out there, for whom growth is a mantra and they don’t think about things like unit economics, or how long does it take to payback customer, lifetime value of that customer?

And that’s not the case here. You can be in growth mode with a fundamentally sound business with really great unit economics and make aggressive, growth investments, but also see a good return on those investments. And when you have a fundamentally good business and then you hit some headwinds or at least you hit some uncertainty choppiness in the water and say, hey, let’s pull back.

But it’s easier to pull back when the core is strong, then when, than when it was growth to hope to get at some point in the future to a reasonable unit economic model. And so, I think that an important element of your business. I do also think to your point, which I loved about the mindset shift and whether people can make the transition or not.

There’s also the challenge of making the transition back to, hey, let’s go be aggressive, right? Because you’re in aggressive growth mode, you’ve got a great product, you’ve got a great business, you get smacked in the face, and you say, hey, hunker down. And I think resilient, not just founders, but teams, early-stage company teams are actually pretty good at that. But then, once you slam on the brakes or even, just pump the brakes, deciding that you want to push the accelerator hard, it’s not always a natural kind of thing, but I think maybe now’s a good time to talk about the next fundraise as like at least an external signal that, hey, we’re ready to put our foot on the gas.

Demetri Themelis: Yeah. So, as I’d mentioned, we ended up putting together, through it all a best year ever. We had known that like multifamily in general, it’s, long-term housing, it’s a shelter, it’s a basic human need. We expected that the category would hold up pretty well compared to retail or office.

When you have hundreds of people living in an apartment building, it’s high density, living area. There’s a lot of things you need to manage, but you can’t just shut it down like an office. This is where people live. And so, we knew our customers were going to have to continue to operate and stay open through the pandemic.

And I’m really proud that we were able to support like all the changes that they needed to make and help them adapt to operate in that environment. It was great. And the result of that was, as I mentioned, like we think we really validated our value to our customers and, that was rewarded with what are our best year ever in, in every way from a growth standpoint.

And so, as we started, as we were finishing the year, the 20-year 2020, and we started to do our forward-looking planning and budgeting process. And we were starting from a blank slate and thinking about the future, we know all of our signs and signals from our business and have been very positive.

And the markets had recovered tremendously probably faster than, than anybody expected. And we had the idea in our head that, our story hasn’t changed, our results have been strong, we don’t need to raise capital right now, but we also know that it’s sometimes it’s a good idea to raise money, even when you don’t need it.

So, let’s go out and raise a raise a round. And that was the thinking that got us into the mindset of that we’d even want to raise a round right now, when we still had a fair amount of capital from the series B that we’d closed earlier in the year.

Scott Jacobson: So, if I remember right, this is late December, you always have this consideration as a board and as a management team, when you go do a fundraise, hey, we can go do the traditional, let’s go talk to 15, 20 plus investors.

Or you can do a more targeted raise. And I think in our case because we had narrowed it down or whittled it down to a relatively small list, when we’re going to have externally led financing back in the beginning of the year, how did you decide that was the right thing for the business, how’d, you narrow in on ultimately who you decided to bring in as a new lead?

Demetri Themelis: So, a couple of motivating factors for that approach. As you said, in the past, we’ve, and I think it’s the right approach most of the time, is to cast a wide net and talked to a ton of people and make sure you find the best possible fit and have as much data points as possible into making sure you’re going to get the best financing deal as possible.

In this case we changed that approach and we went for more of a targeted approach and there were two, two primary drivers for that. Number one, as we talked about, it was, not 12 months since we had gone through that process and we’d gotten pretty deep with a number of folks that we felt like we had a really great chemistry with and possess some really great strategic qualities as potential investors in the business.

And number two was, come to find out, that fundraising is, it’s a pain in the ass. It’s a full-time job for not just, like the founders, but for the finance team and for a lot of people. And it’s fun to tell people about your business and I like selling and I like telling our story and there’s part of fundraising that’s pretty fun. But it’s also a full-time job. And right now, like I want to spend all my time with our customers and our team and growing our business and keeping all of our energy on keeping and building our momentum there. And we opted for the kind of targeted approach as opposed to marketing, starting with a big list and marketing that, and whittling our way down.

And we went to a few folks that we got really deep within the last round, who we really liked, and said to them, hey, we’re we don’t need to raise money right now, but we want to. And if you have a pretty good understanding of our business from the last time that we spoke.

So, if you’re interested in getting ahead of the crowd, cause we’re going to raise money. And if we do, it’s going to get competitive. If you’re interested in getting ahead of the crowd, here’s what we, here’s what we’ll need to make a deal work and offered that to a few people that we really liked.

And we were very fortunate. We had a lot of interest and ultimately got a deal done with the I kind of the ideal partner for our next round.

Scott Jacobson Yeah, it’s in the, on the other side of that table, it’s giving somebody a preemptive opportunity, and sometimes investors will try to create preemptive opportunities for themselves. And sometimes they can be invited to create preemptive opportunities, which I think you did a nice job of creating for the company.

And as you said, sometimes minimizing the time you spend raising capital, even if you might raise it at a slightly lower price than if you did a big process, and you save yourself all that time and energy and effort that you can pour into the business, which probably is the enterprise value maximizing thing to do sometimes.

Demetri Themelis: One question, Scott, I think a lot of founders have, and we certainly have had in, in rounds in the past was, should the company tell investors what terms you want the financing to be at? Or should you let the investors tell you what they think your business is valued at? And I’m, I’m curious, I think a lot of times in the past when we’ve started a big process and a big round, we’ve talked to lots of firms and waited for term sheets to appear to let the market tell us what our company’s worth, for that, at that particular point in time. In the more targeted approach, going to investors and saying, look like this is exactly what we’re going to need in order to make a deal work.

We did that was a bit different for us from putting your investor hat on, like, how do you feel about companies coming to you with a target valuation in mind and letting you know this is the, this is what the deal, this is what the deal needs to look like in order to work versus waiting for you to make the first move on valuing the company.

Scott Jacobson: Yeah. I think it’s an effect. I think it can be an effective tactic in a buy it now context. If you say, if you come to an investor and you say, listen, we’re only talking to you or we’re talking to only a few people, which hopefully is the truth. And we have a valuation in mind and we’re not going to go do a broader market check, if you’re, if you can meet the buy it now price. You’re, what you’re saying is, hey, I’m willing to trade price discovery, right? Because I can go out to the market and I can find out that all the people think the company’s worth a lot more than the number I have in mind, or I could find out that it’s less.

But I’m willing to trade that the value of that price discovery, in order, in exchange for simplicity, and I already liked you and all that. And I think that’s a perfectly valid strategy. The, the downside or the potential risks of that strategy is if you’re way off base with your expectation, that may make people less excited about, as opposed to, instead of hurting your feelings and saying, gosh, you’ve got, unrealistic expectations.

I might just say, hey, listen, we don’t need to be preemptive, we’ll be happy to jump in when you run the full process or something like that. And yeah, there’s a downside risk just around if that price is too high, and how somebody might think about that.

But I think it’s relatively low risk. I think the bigger question for the entrepreneur is how much one, do you have conviction around it and investors such that you would give them a buy it now price, like it’s hey, if this investor were in, this is the right amount of dilution for us, it’s the right amount of capital we can take, and we’d love to have them round the table. To me, then that’s a relatively easy decision. But you’re giving up the opportunity to meet other investors you might like more, or might have more chemistry with, or at a higher price. And so, as an investor, I’ve got no problem with it. I always ask entrepreneurs if they do have valuation expectations or what their valuation expectations are, because I don’t think either of us wants to spend a whole lot of time getting to know each other, doing diligence process, et cetera, if we have very different views on, on, on price. I think it can work anyway. I, in, in any transaction, it’s worth whatever somebody is willing to pay for it. When you sell your house, you don’t put it up for auction, you have a list price. That’s okay. I think it’s fine for entrepreneurs to tell, venture capitalists, and others, this is what I think the business is worth. The same could be asked about, M&A transactions, do you say, Hey, this is the price we want, or do you say you tell me what you think it’s worth and there’s validity to both approaches.

Demetri Themelis: Yeah, I think that makes me think of another, another question, a lot of founders think over is, you know what should I be shooting for? The highest valuation possible or is, is that the important thing too, is that the important metric to be optimizing for in a fundraise?

And I think it’s so interesting how many founders seek to find, that, get the highest valuation possible in a financing and try to minimize dilution, as a result. But one great piece of advice that we had early on was to always be thinking one round ahead. And I think that’s been really helpful for myself and Tom, as founders, as we’ve navigated financings, and to think about, not to think just about the round that you’re trying to get done, but the round ahead, and ultimately your valuation and a financing is it’s just a paper mark.

It’s not your exit valuation, the one that really matters. And if you train yourself to start to think one round ahead, that’s been really helpful for us to, because you’re not getting so caught up on necessarily getting your highest valuation possible, but one that’s truly in a, there is a market, there is a range you want it that’s fair.

And you want the investor that’s joining to help, you want them to be feeling really positive, incentivized, to help add value from the mark that they’re investing in. And anyways, it’s just another thing I feel like a lot of founders don’t always think about is that round ahead mentality.

Scott Jacobson: Yeah. I think that’s good counsel. Valuation, as you described it, definitely is a vanity metric in some measure, although it is it is an estimation of other, people’s either view of where they think you are today or where you can be in the future. And so, there’s some good, there’s things to feel good about when you get a good valuation.

Yeah, my, my view on it is the capital markets are what they are and in some cases the valuations will be higher, and multiples will expand, and it’ll get, a higher valuation. You might get other cases and somewhat independent of whether valuations are what you would consider to be reasonable or not.

If you have the mentality of every dollar demands a return, and, if you got $30 million in the bank at a $300-pre because the valuations are extremely favorable to the founders, then you treat that $30 million like it’s the last round you’re going to get. And you grow into that valuation and you make sure that you spend those dollars wisely.

So, I certainly don’t begrudge founders of the capital markets and, those are going to rise and they’re going to fall. But I agree with your point that, valuation is one of many inputs that you should think about when you’re deciding, ultimately, who to take a term sheet from. And I’ve seen many founders, you guys certainly fall into this category, where, you know, the highest price, wasn’t the one that won, and, within reason, because there’s lots of other important things when you’re talking about building a company over the long term, so I agree with that.

Why don’t we talk about the future for Knock? So, you’ve got, you had a good balance sheet before you decided to raise this incremental round of capital, you raised another $20 million. That’s a great place to be as a business. How do you think about this next vector of growth for the business?

How are you thinking about the go forward?

Demetri Themelis: Yeah, definitely. There’s two really cleared growth vectors for us. So, we, again, we sell our core product today as a CRM and we sell it into the multifamily real estate market. And so, for those of you that aren’t familiar with the market, there’s, let’s just say about 20 million apartment units out there in the United States that we’re selling to. And of those 20 million apartment units that could use a CRM, we’re currently servicing about 1.5 million of those apartment units. And so, Knock can grow by adding more apartment units to our platform. So, when we think about growth, we want to bring in new management companies and ownership groups. And those management companies and ownership groups have portfolios of properties and those properties, each have some number of units. And so, as we bring on units, more units that use our platform, our revenue grows as a result. And so that’s something that we’re always focusing on growing fast.

The other really exciting thing is, if you think about the assets that we’re serving themselves, on a large apartment community, it’s really like a city. You’ve got, 200 or 300 homes stacked on top of each other. There is an awful lot, there’s an awful lot of complexity in making that city run and keeping the lights on so to speak. And so, there’s an awful lot of technology that’s used in order to help manage that complexity and all of those different various operations.

And so, every apartment building out there. And you don’t think of them as businesses, but they are businesses and renters are their customers and they have to successfully attract renters, convert them, and retain them.

And operating that business, there’s just a lot to do. And there’s a lot of technology used to help make their operations as efficient as possible. Our belief is that there’s all kinds of other interesting technologies that kind of sit adjacent to a CRM that we plan to bring to market and build out what we call the, an intelligent front office.

Maybe a simpler way to think about that is like the tech stack within, for our customers. They really, they’ve not there, there really isn’t a, like a dominating top of the funnel tech stack like you might see in other businesses, so we want to really build that out for our business.

So, to back up again, there’s two big growth vectors for us. There’s, adding more units, but then there’s adding more modules and increasing the price per unit that we sell to our customers. So, I hope that provides a little bit of context for anybody on just how we think about growth.

Scott Jacobson: Demetri, thanks for spending time with us today. It’s really fun to relive some of the old stories and to hear about how you’ve thought about fundraising and company building. And just say, I wanted to say how much I’ve enjoyed the journey thus far and looking ahead.

Demetri Themelis: Thank you very much for having me Scott and the feelings totally mutual. Love working with you guys. And I’m very happy that they say there’s a lot of money out there and it’s all green, but I disagree, it’s like having the money from the right partners is really everything.

And we feel very fortunate that we landed with Madrona as our partner for this journey. And definitely looking forward to the next chapter and those after that. So, thank you.

Erika Shaffer: Thanks for joining us for Founded and Funded. If you liked this podcast, please subscribe. And share it with your friends.

Founded and Funded – Building Companies on Open Source with Joe Beda

In this episode, we team with Madrona Partner, Anu Sharma who hosts her own podcast, Traction, as she talks to the founder of former Madrona portfolio company Heptio, Joe Beda. Joe is also more well known as one of the creators of Google Compute engine and Kubernetes. He and another Kubernetes creator Craig McLuckie formed Heptio – a company Madrona backed at day one – to help enterprises adopt Kubernetes. VMWare purchased the company and Joe is now ‘doing cloud native stuff’ at VMWare as his linked in reflects. Joe is a thought leader in so many ways and in this frank conversation with Anu, who brings her own extensive experience at AWS to the table, he talks about open source, open core, open extensibility and how startups should think about building companies around, attached to or based on open source software – and their communities. Turns out this has more to do with ordering a hamburger during these COVID times than you may imagine.

Transcript (this is machine driven transcription so expect some typos)

Anu Sharma: Joe, it’s great to have you on the show. Welcome

Joe Beda: I’m glad to join you.

Anu Sharma: Joe. Open source means different things to different people. What does it mean to you?

Joe Beda: You know, I think open source is fundamentally a positive sum game, and I think this is what’s so great about our industry in general is that it’s really one of the imaginations of how can we have folks come together and do something that wasn’t possible before? And I think open source is really fascinating in my point of view, because it gets a lot of folks that care about something that are coming from different directions, with different expectations and different needs.

They find common cause and create something that wouldn’t have otherwise been created. And so that idea of like I bring something, you bring something, somebody else brings something and we create something that’s greater than the sum of the parts. That really that positive sum game is really what open source is about for me.

Anu Sharma: So, you’re hinting more at the community aspect of open source rather than the open-source aspect of open source. It’s not the code being open source that makes that’s the material aspect here.

Joe Beda: Yeah, I think community is fundamentally what’s at the heart of open source in so many different ways and it really comes, and the more senior I become as an engineer the more I recognize that the hard problems aren’t technical. And so, a big part of this is that you end up with a set of folks that feel ownership over that project in certain ways.

And when somebody feels ownership and when it evokes an emotional response that actually creates, community that creates things that aren’t possible before, when you think about great branding, right? Nike, Apple, these like these top-level brands, they evoke an emotional response and the people that are actually buying those products, working with those companies, they feel a connection there.

They feel ownership over that brand. It becomes part of their identity. And I think open source is a way to do that, both to motivate people to come together to do great things. But I also think there’s opportunities to make sure that you can in a smart and respectful way, use that to your advantage as you’re looking to build a business.

Anu Sharma: One of the ways I think about open-source projects is it solves a problem. A user probably had the problem, approached it in a solution mindset and wrote up software that could solve the problem. And then there’s a different aspect of the productization off that solution which requires documentation, the usage aspect of it, the buying aspect of it, but also the consumption aspect of it. Uh, I don’t want to host it for example, and I just want it to be completely operated and managed by somebody else. And that’s, that’s a whole fully more productized version of it.

How do you think about the separation between open source and the commercial product that comes out of it?

Joe Beda: Well, I think that the words that you’re using there, and I think they’re so close that they sometimes confuse us is project and product. And. And I think oftentimes when folks get really enmeshed in this world, they start to confuse these things and they view the open-source project as the product in and of itself.

Now, I think this is exacerbated because we’re seeing open-source projects become more product like. For instance, um, Joyent started the node ecosystem. And the reality is that you can go and download node and you get documentation; you get an install experience. It feels very much like a product.

And I think that’s part modern open source where it, these lines are starting to blur, but at the end of the day, it’s still just a project, right? It’s not, a product in my mind is something that has a skew, and you pay money and, for goods and services, right?

Like that is a product. And a project really is, you know, there’s still an amount, a, you know, a certain amount of like, you’re on your own here, take it or leave it type of thing. Um, and so I think, you know, part of this is, is a product is the value that you’re adding on top of the projects that you can bring in and charge money for it.

And there’s different things that you can actually, and I think it’s worth talking about what are the size of the modes that you bring, as you start adding that value. And I think that the easiest thing to think about is, is, you know, some support and documentation and trusted builds and that type of thing.

And I think it’s very easy to say, well, we’ll take this open-source project. We’ll provide support. We’ll have a, you know, 24, seven on-call. If you hit problems, we’ll provide extended documentations, and we’ll all wrap it up in a bow for you. And I think that’s the traditional distribution model. And I think this comes from sort of the Linux distribution world where a Linux distribution, you know, I had a former Red Hat employee that, that worked for us call it, walking over broken glass as a service, right? Because the traditional open source is you take all the different projects that maybe some of them have versions, maybe some of them, you know, have, have bugs and they all are built in different ways. And you’re bringing all this stuff together, doing some cross integration tests and say like, here’s a set of things based on open source that we’ve brought together, can work together and we’re going to support it.

And so that’s the traditional sort of open-source support model. And there’s a lot of value to be added there. And, you know, but one of the problems there is that the crappier the open-source projects are in terms of user experience, the more value you’re bringing as we look at these more modern projects, right?

Like it’s very hard to build a distribution over something like node because the project is so darn good that the level of value there. And so, and in that world, what we see is we see companies like Sneak start to come up where now what they’re doing is they’re helping you to, hey, you’re just not using node, you’re using the node ecosystem. The node ecosystem is big and hairy. How can we actually provide a level of, you know, intelligence and thoughtfulness around making sure that as you bring that stuff together, you’re bringing it together in a responsible way. So, they’re starting to fill in some of those gaps around security and compatibility and, and sort of hygiene that you often would use to buy through, the Linux distros. Next level of, of value is that there’s features that you can get when you, when you buy the product, and those features aren’t available when you’re talking about the project and right.

And I think that’s where we get into sort of like, you know, what we were calling previously the difference between open core, where only one company can deliver those enterprise features. Whereas I think open extensibility, there’s a level playing field for multiple folks, open-source projects or, commercial companies adding those value-added features.

And then finally, I think, the last level is the hosting experience around this open source. Where especially when we’re moving into the cloud world, distributed systems, software is not, you know, a static thing, right. I think, you know, old open sources like lib PNG, I can decode PNGs without having to write my own decoder.

Right. Modern open source is Cassandra or Kubernetes or what have you. These things take a certain level of complexity, a certain level of skill and, you know, and dedication. They’re living, breathing things that somebody needs to be on the hook for. I think anybody who’s ever administered a database knows this, right?

Like, like you don’t just launch, you know, launch a database and be like, okay, it’s good. Done step away. Right? No, you need a DBA. You need somebody doing backups and testing those backups. That’s real value that’s being layered on top of this. And so that’s another place that you can create a product out of the project.

And so, I think we’re seeing different companies look across these different ways of monetizing and really constructing both the open source to allow for this stuff, but also, you know, playing around with the different models for how they can start adding value and turn product from project.

Anu Sharma: And going back to the time when you’ve been, you founded and built Heptio, could you wind back a little bit to how your experience has been in building a business around open source?

Joe Beda: So, a little bit of my history here is that I’ve been in industry for 25 years or something now. And while I was at Google, I started Google compute engine and then started Kubernetes. I left Google and then co-founder Craig McLuckie and I started Heptio as a way to take Kubernetes, open-source project founded in Google, but how do we actually start building a company around Kubernetes and really take it to the next level and bring it to customers. And thank you Madrona for being great investors and working with us through that journey. We ended up selling Heptio to VMware and we’re continuing that, that journey and that mission inside of VMware on a somewhat larger stage. The thinking about open source and establishing Kubernetes in general, I think a big part of getting open source out there and building that sense of ownership is releasing it and engaging in building that community probably earlier than when you’re comfortable.

You really need to get this stuff out there when it’s still half baked, when there’s still a lot of things to be done, when there’s big decisions to be made, because then you can involve your community. As you look to make those decisions, you can let them help shape you. And so, this really mirrors the journey that I see a lot of startups go through in general.

This idea that if you wait too long to release your product, oftentimes, you get in your own head and you don’t listen to folks. When you see healthy startups, they have an early customer base. They have a user community for their products, which mirrors the user community for open-source projects.

And they really get this really tight flywheel feedback loop with their early customers that really helps to accelerate and home in on that product market fit that is so critical for startups to be successful. Starting Heptio, we were in a little bit of an interesting situation because the project was already up and running, and successful, and was really finding a lot of traction. So, it was really, our problem was how do we actually construct a business around this open-source project after the fact, with the reality that, you know, a lot of the patterns, a lot of the technology was already in motion and set there.

Now, I think luckily enough, the way that Kubernetes was involved, and I think being part of that, I think we steered it that way, is that there’s parts of Kubernetes where it’s fundamentally extensible and there’s opportunities for us to build up and around on top of that to start building more products that compliment Kubernetes. And I think, that’s one of the keys, and I think we can probably get to this a little bit later. What are the different avenues for commercialization of open source? And I think one of the key things is to actually build the open-source projects so that it’s usable by itself, but it also has extensibility points that create opportunities for you and others to be able to work on top of that and start really bringing that next level of value on top of that open-source base and foundation.

Anu Sharma: Yeah. We spent a bit of time at ourselves on a couple of open-source projects at AWS, where we thought a lot about how to open source a project while still leaving enough room for the community to contribute, to bring in, as you said, their sense of ownership into the progress of the project. How did you think about which areas you wanted to leave open for extensibility?

Or was there a certain principle that you went into it as a tenant, for example, on, we want to leave this extensible and this is why we’re designing it this way?

Joe Beda: I think this is where things get really fascinating because product planning and business sort of planning and strategy starts to meet technical architecture and starts to, you know, so there’s this puzzle of we want this project to be useful enough that it will attract a user and a developer community that aren’t necessarily customers of ours, and we also want to make sure that we have room to find the right customers who maybe don’t have the energy, the time or the wherewithal to get involved in that community so that we can bring them value and build that next level on top of things. Now, with respect to Kubernetes, I don’t think we planned this from the start, but one of the things that we saw as the project continued and evolve is that the project itself was becoming a gatekeeper for new features.

So, everybody was showing up saying, I want to put this into Kubernetes. I want to put that into Kubernetes. And really it was overwhelming the project. We couldn’t keep up with all the ideas and the things that people wanted to do and build into Kubernetes. And frankly, it scared us, because, like we want to embrace that. We don’t want to say no, but we also can’t say yes to everything. And so, I think a big part of our evolution there was recognizing that if we don’t want to say no, but we can’t say yes, is there a third option? And so that third option really is, yes, you can do that, but you’re going to have to build it on top of using these plugin mechanisms.

So, we really let that community help to guide us in terms of what are things that people want to do on top of Kubernetes, and then what are the ways that we can provide a way for them to do that without the project itself, becoming a gatekeeper where it’s you must go through us to get something integrated into the core.

And I think when you look at sort of the way that this market has evolved, and for those not super involved in the Kubernetes cloud native world, you can go to the cloud native computing foundation and they have this landscape slide. And VCs love these things because they’re mapping all the different companies and you’re like, which one should we go and talk to?

And you check them off when you’ve met the founders and stuff. But from the point of view of, from my point of view, that’s a thriving ecosystem and it’s chaotic and it’s somewhat overwhelming. But it’s the sign that, that platform, that accountability mechanism has created enormous amount of opportunity outside of core Kubernetes.

Now from the customer point of view, that is also overwhelming and scary. And we’ll often see customers look at that and their eyes go wide and they, they start getting some cold sweats because there’s so much there for them to understand. But that’s also opportunity for vendors to be able to bring this stuff together and provide a curated introduction or view onto that world.

And that’s very much the point of view that we were taking with Heptio and what we’re continuing to do with VMware and VMWare Tanzu.

Anu Sharma: So, at this point, the project has evolved into a successful community, you’ve built a platform that is thriving with a vibrant ecosystem. As part of the company, when you’re building new features and new technology, how do you think about what goes into the open-source repository and what is part of what you believe is the company’s resource or asset?

Joe Beda: It’s, I think this is a place where you have to have a theory and you have to test it. There’s a couple of rules of thumbs here. And I hesitate to even say these things because for every rule there is a counterexample of it. But a couple of things that I think about when I look at this number one is that developers don’t pay for stuff.

I think once you start getting into more operational roles, and I think that’s what I would view paying for cloud services start to be, then I think those rules start to change, so it really depends on your definition of developer. But the reality is that a typical developer sitting in an enterprise, they would rather spend their weekends writing code, then figure out the purchase order process of their enterprise.

And companies make this hard on purpose to spend money for a lot of their, a lot of their developers. And so often times what you find is that this distorts things where the people who do spend money in enterprises, the people who are your buyers are often not your users. And so, when you think about that user versus buyer dichotomy, it really comes down to what are the features that are critical for users?

Put those into the open source. What are the features that are critical for buyers? Those are the things that you want to actually make sure that you reserve and that you think about building a business around. And this is and this is where it gets more subtle here because these groups don’t operate independently, right?

If you get a lot of traction with a set of users, and now the buyer, whether this be the head of IT or some, some business unit GM, or what have you, those folks have the engineers that they trust. And they’re going to go to them for spot checks in terms of whether the technology that they’re looking at buying is viable and healthy or not. And so now what you want to do is you want to go in there, establish a relationship, establish a brand, establish that ownership and that emotional attachment, and then be able to say okay, we can both maintain that experience that the users love. And then also go through and provide the set of features that are absolutely critical to the buyers on top of that.

And it becomes a reinforcing action from both sort of bottoms up and top down when you think about your sales motion.

Anu Sharma: Yeah, and there are parts or features that are clearly buyer side. There are features that are clearly user side. And then there are some in the middle. For example, you can think of, authentication SSO and maybe SSO falls more on the buyer side, but authentication almost as a core feature of your application, if you’re not authenticating, you’re lacking core security features. How do you think about that element? Is there a gray area in between and how you, how would you disambiguate that?

Joe Beda: There is a gray area in between. And honestly, I’m conflicted about this because I think, it’s not unusual. And I think I saw joke on Twitter, earlier this week where it’s SaaS, it’s you have the free version, you have the solo version that’s 50 bucks a year.

And then you have the enterprise version that has SSO and it’s “call us” and, “call us” means that it’s significantly more expensive. And that’s the common pattern that we see because some of these features, whether we’re talking layering features on top of open source or whether we’re talking about like coming up with the addition’s breakdown strategy for SAS.

Some of these features have outsize utility for the people that have money. So, the idea is that what are the critical features for the folks that have money, who can pay you for it? Those are the features that you want to charge a lot for. And I think as a developer, and as an engineer, it’s somewhat offensive where the value of a feature is not always proportional to the complexity of the implementation of that feature.

And so, breaking that assumption like I’m convinced that you can make millions of dollars with the right bash script. It’s not about, it’s not always about coming up with groundbreaking new, hard technology. It’s really about solving the right problem in the right way for the right person.

And if you can do that, then you can start to do the segmenting and actually come up with the right the right features to actually have for your enterprise edition and all that. And I think, you know, also as an engineer, we find this somewhat offensive. You’re charging how much for what? And I think, but it costs a lot of money to run a company.

It costs a lot of money to be able to actually create and support some of these projects. And I think that, part of building a business is recognizing that you’re going to be giving up some value. You’re not going to be capturing all the value that you create, but in doing so, you’re making a deal where, you know, you can, can capture more reliably, a smaller part of a larger market versus, the entirety of a smaller market.

And that’s some of the trade-offs that I think you make, as you think about whether you’re doing a free edition for SAS or you think about whether you’re going to start getting involved in open source and put real money, real time, real effort, real engineering behind that.

Anu Sharma: You started to get a bit into the monetization bits with buyers. You’ve probably thought about this a whole lot on all of the different options that you have in front of you for monetization. How would you consider that? Of course, how did you think about it for Heptio and how do you think about it now going forward, if you were to start a new project?

Joe Beda: I think looking at Heptio, I think I definitely learned a lot as we’ve gone through, and I think, my thinking on this has gotten a lot crisper than I think we were fumbling our way through with Heptio to be honest, in some degree. So, the first thing to recognize is that they’re different types of open source.

And fundamentally I started out saying, what excites me about open source is this community people coming together? And I think fundamentally when you look at a project, there is an unspoken contract between that project and its community. And you establish that early on and you set expectations with your community.

And as you set those expectations that defines your degrees of freedom in terms of, hey, here’s the stuff that we’re going to be doing to be able to monetize this stuff. And I think one of the worst things that you can do is to unilaterally redefine that contract with your community as you go.

And so, I think a lot of the places where we’ve seen companies struggle with open source is where they’ve had some implied contract or relationship with their community, and then the situation changes and they’re like, we’re going to change the license because we need to be able to monetize. Or we’re going to exert control that we hadn’t been exerting before, because technically we can do that, but because we haven’t done it before, and because of some of these sorts of statements that we’ve said, now, all of a sudden, we’re changing that contract with our community. And so, I would say that the contract that you have with your community, both, will influence the growth and the level of ownerships that people feel with your open-source project.

And it will also, constrain and enable the monetization motions that you can bring relative to that open-source project. And so, I think looking at different types of open source, I think that there’s on one end of the spectrum, there’s what I would call, throw it over the wall open source where it’s like, hey, I’m writing code, but people can read that code.

Maybe even it has an open-source license, but I’m not accepting any contributions. I’m only interested in a user community. I’m not interested in a collaborative sort of contributing community. And sometimes people will call it open source, even if the license is relatively restrictive as they do that.

I think a great example of this would be Android, right? Android is open source. People can take it and do other things with it as noticed by the gazillion Android derived phones that you know in, in far East. But there’s still a core of that, that is, the fundamental Android experience is tied to Google services and it’s very clear that the next version of Android is being enabled by Google.

And the set of flowing back into that code base is very limited. At the other end of the spectrum is what I would call open community, and open governance. And this is what we see a lot with things like projects in the CNCF or the Apache foundation. This idea where you want projects, where the direction and the roadmap of the project is driven by the community itself. And oftentimes you’ll see these things be places where multiple vendors come together. There are things like elections for decision makers inside the process. And so, it’s very much that community is driving where that thing goes. And I think from my point of view, a healthy sign of a project that is open governance is that if any single vendor, even the most critical one to that project, if they were to step back and say, you know what, we’re not interested anymore, the project would still be viable, would still have a life beyond that vendor stepping back.

And in the middle there, what we have is this emergent of what I would call open core projects. And I think this is where I think a lot of folks get very confused. And there’s a lot of companies exploring redefining some of these contracts and looking at this sometimes to great effect sometimes by, ham handedly, redefining that contract with their community and creating a lot of problems for themselves.

And so, I think there’s a way that we can start slicing this more, finally, that I think is useful. Open core often times what you have is a single vendor driving a project. And they reserve for themselves, the right to offer the enterprise edition of that product that has extended features.

And so, if you are a member of that community, fundamentally you can use the open-source version. But if you want to contribute to that open-source version, something that will start to conflict with the enterprise version, they’re going to put a stop to it, close to PR and say, no, right. And we’ve seen this happen with a lot of companies. Now where things get really hard is when like the original license, was very liberal and then going forward, they’re going to be changing license for the contributions they’re bringing to the project. They still own the trademark.

Those are the things that can create a lot of turbulence and can help to really damage communities. Now slightly on the other side of that is something that, we’re still workshopping the phrasing for, this is what I would call maybe open extensibility. And this is I think, where we look at where Kubernetes is. Where the open-source project is open and it’s a level playing field. You may set limits into what goes in that project. So, if somebody comes with a PR saying, we want to add XYZ feature, you may say no, but instead of saying, no, it’s impossible, you say no, but here’s the extensibility mechanisms that you can use to do it yourself.

Perhaps in another open-source project, perhaps in a proprietary thing. So now as a company you’re sponsoring that open-source project, you’re building it, you’re building the extension mechanisms. You’re then using those extension mechanisms to build your commercial products that are complimentary to the project.

But fundamentally it’s a somewhat level playing field between you and other folks because those same extensibility mechanisms could be used by your competitors, or it could be used by complimentary open-source projects. It’s a little bit riskier, but I think it also, from the point of view of business, but also, I think it stays true to a lot of more of the sensibilities and the ethos that a lot of your contributor and user communities will be expecting out of that open-source project.

And so that’s, I think in my mind, the sweet spot is to actually do that open extensibility, but I think it’s worth recognizing that there’s a whole host of models along that spectrum, that, that really come into play.

Anu Sharma: I love it. Open extensibility. And that, as you said, opens the room for more risk, more competition. How do you think about competition? Somebody using the project that you have created, that you feel ownership for, but also then I guess throwing a chip in and saying, I also feel some level of ownership, I also want to build a commercial product. How do you think about competing with them?

Joe Beda: As a company you always like, and I’ll probably, again don’t misquote me on this, but companies love to be monopolies. Like your dream as a company is to have huge modes and to have something that’s so unique that you own a hundred percent of a growing and thriving and critical market.

That’s our dream, that’s not always in the cards, that’s really hard and that’s super risky. And so, I think a big part of the way to view this is, again, I think, would you rather have a smaller part of a large and thriving ecosystem or a hundred percent of something that’s rather small. And clearly, the answer is why can’t I have both. But that’s not always what you’re going to get to. So, I think there’s a strategic decision around, we want to create something, a movement in a rising tide that we can then participate in. That is very difficult to do, if you don’t have a community aspect, if you don’t have that ecosystem to be able to build and build around. There are tons of companies that have Hey, I want to rebuild a windows office, like duopoly type of thing, and it’s yeah, that’s great work if you can get it. But a lot of people have tried and broken themselves against that particular type of goal.

Anu Sharma: And to that point, you might’ve noticed the recent flurry with a bunch of different open-source projects and commercial companies and for projects from other competitors, how do you think about disambiguating some of the narrative there. What would you say in terms of clarifying perspective?

Joe Beda: I would say that a lot of these things are, the fundamental cause is that the way that the communities for the open-source projects were structured was incompatible with the business models for the companies that were sponsoring them. And that’s the type of thing that you can paper over for a while, but you’re going to have to solve that. Either the company goes out of business because they don’t have enough of a business to support that project, or they go, and they redefine the rules and they run the risk where the community will revolt on them. And it’s a problem that I think, you very much, as you engage in open source, you want to make sure that you know how this is going to play out and that you have a game plan there. And I think, to be fair to some of these companies, there’s an emergence of other motions that they probably didn’t foresee like this idea. And I think this is especially common in startups built around open-source databases, where a lot of the monetization comes from being able to run these things and actually bring that experience, the full experience to it. And they found that them being the sponsors of the open-source community did not give them enough of a leg up when it came to be able to manage these things and run these things as a managed service. Oftentimes others are maybe better prepared to make that be a feature of a larger platform versus a standalone product.

And so that’s a really hard situation for everybody to be in. The point of open source is, you take this risk where you put it out there. Other people can do stuff with it, and sometimes they will and sometimes they may actually take it in a way that’s inconvenient for your business. And so, I think that’s something that you got to be, you got to be thinking about and working through as you go. Yeah, I think and some of this is understanding, like where is IP critical and where is IP really secondary to the larger experience that you’re delivering?

And I think one analogy here is I think we’re all sitting at home with, COVID not with COVID, but like quarantine because of COVID. I hope we’re not all sitting at home with COVID and like I’m ordering a lot from restaurants. And it makes you think about where is the value there when you’re doing that?

Because if I have a hamburger. I can make that hamburger at home. Actually, I’m getting pretty good at it. And it can be a good hamburger. And it’ll be a heck of a lot cheaper, right? The IP for making a hamburger is not the fry sauce is a ketchup in tomato, ketchup and mayonnaise mixed together.

Right? There’s this secret sauce is not that secret is in when it comes to a hamburger. So, the IP around this is actually relatively low. But yet there’s still real value for me going to a restaurant and having a hamburger and having somebody do that for me. And there may be complimentary IP Hey, they make this great cocktail and I have no idea what the proportions are, what goes into it right. There may be other, IP that I don’t get, that’s complimentary to that main thing, that is the hamburger. And I think we see with things like delivery services. It’s like somewhere in the middle and it’s the worst of both worlds to some degree it’s more expensive and it’s not as good at being at the restaurant or making it yourself.

So, I think, there’s definitely some lessons to be taken from an analogy like that.

Anu Sharma: I love that analogy. And you know, one of the aspects that we struggle with and hear from engineering leaders in some of our portfolio companies, but even some of the larger ones, is how do you evaluate open-source projects? And of course, maybe an extension to that question is how would you advise investors evaluating open-source projects?

Joe Beda: I think valuing and evaluating open-source projects from those different angles is I think very different. The, I think any engineering org should be thoughtful and responsible as they take on dependencies. And I think we’re starting to see this as we look at, more focused on the supply chain in general, and the risks that you take on board as you look at, sort of like, oh, I’m taking a dependency on this, so this node library. It’s everything from that to I’m buying this vendor product, that’s going to be, you know, where I’m committing to only running on this particular cloud. I think, it’s really important that as you make those decisions, whether you’re buying something, whether you’re building on open source, whether you’re building a component yourself, that you’d be really thoughtful about understanding the pros and the cons and the risk about that.

I think oftentimes in my end of the business, people will talk a lot about lock-in and how like lock-in is bad and, and open source is a way to avoid lock-in and I think, to some degree, there’s true, but I think that’s a somewhat simplistic view. I think the right way to view lock-in is vendor risk.

If I take this bet on this vendor, what are the risks that I’m taking and what are the benefits that I’m getting for that risk? And I think when we look at open source, there’s a different set of risk and benefits from it. Some of the risks may be that I have to run it myself versus having a trusted person.

Some of the risks may be that like, I’m going to have to buy support from somebody versus being able to, and that’s going to be part of the cost. But some of the benefit here is that I have more degrees of freedom. I can always take the source code and build up a team to dig into it.

I can always run it in a way that’s off label because it’s me supporting my own thing. And so, I think there’s a different sort of risk benefit analysis when it comes to open source. So that’s from the point of view of a user getting involved with open source. And I think also some of this is, open governance with a healthy project.

And what happens if that single vendor that’s sponsoring it, steps back, will the project still have a life beyond that? That’s also some of the things that I think folks should take into account as they’re evaluating, taking independency on an open-source project.

From the point of view of an investor, what I would do is when I’ve, advised and looked at folks who are building a business around open source, they should have a very strong thesis for how they’re going to build a commercial compliment to that open source. I think it’s very tempting and I think, to say, hey, I’m going to write a bunch of code. I’m going to get a bunch of users and then magically I’ll figure out how to monetize those. Now in the consumer world, you can do that, right? You get a hundred million people doing anything. You can find a way to monetize it, right? In the enterprise developer, open-source world, you can get everybody to some definition of everybody using your product and it will then be project and it’ll be very difficult for you to be able to monetize that. So, it’s without that theory, without that thesis, without planning for that, I would say, it I would have a hard time investing in a company that is that is basing something on open source.

Conversely, if they view open source through a very evolved smart lens, then you’re like, all right, these are folks who know how to build community, use that community to boost their business while staying true to that community. I think that’s, skills around that are something that’s pretty rare and something that should very much be valued.

Anu Sharma: A hundred percent. That’s what BC as well, and excited for open source in general for the next decade or more even. And we’re continuing to see a whole bunch of new projects that require that kind of balance between community and managing expectations, of course. And, but more importantly ownership along with building the commercial business model and scaling that to a multi-billion dollar business, hopefully.

That’s that was great, Joe. Thank you so much. This was fantastic. Really appreciate you taking time and enjoyed our conversation.

Joe Beda: Thank you so much for having me on.

Anu Sharma: Thank you.

Erika Shaffer: Thanks for joining us for Founded and Funded. If you enjoyed this conversation, please share it with your friends and subscribe. It’s available on all the platforms and we really enjoy making these and bringing them to you. And please send us ideas [email protected]. Thanks very much.

Founded and Funded: The Whys and Hows of (Diverse) Team Building with Founder Justin Beals of Strike Graph

Strike Graph, a company started by two tech guys, and funded in mid 2020 with just an intern, is now growing and serving customers. It is also two thirds women or gender diverse. The road to getting there was clear to CEO Justin Beals before he even incorporated. In this deep conversation with Hope Cochran and Elisa La Cava, Justin talks about the whys and how he set out to build his company this way and what this has meant for their success as a team.

 

Transcript (this is machine driven transcription so expect some typos)

Erika Shaffer: [00:00:00] Welcome to Founded and Funded. I’m Erika Shaffer with Madrona Venture Group. Hope Cochran and Elisa La Cava sat down with serial founder, Justin Beals, to talk about how he set out with intentionality to build the Strike Graph team from scratch to honor and promote diversity. Justin has seen from past experience, with other startups, that diversity of backgrounds and of thought promote a unique team environment that everyone can own and feel a part of.

We all know how being part of a team working toward a common goal is a powerful element of both enjoying work and being successful. Strike Graph received seed funding from Madrona in mid-2020 and was a Madrona Venture Labs incubated company.

I’m sure you will enjoy this discussion of team building and how to find the people who will propel you to growth.

Hope Cochran: [00:00:57] Hello. Today, Elisa and I are here with our friend, Justin Beals. We have been able to work with him over the past year or so as the CEO of Strike Graph. And have been inspired by him along the way, so it is great to start today off with a conversation with Justin. Justin is the CEO of Strike Graph.

Strike Graph is a security compliance company. A software solution that enables your customer to prepare, obtain, and then maintain their security certificates. Having the SOC two certification, for example, can help your customer sales cycle go faster by removing the security concern from their software.

But this isn’t Justin’s first rodeo as a CEO or product expert. He has an impressive career building companies from the ground up with Roundbox Global, that he founded and grew. He focused on the ed-tech space. And then later became the CTO of Koru that applied machine learning and leading assessment science to measure the things that matter most to the employee performance.

But what is inspiring and clear as you get to know Justin is that he approaches everything thoughtfully and with intention. One of the clear intentions that he set is to create a culture and employee base of talented and diverse individuals. And his views are not that this is just an important thing to do, but it is a key element of the success of building a high functioning company.

This is not something that happened overnight, as he will tell you, but with decades of focusing and working on it. Currently at his company Strike Graph, he has built a team, one that I am proud and love working with, that is two thirds women and are gender diverse. And this is not just in the traditional areas of marketing and HR, but 55% of his engineering team identify as female and 30% of color.

What I love to see is that I get to work with them. I don’t think, oh, this is a female CTO. I think this is a talented individual who’s getting stuff done. The team is full of talent, grit, and a focus on completing things. And one that I love to work with. So welcome Justin.

Justin Beals: [00:03:11] Thanks Hope. And thanks, Elisa, I’m really glad to join today.

Hope Cochran: [00:03:15] Before we jump into the topic at hand, you have become an amazing leader. And I would just love to hear about your leadership philosophy that I know you’ve honed in over time.

Justin Beals: [00:03:25] Sure. I was given the opportunity. I think that’s the way my family would have described it. I would have called it the chore of being a leadership or supporting in leadership from a really young age in their community, the religious community. And so, I hated every second of it, but I was the one that went every Sunday. And so, you wind up being the one, the troop leader for boy Scouts. I and I’m lucky in a way that I’ve gotten a chance to really go through the painful process of learning something about it and the time to do that. My philosophy is really service leadership.

I know that’s a hot phrase right now, and it’s maybe hard to define, but through just the experience of trying to be successful as a team, what you realize is that a leadership role is always in service. You’re in service of your colleagues, you’re in service of your customer. You’re in service of the mission of the organization.

And you have to set the right example. That example is the leadership that people need to see, and it doesn’t come across as dictatorial. Often times it comes across as doing the work side by side with the team and showing that you’re also not afraid to get engaged and get involved. The art of my philosophy of leadership is that it’s very hard to manage the balance between your self-confidence, like I can go and be a leader I can accomplish this thing, or we can, and as well have this really intense humility. This ability to be constantly open, aware, and listening, confronted with the challenges, taking on the hardest parts of the problems that your team is encountering. And so, it’s not an easy role to play and it requires immense strength, like just, the thing I grapple with on a daily basis is knowing like, not micro-managing my teammates, giving them the freedom to do what they need to do, but also know when it’s time to take a decision. Because for the team to effectively meet their goals, they need a clear direction.

Yeah.

Elisa La Cava: [00:05:34] I’m so excited to be here, Justin. This is Elisa It’s so interesting, I, another way you’re setting an example and kind of building this strong team. I remember at a board meeting recently; we were all talking about how quickly the team has grown in the past few months. And your response to that was I’m really big on building habits.

And I thought that was a really interesting thing to say. And I’d just love for you to elaborate. What do you mean by building habits or specifically what habits are you helping cement in your team at a foundational level, given how quickly you’re growing and some of your leadership philosophy?

Justin Beals: [00:06:07] Yeah, this is probably some of me coping with my own inadequacies, but I find it very hard to build like a super long-term strategy, way out in the future and yet not have an incremental and effective method of reaching there. You have to climb the ladder, you have to climb the mountain and you’re not going to get there by imagining what the top looks like, but by putting one step in front of the other and you almost have to forget or be able to let go of that larger end goal to work in the increments. One of the challenges in engineering is really scoping the time it takes to deliver something. And the number one thing you can change about being precise in your prediction is reducing the amount of time or amount of work you’re scoping. So, it’s these incremental habits that matter. In our company and especially with COVID, the daily standup is critical. I need to show up, and this is my opportunity, to that leadership question, to show what I’m working on alongside my team with them.

But then a regular planning meeting once a week is critical and it’s always on the books and we always show up and it may not be the best planning meeting. We maybe could improve the rigor with which we do it. But the fact that we can have that habit on a regular basis is critical.

And then it comes down to even communication styles, being clear and transparent as a habit. And the feedback, as a habit, is critical as well, because otherwise we’re not getting that loop going where we’re learning and improving.

Elisa La Cava: [00:07:42] I love it. It’s so exciting seeing your team work together from our vantage point. And one thing I’ve also noticed when we have our meetings together. If it starts at 8:00 AM, every single person is online, video on, ready to go at eight, like on the dot, and you are like, we are starting the meeting and it’s like full jumping in as a full team, every single time, fully prepared.

And I think that’s so incredibly impressive and a testament to how coordinated the leadership team is. And in being productive and working together and getting to the point and making those plans and probably making the most of your daily stand-ups as well.

Justin Beals: [00:08:20] Recognizing that example, right, Elisa, that you set, like if I’m there five minutes before the meeting starts, I find my team shows up too.

Elisa La Cava: [00:08:31] So my next question is flipping this on its head, Justin. And you are a CEO now you have been in leadership roles at companies for a very long period of your career. But thinking about the moment leading up to being CEO and founder of your own company who is someone, in your career journey who has inspired you, inspired your leadership philosophies and someone who or even, a peer or mentor who’s helped you hone those capabilities since you’ve founded Strike Graph.

Justin Beals: [00:09:02] Yeah, I think that’s a great question. One thing I wouldn’t say is that I’ve been super inspired by the business world, necessarily. I really appreciate the achievements of Steve Jobs or Elon Musk, but I have my criticisms as well. It goes both ways. I think more when I think about as a community of inspiration, it’s really the inventors and the scientists of the world that I find affinity for my motivations with. I really believe that the best part of living is in the boundaries. The boundaries of what you think you’re capable of, the boundaries of the relationships that we live in, and exploring those, and what we know about the world around us. And those individuals that are a little unafraid to question and lean in and test those boundaries are learning and living at the edge of their own context.

It’s really exciting and amazing. I think that I’ve had people along the way that certainly inspired immense confidence that I didn’t have. The first person to ever give me a contract at Roundbox Global for more than a hundred thousand dollars was a gentleman named Troy Viss. And he was a creative director at McGraw Hill, and he believed in me and no one else did. He thought I could get it done.

He actually baked our services company, Roundbox Global, off of a really massive services company and we won the contract. And that little moment with Troy, was an immense confidence boost. And all of us probably have those stories where someone that didn’t have to believe in us believed in us a little bit and gave us a chance and our whole world changed.

And I hope I’m doing that every day for my teammates. I hope that I’m giving them the opportunity to fail, but the confidence to go try.

Hope Cochran: [00:10:57] That’s really inspiring, Justin. And, as you think about giving them the confidence to try, you have really built a unique team and I see it firsthand at Strike Graph, but I know that this is your at least third time. This is not new for you. This is, as Elisa pointed out, a habit that you have formed. I’ve also, you and I have also talked about the fact that building this diverse team is vital to the outcome of the business.

And that you think that it’s an important element of a successful business outcome. So, I would love to hear from you why you think that’s such an important element to the outcome of the company.

Justin Beals: [00:11:36] The reason that this is so important for a startup, especially, but in any new venture. I think even if you’re in a large organization and you have an internal startup, you’re starting a new team, now you’re going after a new initiative, is that you want that group of individuals to bond around a new identity.

What we do is a team sport. When we build product, as we build an organization, that’s delivering a service, as we put together a marketing plan, that’s all collaboration, that’s all team driven. And for it to be successful, it has to operate that way. But you need a team identity to belong to, to negotiate that collaboration. And if the identity of the team is homogenous because they all come from the same background, you wind up not being able to bring a unique identity but living by the identity that homogenous environment brings. And so, when I want to build Strike Graph, Strike Graph is going to provide a unique service and it needs to differentiate itself and its teammates need to feel differentiated themselves from the other teams that they’re competing against.

So that’s why I think bringing in a diverse team gives me the opportunity and that team to craft their own identity. And so that’s critical in a startup space. The second thing that happens a lot when you build a diverse team, is that when you bring a group of people from a diverse set of backgrounds together, they actually tend to drop off the bad habits of their specific cultural affects or backgrounds.

They can build new, good habits around the new identity. And so, it’s a liberating opportunity to leave your bad habits behind and bring good new habits or your better habits to the larger team. And so, diversity diminishes the opportunity of one cultural or specific set of experiences driving that group identity or those group habits.

And really, it’s all about effective collaboration. That’s both to efficient collaboration, like how can we efficiently reach a decision as a team, and effective, like how can we reach the best decision as a team? And optimizing for both of those requires having your own identity and mission clearly understood and then leaving behind the old habits, so you can create the new effective ones for crafting the right next solution to build, the right next marketing message, the right next demo for a product.

Hope Cochran: [00:14:16] That’s wonderful. And one of your first roles as CEO that you chose yourself was building Roundbox. And you often refer back to that and say people were my product. And I actually feel that way in all companies today, people are our product because software is one thing, but it’s only created by the talent and the people around us.

You had a drive to create that environment and to create that company and to bring those people together. What was that drive that you had, as you set out to build Roundbox? What inspired that?

Justin Beals: [00:14:55] Yeah. I think the inspiration to build a company was a little twofold. One, is that I wanted to build a tribe, a group of people that I really enjoyed working around and I had some jobs that weren’t great, or some cultures that weren’t very accepting and thought there’s got to be a more collaborative, beautiful way to work every day. And really just set on the path to find that. Another factor that affected it is, my college degree is actually in theater, and to me a start-up is very much like putting a play on. And so, you get this crazy cast of characters together, you have an idea of this production, you’ve got to put on, there’s a deadline, you’ve got to launch it on the server and then you suffer the financial outcomes of your goals.

And I loved that habit.

Hope Cochran: [00:15:42] I have to just interject here that you and I have this in common because my degree is in music. And I always say that music is what I use every day, not my econ degree for the exact same reasons. Practice makes perfect. Bringing a diverse group of people together and trying to unify them and put something on is an incredible challenge.

And these are the skills that I use every day. So, I love that we bring this similar philosophy to the workplace.

Justin Beals: [00:16:09] There’s a joy in sharing, Hope. Sharing yourself, sharing of someone else, getting it back and forth. It’s, it’s enlivening. Yeah. Roundbox, specifically, was an interesting journey. I had a number of failures and this was the next kind of iteration of trying to found a company. I didn’t really have access to capital, it wasn’t my background or a community at the time. And so, we had to bootstrap it, which means that services company almost always. I really think that most founders should go through one bootstrapping experience of a business. There’s no better teacher of what is necessary from nice to have than having immediate financial issues as you roll out your company.

And so, it’s a great training ground. The other thing though, is as a services business, you’re billing a customer for every hour an engineer spends working on their software and they’re really communicating to you a vision of what they want to change about their company or the product for their customers.

And you’ve got to connect those things. I think it’s liberating to really perceive a company so precisely as the people that do the work are the product that we deliver. There’s a disintermediation in the enterprise SaaS sometimes, where you’re like, oh we hire great people to build a product, but we don’t talk to them that much, or as little as possible, so we can afford to charge as cheaply as we do. But it is a critical day-to-day understanding of the people working on the projects.

So, I remember having this really interesting conversation with our, one of our software development centers in San Jose, Costa Rica. And I was speaking with about 90 engineers at an all hands for Roundbox. And I remember telling them that, while we produce code, while we manage massive software systems for enterprise education delivery, and we really support incredibly complex technology. Our true business, the work that team is engaged in is relationships. It’s our relationships with our customers that had to be healthy for Roundbox to be successful and grow as rapidly as it did. And if those relationships aren’t healthy, there’s no chance of us having an effective delivery. And so I told them we’re in the relationship business, not the technology services business.

Elisa La Cava: [00:18:33] So Justin, one thing I’d love to do is talk about team building again, because I think that’s such an incredible topic. Many people and leaders struggle with sourcing unique and diverse candidates.

And we all know when you have limited capital resources each head count is vital. And what I think is notable is in the period that you founded Strike Graph, over the past year or so, you’ve gone from zero to 22 employees, notably two thirds of your company is women or gender diverse. And overall, you have 30% people of color.

This is an incredibly diverse and talented team. And I think one thing a lot of people struggle with is achieving these kinds of goals as fast and as intentionally and as successfully as you have. And so maybe you can share with everyone what’s one of your secrets. How do you find these people?

Where do you go to source candidates like this for your company?

Justin Beals: [00:19:28] Yeah. As you say it, Elisa, I’m really proud, actually. The accomplishments and putting together such a diverse team really comes from the team itself. So, I want to laud praise on their shoulders cause it’s not just me that achieves that, that outcome. But what was important, for me as the CEO and founder in getting there is the first three hires are a critical decision.

And I think this is true, no matter what outcome you’re optimizing for in your team building, because those first three hires are going to make critical opportunities for the next 30 for the next 60 and the next 90. Think about them. I build in my mind a model of the perfect candidate – for the role, that first role, our first CTO, our first VP of sales, our first head of customer success – and it’s not just, I want five years of customer success experience, or I want someone that has been an engineer for 15 years. It’s actually, I wonder if they would have experience in this type of architecture, or I wonder if they have a deep interest in the psychology of customer purchases.

One time I made a hire of a PhD to a computer science position, a software developer position, because we were doing research into the scientific area that they came from. And even though they wanted to be a software developer, I was looking for that third, fourth, fifth skillset that they came with.

And you’re playing Moneyball, with talent, you want six different things that they’re capable of doing. One of those things that you want is a diverse cultural background. That diverse cultural background brings different types of experiences and different ways of thinking and pushes that three-person collaboration, because that three-person collaboration is how the next group of people, as you scale up, are going to collaborate.

They are setting the tone, the deep-seated cultural architecture of everything that will follow. Pragmatically, just to go find them and get them on board. Once I’ve got in my head who that perfect candidate is, I go search them on LinkedIn. And I am known for finding three or four people and writing them a direct message from the CEO and saying, I think you’re a perfect candidate for us.

I haven’t posted a job description, but you have these skillsets, and they are exactly what the problems we are trying to solve. I think you would get great joy out of solving those problems with us. And typically, I send three messages out and somebody responds, and we go through an interview process and it’s been incredibly successful.

The other thing I think, Elisa, is this is why networks matter. This is why your long-term business relationships matter. Because I can tell you that I started recruiting the first three hires for Strike Graph before we ever incorporated Strike Graph. I had meetings with them, I told them what I was working on, I talked about the types of things that we would like to build, I gathered their feedback and interest and I tracked them the whole way.

Elisa La Cava: [00:22:47] I love that. I also wanted to touch base on another point you’ve made before about looking for people in candidates who want to join your company, who are reaching up.

Can you tell us a bit more about what you mean by that?

Justin Beals: [00:23:01] Absolutely. I think that’s one of the critical traits for any startup that you’ve got to look for. When you find someone that has been overlooked, for whatever reason, the color of their skin, the gender, diminished or demeaned from typical communities that they might work in, you’re finding someone that wants to achieve, but no one has unlocked their ability to go and see what they can do. You want to give them an opportunity to operate within their boundary. And that’s your job as a CEO is to unblock the talent to deliver everything they can. Not to tell them what to do, but to give them the best opportunity to even outsize the deliverable that you expected of them.

And so that grit, it’s really important to me. And I think that nontraditional candidates are a great way to source that grit, because if they are exhibiting courage, to go and try, they just need a vehicle to travel in. And a startup is that because the one thing a startup can give employees is an opportunity to grow quickly and opportunity to work on new problems and opportunity to do things that, bigger company might have more clearly delineated in roles. And when I have a developer that says I’m interested in dev ops, I’m like, great. We have a lot of dev ops problems. You can get a chance to grow in that way.

Hope Cochran: [00:24:32] Justin, I love this concept of unlocking their potential and finding people who want to reach up, but just haven’t had that opportunity. You and I have talked about some of the ways that you find these candidates. And you’re very intentional about looking for them. Can you walk us through some of the ways you’ve done that? It doesn’t happen by accident.

Justin Beals: [00:24:57] Yeah. So, I think the first step is to understand the context that you’re operating in. So, for example, with Roundbox sometimes we operated in new international contexts – Chile or Costa Rica. And so, geography was a really important limiter to what we were looking for. When you understand the limitations of your sourcing or who you’re going to hire, i.e.., they need to be in the Seattle area or it can be more international or they need to have at least this baseline certification, then you can start to get very creative about where you source it from.

And you need to understand that you’re competing for talent. You’re buying talent, you’re competing for their interest in you, their ability to come work for you and you need to go find them. Now, if you buy the most expensive talent possible, as it gets more expensive, I find there is more and more variation in the actual success of that talent when you bring them on board. But if you look for the places where others are overlooking talent, you will find amazing, talented individuals that are looking for a real opportunity to do that reach up, to climb a ladder, to learn more and grow. And so, I tend to find the educational institutions that are in the area, that are teaching the types of skills we need as a baseline, but are reaching into lesser served communities, people of color, historically black colleges and universities. My own college, Fort Lewis College had an attendance of 30% first nations, native American population. It’s great environments like that.

And here in Seattle I’ve worked closely with the ADA Academy, which focuses on women in coding. And so, these are just really exceptional educational institutions. The talent is high class. I spent time learning about these educational institutions so I could rely on what the students learn, and they’re just an amazing source of talent through and through. That’s that exponential effect because once you bring in one person from the local community college, new graduates are coming out all the time and interested in the opportunity that they’ve seen someone else achieve.

Hope Cochran: [00:27:06] Yeah. I just want to emphasize Justin cause it’s something that I’ve been so impressed by in working with you. When you started Strike Graph, you didn’t say, hey, I’m going to go check out this college and form a relationship, you had formed that knowledge and relationship with those institutions’ years ago.

This is a process. This is not something that just happened because you decided one day that you needed candidates. You have been working with ADA now for years. And as a result, we have some amazingly talented engineers in your organization as a result of that relationship. Same with the colleges, you know where to go because you have done the background work. I just think that’s so impressive. This doesn’t happen opportunistically or by mistake, it was with well laid plans, so congrats to you on that. I think in general, one thing we can’t overlook is you have built this company during the time of lockdown and COVID. And we all talk about how bringing on new hires during COVID has been the challenge.

Your entire company has been new hires and you have built an entire company during this period. So, as you have brought together this amazingly talented and diverse group, can you talk a little bit about also the challenges of doing this in this unique time period?

Justin Beals: [00:28:29] Sure. I’d be happy to. With compassion, this is a really hard time. And one thing, when I’ve been knocked down in business, it’s generally been something chaotic that I never could have predicted happening. And this is chaos in a lot of ways. And I want to respect that I’ve talked to colleagues that have had a horrible year in business.

It’s been really awful. And colleagues that have been very successful because of the chaos. And it’s very hard to predict. I will say that I started Roundbox in 2000 when the internet, no one liked it much anymore. It’s actually a little bit liberating to start a company in some form of downturn or crisis because you can grow as everything starts coming back, which is helpful.

You’ve mentioned the network being really valuable and it is probably my greatest pride, is all the amazing people that I’ve had a chance to work with and learn with, and the future opportunities that I want to create to work with them again, if I’m not already. That network was super important to getting a company off the ground with COVID. And I think, and I’m not sure if this has been your perception, that talent is looking in this COVID time for a team that they can work with and rely on since they can’t go to the office as well. And so, the, their networks have been more valuable to them in selecting a new position or looking for a new opportunity. And I took advantage of that, of course in building a strong team ourselves. Those habits that we mentioned daily, stand up. Planning meeting, writing tickets in our JIRA board, making sure that we’re keeping each other healthy and on track. It is, I think also critical in, in these COVID times. And then the final one is you have to express an outsized empathy. I used to say, a lot of remote teammates over the years, I used to say that you need go see each other every quarter to humanize each other again. So even though you’re on the phone, you remember that you’re talking to a person on the other line and even I get off base with that. It’s hard to remember the humaneness that, that we need to engage each other with when it’s just over a phone or video. We can’t do that now.

And we can’t make those physical connections. And so, I’ve intentionally tried to have moments with all our teammates that are not about work, but just about life. So, we can connect over the water cooler and continue to build a human relationship. Something beyond just the work that we do and enjoy each other in that way as well.

Hope Cochran: [00:31:10] Thank you. Justin, every time I work with you interact with you, I’m inspired. I’m excited to build this company with you. I’m excited to have that opportunity. And I’m just excited about what we’re going after together. So, thank you for letting Elisa and I be part of your journey.

Justin Beals: [00:31:30] Hope and Elisa and Madrona Venture Group and Madrona Venture Labs, our incubator, I have grown over the last year immensely, so I am not static in this process, as well, and all of you have been critical mentors for me, and I’m eternally grateful just for the opportunity to work alongside you and to achieve some success in and go after the next boundary.

Elisa La Cava: [00:31:53] Thank you, Justin.

Erika Shaffer: [00:31:57] Thanks for joining us for Founded and Funded. I hope you enjoyed this episode.

Founded and Funded: StartUp Studios and Accelerators, Which is Right for You?

The path to building a company (and getting venture funding) can be varied and long and winding. In the latest Founded and Funded we talk about two of the paths – Startup Studios and Accelerators. They each offer different benefits. Madrona investor, Elisa La Cava sat down with Madrona Venture Labs’ Mike Fridgen and FFA’s Leslie Feinzaig to dig into the differences and the types of companies that benefit these types of programs.

Transcript (this is machine driven transcription so expect some typos)

Erika Shaffer: [00:00:00] .
Welcome to Funded and Funded. I’m Erika Shaffer and I work at Madrona Venture Group. In Founded and Funded we want to tell the stories of founders of venture funded companies. In this episode, we’ll look at how companies get to be venture funded. Two different tracks to that, or joining a startup lab, which is sometimes called a startup studio or joining an accelerator.

We sat down and talked with Leslie Feinzaig of the Female Founders Alliance, which runs an annual accelerator called Ready Set Raise. And with Mike, who runs Madrona Venture Labs, a startup studio that is the innovation arm of Madrona Venture Group. They both sat down to talk with Madrona investor Elisa La Cava.

Elisa La Cava: [00:00:52] Hi everyone. My name is Elisa La Cava and I am an investor at Madrona Venture Group, and I am beyond thrilled today to have two incredibly important people in our Seattle ecosystem on the Founded and Funded podcast. First let me introduce Leslie Feinzaig.

I actually met Leslie when I first joined Madrona two and a half years ago because attending an FFA pitch event was one of the first things I did in my role, as an investor in the Seattle area and meeting some of the first entrepreneurs you worked with in your Ready Set Raise program. So I have been a big fan of Leslie and what she’s been doing for the past two and a half years since I’ve been in my role.

And I know Madrona has been a supporter of FFA. For the full three years that you’ve been doing this program. So this is incredible. But more about Leslie, cause I know you all want to know about her. She is an entrepreneur and investor. She is the founder and CEO of Female Founders Alliance, which we call FFA. And it is a national community of founders, executives, investors, and supporters that collaborate to help under represented founders succeed. And her accelerator Ready Set Raise is three years old and it has been dubbed the Y Combinator for female founders by Tech Crunch. So welcome, Leslie.

Leslie Feinzaig: [00:02:11] Thank you for having me. I’m so excited to be invited to the Madrona podcast.

Elisa La Cava: [00:02:15] Yay. We’re so thrilled to have you. Okay. So I’d like to introduce our second guest, Mike Fridgen. He is the managing director of Madrona Venture Labs, which we will also be calling MVL. So we have MVL and FFA. And he has been managing director of Madrona Venture Labs since 2015. And it is the incubation program of Madrona Venture Group. And Mike has an incredible story, career, as an entrepreneur himself , founding companies since he was in college . Notably, he was part of the founding team at Farecast, which sold to Microsoft. And he was also a founder and CEO at Decide.com, which sold to eBay. So welcome Mike.

Mike Fridgen: [00:02:58] Thank you so much. This is going to be fun.

Elisa La Cava: [00:03:00] Yeah. So the topic were, today is labs and accelerators and this wild world we live in entrepreneurship where people decide to start a company, they have this idea. Maybe they have a co-founder, maybe not, and they decide to start a company and then suddenly think, okay, How do I do that? What’s next? How do I get the resources? Make the network, meet people, understand what the steps are. I need to take both fundamentally to build my business. But also to get customers to, hire your first recruits for your leadership team to get outside funding, if you’re looking for outside investors and there are tons of different ways you can do that.

And so we’re going to talk about two of those ways, which you are both experts in, which is the labs model and the accelerator model. So maybe I’ll just start off with an open question. What the heck is the difference? And what are they?

Leslie Feinzaig: [00:04:02] I think you should go first, Mike.

Mike Fridgen: [00:04:04] Okay. Happy to do it. So I say the difference in a word is the stage. So startup studios began with founders at the earliest possible stage. This is day one with an idea and at MVL there’s really two paths. One is , the path is where it’s our idea and we’re recruiting founders in. And generally when we get to that stage, we’ve done deep market analysis and research.
We’ve talked to dozens of customers. We’ve pretty, sold this idea into a set of investors to see if there’s a market for it. We’re really building conviction that there’s a product to build, there is a real burning problem to solve and the customers want it. And at that point we move forward and we recruit a founding team and we start with the CEO to begin a journey of further validation, then building traction, and then ultimately fundraising.

So that’s one path. A second path is when the founder has the idea, but it’s still very early, it’s at a conceptual level. And we’re going to then engage with that founder to go through our process. To really get it to the next level and ultimately get it to funding and on their way.

Elisa La Cava: [00:05:10] That’s exciting. And we can come back to this later, but the difference between having an entrepreneur who has that concept and then knows to come to you and the MVL team. Versus you and the team coming up and developing and vetting this concept, but then realizing I need a founding CEO. I need to reach out deep into my network and find someone who I think would be incredible at taking the helm of this idea that we’ve already started and launching it from there.

So I would love to, we can circle back later into kind of the process for how you get in touch with these two different profiles of entrepreneurs. Super, incredibly interesting. But before we go any further, Leslie, what’s an accelerator? And how do you think about that in context of what you’re doing differently with FFA?

Leslie Feinzaig: [00:05:59] Yeah. The, let me tell you the bad news is that the word accelerator now means a ton of different things to different people. The first piece of advice that I have for any founder out there is that when you see something described as an accelerator that you double click and go research what they actually mean because it can be like a traditional pitching and fundraising.

Like we are a traditional accelerator we’re pitching and fundraising accelerator. We were modeled after Y Combinator and Tech Crunch and TechStars rather. But there’s also development accelerators, there’s sales accelerators. There’s programs that call themselves accelerators, but all they really do is introduce you to people and you don’t actually accelerate anything.

So it really has a lot of different meanings. I’m going to talk specifically about these pitching and fundraising accelerators that are designed to help a company raise their first round of capital. That’s what Ready Set Raise is. You come into the program and in a few short weeks, we equip you to give a pitch, that is we call it the perfect pitch. And then we put you in front of hundreds of investors nationally. Try to match you as much as possible. We develop a mentor network for you and give you the relationships that you’re ready to walk out of that accelerator and ready to have a very successful fundraising season. So it, it’s less about, it’s less about a short MBA where you learn about sales and marketing. Although we can do all that stuff. It’s more about accelerating your capacity to first to raise that first round of capital and getting your company ready to do that.

Mike Fridgen: [00:07:33] I think it’s so helpful that Leslie points out that accelerator can mean a lot of different things to different people in different organizations, and it matters so much who you’re working with. And it matters so much like the team that’s surrounding you to support you. And when I think about accelerators in terms of stage, I think it’s at a later stage. So this is generally where the founding teams in place, there’s an early product development, product developed. And in some cases they’ve even raised some funding, but they’re looking to take it then to the next level. Most accelerators generally work within a three month time horizon. So something within that range, when you’re talking about a startup studio it’s much earlier, so you’re really at that earliest point and working over six, nine, 12 months before you’re getting to the funding stage, just to help clarify some of those differences in terms of timing and in terms of the idea.

Leslie Feinzaig: [00:08:23] One of the great ways of judging that is we if you are not ready to raise a round, you’re not ready for our accelerator. And that’s a key thing for people to, to be introspective about because just because you need money doesn’t mean you’re ready to raise money. And I mean that in, in the sense of where the business is, there has to be an investible story and we’re going to help you pull everything together to tell it and fundraise successfully versus an accelerator, ours is not the place where you come in to figure out your business.
We assume that you did that on your own already. Versus if you go to a lab, you’re going to have a lot more time, a lot more support to figure out the operating company itself.

Elisa La Cava: [00:08:57] I love what you just said. Leslie, you said just because you need money, doesn’t mean you can raise money.

Leslie Feinzaig: [00:09:03] Which sucks, just to be clear, because when you need money you need money. But the truth of it is it’s in the long-term. Not good for you to get money when you’re not ready for it.

Elisa La Cava: [00:09:14] Right. And when you are ready to bring on outside funding, investors are investing, explicitly because they hope to get a return on their investment at some point. And you have to be in a position to prove that you’ve, de-risked certain elements of your business to be able to deliver on that promise of return one day . Oh, go ahead, Mike.

Mike Fridgen: [00:09:32] I’m just going to say again, I think this was really helpful because so many people have these questions about the differences and how to think about these different models. I think w it’s just such a great point that they have to be ready to raise, and she doesn’t have confidence that, you’re going to be in that spot.

Then it’s just going to give her reservations. Cause she wants to put, people are going to be ready in front of investors and have this be a successful model. And similarly we’re looking for a set of traits around the CEO really early. One of the things that I was going to share though, that I think would be helpful.

Is that also within the studio model, there’s a set of doers that surround the founding team. And what I mean by doers, people actually co-building with you through each phase.

Elisa La Cava: [00:10:11] Maybe talk more about this Mike, because how does it change if it’s an entrepreneur coming to you with an idea versus your team building the idea and then hiring an entrepreneur in.

Mike Fridgen: [00:10:23] In both case, if we have conviction that this is something that needs to exist in the world, this is a real problem. And we are going to partner with the CEO, whether it was our idea or their idea to go build it and to go serve customers and to go create evidence and proof that we can then, without traction, go to investors and make a compelling case to fund it and that we can then take it forward. And what I mean, doers, with our team, we’re a team of former founders across engineering and data science and product and design, et cetera. And so when we work with the founder, we call it swarming.

We really swarm around the founder. And so you’re fast tracking your development. You have a team of people who’ve done it and they can help you take the shortcuts to get that product in market and have it land successfully. So I think those are two differences because the models are different too.

You’re going to, to be clear as an entrepreneur, you’re going to give up more equity generally in a studio model, and that doesn’t make sense for some founders. Some founders are ready for investment and accelerator is more suitable to them, and it makes more sense financially for them because they’re going to, they’re gonna, give up less of a trade off around equity.

Leslie Feinzaig: [00:11:33] To that point, it’s worth mentioning that traditionally one of these fundraising accelerators is going to take, I actually forget what the latest the terms are, but somewhere around 6% of the business and they pre value your business. So you don’t get to negotiate what chunk of equity you’re going to give up and for how much money. We just by virtue of how we started as a bootstrapped company ourselves, right? We’re bootstrapped accelerator. We started off by making it equity free, so we actually don’t take any equity in the companies, what we take this investment rights. So that, that down the line, when you are raising your round, on your terms, on the terms that you set with your lead investor, then we can participate in those terms.
And we are very strict about not negotiating that, so we do take those investment rights and we have the right to invest in you down the line because we believe in every company that comes on board. But like Mike said, that is actually a much like whether we invest on the spot or later on, like that’s a much more traditional participation in the company versus if you go to MVL, like you are co-building that company with an entire team of people, we’re not doing that for you. We assume that you built your business on your own. And we’re going to put the equivalent of the world’s most bad-ass advisor group working for you for free, right? Need to spiffy up your model. We got you. We got your CFO on hand. You need to build that deck beautifully. We got you. We can put the right people in front of you. We’re going to work with you endless hours in a short period of time, but we’re not actually going to do any of that for you. We’re going to put the right people in place that you can do it yourself.

Elisa La Cava: [00:13:10] I love that you bring this up, Leslie, cause this was my next question is that next level down, what would an entrepreneur exactly get or receive in working with a lab or an accelerator? And I love how you frame that saying, if you need specific help, we have people we can connect you to, to flesh out your model, your financial model to go through your investor pitch deck and help you craft that story , to give you access to a number of different advisors who can coach you, but you still have to do all of the work.

And so I’m curious, is there anything else you’d add in terms of specifics for you know what entrepreneurs can hope and look forward to receiving in working with a group like FFA.

Leslie Feinzaig: [00:13:55] I’m channeling my COO here. And what we like to tell entrepreneurs is that you get what you put in. We are not here to do for you. We are here to accelerate you. So the way to think about it is like, whatever work you put in, we’re going a 100x effort by putting you in front of the right people. I don’t know if a100x is the right number, but like we’re going to, we’re going to accelerate and amplify all of the things that you are doing on your own. Need to hire? Let me put you on my 20,000 person newsletter. Need to get on, need to get your press release? Let me put you in touch with whoever at Tech Crunch, GeekWire. Need a specific area of expertise? Opening up our Rolodex. We’re just going to open up all of these network opportunities and to some extent, the people that are really great at supporting startups and all of this stuff can’t support every startup, right? So we become for them and actually for you guys , for Madrona Venture Labs and for Madrona Venture Group, we become like the curators of who they should be supporting.

Like we bring you and say, we just selected these eight companies from 400 of the country’s most promising entrepreneurs. These are worth your time. The primary outcome that we look for in the companies is a successful set of fundraises down the line. So it’s not just about raising our first round.

It’s about setting yourself up for multiple like, for getting on the path successfully for the long term and having a great outcome for your investors. That frequently looks like getting ready to start a round and closing and successfully, but , as it’s turned out we end up having a long relationship with some of these companies, right? Like either I will get on their advisory board or on their board, or, I don’t have the capacity to get everybody’s boards, but they’re, they’ve been recruiting from our mentoring network to put people on their boards. They’ve been recruiting from our mentor network to hire actual employees and C-levels into their companies by introducing each other to investors down the line, lots of media sharing, lots of like stuff that you just share with founders. They’re also a great founder cohort support, right? They actually, even right before we started recording this podcast, I had my monthly Ready Set Raise community check-in where we get all the founders together once a month from all the cohorts and just talk about what’s going on and celebrate each other’s wins. Nobody understands what you’re going through better than somebody who’s going, who’s walking the road with you. So you get that, that Vistage, like network for life.

Elisa La Cava: [00:16:12] And you’re building the power of that network over time with each additional cohort, which is amazing.

Leslie Feinzaig: [00:16:16] That’s exactly right. The, the students become the teachers. These founders are even taking us like the Female Founders Alliance ourselves into their fundraising journey. So all of a sudden we are, our investor network explodes, and we are able to, Hey, you invested in this company, let me show you these five others that came through our accelerator, because I think that you’re going to like that.

So really amazing things have happened. And I talk it up to the fact that there’s a little bit of, if I just survive a little bit longer, right? This is going to absolutely explode. It’s only been three years and we have so much. There’s so much big announcement stuff coming down for the companies that have participated that it’s almost daunting to imagine where they’re all going to be next year.

Elisa La Cava: [00:17:04] And, you bring up kind of another point that we’ll dive into in a minute, which is the fundraising journey. Which is , deserves chapters of its own. But Mike, I wanted to quickly, get back to the labs model and just get the next level down when going back to the original question I just asked Leslie on what can founders hope to specifically get help with in lock step with you and your team.

I know you mentioned creating evidence and proof and you have this kind of swarming process you do, but what does that actually look like?

Mike Fridgen: [00:17:36] Absolutely. So really when you’re talking to day one founders and what they, when we asked them, what are they looking for? What do they value? There’s really two things. It’s de-risking and fast-tracking building a venture scale company. That’s what they’re looking for. And again, I’m talking about day one, I’m talking about really early because there’s other options.

And other options to bootstrap, which can be a lonely, expensive process over a long period of time. And the idea of coming in MVL is really de-risking and fast tracking. And part of that, is the team. Working with the team to vet the idea, using a proven process that’s been used from, by founders. And, our team has been doing this for decades, but then also over the last dozen companies that we’ve built, we’ve continued to refine this validation process. So that’s an important part. The second piece is we mentioned getting to actual traction and building. We have a process around doing that quickly and access to an incredible network within the Seattle area, not only our personal networks, but frankly Madrona’s deep network in our community to have access to companies and talent.

So when we are building and maybe we just started with the CEO, but we’re out in the market and we’re bringing on an incredibly talented CTO and, lead product, head of design, et cetera. We’re forming that team together, leveraging our network, as we’re working with customers, as we are building that product out. And then ultimately getting to funding, where we’re, de-risking that process all along the way as well. With us, we start talking to investors incredibly early and we make them part of the conversation, so by the time we’re raising there’s a lot of familiarity there and there’s a lot of lean in and interest in leading the rounds and participating in the funding round.

So that’s all part of the mix when you think about de-risking and fast-tracking what might take two years to bootstrap in your garage, you can do over a six to nine month period with people who are focused on your success and have been doing this on a repeated basis throughout their careers.

Elisa La Cava: [00:19:39] okay. Amazing. You just make me think about the sheer number of entrepreneurs and companies who are hoping for help growing their businesses or for raising outside funding. And, you look at MVL and FFA and you have limited resources, namely your time, in how you choose to allocate what kind of companies and what kind of entrepreneurs you’re able to help.

So, and Leslie, you mentioned earlier a stat on 400 people applied to your most recent cohort which means most entrepreneurs and companies don’t fit your program. So can you talk a bit more about what, what doesn’t work with your models?

Leslie Feinzaig: [00:20:22] This a really tricky thing because we don’t want to discourage people from applying. We in fact, want to encourage people from applying. We think that there’s great benefits in going through an application process, because we’re basically asking you to describe your pitch in, in, in like long form.

So as you’re preparing to go into a fundraise, even going through an application like this is good. Second , specifically with women and specifically with women of color it’s important to encourage entrepreneurs to just try, because if you don’t try, you are undercounting yourself, right?

Like you’re immediately assuming that you’re not going to be the one that makes it through. We have more than one example of companies that did not, were not selected one year applied again and were selected the next year. And the companies that we like from there, we end up building relationships with. So who is it for? So the first thing to know is usually when you’re not accepted into a program like this it’s less than there’s something wrong with you or your company. It’s more that there’s a company that fits the program a little bit better. So we’re going to end up selecting companies that we believe we can accelerate the most.

LeslieFeinzaig: [00:21:38] Does that make sense? The best use of my time or the best use of flexing our entire program’s muscle on someone’s behalf is somebody who is absolutely ready and is just missing, it’s just missing that, like that rubber stamp of de-risking. So, very frequently, it’s just somebody who is a little further ahead, who has better chance of opening and closing around at the end of the accelerator, at the moment in time that they’re applying . Who is this not for?

The one thing that we encourage people to do before they apply is to find true evidence of demand for what they’re building. And Mike was talking about how much work, imagine how much work Madrona Venture Labs spends validating those ideas before putting people and money against them.

Think about your own idea in the same way. So we generally don’t admit idea stage entrepreneurs. We admit people who maybe they haven’t built their product because it’s expensive to build something, but they have hacked the backend and demonstrated demand. That might look like a waitlist, that might look like some LOI, some letters of intent signed with possible B2B customers, that might look like a big pipeline of people that you have relationships with that have demonstrated interest in working with you.

So it has different ways, but like show, you need to show us that people that are not your mom and dad and brother, and sister want to buy the thing that you are selling. And that they want to invest their time with you. And it’s not a survey. Like it’s not it’s not the results of the survey. Tell me that 70% of people want to do X. No. It’s like a real signup.

So that’s one category of I don’t want to say don’t apply, but I do want to say, go find evidence of demand that you can demonstrate to us before you apply and you’re going to have a much better chance of being admitted. And, hey, by the way, you’re also going to have a much better chance of raising capital if you have demonstrated evidence of demand.

And the second is we get a lot of applicants who have been at it for a really long time and bootstrapping for a long time and you get into this catch 22 problem, or you are successfully bootstrapping, but also not growing at a pace that, that makes it interesting for investors. So when you think about moving away from a bootstrap for X number of years , not weeks, not months, years to I’m going to raise venture capital. The problem that you get into there is that you don’t have velocity and investors look at it and the investors want to know if we put money into this, is it going to catch velocity and like really take off?

So frequently we get applicants who are like, this is my last ditch attempt because nobody wants to invest in, okay, but I can’t help you. So if that’s you, if you have the five-year trajectory, the thing that we want you to do before you come apply is find evidence of velocity, throw out a new program, right? Get, get a new hire and build in something that demonstrates that you are picking up speed and that there’s a reason to invest in your company now. And again, that kind of goes back to the difference between needing money and being ready for money. If you don’t have, if you’ve been working for a long time and you don’t have any kind of, what changed this year to make it a good investment now, versus it was five years ago? Then it’s going to be really hard for us to get investors excited or to help you execute a round successfully. And I know that it hurts to hear this and I’ve bootstrapped companies myself, so I definitely appreciate how much work it takes. But the more, the more I have developed my own journey and startups and venture capital, the more I realized that this is not about good businesses. This is about venture capital investible businesses. And those two are not necessarily the same thing.

So you might be building an excellent business that needs a different type of capital. So those are some of the things that like, we really want you to think about and look at before you apply, because they’re going to help you make that application a lot more successful. But having said that I, it’s very important to us that people don’t hold themselves back from trying and learning what they can.

We also, unlike I think every other accelerator out there, I don’t know anybody else who does this, but we actually give people feedback, if they ask for it. Every single person who gets rejected and wants to know why, we will gladly, it ends up being a huge time suck for the team, but we will gladly sit with you and help you see it from our eyes.

We, we have an interim step where we ask people to do a self evaluation. So that we’re not just going in blind and like telling you, hey, these like 70 people who you’ve never met think that you’re too early and that’s meaningless. So we ask you to invest in yourself first by, what do you think happened?

And then we confirm or deny some of the things that you’ve and we’ll add some color from the comments that we get on your on your application. So even for that there’s a huge value add in like putting your story down on paper and getting it reviewed by a very large group of like really smart people who do this for a living. And it allows your team to have a very structured way to give that actionable feedback at volumes,

If we’re not, if we’re not helping founders, then what are we doing here? You know what I mean? There’s a natural tension for us specifically for the female founders lines, there’s a tension between how selective venture capital tends to be with how inclusive we need it to be. And so this is why it’s important for us, but like Ready Set Raise is one part of what we do, but it’s not all of what we do.

So any company that does not get selected for Ready Set Raise still has access to a hundred percent of the rest of our programs, many of which are either free or like incredibly cheap. So like our goal is to accelerate the success of every founder who wants to do it. We don’t go so far to do that for you. You have to do it yourself. But we will enable it as to the best of our ability. We just can’t let go and go that deep with like every company you will hate the image of me on zoom after a while.

Elisa La Cava: [00:28:04] Yeah. Mike, what about you with the lab model? Who doesn’t fit working with a lab model?

Mike Fridgen: [00:28:10] The way I was thinking about this for us is it’s, everything is about idea and founder selection. And when you think about, from an idea standpoint, we’re really focused. We’re focused in AI driven applications. We’re focused in RPA and automation. We’re focused on future of work. We’re focused on things where our core MVL team has a track record of execution and experience, Madrona has an investing history and where Seattle has unique capabilities around talent and such. So we’ve narrowed our world around ideas selection. We have a process for vetting ideas within those areas. And then the next piece around founders, this is everything.

So you have to get the idea, right and then you have to put the right founder in that company for it to reach its, meaningful scale and see its full promise through. So we have six things I’ll go through them quickly. We look for in our, this is our founder framework founder selection framework.

One is domain insight. So do they have deep insight in the domain that they’re operating in related to that, are they obsessed about the problem? We have two great examples. One in Brian Camposano who joined us in a company called Stratify. He had been a CFO, he had experienced problems around budgeting and forecasting and Stratify specifically solves that. It was a perfect fit and match.

Another example is Justin over at Strike Graph, the CEO who had problems with SOC two compliance with his business and was driven to go solve that for others in a similar spot. So domain insight, and then obsessed about the problem. And then along with that is a real bias for action. And this is something we tease out, especially in a world where we’re talking to founders who have a long history working in larger companies. The pace of a smaller company is just much faster.

And some people are wired that way. They’re just wired as entrepreneurs and they’ve operated that in every context in which, in their careers, but others haven’t. So we really try to tease out that next piece which is bias for action. And then what goes well with that is rate of learning. You’re taking action and are you humble and grounded that you can learn quickly? You can take from all that effort the right takeaways to, to adjust your business. And then the last one around the core set is strategic judgment. Do you have vision for where to take your company?

And I’d say the most important thing and it’s wrapped in all of those components is, force of will, ambition, drive. We don’t talk about this enough. The people are building meaningful companies have a calling to do it. It is their mission. They can’t not do it. Because these are not people who are doing the math. If they were doing the math, the financial opportunity cost doesn’t make sense, personal sacrifice doesn’t make sense. Probability of success, super low. So people who are doing the math should run, not walk, from doing this. It doesn’t make any sense for them. So you have to be a little crazy, you have to have a calling, and all those other attributes are nice, but if it’s not wrapped in that ambition and drive, it really, isn’t going to amount to much.

Leslie Feinzaig: [00:31:19] Mike, this is all hitting a little close to home. I like to tell people about, you have to be crazy to do what I do. I feel like anybody who’s building something huge, you have to be crazy to live this life. That’s why I’m not scared of people seeing our deck and sure you want to copy it? Like you think you can, you think you can live like this, please? Let’s do it together.

Mike Fridgen: [00:31:41] And this is where it goes back to Elisa’s question around who should not do this. If you’re not crazy and that doesn’t sound like you that’s okay, but you probably shouldn’t do this. I think that to me, that’s the kind of like the long journey to that answer is yeah, if that’s not, you don’t put yourself in that situation. And if you can’t not do it, if you know all of that, you know what doesn’t make sense on paper and you’re still called then it’s, you should go do it. You should go through your life into it.

Leslie Feinzaig: [00:32:07] There is a pace to a venture backed startup that is different from the pace of a business building. So I come from a family of small business entrepreneurs and I think that there’s a lot of people who feel the calling to build a business to create value.

And like to encourage as many people as possible from doing it. And maybe once in your career or twice in your career, you can try to go this kind of high velocity route. But it’s not to discourage people from starting companies. I think that starting a company can be one of the most rewarding things that you will do with your life – create jobs and create value and build products and satisfy customers and make people’s lives better. I think that building a company is one of the coolest things that you can do with your life. And I want more people to do it and more people to try it.
Going down the venture capital route, you have to be willing to kill that company. That’s you have to be crazy enough to grow that company so fast that you would be okay if you failed, but you’re not going to stop trying, like you would rather fail than not try hard enough.

And that is not something that is comfortable, that it’s certainly something that you’re dramatically underpaid compared to the level of work that you’re doing. And as you’re describing the journal venture labs, I’m like, oh, imagine building a startup with health insurance from day one. What is that like? Oh my goodness. Crazy. But like an office space that is nice and people like their snacks there. That sounds amazing. Most of our lives in the early days are like spectacularly unglamorous. And it’s worse because every, like you got one article and everybody thinks that you’re flying high, but actually you’re like eating crap all day, right? ,Like you’re cleaning desks and like sucking up to people and writing 15 different blurbs about yourself, all of which give you imposter syndrome. So you really, you got to want to go big and I hope that you do. Hope more people do. It’s fun. Try it.

Elisa La Cava: [00:34:07] So when people go through your application program, or Mike, they, get in contact with you and you decide who to work with. Now, you’re surrounded, especially with Ready Set Raise, you’re now surrounded by eight different teams of people who, to your point, Mike and Leslie, are ambitious are driven, are, you have everything you’ve learned about them checks those boxes of how much they want to build this company and need to build this company and are willing to break down walls to do it. And so one thing I thought would be fun to share is show off something that has been successful for a team you’ve worked with either at MVL or FFA.

What’s an example of great success you’ve seen of someone who’s gone through working with your teams and your program and has achieved their goal? And how you know, or how have you personally really helped an entrepreneur get past a roadblock that they were facing?

Mike Fridgen: [00:35:02] I’m happy to share a story. Daniel Perrone who is a co-founder and VP of engineering at Chatative. So I’ll tell you where the story ends. Chatative just sold to MailChimp. It was a successful outcome and great for the team and shareholders, and that’s all wonderful, but I’ll tell you this is a company that had many near death experiences and for Daniel coming in, working with the MVL team in early 2016 there was a ton of uncertainty as multiple factors unfolded over time around, product and customer and the team and, a market around conversational commerce and messaging that really took some time to develop. A lot of companies didn’t make it that were funded high flyers over the years. But Daniel was really the heart and soul of this company and keeping it together, keeping a great technology team together, delivering a high quality product over time. Gaining real traction and ultimately to the outcome that company has seen just recently. And, and what it really highlights is that it takes, it does take a village. It takes a lot of people around the table who cared deeply and passionately , are passionate about making the company work.

Like it really does. It’s more than just the CEO or the board. It takes multiple people. And for this business, Daniel really brought everybody together through, everything we talk about the trough of sorrow, the near death experience and got this company to the other side. So he’s a recent success story, but it’s not something you read about or will see. We saw him when the times were darkest, have the biggest impact and keep the company moving forward.

Leslie Feinzaig: [00:36:44] That’s it’s like the trough of sorrow is like, just imagine it sounds like a thing in Game of Thrones, but it’s a real thing that every founder goes through and it really is that dramatic. That’s right. Get yourself a good founder therapist.

Let’s see, so some success stories. It’s just like such a huge privilege to go through this journey with founders and like seeing them come out the other side.

There’s a few notable stories. We had one company from the last cohort in 2019 that it’s a sexual health, so like a sexual wellness company. It’s super cool, huge growth, but a tricky space to fundraise and the founder is an unapologetic. This is a sexual health company and this is what healthy sex looks like. And she just closed $1.2 million and she did it $25,000 at a time. Can you believe what that takes like? That is a crazy person. That is what crazy looks like to not stop and raise $1.2 million $25,000 at a time. That is insanity. I’m incredibly proud of her, that she closed it and her growth is like just amazing this entire time. So that’s one that, that we just learned about.

There was another company in the accelerator last year, that was a local company here in Seattle, technically in Tacoma and Her experience. So this is the company called the Give In Kind, the founder is Laura Malcolm. Laura had bootstrapped this company for four years by the time she got to Ready Set Raise. She started the year like, 2019, she started the year, I’m going to forget her metrics, but like tens of thousands of users, 20% month over month growth. Reliably every month without spending a penny in basically anything. She moved her company to , she moved her company to Thailand, twice, to save on the costs of rent and childcare and development. This is how crazy she was.

And she came back to Seattle early 2019 with these amazing metrics. She started fundraising. She was trying to raise $500,000 on a 3.5 million valuation, which if you know anything about how far this company had gone, is like an insultingly low amount, and she couldn’t even raise a hundred. There was just like, nobody would give her a break. She came through Ready Set Raise and this was almost purely like a change in how to tell your story, drilling down in your business model so that you can demonstrate how it grows and how big the market is.

She ended up raising three times as much as she was aiming for, so she ultimately raised $1.5 million. Madrona participated in that round. I invested in that round. She like doubled or tripled her valuation. Six months later, she raised another million dollars as a bridge, because guess what? Her company was built for COVID and exploded.

And now she’s gearing up to raise her next round. She recruited from the accelerator, and ended up on Tech Crunch, the Today Show, like Digital Properties, like just all kinds of incredible goodness. And a lot, a big part of that was going through the journey with us, which, it’s just one of the most impactful, turnaround stories that I’ve had the privilege to be a part of. And, when you think about what that company does. So this is a company that enables people to support others through in kind help. So what do you do when somebody dies and you want to send a telegram or flowers? She has a marketplace so that you can send things that actually, that are actually helpful and not just, taking up space. So this year through COVID and through her growth, they powered 1 million instances of people helping each other. It’s just mind blowing to have been a part of that.

So that, that’s probably the certainly the most public story, because it’s all out in the public domain. There’s a lot more than I can’t talk about cause it’s coming up later, but that’s a very prominent one that I’m very proud to, I’m very proud to have co-invested with you guys.

Elisa La Cava: [00:40:45] Yeah, it’s such a powerful story. And you hope every company can find breakout success like that, with the help of such a powerful network that both of you can help bring. You touched on COVID. We are in a global pandemic. Why would anyone in their right mind try and start a company right now?

Mike Fridgen: [00:41:06] Yeah, I think this is a great time to start a company. I think there’s three reasons. Okay. So one is talent. If people are so compelled to start a company right now leave their comfy jobs and all the things that come with that, they must be real. They must, they must want it deeply, right?

This is not wantrepreneur time. This is like for the real people who are driven. And can’t cannot do it. So you have, I think for that reason the real strong founders step up in these moments. And I think also, this is also a time of people are drawn to mission.

I think a lot of you can tell just in our community and in our world, so doing something that they really love and believe in, I think there’s , people are putting more stock in that personally, willing to Millie to make those leaps. Second is opportunity. During these types of moments, people change behaviors.

If you go back to the 2007/2009 timeframe, that’s when Airbnb was built. They just had this massive IPO. They’ve totally changed the face of lodging. Go back to that moment. What was happening. People were looking to save money on lodging, as a consumer, people were looking to make some extra money, renting out an extra room in their home.

So there was a moment of change and a company seized that opportunity. And if, if you can go back and listen to their story. Talk about near death experiences. I mean that they had a very tough road, but they caught a moment of a behavioral change and they had a model that really added value within their marketplace, both sides of the equation.

And certainly we’re seeing that with more remote work and work will never be the same for us. So are we seeing massive behavioral change right now? Absolutely. There are new opportunities. We couldn’t have imagined a year ago. And then the third thing I’d say is there’s less competition. You have incumbents retrenching it’s again, there are fewer people taking the leap and trying to build companies.

So I think there’s this real sense of if you are passionate about a problem and you put your head down and in this, the next couple of years through this pandemic, as we come out of these things are building a great product, finding product market fit, demand will come back. So those, so then you’ll see the benefit of everything coming back your way as we emerge out of the pandemic.
So I think for the right founders and the right ideas, this could be a better time for, for some for some companies to be built.

Elisa La Cava: [00:43:23] Wearing my investor hat, there is so much optimism and energy in the private capital markets right now in terms of investors, venture firms wanting to invest and put a lot of money into new startups, against all odds with how crazy 2020 has been, I’ll throw out an interesting stat.

So much capital is going towards new startup creation, but there’ve also been a lot of reports talking about the lack of improvement and even backwards slide in fundraising that supports women entrepreneurs, black entrepreneurs, people of color leading these startups.

And so I’m curious, what is your approach, in the worlds that you live in labs and accelerators, how do you think about attracting founders and incredible teams to your programs and even how do you access founders outside of your networks? How do you reach this incredible population of people you may not be connected to now?

Leslie Feinzaig: [00:44:26] I think when we all went back to zoom and these open networks closed themselves and you have to like book time with people , you know, we also closed avenues for it, it the clique became more cliquey on a nationwide basis, number one. Number two, the entire economy has suffered a woman’s recession, right?

So like we see it in the economy at large that really the big losers in 2020 were women. And that’s partially because of the sectors that were most effected in terms of unemployment, but it’s also partially because we are, we are still the primary caretakers of our children and all of our kids came home.

I can tell you what it’s like to try to run a full-time business, while caring for two toddlers full-time in the household. I am lucky to have a partner that, that is an equitable partner in my house. But even then that was an untenable situation and I’m not surprised that we’re coming out of the next of the past few months of COVID with these very dramatic inequities.

And so the fact that venture capital has retrenched. Is both sad and also a huge missed opportunity for every investor. Okay. I’m off my soap box now. All of that said, I think of like the female founders lines.

Our purpose is to be the conduit of great deal flow for everyone. That’s what we want to do. Like we want every investor in the country to come work with us and to put companies in front of them. I don’t, I don’t, I don’t even know how to answer the question. How do I get away from my network?

There’s 2000 verified companies in the Female Founders Alliance already and thousands more people who are at idea stage or at like founder curious stage. So need the deal flow? Please. Come help us, come work with us, like we, nothing makes me happier than finding rounds that are being led by external investors for people who have been in our community for a long time.
So that’s our reason for being and, and that’s my open invitation. So, what I would like to see is for, for these VC firms to build systems so that they can bring diverse women, non binary people of color, so they can bring these founders into their traditional process and invest full-size rounds equitably. If you’re not. Making like building a real process to evaluate these companies and make them a part of your primary deal flow pipeline, then you’re not actually making a big change.

Elisa La Cava: [00:47:07] Very well said, Mike and Leslie, thank you so much for being a part of our podcast today. It has been incredible to talk with both of you and we’ll continue the conversation.

Mike Fridgen: [00:47:18] Thanks so much.

Leslie Feinzaig: [00:47:24] Thank you so much for having me. This has been super fun. This is like the most social life that I’ve gotten in weeks. So let’s do it again sometime.

Mike Fridgen: [00:47:27] Let’s

Elisa La Cava: [00:47:27] Awesome. Thank you.

Erika Shaffer: [00:47:29] Thanks for joining us for Founded and Funded. If you want more information on either Madron