Robotics Expert Sidd Srinivasa on Trends and What’s Ripe for Innovation

In this episode of Founded and Funded Madrona Investors Aseem Datar and Sabrina Wu sit down with robotics expert and University of Washington Professor Sidd Srinivasa to talk about the technology and sociological trends that are leading to innovation in the robotics space, where Sidd sees opportunities for founders, and why now is the time to pay attention to what’s happening in the space. Sidd also shares why he is what he calls an “accidental roboticist” and some of the hard-learned lessons from throughout his extensive career.

This transcript was automatically generated and edited for clarity.

Coral: Welcome to Found it and Funded this is Coral Garnick Ducken, Digital Editor here at Madrona Venture Group, and this week we are diving into a topic that I think we can agree everyone loves to talk about — robotics. George Devol created the first digitally operated and programmable robot back in 1954. And since then, we have been awed by the likes of C-3PO from “Star Wars,” Tipsy, the cocktail serving robot in Las Vegas, and Scout — Amazon’s delivery robots in Snohomish County here in Washington. Robots are transforming productivity, efficiency, cost, output, and product quality for companies, and many trends are coming together to push the move to automate from the pandemic, of course, which has pushed for a more touchless remote-first way of operation to an enduring labor shortage, to technological innovation in computing, AI, and machine learning to technology, infrastructure and data quality advancements that means the use of computer vision in real time is now possible. All of these trends come together to create almost endless opportunity for founders in the robotics space.

So, this week, investors Aseem Datar and Sabrina Wu are talking with robotics expert Sidd Srinivasa about all of this and so much more. Not only do we learn how Sidd is actually what he calls an accidental roboticist, but he outlines the areas of robotics that he sees are ripe for innovation and some of the hard-learned lessons from throughout his extensive career. With that, I’ll hand it over to Aseem and Sabrina to dive in.

Aseem: Hello everyone. My name is Aseem Datar and I’m happy to be here today with one of my fellow investors, Sabrina Wu and our guest of honor, Professor Siddhartha Srinivasa to talk about our favorite topic — robotics. So recently there’ve been a whole bunch of technological advancements in the field of robotics. That means that the world is prime for accelerated innovation and adoption, especially within sectors like industrial, manufacturing, logistics, and many, many more. At Madrona, we’re excited to see where entrepreneurs take it and the kind of companies that they buried using this technological building block per se. We wanted to bring in one of the foremost experts in robotics to talk about some of these recent trends and why now is the time to pay attention to what’s happening in the space.

Sidd, thank you so much for joining us and welcome to this conversation.

Sidd: Thank you so much for having me, Aseem and Sabrina. It’s a pleasure to be here and it’s a pleasure to chat about robots. One of my most favorite things to talk about.

Sabrina: Yes, Sidd thanks so much for being here. We’re really excited that you were able to join us today. You know, looking at your background, you were previously at Carnegie Mellon University for 18 years, and many of those years you were running the robotics institute. Thankfully we were able to steal you away from them and have you join the University of Washington, where you’re now an endowed professor focusing on human robotics interactions. Uh, You, of course, we’re also one of the First Wave Founders of Berkshire Grey. Now publicly traded on the New York stock exchange after having revolutionized the use case of robotics and AI for fulfillment at scale. So, you know, why don’t we start though with how you really got interested in robotics in the first place. Was there a pivotal moment for you when you were growing up that got you interested in the field or, you know, really what was it?

Sidd: That’s a tough one. I wish I could say that there was some origin story one day in which I had this revelation. But I’m actually a very accidental roboticist. It was in 1999. I was ready to go do a Ph.D. in mathematics at CalTech or in fluid mechanics at Cornell. The then director of the Robotics Institute Raj Reddy, visited IIT Madras, where I was doing my undergrad, and he happened to come home and was talking to us — my dad was a professor there as well. Then he asked me what are you going to do with your life? And I said, “Oh yeah, I’m going to do one of these things.” He said, “Nope, you should do robotics and apply to this robotics Institute place”— that, you know, back in 1999 was fledgling. I said, “Why not?” I still remember after I got my acceptance, my dad sat me down and said, “Son, you know what the future is? It’s turbines. It’s not robotics. Robotics is just a fad.” I still talk to him about that, about how turbines are doing compared to robotics. I’m sure they’re doing really well. But certainly, I’m glad that I pursued robotics. Then ever since, it’s been such a pleasure waking up every morning, working on robots. I just continue to be flabbergasted that people pay me money to do something that I would in a heartbeat do for free.

Aseem: That’s awesome. I thought that there was going to be some, “I was watching “Small Wonder” kind of story'” but maybe now, and who knows maybe your someday going to build robots that operate turbines, and you’ll bring the best of both worlds together. I think we have the most fun learning about backgrounds — these stories that don’t surface on LinkedIn. So, thank you for sharing that. As we at Madrona are thinking about robots, the one obvious question we sort of always come across in our minds as we think about the spaces and build a prepared mind kind of framework is why now? What’s changed in the world — robots have always existed in some way, shape, or form for decades. Following on that question, what are some of the driving factors that you believe are leading toward the acceleration, the investment in the field and ultimately toward adoption?

Sidd: It’s been a slow boil of robotics. I must say. It’s not that there’s been some step-function improvement. One of the things that has actually been hugely beneficial is Moore’s law. Computers are getting faster and faster day by day. Essentially the same algorithms that we used to run 20 years ago when I started my Ph.D., now take seconds to run instead of tens of minutes. I think that’s a huge win because one of the interesting things about robotics is that your clock is set by nature. It’s set by gravity, right? If you have a coffee mug that you’re trying to pick up and it starts dropping, then you can slow down time so that your computation reaches up to it. You just have to make it not fall. You have to grab it. I think the ability of our computing to finally catch up with nature and potentially exceed nature has been a huge tailwind for us. I think additionally, there are a few other factors. One is hardware, particularly perception hardware, which has gotten much better and much cheaper.

Some of that has been driven by the self-driving car industry. You know, back when I started my Ph.D., you had to pay tens of thousands of dollars to get a FireWire camera and then buy a giant board that then you would attach to your computer and have to write like custom software to even be able to grab pixels out of a camera.

That’s no longer true, things are much cheaper now. And that’s super useful. It’s super useful, not just to bring down the bond cost of your product. But it’s also super useful to prototype things. It’s much faster and easier to prototype things when parts don’t cost tens of thousands of dollars. That means that now we can very speedily go through several iterations of a robot or a robotic system, without necessarily having to think too much about like, oh, what am I purchasing right now, so you don’t have to prematurely optimize just yet.

Aseem: Yeah, that’s so interesting and so relevant. I remember the time when I was writing code on embedded systems, and you would think about memory management, right? Like you would think about how much memory is my algorithm using. And now when you graduate from college, you’re just commissioning another VM. You’re just buying more compute at cents on the dollar, right? I think that’s just fascinating in terms of where the world has gone. Sidd, what about networks? What about latency? Is there something to unpack there in terms of 1) time to making a decision getting faster and 2) what about advances in hardware itself — in terms of precision arms, in terms of actuators and so on? Is there something there that’s also a, I would say light tailwind that’s pushing this forward?

Sidd: I think one of the things that we’re seeing recently is that there has been a greater availability of compliant manipulators, you know, things that can work with and around people. We call them human safe, but essentially, they have the ability to feel forces and respond to them just like our arms do. And one of the advantages of that is that it transfers a lot of the complexity from the metal to the silicon. These robots that are not industrial manipulators, but combined manipulators are much more complicated to program and manipulate, but they are intrinsically safe and intrinsically more capable because they are able to feel forces and modulator their forces.

And I think our ability to wrangle this new piece of technology better is going to be a big unlock for the future. You’re already seeing how, if you look at even automotive, a majority of their manipulation or their assembly is done by these giant industrial manipulators that just pick and place. But a lot of their relevant and important manipulation, particularly of flexible things like brake lining or seat cushions need forces and torques and very careful manipulation. And that even now is done by people. That is particularly challenging. I think a future that I can see is the ability for robots to be able to perform those careful force-guided tasks that we humans do so effortlessly.

Aseem: I think that’s a great characterization of what things are coming together. You hinted a little bit at the industrial sectors and so I want to go down that path of how do you think about the market? What are areas that you see are ripe for robotics to play a huge role in? How do you think about industry focus? What are industries where robots are an obvious solution? And tell us a little bit about your thinking around the application of robots to those use cases.

Sidd: One thing I would say is that I have a bias to be a very full-stack roboticist. I like nails and I like to hammer them with whatever hammer is available. I think for me, there are a few criteria that are really important when trying to decide what the right nails are. One is how relevant is it? There are a lot of places where we may think robotics is relevant, but the technology that’s needed to do it is not there at all. Part of the reason for that is that we tend to anthropomorphize. We think, oh, this is easy for me so surely this must be easy for a robot and that’s sometimes true, but it’s more often not true. So, I think being able to find the intersection of something that robots are capable of doing and something that is of value to people is really interesting.

From a sort of vertical point of view, I think there are a few places where robotics has a lot of potential. And I think a lot of that is related to how complexity can be addressed via either changing the process path or changing how the work is done. One of the places that I am particularly excited about is being able to use robotics in farming or agriculture. I think that there’s tremendous potential in being able to merge the way food is produced, the science behind how food is produced, and the way food is harvested, and the way it’s packaged, and the way it’s sold. I think sometimes we assume that, and this is funny because we assume that strawberries have to grow in a particular way. But that’s not even true, right? Like we humans have manipulated the way strawberries grow and appear based on a lot of criteria that we care about. But you can imagine a world where we are optimizing those criteria, not just for our consumption, but also for the ability for robots to be able to pick them. The ability for robots to be able to identify them. The ability for robots to be able to package them. I think when you think about it holistically as my goal is to be able to produce really delicious food and to be able to automate its harvesting and delivery to a person, then you can really think of ways in which you can automate the entire process and think about how you can manipulate the entire process. So that’s certainly something that I’m interested in.

I think another piece that to me is really interesting that I continue to be fascinated by is last mile. You look around outside and outside any doorstep, there are packages and it’s interesting and challenging to understand how those packages can be delivered faster, better to you. Right now, it’s both labor-intensive and energetically inefficient. I don’t just mean packages, right? Even if you think about food delivery, I think of it as a full stack of how would we imagine the preparation and the combination of the food such that it continues to be delicious.

But also, something that can be automated and delivered on time to us. Some foods are actually very, very hard to deliver as we all know. Getting fries delivered at home or getting a nice, like Indian samosa delivered by let’s still crispy and not soggy is super hard. But I think part of that is because of the way those food items are created — because they were never created to be packaged in a box and delivered to us. They were created to be eaten hot off of the tava or the plate into our mouth. So, I think, thinking through how that entire process might work, I think it would be interesting and valuable.

Aseem: That’s so cool because it’s complimentary to our view we have yet at Madrona around, there’s a strong wave around, you know, COVID start us that, a lot of systems, processes now are moving towards more autonomous touchless, contactless as well as, high-quality outcomes, right? Because the more systematic approach you take, the more consistent quality comes out of it. An area that we’ve not talked about here but it’s interesting to us is also around the smart factory, the autonomous vehicle assembly. I think all these things coupled with the problem of like, you know, an aging workforce slash shortage of labor, we believe are just areas that are ripe for disruption, or I would say opportunity from a robot standpoint.

Sidd: Yeah, I completely agree with that. I also think that part of this might be to rethink. How processes are engineered. As an example, if you wanted a robot that would do your laundry, this is everybody’s favorite robot. Building a robot that like is in your home, that’s loading your washer, pulling it out, putting it into the dryer, taking it out, folding your clothes might be incredibly challenging.

But you can imagine a world where some entity takes all of your dirty laundry, takes it to some centralized location where there’s a larger physical space, which does all the cleaning for you and delivers it back to you as quickly as possible. By changing the way things are processed and turning it from many small things to one aggregated larger thing. I think you can get potentially a lot of wins. That of course demands that we, as humans, change the way we want to live to some extent. But there’s a lot of evidence to that. Right? In that, like, we’re willing to change the way we work, and we live if it is longer term more convenient for us. We haven’t talked about consumer robotics — robots in the home. I find that to be the most challenging market and something that like I haven’t particularly thought about because building something boutique for everyone’s home is way, way, way harder than building something that sits in its own physical space that can be controlled and manipulated by you and everything goes to it and comes out of it.

Sabrina: We have this debate a lot at Madrona as well of just where is the best use case for robotics? Is it in the enterprise setting? Is it in the consumer setting? And I’m curious, you touched upon it a little bit about the different verticals in agriculture and other, but to be a little bit more specific, if you’re a future founder you know, listening to this podcast today, what opportunities are you seeing? What white spaces are you seeing for a founder to come in? Is it specifically within verticals or applications or do you see it more on the hardware or software side? Just curious what your thoughts are around that.

Sidd: I do think that there is potential everywhere. My own personal interest has always been in trying to find a vertical opportunity and then do whatever it takes to solve that problem. Also specifically look at a place where automation is not necessarily a must have but can be a ramp function value add. I think if you start off with,” Hey, if I don’t build Rosie the robot, then I don’t have a business.” Well, then you’re in trouble. I think we want to make sure that there is a business case even with very limited automation. Even there like I would stair-step automation as oftentimes quality assurance prediction is much easier than actual physical manipulation. If you can actually have a value add that’s just about having sensors in your world that help you understand your process better or someone’s process better such that it can make it more efficient. That’s already a big win. And every single motor that you add to your world is an order of magnitude, greater complexity because everything breaks when you interact with the physical world. So, I think even there, when you’re starting to add automation, at first ask the question. Can you add automation that doesn’t move but that is able to monitor and enhance your process path through AI, computer vision, machine learning, and then subsequently use that to bootstrap how you might want to integrate physical automation in.

I think that’s a place where I think that there’s a lot of potential, right? Like even thinking about quality assurance. I think the biggest challenge with just inference and perception as a business is that you might get sharded by so many different applications. You know, someone has a light bulb that they want to assure, someone else has a PCB. Someone else has a salad that they want to know whether any of the produce is old or not. Someone else may have bananas. Someone else may have other things. So, I think the challenge that is in making sure that there aren’t so many different verticals that you’re chasing, that you end up doing a poor job of any one of them. I think this is the biggest challenge that I see in this particular space is that sometimes people either focus too much on a vertical and that’s too narrow. It’s one of the teeth in a comb and it’s too small or they try to build infrastructure and that becomes too broad, like, I don’t want a machine learning model. What I want is a managed service. I want someone not to hand me over like a piece of code. I want someone to solve my problem. My problem might be, I want to be assured that the chicken I’m selling are all of the right shape, or I want to be assured that the fries that I’m selling are all numbered, 37, there are 37 fries in each bag that I’m selling. I think being able to produce value while still being able to not be sharded by too many teeth in the comb is interesting and challenging. I don’t think anyone’s cracked that yet, but I think that there’s a lot of opportunity in that space.

Aseem: Yeah, you alluded to this, but I want to ask you this million-dollar question, or maybe it’s a millions of dollars question these days with how companies are performing and creating value. Hardware, robotics, or software robotics? Let me qualify that a little bit. There’s generally healthy tension on — do I solve a problem using hardware smarts and precision and building more complex arms, or do I actually solve it using the power of software and intelligence and ML models and CV? How should one think about that?

Sidd: I think about this a lot, I must say. The way I think about it is so first of all, I don’t have an answer. I just have a thought about it. I think that the constraints of the built environment often tell us what’s possible and what’s not possible. So, if you look at automating your kitchen, for example, it’s very hard to put belts and pulleys and tubes in your kitchen that plop food on your plate. Just the natural constraints that you created because it’s a kitchen that you want to use — it’s a kitchen that has certain dimensions — makes certain hardware choices possible or not possible.

The fewer constraints you have, the easier it is to solve using only hardware. You can use off-the-shelf mechatronics to solve a lot of these problems. Our beer factories and our Frito-Lays factories are great examples of solving a very hard food manufacturing problem effortlessly because we’ve removed a lot of the constraints that exist there. My personal taste is in looking at spaces where the constraints of the built environment make it nearly impossible to use off-the-shelf mechatronic solutions that compel us to use a combination of what we call robotics. Whether it’s robot arms or more complicated actuators and a lot of intelligence — computer vision, machine learning nonlinear control.

I think those are the spaces that lie at the intersection of things that are very valuable because no one has a solution for it and things that are fundamentally going to get better. Our compute is always fundamentally going to get better. So, I think to answer your question of like hardware versus software, there are many problems that can be solved using just hardware. But I think I gravitate towards problems, which are much, much harder to solve, either constraint wise or from a value proposition point of view, with off-the-shelf mechatronic solutions.

Aseem: That’s very cool. A slightly related question. There’s always this concern around safety, robotic operation, like human in the loop. You know, what happens when a robotic system like Tesla goes off the road and what’s the correction mechanism. I know Sidd, last time we chatted, you had a really cool posture on how you think about humans in the loop. I remember distinctly your comment about these things will fail. We know that they would fail as we are building and getting better. How should you design for that?

Sidd: First of all, I do agree that safety is a requirement. It’s not a nice to have, it’s a must-have. I think also that we have to assume that robots will fail. I always believe that it’s not the happy path. It’s not the YouTube video that you should be looking at. You should just be looking at all the times that the robot fails, right — the unhappy path. And I think that humans also have perceptions of robot capability based on happy path that they see. I think as an analogy if an alien being watched YouTube videos of 7- to 10-year-old children, they would think that their virtuoso pianists, incredible gymnasts, amazing singers, the best at math — can recite thousands of digits of Pi because they don’t see the unhappy path. Which is they’re running around kicking and screaming most of the time. I think it’s the same with robots, right? I think when people look at videos of robots, what they see is the happy path of robotics.

A lot of what I do is anticipate what the unhappy path will be and address it. This is actually hard because sometimes your robot doesn’t know when something goes wrong. This happens commonly, you know, the robot fails to grab something, and it doesn’t know that it’s failed to grab something.

So, there’s an observability question of we need to make sure that the robot knows that something has gone wrong. I think the second piece is around creating exception paths, such that you can gracefully fail. In most situations, you can gracefully fail. There are a lot of opportunities for correction, particularly if you own the full stack. A lot of the design engineering that is needed is to make sure that we are able to identify what the exception paths are and handle them. Actually, if you watch a high-speed video of yourself grabbing a coffee mug, you’ll notice that you’re just fumbling all the time. You’re failing and failing, and then grabbing the coffee mug. But all of that happens in less than 10 to 15 milliseconds. So being able to react to these in an elegant way is important.

In terms of human in the loop. One of the things that I believe strongly in is to be able to leverage human feedback whenever and wherever possible. You always want to build systems where you can either offline or even online annotate data, annotate the robot, such that it’s able to learn from its experiences as well as it’s able to learn from human supervision. I think that we have a lot of tools available now that help us do that. We have the ability to capture large amounts of data. We have the ability to send that data to annotators who are able to annotate it for us. I think that’s, to me, being able to build continual learning algorithms and being able to formalize that is a way to capture human insight without necessarily having to rely fully on it.

Sabrina: That’s fascinating. I’d love to pivot a little bit and have you tell us about your journey at Berkshire Grey? You were one of the first founders of the company, and now they are one of the leaders in providing robotic picking and packing technology used by companies like Target and FedEx. Can you tell us a little bit about how that came to fruition? What were the challenges you saw in the industry at the time? And I would love to learn a little bit more about your experience, scaling the business and ultimately making a bet on the future.

Sidd: I still have such warm feelings about my time at Berkshire. I really loved it. It coincided with my daughter being born. So, it was pretty epic time for us as a family. I see my daughter grow —she’s seven years old now. I can tell how old Berkshire Grey is based on how much Sameera has grown. Obviously, full credit goes to a lot of people. I’m just one of the people who is part of this journey.

But I think the central thesis was always this idea of being able to build a full robotic stack for automation. One of the things that we had observed was that there were some really amazing companies that were out there, but they were providing a Lego block that would attempt to fit itself into a giant jigsaw puzzle. Like Saying, “Hey, I have a nice picking system, or I have a nice system that can move a tote from one place to another.” You realize very quickly that to integrate a picking system with a very complicated warehouse management system that has so many inputs and so many outputs is much harder than building the picking system itself. Even if you have the best picking system in the world, your ability to integrate it with even one integrator is very hard and to think about like having to integrate with 10 or 20 of them, right? Those kinds of businesses were failing. Not because they didn’t have a beautiful, perfectly crafted Lego block, but it’s because it didn’t fit in the house. It was too much work to make it fit in the house. You have to take the house apart and put it back together. The sort of central pieces of Berkshire Grey was, give us an empty space. As an input, trucks come in and as an output, packages come out and, we won’t tell you what’s in this empty space and you don’t tell us how to control that empty space. It was a huge bet for us to think about automation that way. Because we had to believe that people would give us this empty lot. It’s a huge investment on people to give us this empty lot, but the positives were that we could fill this empty lot with whatever we wanted — people, robots, anything — and we controlled the entire experience. That was what we really sought to do. I must say, initially a large part of it was not automated, but still, the input-output relationships were maintained. I think over time as more and more maturity came about — and obviously, since I left Berkshire Grey, they’ve become even more mature on everything that they’ve been doing. I think you fill out more and more pieces of this Lego house, but you control everything that happens in there. So, I think that was a big learning for me. I think another learning is also that you know, when we were four people each one of us had to write code, talk to vendors, be a program manager, weld robots. I really enjoyed that. I really enjoyed that because I just love building robots. As the company grew to like 100 and then 200 people, I think we had to organize ourselves into various roles. A lot of fun too, but fun and a different way and potentially needed a different set of people. Obviously, I’ve done a few things since Berkshire Grey, and I realized that it’s almost like shedding skin. You have to have one skin and then you molt, and you shed that skin and then a new skin comes about. And you have to just accept that the people who were part of the original skin may not necessarily be the ones who are ready for the next one. The one after that. Some people might grow into those roles and those opportunities. But I think just acceptance of that was valuable.

I think another lesson that I learned was customers don’t want to tell you anything. This is incredibly frustrating for us because we just wanted to know what actually they wanted to solve.

If we knew what they wanted to solve, we could do it, but it took us a material amount of time before we earned sort of their trust for them to be able to open the door more and more. I think that was really interesting for us.

Sabrina: That’s awesome. I hadn’t heard that story before. You know, from your experience at Berkshire Grey, and as you mentioned, you’ve now worked with a lot of earlier stage companies and ideas since then, curious to hear what mistakes you’ve seen, people make along the way, and any advice that you have for new founders as they think about their journey in robotics.

Sidd: Oh, boy, I haven’t made a lot of mistakes. So, I think that in some ways the scars that we have are what help us not make those same mistakes again. I think that’s probably the only value that I provide is that I’ve made more mistakes in robotics than other people. So, I cannot just tell you what not to do. I think it’s really important to carefully think about what your minimum lovable product is. I cannot stress how important that is. I think that people fall in love with a certain way of doing something or fall in love with a certain piece of technology, and they forget that in the end it has to be valued and loved by your actual end customer. This was, frankly, a big struggle for me too because I’ve been building robots for so long that I have a way of building robots. I have to unthink that sometimes, because I don’t want to be stuck in that same rut. I think the other thing is that a lot of people who want to build robots come from software or AI or machine learning and forget about, or at least don’t have enough scars from, just long lead times for getting anything. I was actually just talking to somebody who is fascinated by how hard it was to do integration testing in robotics. They were telling me, “Oh, you know, with software, you just click this button and then you can run a, you know, integration tests on everything. How do you do that with hardware?” I was like, “Nope. It can’t be done.” You have to actually have a QA team that goes out and does these tests for you? You have to pay them a fairly significant amount of money to go do that and that takes a significant amount of effort.

So, I think there are certain mental models when you’re only building software that you need to undo yourself of. That said, there are other people who will only build hardware who want to build robots? You know, they build amazing, beautiful hardware systems and there too, there’s a failing because you believe that everything can be done with hardware ingenuity. Whereas, you know, I keep telling them, computers are free and instead of building a mechatronic way of, let’s say isolating a part, “Hey, just put a camera there and then it’ll tell you where it is”.

So, I think that robotics is a funny space, which requires you to know both hardware and software, and I think my advice would be make sure that you have enough people in the room who have enough scars of making enough mistakes in hardware and software and have the nuance to be able to.

Lead them to do the right thing. I think that’s been the biggest learning for me.

Aseem: Yeah, very profound. It’s almost like go hire the people who make mistakes so that the robots don’t make the mistakes. It’s amazing what we take away from this conversation. Hey, Sidd, I know that the only thing between you and dinner is us and ever since you mentioned samosas, I’m envisioning, you’re going to go off to a room it’s a Bat Cave in your house, you’re going to press a button and the robot is going to start frying a samosa.

Thank you so much for making time. I think there’s a lot of aspiring founders that we’ve talked to who are deeply interested in, you know, very passionate about this space and I’m sure they will take a lot away from this conversation. So, thanks for spending the time and thanks to those of you who tuned in.

Sidd: Thank you.

Coral: Thanks for joining us for this week’s episode of Founded and Funded. If you’re interested in learning more about Madrona’s investments in the robotics space, you can check out the show notes for Aseem and Sabrina’s contact information. Thanks again for joining us and tune in, in a couple of weeks, for our next episode of Founded and Funded with Snorkel’s Alex Ratner.

SeekOut CEO Anoop Gupta and VP of People Jenny Armstrong-Owen on AI-powered talent solutions, developing talent, and maintaining culture

SeekOut CEO Anoop Gupta and VP of People Jenny Armstrong-Owen

This week on Founded and Funded, we spotlight our next IA40 winner – SeekOut. Investor Ishani Ummat talks to SeekOut Co-founder and CEO Anoop Gupta and VP of People Jenny Armstrong-Owen about their AI-powered intelligence platform, the importance of not only finding and recruiting new hires but also developing and retaining employees within a company, and maintaining SeekOut’s own culture while seeing significant growth over the last year.

This transcript was automatically generated and edited for clarity.

Soma: Welcome to Founded and Funded. I’m Soma, Managing Director at Madrona Venture Group. And this week we are spotlighting one of our 2021 IA40 winners – SeekOut. Madrona Investor Ishani Ummat talks with CEO and Co-founder Anoop Gupta and their Head of People, Jenny Armstrong-Owen. SeekOut is one of our portfolio companies, and so we were very honored that our panel of more than 50 judges selected them for our inaugural group of IA40 winners. SeekOut provides an AI- powered talent 360 platform to source, hire, develop, and retain talent while focusing on diversity, technical expertise and other hard-to-find skillsets.

We led SeekOut’s Series A round of financing, and have worked with the team closely since before then as they fine tuned their initial product offering. The company has had massive success. And earlier this year they secured $115 million Series C round to scale their go to market and to build out their product roadmap, including powering solutions for internal talent, mobility, employee retention and the like- all topics that are Anoop and Jenny will dive into with Ishani today. With that, let me hand it over to Ishani.

Ishani: Hi, everyone. I’m delighted to be here with a Anoop Gupta, the CEO of SeekOut, and Jenny Armstrong-Owen, SeekOut’s head of people. SeekOut is building an AI powered talent 360 platform for enterprise talent optimization and was selected as a top 40 intelligent application. We define intelligent applications as the next generation of applications that harness the power of machine intelligence to create a continuously improving experience for the end user and solve a business problem better than ever before. I’m so excited to dive in today with Anoop and Jenny, thank you both so much for being here.

Anoop: Hey, Ishani, it’s wonderful to be here. Thank you for making time for us.

Jenny: Agreed. Thank you so much. It’s great to be here.

Ishani: So, I’d love to start out by going way back. Anoop, you were a professor of computer science for over 10 years, co-founded the virtual classroom project that quickly got acquired by Microsoft. In 2015, you left Microsoft to start the precursor to SeekOut. Tell us about what led you to the core talent problem that SeekOut is solving today.

Anoop: So, Ishani, when we left Microsoft, we left because you know, Microsoft was just an absolutely fantastic place to innovate, but what Microsoft legitimately wants you to do is to get on an 18-Wheeler and discover some big island, and we wanted to be on a mountain bike exploring opportunities because it’s such an exciting world out there. Given my background of running Skype and Exchange, actually the first thing we settled on, was Nextio, which was a messaging application. And the whole notion was that today people hide their email address and phone number because once you give it out, people can spam them. And we were not being so successful there, so we built an application called Career Insights. What Career Insights was about is you analyze all resumes in the world, and if you do that, then we can say, “Hey, if you are a UI designer at Microsoft, what are the next possibilities? Where are your peers going? And if they were going to Facebook, we could tell you where are the Facebook UI designers leaving for and doing next. So, it became Career Pathways inside that. And we said, “Oh, this is so useful for recruiters and talent people” that we pivoted there, and since then, our passion, our understanding of what is missing and what could be done better has led to our growth of SeekOut and talent acquisition and what we bring to the table.

Ishani: That’s so great. You sort of found your way to the recruiting market, to the recruiter as an end customer, but beginning with this problem of career pathing and pathways. It’s only something that’s amplified over the course of the last decade, let’s call it and it seems sort of prescient, but now that we look at this moment in time that seems like a very acute foresight.

Jenny I’d love your perspective. This talent environment has evolved so much in the last few years in ways that even Anoop and SeekOut could not have predicted with the pandemic and everything like that. We all see and feel the Great Resignation, the ongoing talent war in the tech world. You’ve been in talent teams for 20 years — what elements of this were predictable and what has taken you by surprise?

Jenny: Well, definitely what is very predictable is that the tech world continues to explode and grow. I read a statistic in the New York Times that the tech unemployment is 1.7%, which is basically negative unemployment. So, that’s not a surprise. What was not predictable was COVID, was the ability for folks to literally work from their homes. And it released the boundaries around what was possible for folks. And I think that’s one of the biggest challenges for organizations. And if you didn’t snap and adapt to that, you were not going to be able to meet your hiring goals.

One of the things that I love about being here at SeekOut, is going and finding people wherever they are. And so for us, we’re not restricted to Bellevue, Washington, or Seattle, Washington, and I think that’s one of the things, especially about our tool, that is so incredibly powerful. If you’re an organization that can embrace remote, that can actually make you so much better than restricting yourself geographically. That’s one of the things that I think has been a huge benefit for us. I think we’re embracing a new paradigm of relationships with employees, and it’s going to be a much more virtual relationship at times than it is a physical one.

Anoop: One of the things when we got into this, is we said, “Hey, digital talent, technology talent, is really important,” and what COVID did was, Satya said “Two years of transformation in two months,” right? So the accelerating rate of digital transformation, something we were focusing on, wasn’t there and that really increased the value of what we’re doing. The second thing that’s happened over the last two years is the emphasis on diversity. A lot of young people are saying, “I don’t want to join a company if I don’t see that they are embracing diversity, inclusion, and belonging in a genuine, authentic way.” We believe a lot of talent exists. It begins with how do you hire, how do you understand what exists in talent pools, and then being able to find them. The problem that leaders have — business leaders, talent leaders — is, they have good intentions, but translating those great intentions into concrete actions and results has been hard, and SeekOut really facilitates that.

Ishani: It’s such a good point on the market, evolving in some ways that you are able to control and some ways you can react really responsibly and control around. In other ways, that they are so out of your control where you sometimes tools can help you with that, tools like SeekOut, and sometimes you have to build that internally. It’s a culture thing. It’s an intangible. But let’s talk a little bit about the tool you’ve actually built. The way I think of SeekOut is it’s a product that’s evolved a lot from a talent acquisition tool to really a more 360 degree talent intelligence platform. But it didn’t start that way. Walk us through this journey from a talent acquisition tool to really an intelligence platform.

Anoop: My Ph.D. thesis was on AI and systems. My co-founder Aravind came from building the Bing search engine. When you look at all of these areas, AI is just a core part of it. So, to use an analogy — when you go to Google and do a flight search — UA 236. It understands that you are doing a flight search that UA is United Airlines, and you’re probably looking for arrival or departure times and therefore this is the relevant information. So, in a similar vein, SeekOut is a people search engine. So, we need to understand a lot about people. So, when I search for Anoop Gupta, our search engine realizes that Anoop is a first name and Gupta is a last name — and that it is a common name in India, right. So, we can get a lot of information that helps us. Similarly, normalizing for universities and companies is really important. SeekOut is very special in that it brings data from many, many different sources and combines it together. So, as we want it to go to technical folks and technical talent, and I’m just using that as an example, and you get GitHub, you see the profile on the GitHub, how does it match to the profile, you know, they might have LinkedIn and they are the same person. You know, it takes AI to figure that out. Then you want to look at all the code and information that you find, and you say, what is their coder score? How good a coder are they? Do they know Python? Do they know C++? So, we started bringing those things inside of it and all of those are inferred things. When we do security clearance, as an example, people don’t mention security clearance often, so what we go and look at is we look at job descriptions for the last many years, and we say did the job description say “This role requires security clearance and top secret or whatever?” And then we say, if there are enough of these positions where that is required at that company, at that location — then we say, you likely have security clearance. So, AI is fundamentally baked into the product, but we also take an approach that while AI is everywhere, it is designed as a complement to the human and not as a substitute to the human recruiter or sourcer that is there. That is an important principle for ourselves. The human is doing what they are best at, and all of the AI and logic are doing what they are good at to facilitate the human being more successful.

Ishani: We talk a lot about intelligent applications having a data strategy. And in order to augment workflows and make them solve a business problem really better than ever before. All of what you described is so well steeped in that philosophy around pulling in data from a host of public sources and then being able to really drive a better product around that and surface insights that matter. Customers love as one of the core features of SeekOut, the search functionality. So I’m sitting on top of all that data, the search just works. Can you talk a little bit about how you handle and process all of this data to just make it work like magic for a consumer?

Anoop: So one is, you’re very right. It’s actually a very hard problem when you have 800 million profiles and data coming from lots of sources, and the data is not static data — people are changing jobs, people are changing things. It’s all dynamic data, so, how one makes it work, how one makes it very performant? You know, my co-founder again — one of the movers and shakers behind the Bing search engine, and because we come from that background, Googles and Bings have to handle very large amounts of data, so how do you construct the index structures? How do you do the entity formation combined together? So that is core to what we do. And then on top of all of that big data, when you say can you clone Jenny and find us similar features? Now that is an impossible task. Because people may do the job with her humor, and her other parts are so hard to replicate, and the nice person that she is, then you have to do all of the matching, right? Or when you parse a PDF resume, how do you extract the skills or when you parse a PDF job description, how do you parse the requirements and what are the must-have requirements? What are the nice-to-have requirements? So, there’s just infinite amounts of problems, and we keep tackling them one at a time.

Ishani: It seems like you also, though, have to be so semantically aware of the context, right? That’s exactly what you’re talking about with the job description. How do you parse out requirements versus any of the other components? And how do you parse out whether someone might have met those requirements? So much is evolving in this field of semantic awareness, semantic search, and natural language processing. What are the kinds of underlying models that you use? Have they really evolved in the last few years as we see some of the transformer models or CNNs start to make a step-change in technology?

Anoop: Our models are continuously evolving based on what the users are doing, how they’re using it, and what their needs are. We do a lot of building ourselves, but we also leverage third parties. We also, you know, we have a notion of a power filter or something. So, if you think and look at synonyms, right? So, you say people who know JavaScript, they are a short distance away from TypeScript, right? Or people who know machine learning, there’s so many different kinds of words that people use in GitHub, whether it’s Keras or TensorFlow, PYTorch, whatever kinds of things, how do you find the equivalencies? You can find some things through correlations or other algorithms. What makes sense, what does not make sense. So, Ishani, there’s just a lot of different things that we are continuously doing. There are different kinds of algorithms and networks that get used for different types of natural language parsing and what we do. But I’ve always said from when we were at Microsoft, eventually, it is the data that you have because everybody publishes their algorithm and if you have the right data, you can do so much more. It is the data, and then the intelligence on the top that I think is really important. You got to have the right data. And then, of course, the right people and the algorithms to get to that intelligence.

Ishani: So, it really goes back to this concept of having a data strategy early. Being able to be nimble in evolving underlying technology and application intelligence. We always talk about garbage in, garbage out. So, being able to really understand where your data’s coming from, semantically parse and structure it to then be able to give to your end user as we call it magic.

Anoop: Yes. Yes. The problem with data is data is not clean. So, you know how you can efficiently clean up that data and use ML models to say these are extreme, exceptions and what to look at become super important.

Ishani: So let’s zoom out a bit. We’ve talked about this briefly, but over the last two and a half years or so, work has changed so much. Hiring has become hard. Engaging with employees has never been more important than it is today. Retention is hard, and SeekOut is doing really well in part because of that macro tailwind. From a company growth perspective, how did you recognize and take advantage of that moment in time?

Anoop: Helping companies get a competitive advantage, recruiting hard-to-find and diverse talent was a model for us from the very beginning. Then all these things happened and we’ve grown 30X in revenue over the last three years, our valuation is 50X where it was from three years ago and we have very high net retention and amazing customers. But we hadn’t thought of everything. We were focused on talent acquisition. That is how do we bring external people? Then with COVID, and the great reshuffle, the great resignation, many companies like Peloton stopped hiring externally and we said, what are the opportunities we can create for the people that are inside? So, our more recent focus on retention is really big. So, here’s the big story that we talk about. It is truly about the future of enterprise. We believe winning companies are realizing that the growth of people and the organization are inextricably linked. So, our mission has broadened, and it’s become to help great companies and their people dream bigger, perform better, and grow together. So that’s the mission and it’s a fundamental mission for every CEO and business leader and not just the HR leader. Then what we are doing is, you know, use technology to ensure that companies and talent are aligned and empowered and growing together. Or in another way what we’re saying is, “Hey, we going to help organizations thrive by helping them hire, retain, and develop great and diverse talent.”

Ishani: You know, SeekOut was really the right place at the right time to take advantage of, and actually really help people through that transition. But you have to be experiencing this internally as well? You talked about 30 X in terms of growth, but you also have triple headcount in the last year. I think you anticipate doing it again this year. How do you maintain, and Jenny, this is a question for you, culture and such a high growth environment?

Jenny: It’s one of my favorite questions I get it a lot in interviews. Culture has become probably the most important thing in a world where people are free agents, and they want to work at a place that aligns with their values and the way that they want to grow and develop with a company. So, I will share this. For me, I was looking at a number of different companies, and I met Anoop, and our first conversation, Anoop, I don’t know if you remember this, it was supposed to go for an hour. We went over 90 minutes, and in that moment, I knew that this was different. This was a different place. The culture here really does emanate from Anoop, Aravind, John and Vikas — the folks that started this company. From my perspective, our job is to make sure we don’t have cultural drift because we don’t have to fix our culture. Our culture is phenomenal. Candidates across the board tell us they’ve never had a candidate experience like this before. Everybody they meet with is super kind and helpful and collaborative. So for us, it’s really keeping our eye on these cultural anchors and making sure that we’re staying true to those.

So, in the hiring process, making sure that every single person who comes here, there’s a diversity interview where we talk about what is important to you in terms of diversity, belonging, equity, and inclusion. To Anoop’s point, people want to go where they feel like they’re going to belong. And then diversity can thrive, and equity can thrive, but you have to have that sense of belonging first. So for us, it’s very much staying focused on that. And everything that we do is around driving programs and opportunities and conversations that reinforce that. We start every Friday All Hands — in fact, I will admit, I suggested to Anoop early on that this was not going to scale as we grow. We’re 150 people today. But we start every all hands with 15 minutes of gratitude. I admit that it is absolutely scalable, and we’re going to continue to do it because it is by far the most favorite meeting of the entire week. That moment that we set aside to say nothing is more important for us in this moment than sharing our gratitude with each other. So I think that’s, for us, I feel super fortunate to be able to be at this intersection at a time where, it is tough, right? Companies are struggling to keep their culture intact in a world in which everything’s shifting so quickly.

Ishani: That’s such a good point that begins in the interview process and it continues in the onboarding process. Then it’s an everyday commitment to reinforcing your culture. I think people do have really good elements of each of those. But it’s rare that you find somebody so committed to all of them.

Jenny: It starts with Anoop.

Anoop: So, you know, so Jenny said it so well it comes from just a deep belief that people are the most foundational element to our success. We truly, believed that for ourselves. I’ll give you an example in a story. So we were looking for, I think the CRO, we had an executive search firm, and they said, ” Anoop you seem to be open to meeting a lot of people. Are you sure you have enough time?” And I said, ” I’m always there when it’s a people question. People are so important.” We have four OKRs now, these are the company goals. Our main goal is our people, culture, execution are our competitive advantage. I truly believe in that. It is not our AI knowledge. It is not we are smarter. It is that as a company, who we bring in, how we think, how we execute, how we collaborate, how we decide to disagree, yet, find commitment, you know, hold each other accountable, be nice.

We want to be the ones to show that nice people can win. Kind people, people with empathy can win. You don’t have to be a jerk to get ahead. So that is just a fundamental belief for us. And that has helped with our retention. That’s helped with our recruitment. That’s helped with the energy and their whole self that people bring to the company every day. And I think that’s a huge part of our success.

Ishani: The recruiting example of the CRO is so interesting because it really does delineate there is a real and important place for tools, but there’s certainly a line where that stops. Where you, Anoop, taking the time, you know, it wouldn’t be a little bit facetious as a talent optimization platform, if you didn’t take the time to bring in your own talent and really make sure that they fit the organization’s culture and the ethos, and they want to be where they are. So certainly, it has, there’s good continuity there with SeekOut’s mission and SeekOut’s product and how you operate.

But also, that there’s a role for the talent optimization platform that you use. And that presumably you use SeekOut, at SeekOut.

Anoop: So, you know, the other side story is. Every exec firm that I talk to, they give me some candidates and sometimes they are diverse, sometimes they’re not diverse. I say, well, let me find you some women candidates, let me find you some, you know, black candidates. They exist — you just don’t know; you need a better tool.

Ishani: It’s very much clear that there are roles, and these tools are augmenting how people do their jobs and in ways that haven’t ever happened before. But that it is an augmentation with learning, with intelligence, and with automation. But there’s still very clear roles for how do you build, for example, a culture like Jenny, right? And how do you maintain that? It also speaks to one of the product focus areas of SeekOut, which is on retention and really retaining your talent and looking internally. Jenny, talk to us a little bit about some of the strategies that you use, whether or not it’s related to SeekOut’s product, to maintain the talent and retain talent.

Jenny: Yeah. And thanks. I think it’s actually one of the reasons why, when I with Anoop, and he cast the vision for what SeekOut was going to be, was what got me so excited. As someone who’s led people teams now for way too many years to admit, I think getting folks in the door, getting them hired, is absolutely critical and important. I think growing, developing, and evolving as teams with folks who are committed and engaged, that is the job, right? That is every day. All day thinking about the people that we already have here. That’s one of the things about the enterprise talent optimization, where we’re going there, it’s going to revolutionize people teams. I mean, it’s like the best way for me after so many years of not having really effective tools on people teams —you know, we’re building a world in which they are going to be so complementary and it’s going to free people teams and leaders up to do what they do best, which is really about developing people.

So, for example, yeah, we’re 150 people. Well, we’re going to be implementing a people success platform. We’re going to be making sure we’re touching base on the things that matter the most to people, which is all about skill development, acquisition, growth. That’s fundamentally why folks will leave, right? Especially in the tech world, because they want to do different things, or they want to be able to stretch and grow. One of the things that’s awesome about startups is you have infinite ability to grow your people in whatever direction they want to, because the opportunity is here. It’s one of the reasons why I stayed at my first tech company for so long — I was able to do and grow and be so many things, and that’s one of the things that we talk to people about in terms of our value prop when we’re interviewing them is, “Hey, we are interested in you for this, but guess what? The world is your oyster at SeekOut and wherever your passion wants to take you, we are going to support that passion.”

Ishani: What you’re saying around giving people, the opportunity to grow is incredibly aligned with SeekOut, with the mission of the company. But also again, the product. It is also very hard to execute on. To say — we have a high-performing software engineer in our machine learning division who wants to go try out product management. Right? What are the tools that you used at SeekOut, and how do you actually execute on that?

Jenny: Well, I think that we are still in our nascent stages. We started last year at 40 people. We’re now at150 people. What I would say is building the capability in leaders to be aware and to be having these conversations and to be free enough to be able to think beyond the roadmap and the things that are getting done today. So, I think you have to hold both things tightly and loosely at the same time, if that makes any sense. And it requires a high level of change management and org development skills. Like we have to build whole-brained leaders who can look at our people with both things in mind. Executing on the deliverables that we have today, but fundamentally making sure you’re having this other conversation and that you’re driving that consistently in a way so that there’s never any dissonance. I think that’s the challenge? Creating too much space between those conversations or even having those conversations at all creates the dissonance. Then that creates the drag and the drifting. So, for me, that’s one of the things that we talk about a lot is who do we have?

Anoop, I would love for you to give your kind of ETO summary, because I think it is so compelling about the tools that we’re going to be able to provide. To your point, Ishani, I don’t have specific tools today. I mean, I can use my SeekOut tool, which is awesome, but we’re also small enough that we kind of can do a lot of this, you know? One-on-one but Anoop, if I would love for you to add onto that.

Anoop: You know, the cost when a great employee leaves is almost two X their salary for the annual salary, because it takes so much for the new person to come in and get up to speed, and meanwhile, the products are delayed and other things that delay whatever function they might have been going. So that’s why it’s so critical. And that’s why people care about it a lot. One of the things I say is that companies are deluged with data. There’s data flowing out of everything, but when it comes to data about their people, companies don’t understand the data is siloed. The data doesn’t exist. They may not have the external data. They may not have what they did before. And there is missing data. You know, your manager doesn’t know, Hey, in a large company like Microsoft or VMware or Salesforce where are the open jobs. What are the matching jobs? What are the skills? What does it look like? So, the data about employees is missing, the data about opportunities is missing, and then how do you take opportunities and data to match them to people? So, we can tell you about career path, if you’re going from a software development to a product manager, we can point you to people who made a different transition. We might be able to point you to people who made that transition, who might be from the same school, might be from the same gender and you don’t have to talk to the hiring manager, you can talk to people below and say, what is the culture of the team? Basically, we bring amazing data from outside. But then we take data from inside the company —this may come from management hierarchies. This may come from Salesforce. This may come from your developer systems and GitHub — and give you the most comprehensive thing. Then we engage with people. We really have two audiences. One of our audiences is the employee. Okay, who in a private secure way are mapping out their career, their growth, their learning journeys, their growth and development journeys. The second is the HR and the business leaders who are saying, we’ve got to deliver. There’s a strategy we want to do. Do we have the right talent? How does my group compare to competitors? How does it grow across the companies and how do we optimize?

So, we are super excited about it in any conversation that we are having, with CHROs, with other leaders, there’s a lot of excitement about what’s possible what SeekOut can do for them.

Ishani: So, SeekOut today is a really amazing example of an intelligent application for 360 talent optimization, not just the external component, but also internally. This speaks so much to both the environment and you’re reacting and being nimble around, how do you create offerings that people need? Without revealing too much, give us a peek into what the future holds for SeekOut.

Anoop: So future wise, Ishani, each of these broad areas that I’m talking about, there is immense depth in that. As we go deeper into it, there is a lot of work that is involved. So, if you look three to five years just executing on even the components that we have talked about and becoming a star We’re thinking you know, I believe this is a new category. HR don’t even realize what is possible in terms of data, the insights they can have, what they can do for their employees. So, there’s always a market and a mind shift that is involved and people are the slowest to change in some sense. So, I think our journey just making it, and if we do it right, and if we are the leaders, this is more than a hundred billion-dollar company, I believe. Okay. So there’s lots of growth and possibility, in this because talent is central to organizations and their success.

Ishani: Anoop and Jenny, we tend to end these podcasts with a lightning round of questions. So, we’ll go quickly through three questions that we ask every company that comes on this podcast. The first for both of you, aside from your own, what startup or company are you most excited about that is an intelligent application?

Anoop: So, for me, I would say, you know, some company like Gong or basically people who give you intelligence about how your salespeople are doing, how can you be better? What those calls are. Do the natural language analysis and all of that. So, it is just a hot topic, so it could be more, but that’s top of mind for me.

So let me just name that.

Jenny: I have an appreciation for Amperity and what they’ve been up to and what they’ve been doing. So that would be mine.

Ishani: Awesome. Both actually are also intelligent app top 40 companies. So, congratulations to Amperity and Gong. Outside of enabling and applying AI and ML to solve real-world challenges, what do you think will be the greatest source of technological innovation and disruption over the next five years?

Anoop: Certainly, you know, machine learning/AI will have a huge impact. But I think it will also be coupled with that it works on lots of data. We are instrumenting everything, on how the washing machine is being used, how your toaster is being used, how you’re driving. So, I think, the data and the machine learning together. But with the caveat of us making sure that it is not biased. Every tool in humanity can be used for good and it can be used for bad. But I think if we use these things intelligently, we can make a lot of good happen.

Jenny: Yeah, I would have to agree. I can’t say it any better than Anoop did. I think that making sure that technology is being inclusive as well. I think that’s a huge area of focus and concern.

Ishani: I couldn’t agree more. Final question. What is the most important lesson? Likely something you wish you did better, perhaps not, that you’ve learned over your startup journey.

Anoop: I will say, throughout my career, I always kind of knew people were important, and culture was important. You know, people would talk about it. But my appreciation and conviction that it is about people and culture as the fundamentals and foundations to success has been a realization. You know, if you asked me this question five years ago, I would not have answered it this way. You kind of take culture for granted, is not granted in the sense that it is already kind of baked for you in a larger organization. I think here, there was the opportunity to say — you get to define it — then it just made so much sense that this is the thing to focus on.

Jenny: That’s awesome, Anoop. I love that. I would say that for me learning that, you can put people at the top of the pyramid, and you can be very successful, is something that makes me incredibly happy that I’m getting the chance to learn and experience.

Ishani: Anoop and Jenny, it’s been so great to talk to you today about SeekOut, but also about people and how important they are in the organization. SeekOut is a great tool that enables you to find, recruit, and hopefully retain the best people that are going to build your organization. Thank you so much for taking the time and it was a great chat.

Anoop: Thank you so much for having us really appreciate the time.

Thank you for listening to this week’s episode of Founded & Funded. Tune in in a couple of weeks for the next episode with UW’s robotics expert Sidd Srinivasa.

 

Hugging Face CEO Clem Delangue and OctoML CEO Luis Ceze on foundation models, open source, and transparency

Hugging Face CEO Clem Delangue and OctoML CEO Luis Ceze

This week on Founded and Funded, we spotlight our next IA40 winners – Hugging Face and OctoML. Managing Director Matt McIlwain talked to Hugging Face Co-founder and CEO Clem Delangue and OctoML Co-founder and CEO Luis Ceze all about foundation models, diving deep into the importance of detecting biases in the data being used to train models as well as the importance of transparency and the ability for researchers to share their models. They discuss open source, business models, the role of cloud providers and debate DevOps versus MLOps, something that Luis feels particularly passionate about. Clem even explains how large models are to machine learning like what Formula 1 is to the car industry.

This transcript was automatically generated and edited for clarity.

Coral: Welcome to Founded and Funded. This is Coral Garnick Ducken, Digital Editor here at Madrona Venture Group. And this week we’re spotlighting two 2021 IA40 winners. Today Madrona Managing Director Matt McIlwain is talking with Clem Delangue Co-founder and CEO of Hugging Face and Luis Ceze Co-founder and CEO of OctoML. Both of these companies were selected as a top 40 intelligent application by over 50 judges across 40 venture capital firms. Intelligent applications require enabling layers, and we’re delighted to have Clem and Luis on today to talk more about the enabling companies they co-founded, which can work in tandem and are both rooted in open source.

Hugging Face is an AI community and platform for ML models and datasets that was founded in 2016 and has raised $65 million, and OctoML is an ML model deployment platform that automatically optimizes and deploys models into production on any cloud or edge hardware. OctoML spun out of the University of Washington and is one of Madonna’s portfolio companies. Founded in 2019, Octo has raised $133 million to date.

I’ll hand it over to Matt to dive into foundation models, the importance of detecting biases in data being used to train models, as well as the importance of transparency and the ability for researchers to share their models. And of course, how large models are to machine learning like what Formula 1 is to the car industry. But I’ll let Clem explain that one. So, I’ll hand it over to Matt.

Matt: Hello, this is Matt McIlwain. I’m one of the Managing Directors at Madrona Venture Group. So, let’s dive in with these two amazing founders and CEOs, and I want to start with a topic that’s important not only historically in software, but certainly relevant in some new and different ways in the context of intelligent applications and that is open source. Luis, I know your company, OctoML plays on top of your open-source work that you and your team, built with TVM, how do you think about that distinction between the OctoML role versus TVM.

Luis: Just to be clear, the OctoML platform is really an automation platform that takes machine learning models to production. That involves automating the engineering required to get your model and tune for the right hardware, the right choices, reasons, rights, other pieces of the ecosystem, and then wrapping it up into a stable interface that it can go and deploy in the cloud and in the edge.

And TVM is a piece of that, but TVM is a very sophisticated tool that is usable by, I would say machine learning engineers in general. So, the platform automates that and makes it accessible to a much broader set of skill sets, a much broader set of users, and then also pairs TVM with other components of the ecosystem. For example, when should you use a certain hardware-specific library is something that we automate as well. What we want here in the end, is to enable folks deploying machine learning models and teams deploying machine learning models to treat ML models as if they were any other piece of software. Okay, so you don’t have to worry about how you’re going to go and tune and package it to a specific deployment scenario. You have to think about that very carefully today with ML deployment. We want to automate that away and make that be fully transparent and automatic.

So why do we make Apache TVM open source? One of the things that TVM solves — we call the matrix from hell. And if you have a bunch of models and a bunch of hardware targets, and you are mapping any model on any hardware, this requires a lot of diversity, right? What better way to deal with diversity of these combinations of models to hardware than actually having a community that is incentivized to do that. For model creators and framework developers, by using TVM, they have more reach to hardware. So, creating this incentive and folks participating and putting all hands on deck and creating this diverse infrastructure is a perfect match for an open source. So TVM is, and will always be, open source and very grateful to that.

Matt: Clem, frame a little bit for us, how you thought about open source and how you’ve thought about it in the context of your marketplace.

Clem: Basically, at Hugging Face, we believe that machine learning is like the technology trend of the decade, that it’s becoming the default way of building technology. If you look at it like that, you realize that it’s not going to be the product of one single company, it’s really going to take collaboration of hundreds of different companies to achieve that. So that’s why we’ve always taken a very open source, collaborative, platform approach to machine learning.

And a little bit, like what GitHub did for software, meaning becoming this repository of code, this place where software engineers collaborate, version their code, and share their code to the world. We’ve seen that there was value, thanks to the usage of our platform, in doing something similar, but for machine learning artifacts — so for models and data sets. So, what we’ve seen is that by building a platform, by being community first, we’ve unlocked, for now 10,000 companies using us, the ability to build machine learning better than what they were doing before.

Matt: So, Clem, that’s really interesting. Maybe just to build on that last point. When people are trying to use these models, there is often some kind of underlying software that’s involved with the building, the training, the leveraging of the model. There’s also datasets — some that are open public data sets, some that are not. So, in that context, how do you all work with both the software and the data set elements that are more or less open in terms of leveraging your platform?

Clem: Yeah. So, something that we were pretty convinced about since we started working on this platform three years ago, is that for it to work and really empower companies to really build the machine learning, it had to be extensible, modular, and open. We don’t believe in this idea of providing an off-the-shelf API for machine learning — like having one company doing machine learning and then the rest of the world won’t be doing machine learning. It can be useful for a subset of companies, but the truth is at the end of the day, most companies out there will want to build machine learning. So, you need to give them tools that fits their use cases that fit their existing infrastructure that can be integrated with, parts of the stack that they already have.

So, for example, for private-public, what we’re seeing is that by giving the choice to the companies to pick which part they want to be private, which part they want to be public — what’s interesting is that it usually evolves over time in the machine learning life cycle. If you think of like the beginning of a machine learning project, what you want to do is maybe train a new model on public data sets because it’s already available, it’s already formatted the right way for you task. That gets you to a minimal viable product model really fast. Then once you’ve validated that it could be include into your product, then you can maybe switch to private data sources and then train a model that you’re going to only keep for your company and keep public. Maybe you’d use that for one year, two years, and then you’re like, okay, now I’ve used it a lot and we’re comfortable sharing that with the world, and then you’re going to move your model into the public domain just to contribute to the whole field. It’s really interesting to see the timeline on these things and how the lines between public and privates are probably much more blurrier than we can think looking at it from the outside.

Matt: That’s super interesting. At one level delineates between the public data sources that presumably people are free to use and the private data sources, which might have some proprietary usage, rights, and permissions. Maybe one other level in there is kind of the — I want to know what data was used in my model. So, kind of this data lineage piece, and how do you help people with that topic.

Clem: So, we have a bunch of tools. We have a tool that is called the data measurement tool that is very important and useful to try to detect biases in your data, which is a very important topic for us.

We have someone called Dr. Margaret Mitchell, who co-leads and co-created, the machine learning ethics team at Google in the past, and who created something called Model Cards that are now adapted to data, too, which are a way to bring more transparency into the data. Which for me, is incredibly important most actually on the data side than the model side, because if you look today at a lot of the NLP models, for example, if you look at BERTs, it’s incredibly biased, right? If you take like a simple example, like you ask the model to predict the word, when you say, “Clem’s work,” “Clem’s job is” or “Sofia’s work is.” You’ll see that the word that is predicted is very different if the first name is a male or if it’s female. You’ll even get on the woman’s side, the fist prediction of a BERT model is “prostitute,” which is incredibly offensive and incredibly biased. So, it’s really important I feel like today in our field that we just acknowledge that. That we don’t try to put that under the rug and build transparency tools, bias mitigation tools, for us to be able to take that into account and make sure we use this technology the right way.

Matt: Yeah, that’s incredibly powerful and helps illustrate beyond the sort of the first set of challenges of building machine learning models that there are these second- and third-order derivative challenges that are going be hard to tackle for a long time to come but are important as you point out to put on the table and acknowledge and work on.

Luis, I’m curious, you referenced this data engineer as your initial customer. Can you tell us a little bit of what you’re learning about the state of these customers and who this data engineer is? Who else might be key decision-makers and using, let’s even put aside like paying for your stuff, just wanting to use it?

Luis: I wouldn’t call them necessarily data engineer. It’s more like ML engineer or ML infra-engineer. So those are folks that think about how to deploy machine learning models today. But what we want here is to have any software developer to be able to deploy the machine learning models and use their existing DevOps infrastructure and existing DevOps people. Right? We are learning a bunch of things from them. First is that it’s just incredibly manual. There’s something that we call the handoff problem from, a model created by a data scientists or folks that create that model to something that’s deployable today involves many steps that are done by humans.

For example, turning a model into code is one step that’s done by hand. Then after that, just figuring out how you’re going to run it. Where are you going to run? It is something that requires a lot of experience with system software tools. If you’re going to deploy on Nvidia, you have to use a certain set of tools. You’re going to deploy an Intel, CPU’s are going to have to use a set of tools.

That’s done by different companies and different customers that have different names for this. Some of those are sophisticated DevOps engineers. Some companies call those machine learning infrastructure engineers, and as the maturity of ML deployment increases in these companies. I’m sure there will be a common name across them, but honestly, if you talk to 10 customers, you’re going to have more than 10 ways of calling those people.

Matt: Is this the same entry point for you, Clem?

Clem: Yeah. What’s interesting to me, the other day I was thinking about, if we want to make like machine learning, the default way of building technology — like software 2.0, in a way. It’s interesting to look at how software became kind of like democratized. If you think about software, like maybe 15, 20 years ago, and who was building software. You realize that maybe, obviously software got adopted really fast, but if there was one thing that was limiting is how to train a software engineer. Because it’s hard, to take maybe someone who was a consultant before, or like was working on finance and then train them to become a software engineer is hard work. It’s not something that they’re going to do really fast. What’s beautiful with machine learning is that, this wave of education of software engineers almost kind created the foundations to go much faster on a machine learning because turning a software engineer into someone who can do machine learning is much faster. For example, with the Hugging Face course, which takes a few hours to take, we see software engineers starting this course and at the end of the course, being able to start building machine learning products, which is pretty amazing. So when you think about the future of machine learning and the rates of adoption, one of the reasons why I’m super optimistic is that I think it’s not crazy to think that, maybe in four or five years, we might have more people able to build machine learning than software engineers today. I don’t really know how we’re going to close them. Maybe they’re still going to be called software engineers. Maybe they’re going to be called machine learning engineers? Maybe they’d have another name.

Luis: Maybe just application engineers because applications have any intelligent components, it should just be application engineers, right?

So, Matt I have a bunch of questions for Clem too. So let me know when we can ask questions to each other here.

Matt: Let me ask one question of you and then you can go. You’ve shared with me a few times that you think this whole construct of MLOps, which I guess arguably today is the cousin of DevOps is just going to go away and maybe this gets back to this, what are we going to call the people? It doesn’t really matter, maybe they’re all application engineers over time. Do you see MLOps and DevOps merging or is MLOps just automated away? What’s your vision around that Luis?

Luis: To be very clear for the rest of the audience here. So creating models or arriving at a model that does something useful for you, it’s very distinct to how we’ve been writing software so far. I know to Clem’s point, he put it very well. That part, I don’t know what name that has. I do not include that in MLOps. But MLOps, I mean, like, once you have a model, how do you put it in operation and manage it? That’s the part that whenever I look at it super closely today, it involves turning a machine learning model into deployment artifact, integrating the machine learning model process and deployment with the regular application life cycle deployments, like CICD and so on. And even monitoring a machine learning model once it’s in deployment. So, all of that, the people call MLOps. If we did it right and enabled a machine learning model to be treated like any other piece of software module today, you should use the existing CICD infrastructure. You should use the existing DevOps people. You should even use your existing ways of collecting data for things in deployment, like what Datadog does, and then put views and interpretation on top of that.

So, our view here is that if we do all of this we should be able to, once you have a model, you turn that into an artifact that you can use the existing DevOps infrastructure to deal with. So, in that view, I would say that MLOps shouldn’t be called anything else other than DevOps. Because you have a model that you can treat as if it were any other piece of software. So that’s our vision.

Matt: Clem do you agree with this vision?

Clem: Yeah, yeah — I think it is very accurate.

Matt: Good. Luis, what were you going to ask Clem?

Luis: First, what makes some models wildly popular? Out of these tens of thousands of models I’m sure there’s a very bi-modal distribution there. Do you see any patterns of what makes models, especially popular with the general audience?

Clem: It’s a tough question. I think it varies wildly based on where the company is in terms of like their machine learning life cycle. Like when they start with machine learning, they’re going to tend to use the most popular, more generic kind of models. They’re going to start with BERTs, with DistilBERT, for example for NLP. And then move towards kind of like more sophisticated, sometimes more specialized models for their use cases. And sometimes even training their own models. So, it’s very much kind of like a mix of what problem it solves, how easy it solves the problem, how big the model is. Obviously like a big chunk of your work at OctoML is, you know, to make the scaling of these models cheaper for companies to run billions of inferences. It’s all that plus I think one layer that we really created that wasn’t there before is the sort of social or peer validation.

And that’s what you find on GitHub. It’s hard to assess the quality of a repository if you didn’t have things to like numbers of stars, numbers of forks, numbers of contributors to the model. So that’s what we provide also at Hugging Face for models and data sets where you can start to see oh, is this model has been liked a lot. Who’s contributing to this model? Is it evolving and things like that? That also, I think provides like a critical way to peak models, right? Based on what your peers and what the community has been using.

Luis: Yeah, that makes sense. Peer validation is incredibly powerful. I want to touch on another topic quickly and then I’ll pass the token back, you mentioned public data versus private data. There was a really interesting discussion that I think parallels really well with the trends in foundational models. Where you can actually train a giant foundational model on public data and go and refine it with private data. Of course, there’s some risk of bias and we need to manage that. But I’d love to hear your thoughts and where you see the trends of, making the creation of foundational models or even the access to foundational models be something that’s wide enough to have many users refining upon that. We keep hearing about some of these models costing a crazy amount of money to train. Of course, folks are going to want to see a return on that.

Clem: Yeah. I mean, for us, transparency and the ability for researchers to share their work is incredibly important for these researchers, but also for the field in general. I think that’s what powered the progress of the machine learning field in the past five years. And you’re starting to see today some organizations deciding not to release models, which to me is something negative happening in our field, and something we should try to mitigate because we do believe that some of these models are so powerful that they shouldn’t be left only in the hands of the couple of very large organizations.

In the science field there’s always been this trend and this ability to release research for the whole field to have access to them and be able to, for example, mitigate biases, create counter powers, to mitigate like the negative effects that it can have. To me, it’s incredibly important that researchers are still able to share their models, share the data sets publicly for the whole field to really benefit from them. Maybe just to, to complement on that we’ve led with Hugging Face, an initiative called BigScience, which is gathering almost a thousand researchers all over the world. Some from some of the biggest organizations, some more academic — from more than 250 institutions to train ethically and publicly the largest language model out there. It’s really exciting because you can really follow the training in the open.

Luis: I’ve been seeing that’s fantastic to see that.

Clem: I like to joke sometimes that very large models are to machine learning, what Formula 1 is to the car industry. In the sense that the two main things that they do is first they’re good branding. They’re good PR, they’re good marketing — the same way Formula 1 is. And second, they are pushing the limits of what you’re able to do to have some learning. The truth is you and I, when we are going to work, we’re not going to use like Formula 1, because it’s not practical. It’s too expensive. And so that’s not what we’re going to be using. And not all like car manufacturers need to get into Formula 1 — like Tesla is not doing Formula 1.

Matt: I’m going to have to ask you about Charles Leclerc then. Because I have a feeling you might be a big fan.

Clem: Yeah, absolutely. But so, if you think about large language models, that way. And if you realize that the biggest thing is the learning that you get by pushing everything to the extremes, then it creates even more value in doing it in the open. And that’s basically what, BigScience it is kind of like doing this whole process of training a very large language model in the open so that everyone can take advantage of the learning of it. So, if you go on the website, if you check on GitHub, all the learning in terms of oh, it failed because of that, it worked because of that. We tweak that and completely change the learning rate and things like that. So that’s super exciting about that in the sense that it’s building some sort of an artifact for the whole science community, for the whole machine learning community to learn from and get better at doing these things.

Luis: I like the parallel a lot. One of the parallels that I like to think as well as the training these giant models should be equivalent to building a large scientific instrument, say the Hubble Telescope. We spent, a few billion dollars to put it in space and a lot of people can use it. On the commercial side you build a giant machine that you give people some time on to go and do things. I see the parallel, like as any huge engineering effort that’s done upfront to enable future uses. I think that’s the computational equivalent of that, where you have a giant amount of computation whose result is an asset that should be shared. So, in a way that makes sense.

Matt: What I’m trying to get my head around, not to extend this analogy too much is, every team has to build their car. And they don’t tell you everything that they’re doing to make it the fastest car on the track. So, what’s the right layer or layers of abstraction here. Open AI with GPT-3, there’s some things that you can work with and play with, and you can do prompt engineering and all, but there’s some things that are let’s call them in more of the black box, what has been additive about OpenAI’s efforts? And maybe touch a little bit on, with projects like BigScience, what are different and also needed to put it that way.

Clem: I think different layers of abstraction or needed by different kinds of companies and are solving different use cases. Providing an off-the-shelf API for machine learning is needed for companies that are not really able to do machine learning — who just need to call an API to get the prediction. It’s almost the equivalent of a Wix or a Squarespace for technology, right? People were not able to build software to write codes, they’re going to use kind of like a no-code interface to build the websites. And that’s the same thing here, I think. Some use cases are better served with providing an off-the-shelf API and not doing any machine learning yourself. Some others you need to be able to see the layers of the model and be able to train things, to understand things for it to work. So, I think it really depends on the use case, the type of company that you’re talking to. So, for example, the largest open-source language models are on Hugging Face. So, it’s like the models from Editor AI, it’s like the biggest T five models. And they have some usage, but it’s not massive to be honest. Even if they’re like a fraction of the size of the ones that are not public. So at the end of the day, again, it’s Formula 1 there are a couple of cars that a couple of drivers are building, but most of the things that are happening today are actually happening in much smaller models. From what I see, I don’t know if Luis is seeing the same thing. Even like Codex for example — the one that is actually used in production is much, much smaller than what the, like the big number it’s claims in terms of size of the models. I don’t know. Luis, are you seeing the same thing?

Luis: Yeah, similar thing even private companies, right? So, they develope their large models in private, and they go and specialize it — they have their own foundational models and specialized specific use case and deploy that to typically much smaller and much more appropriate for the broader, deployment. I think it’d be interesting to see in the spirit of building communities around it and having people refine on top of large-scale models, is creating broader incentives for folks actually go and pay the high computational costs of training these models. But once they make available, is there a way for them to share some of the upside that people get by refining those models specific use cases. Again, like how I repeat what I said before. I see this giant piles of computation involved in training these models as producing an asset, so that can be used in a number of ways.

Matt: That’s actually a great segue into business models. So, I take a pre-chain model that’s in the Hugging Face market, and I decide to use it and adapt it for my own purposes. How does that work from a business model perspective?

Clem: So, I think the business model of open source and platforms are always similar in terms of high level, in the sense that they like some sort of a premium model, where like most of the companies that are using your product, are not paying most of the time and it creates your top of the funnel? For us, it’s 10,000 companies using us for free. Then a smaller percentage of the companies that are using your platform are paying for additional premium features or capabilities. What we’ve seen is that there was definitely some companies that were obviously very willing to pay because they had specific constraints. When you think about enterprise, especially in like regulated industries. If you think about banking, if you think about healthcare. Obviously, they specific constraints, that make them willing to pay for help on these countries. So that’s one way that we monetize today. The other way is around infrastructure because obviously infrastructure is important for machine learning. And what we’re saying at Hugging Face is that we almost becoming some sort of a gateway for it in the sense that because companies are starting from the model hub, taking their models and then making decisions from them. We can act somehow as a gateway for compute for infrastructure. It is definitely like very much early days, right? As most of our focus has really been on adoption, which I think is what’s making us unique. But I think there is a growing consensus that as machine learning is becoming key for so many companies that machine learning tools, providers, are going to be able to build these big businesses — especially if they have a lot of usage.

Matt: And Luis, similarly, you’ve got a lot of demand and interest for your SaaS offering, as you call it. Maybe tell us a little bit more about that and what you’re seeing in terms of early usage and thoughts about business model.

Luis: Yeah, absolutely. We call it the OctoML platform. So, it’s model in, deployable container out. It’s a simple model people pay to use it. And then the pricing is a function of the number of model hard repairs and also the size of deployment. And what customers are paying for there really is first for automation, right? So often when you’re replacing what humans are doing when taking models to deployment. It’s turning to either using our web interface or an API call. Imagine instead of actually having an engineering team where data scientists say here’s a model and then the deployment folks like, oh, give me the container to deploy it. We put an API on that and run it automatically. It’s a different motion than what Clem just described because the open-source users of TVM — and these are folks that are more sophisticated, they’re using TVM directly. Some of them want to use a platform because they want more automation. For example, they don’t want to go and have to set up a fleet of devices to do tuning on. They don’t have to go and collect the data sets to feed TVM for it to do it’s machine learning, information learning things — all of that is just turn key. And we have, what I call altar loop automation, where you could give a set of models, get a set of harder targets and we solve the matrix from hell for them automatically. Given that there’s a huge difference between using TVM directly or the experience of the platform provides that in that case, it’s very clear. And the platform is a commercial product folks have to pay to use.

Clem: I’d be interested Luis, to hear you about how you see your relationship with the cloud providers is that mostly as, you know, potential customers, partners, competitors. How do you see them?

Luis: Oh, great question. And it’s a good segue here too. I see them as potential customers and partners. Less so as a competitor, and I’ll elaborate. Even though there is some specific points that might seem contradictory to them saying. First of all, so some cloud providers happen to have popular applications that they run on their own cloud and these applications use machine learning in that case, customers — I call that “sell to.”

But the bigger opportunity that I see here is “sell with.” And, from all cloud vendors, what they care about is driving usage in their clouds. So, the way you drive usage in their cloud is to make it very easy for users to get machine learning models, use a lot of computation, and make it really easy to get them on their cloud. So, in whether a service provides us turning models into highly optimized containers that can be moved around in different instances and the cloud vendors like that because it drives up utilization in their cloud.

So, in that case, we’re not seeing resistance. In fact, we’re seeing a lot of encouragement in working with cloud vendors as partners. So talking about selling to and selling with — now, of course, one of these cloud vendors have a service that also builds on TVM — Amazon has something called SageMaker Neo, which is an early offering of using TVM to compile models to run on Amazon cloud. We see our services differentiated in a number of ways. First, there’s some technical differentiation of how we do the tuning of the model to make the most out of the hardware target by using our machine learning for machine learning magic. But more broadly, I would say that the key thing that there’s no competition here is because we support all cloud vendors. And if there’s that one cloud vendor where they can’t be is to be the other cloud vendor at the same time. So, the fact that we sit on top of all these cloud vendors is a huge selling point that I feel likes makes the competition not be relevant. be

Matt: What I think is really interesting here is it’s like what are going to be the right abstraction layers to deliver value in the future? What are the kinds of application areas that are most exciting to you all for the future?

Clem: What I’m super excited obviously is that transformers are starting to make their way from NLP from texts to all the other machine learning domains. If you’re starting to look at computer vision, you’re starting to see vision transformers, if you’re starting to look at speech, you’re seeing like a WAV to VIC, you’re starting to see things in a time series. Uber announced that they’re using transformers now to do a time series for their ETA right? You starting to see biology and chemistry basically taking over all the science benchmarks. So it’s really exciting. Not so much because I feel like the other fields are going to get accelerated as fast as the NLP field did, but also because I think you’re going to start to be able to build much greater bridges between all these domains, which is going to be extremely impactful for final use cases. Let’s say, for example, you think about fraud detection, which is a very important topic for a lot of companies, especially financial companies. Because before, like the domains were very siloed and separated, you were doing it mostly with a time series, right? So, prediction on events and things like that. But now if you’re seeing that everything is powered by transformers, you can actually do a little bit of time series, but also NLP. Because obviously fraud is also predicted by the kind of texts that someone trying to fraud or like a system trying to fraud is sending you. And so you’re starting to see these frontiers between domains getting blurrier and blurrier. In fact, I’m not even sure that these different domains will really exist in a few years. If it’s not going to be all machine learning, all transformers just with different input, right? Like a text input or audio input, image, input, video input, numbers input. And that’s probably like the most exciting thing that I’ve seen in the past few months on Hugging Face. Now we’re seeing it out of adoption for computer vision models, for speech models, time series models, recommender systems. So, I’m super excited about that and the kind of like use cases that it is going to unlock.

Luis: I feel like it’s pretty clear today that almost every single interesting application has multiple machine learning models in them and as an integral part of that. And they’re naturally multimodal as well. There’s language models with computer vision models, with time series models. I think the right abstraction here would be you declare it, that you know, where your ensemble of models are and you should give it to the infrastructure. And infrastructure automatically decides where and what should run, that includes mobile and cloud, right?

So almost every single application has something that’s closer to an end-user and cloud counterparts and even knowing what should run on the edge, what should run in the cloud, that should be automatically done by the infrastructure. So, for us to get there, it requires a level of automation that is not quite there yet. Even like when you give a set of models and deciding maybe a given model should be split into two, where part of it runs in the cloud and part of it runs on the edge. So that’s where I think the abstraction should be. You should not worry about where things are running and how. That should be fully automatic.

Now on the — what is an exciting application? This is going to be more personal and Matt, that’s probably not going to be a surprise to you. I think there’s so many exciting applications in life sciences. It’s inherently multimodal — from using commodity sensors in smartphones to make diagnostic decisions. There is a lot of interesting progress there using microphones to measure lung capacity, for example, for using cameras to make skin cancer early diagnosis and things like that. All the way to, you know, much larger scale computations and everything that’s going on in deep genomics in applying modern machine learning models into giant genomic datasets, is something that I find extremely exciting and not surprisingly a lot of those use transformers as well. So what I’m seeing actually, I’m also very excited about what, Clem said. It’s fantastic to see what Hugging Face has been doing and showing the diversity of use cases, transformer models apply to. Just like, bring it a little bit closer in terms of the actual application, I feel like life science is the one that inherently puts everything together into a very high value and meaningful application of human health.

Clem: And something I wanted to add because it’s easy to miss it if you not following closely, but already today, if you think about your day, most of it is spent in machine learning. And that is something new you have to realize because maybe two, three years ago, there was some like over-hype about AI, right? Everyone was talking about AI, but there was not really a lot of final use cases. Today, it’s not the case anymore. If you think about you day you can, do a Google search — it’s machine learning-powered. You’re going to write an email — autocomplete its machine learning-powered. And you’re going to order Uber, your ETA is machine learning-powered. You’re going to go on zoom or this podcast, noise-canceling and background removal is machine learning. Going to go on social network, your feed is machine learning-powered. So already today you’re spending most of your day in machine learning, which obviously is extremely exciting.

Matt: Yeah, it kind of leads to a question what’s the technology, that’s the greatest source of disruption and innovation that you see in the next five to 10 years.

Clem: So, for me, it might not be a technology in itself, but I’m really excited about everything decentralized. And not just in the crypto blockchain kind of sense. So, for example, Hugging Face, we’re trying to build a very decentralized organization in the sense that decision making is done kind of like everywhere in the organization in a very bottom-up way rather than top-down. And I’m really excited about applying this notion of decentralization. I think it’s going to fundamentally change the way that we build technology.

Luis: For me, it is impacted by AI too, but it’s molecular level manipulation. It’s just everywhere. You saw Nvidia’s announcement of 4-nanometer transistor technologists, soon we’re going to see 2 nanometers — we’re closely getting to the molecular scale there. So, this is applied to manufacturing electronics, but then, going back to life sciences, our ability to design, synthesize and read things at the molecular scale is something that’s there today already. So just think about DNA sequencing. You can read individual pieces of DNA with extreme accuracy, in large part because of AI algorithms that decode very noisy data, but our ability to read individual molecules is there and the ability to synthesize them.

So, I hope I’m not being confusing putting these two things together. I think in the end, being able to manipulate things at the molecular scale has a deep impact on how we build computers, because computers are in the end dependent on how you put the right molecules together, and same thing applies to living systems. So in the end, we’re all composed of molecules and being able to engineer synthesize the right ones has profound impacts on life. So that’s my favorite one, yeah.

Matt: I don’t know how I can bring us back down after that. Basically, to synthesize it, the journey from atoms and physics to bits and computing, to bases and biology, you know, and the intersections of those worlds. And what’s going to happen in the future as a result.

I know you and I are both passionate about that and no doubt from what Clem is saying, too, and bringing in this point about decentralization as well. And how does that change the way that we can work and learn and discover together. Very exciting. Hey, is there a company, in this intelligent application world, maybe more up at the application level, as opposed to the enabling level where both of your companies are playing today, that you’re, you really just admire and think a lot of maybe it’s because of some of these cultural attributes about the centralization clam, or maybe cause of the problem that they’re trying to solve that you’d say, wow, that’s one of the coolest, private, innovative, intelligent application companies?

Clem: I recently talked to a Patricia from a Private AI, which to me is doing something really exciting because initially it sounds like a boring topic in a way, which is a PII detection, like detecting personal information in for example, your data or your sets. But I think it’s incredibly important to understand better what’s in your data, what’s in your model, in terms of problems, right?

Like is there personal information that you don’t want to share? Are there biases? I think of being much more like valuing forums and kind of like building technology with values rather than thinking that you’re just a tool, that doesn’t have value and kind of like the harm comes from people using your tool. I think it’s a very big technology switch that we’re seeing happening now with companies and organizations having to be very intentional about the product decisions that they take, to make sure that you reflect their values and the values that they want to kind of like broadcast.

Luis: One company that I think is doing really cool, intelligent applications is a company called RunwayML. That’s the ability of manipulating media in a very easy way using machine learning, really cool. Like for example, how you can very easily edit videos in a pretty profound way, that had been incredibly manual and hard in the past. Now turning that into something that’s point and click it’s pretty exciting. Also comes from the ability of training, large you know, models to generate visual content. So that’s one of them.

Matt: Let me bring us to kind of a wrap up with a question around your own entrepreneurial journeys. We have a lot of folks that are listening that are starting or thinking about starting companies. And if you could share with us, one or perhaps two, the most important lessons, things that you’ve learned, wished you knew better going into the entrepreneurship journey that might be helpful for others. I think that would be tremendously valuable to our listeners.

Clem: It’s a tough question because I think the beauty of entrepreneurship is that you can really own your uniqueness and really build a company that plays on your strengths and doesn’t care about your weaknesses. So, I think there are as many journeys as they are startups. Right? But if I had to kind keep it very general. I would say for me, like the biggest learning was to take steps, just one at a time. You don’t really know what’s going to happen in five years in three years. So just like deal with the now, take time to enjoy your journey and enjoy where you are now because I don’t know if Luis it’s the same, but you obviously look back at the first few years, and at the time you felt like you were struggling, but at the end of the day it was fun. Then, yeah, obviously to trust yourself as a founder, you know, like you’ll get millions of advices, usually conflicting. For me it’s been a good learning just to learn, to trust myself, go with my gut and usually it pays off.

Luis: It’s hard to top that, but I will say, for me, personally coming from academia, it’s been fantastic to see a different form of impact because as a professor, you can have impact by writing papers that people read and then can change fields or training students that go and do their own thing and become professors and so on. But then I see building a company out of research that started in universities and all the ways of impact that actually putting products in people’s hands. Some of the lessons that I’ve learned as you know, Matt, there’s massive survivor bias here, but you know, just picking people that you generally like to work with is incredibly important. People that are supported, they can count on people around you and feel like there is a very trusting relationship with the folks that you work closely with. It’s just something that is true in building a company. I’m sure it’s true in many other things in life as well, but I’m extremely grateful to be surrounded by people that I deeply trust. I have no worries about showing weaknesses and having to be always right. No, I think it’s great when you say you know what I did wrong, I’m going to fix it. It’s much better to admit if you’re wrong and fix it quickly than trying to insist that being right is important. But a funny thing that I’ve learned like yet again, is that we overestimate what we can do in the short term, but we underestimate them, what we can do in the long run. When putting plans together, we all have this ambitious things, we’re going to get this into the next two months. And you almost always get that wrong because you overestimate that. But then when you think about a plan that is a few years, like a couple of years out, you almost always, undershoot, right?

So, when I keep seeing this time, and again, and this is something that I think affects how you think about building your company, putting plans together, especially when things are moving fast. It matters a lot. So put a lot of thoughts into plans, writing things down a lot.

Matt: Well, you’ve heard this from me before Luis, but Clem, I love what you said too, because it is, the customer and the founder are almost always right. And the VC is often wrong. So, they’re trying hard. We try hard! Well, gosh, I’ve just so enjoyed getting a chance to listen to both of you and asking a few questions and, you know, excited to see where this world of enabling technologies like Hugging Face and Octo ML and the underlying capabilities around that go in the future. What that portends for the future of intelligent applications that are brought together and really can, I think, transform the world where I think you’re probably both right. That in the future, we’re not going to think about DevOps and MLOps, we’re not going to think about apps and other apps. We’re just going to have this kind of notion of application engineering. But there’s lots of problems to solve along that journey. So thank you so much for spending time with us. Congratulations again on being winners in the intelligent application inaugural class.

And we look forward to seeing all the progress in the future for both your companies.

Clem: Thanks so much.

Coral: Thank you for joining us for this IA40 spotlight episode of Founded and Funded. If you’d like to learn more about Hugging Face, they can be found at HuggingFace.co to learn more about OctoML, visit OctoML.ai. And, of course, to learn more about IA40, please visit IA40.com. Thanks again for joining us, and tune in in a couple of weeks for Founded and Funded’s next spotlight episode on another IA40 winner.

Starburst’s Justin Borgman on entrepreneurship, open source, and enabling intelligent applications

Starburst CEO Justin Borgman

This week on Founded and Funded, we spotlight our next IA40 winner – Starburst Data. Managing Director Matt McIlwain talks to co-founder and CEO Justin Borgman about how launching his first company was like getting a Ph.D. in entrepreneurship, and then they dive into the customer problem Justin saw that made him believe the time was right to launch his second — Starburst. The two discuss open-source alignment, why making use of cloud partnerships early, especially cloud marketplaces, can be so beneficial for startups, why Starburst had to change the name of its query engine from Presto to Trino, and Justin’s guidance for creating a future-proof architecture.

This transcript was automatically generated and edited for clarity.

Coral: Welcome to Founded and Funded. This is Coral Garnick Ducken, Digital Editor here at Madrona Venture Group. And this week we’re spotlighting another 2021 IA40 winner. Today Madrona Managing Director Matt McIlwain is talking with Justin Borgman, founder and CEO of Starburst Data, which was selected as a Top 40 intelligent application by over 50 judges, across 40 venture capital firms. We define intelligent applications as the next generation of applications that harness the power of machine intelligence to create a continuously improving experience for the end-user and solve a business problem better than ever before.

These applications require enabling layers. And we’re delighted to have Justin on today to talk more about the enabling company he co-founded in 2017. Justin walks us through how launching his first company – Hadapt – was basically like getting a Ph.D. in entrepreneurship and then through the customer problem he saw that led to the launch of his second company – Starburst. Matt and Justin discussed why making use of cloud marketplaces early can be so beneficial for startups. Why Starburst had to change the name of its query engine from Presto to Trino, and Justin’s guidance for creating a future-proof architecture. But I don’t want to give it all away. So, with that, I’ll hand it over to Matt and Justin.

Matt: Well, hello everybody. I’m Matt McIlwain, I’m a Managing Director here at Madrona Venture Group, and I’m just delighted to welcome Justin Borgman, Founder and CEO of Starburst Data. Starburst is really behind the popular Presto-based open-source project called Trino that helps customers carry out complex analytics on disparate distributed data sources. We’re going to talk all about that here with Justin and, you know, Starburst was selected as one of the top 40 intelligent applications, as an enabling application. And as you’ll see, Starburst is very much the kind of the core of that. And one of the things we’re going to dig into today a bit is at what layer of abstraction this next generation of data enablers actually lives. But before we get into all of that, Justin welcome.

Justin: Thank you, Matt. You know, we’re honored to be selected, and it’s a pleasure to be here with you today.

Matt: I think it would be just great because prior to Starburst, you’ve done some really amazing things, and I think they kind of inform ultimately how you got energized and excited to create Starburst. Can you, for our audience, just walk us through the time before Starburst?

Justin: Yeah, sure. My journey, at least in big data and analytics, really begins back in 2010. So, 12 years ago with the founding of my first company, which was called Hadapt. And that business was really based on some research by the folks who became my co-founders in that company, Daniel Abadi and Kamil Bajda-Pawlikowski who were a professor and Ph.D. student at Yale University and co-wrote a paper called HadoopDB. And the basic idea of back in 2010 that they had, and really were pioneers with this paper — was could we turn Hadoop, which was becoming the data lake. In fact, the term data lake was really created in the context of Hadoop back then — could we turn that into a data warehouse? Could you actually run SQL analytics on data in Hadoop? Could you connect BI tools? Could you use this effectively as an open-source data warehouse? And I was in business school at the time. I had a computer science degree previous to that. I was a software engineer for the first few years of my career before going to business school. I read this paper, and I was like, this is the coolest thing ever. I walked over to the computer science department and talk to those guys into starting Hadapt with me, which was really the commercialization of that research.

Ultimately, we built that business over four years and learned a tremendous amount in that process, both in terms of the market but also as an entrepreneur, as a first-time CEO. Even though I was in business school, maybe my Ph.D. I guess you could say was going through that first startup. Cause there’s so much that you learn through experience that you really can’t read about and almost can’t be taught without going through it. And some of the lessons of that startup that we saw, and this was particularly evident to me when the company was acquired by Teradata in 2014. So, I became a VP and GM at Teradata. And one of the things that became very clear to me at Teradata, which is by the way, like the pioneer of the enterprise data warehouse, right. They’ve been around 40 years and they kind of created this concept of a single source of truth, get all of your data into one place. And what I found was that despite their success none of their customers had gotten all of their data into one place. And that was a really eye-opening moment to me that centralization might not be possible. If the leading company for 40 years couldn’t do it, why should we expect we can do it now? That got me thinking about the future of data warehousing in a more decentralized fashion. And that coincided with me meeting the creators of an open-source project at Facebook called Presto at the time. And we began to collaborate — Teradata and Facebook — which may seem like an unlikely pair. We started working on how we could make Presto an enterprise-grade solution, to really allow you to query data anywhere. And that was what excited me about the technology. It was a query engine for anything.

Matt: Wow. Can’t wait to dive more into that. It’s interesting, your observation about Teradata, which really was a pioneer in data warehouses and sort of this point of how hard it is almost more from a sociological perspective to get all the data into one centralized place. Was there also, as you learned more about Teradata, a technological constraint? And what did you find what’s? I mean, congratulations. I mean, it was incredible to build Hadapt and to be acquired by one of the really, truly great technology companies. But what was the constraints there, too?

Justin: Those are great questions. By the way, I want to put an exclamation point on the sociological piece. I think as technologists, we naturally think that – it was a great engineer and leader who gave me the advice maybe 10 or 12 years ago. He said, “There are no technical problems, only people problems.” And that has stuck with me because I think as technologists, we often underestimate that. But to your point on the technical side, and I would say this is maybe just part of a function of the business model of the day, Teredata sold their product as an appliance. And an appliance for anyone listening, who doesn’t know what an appliance is. It’s just hardware and software combined.

And the goal of an appliance is well-intentioned — it’s to provide simplicity to the customer. You just plug it in and go. But it also makes it very inflexible to the world that’s evolving around you. So, I think that was one of the challenges you were buying basically high performance, almost like a supercomputer database, and you were paying a lot for that as a result. So, you really couldn’t take advantage of increasingly low-cost commodity hardware, and then even more so, you couldn’t take advantage of the elasticity and the separation of storage and compute that the cloud provides. Incidentally, that was, I think, what really helped give rise to one of your portfolio companies, which is Snowflake, right?

Which really was the first to take advantage of that storage compute separation.

Matt: Yes. And then to effectively say, well, I’m going to let the cloud be the kind of underlying resource around which I can build an abstraction layer on top of that, which in that case was a cloud-native data warehouse. But you have, in a sense, taking a different approach, complementary but different. Bringing us back to the story of the founding of Starburst — tell us a little bit about the Presto team, maybe build on the beginnings of that story of that collaboration and how that led ultimately to the formation of Starburst.

Justin: Absolutely. Presto was first created by Martin, Dane, David and Eric. They all are here at Starburst of course today, but they created it in 2012 at Facebook and then open-sourced it in 2013. And it was really, one of the goals for them was to provide a much faster interactive query engine compared to Hive, which was the previous generation also created at Facebook by the way. So, Facebook was very much pioneers in open sort of data lake, data warehousing analytics. But Hive was not fast enough. Presto was designed to be much faster, and it had this really interesting abstraction where it was truly disconnected from storage, meaning that they were agnostic to data source. So it wasn’t just a SQL engine for Hadoop. It was a SQL engine for anything. You could query my SQL, you could query Postgres, you could query Kafka, you could query Teradata, you could query anything. That was what attracted me to it and began the collaboration. And you’re absolutely right, I think this is one of the hidden secrets of the Presto/Trino history. Teradata played a really important role in those early days in terms of making it by companies outside of Silicon Valley — companies who need access controls and security enterprise features.

Matt: Enterprise abilities and your insight to listen to the customer and understand that those abilities were going to be needed, especially when you’re talking about data and accessing data, you know, it’s a little before your time. One of the very first companies that I became familiar with at Madrona, and it was an investment we’d already made when I joined in 2000 was a company called Nimble Technologies. And this was a precursor, and it didn’t work to be candid. And part of it was the sociological reasons, you know, who moves my cheese, who moved my data. It was trying to do it in a way that was distributed like Presto and Starburst do, but there was so much concern about the abilities – the securability, the reliability, the availability that at that point in time, I don’t think the technologies were ready either, created the challenges. What were the early use cases that you were seeing? I mean, I’m sure there were some inspired by Facebook that were just so much: is such a problem, I’m willing to go take the risk on this new open-source project in this company, building a hardened layer on top of it.

Justin: Well, there are really two categories of use cases. I think, where the Silicon Valley internet companies at the time were using the technology and still do today, the Airbnb, Netflix, Lyft, LinkedIn, Twitter, Uber, Dropbox were effectively using this as a data warehouse alternative. Those companies deal with such a volume of data they just couldn’t possibly fathom buying expensive appliances, let’s say, to store all of this data and analyze it. And so this became the way that they ran all of their analytics. So that was one category— essentially, I have my data in a data lake. In the early days that was Hadoop. In the more recent years, that’s probably S3 on Amazon or Azure data lake storage or Google Cloud Storage. So, you know, I’ve got really cheap storage. I can store my data and open data format so I can use different tools to interact with it. I can train a machine learning model using Spark, and I can query it with Starburst or at the time Presto, which later became known as Trino. And the reality is, that has been a very core bread and butter use case. Some call that use case now a Lakehouse, basically doing a data warehouse in a data lake.

The other category though, which I think you’ll find interesting Matt, and was a big reason why we built a business around this. We were seeing that fortunate 1000 global customers had a slightly different need that I think actually we could only uniquely solve, which was the fact that they had data silos. They had data in a variety of different systems. So, if you’re a big bank, a big retailer, big healthcare company, particularly regulated industries, you have decentralization, and that’s never going to change. It’s just impossible, truly for those types of enterprises. So, what we were able to do is essentially join tables in different systems and give you fast results.

So maybe you’ve got product data or customer behavior data in a data lake, and you’ve got billing data or finance data in a data warehouse. And you want to be able to join these two together to understand how the customer behavior is driving profitability or revenue, or what have you. So those are classically living in maybe different data sources, and we can execute those queries in effectively real time or at query time and give you fast results. And some people will say, well, that sounds a lot like data virtualization of 10 or 15 years ago. The big difference here is that Trino and Starbursts are actually an MPP execution engine. MPP just means massively parallel processing. So, it’s running on a parallel cluster, not just one machine. And because of that, you can get performance and scale that you could never get with those previous generations.

Matt: And I think that was the technological limitation back in the day is that you didn’t have this MPP capability that has subsequently come along. And for that matter networks so that you could do that in a distributed way.

Justin: That’s exactly right. People ask me, “well, what’s different now.” It is those two points. It’s MPP and its network bandwidth. You’re a hundred percent spot on.

Matt: And so what’s interesting, there is that enables these big institutions to create their own intelligent applications effectively, or their own intelligent analytics platform. They may not turn it into an application. They made us choose to use it for some in-house continuous insights. Is that where you have found more of those types of use cases in contrast to somebody using Trino and Starburst as a platform to build an intelligent application as a service?

Justin: So, in house, I would say was definitely where the business started. And, really began with power users who really understand the data that exists in the organization and just don’t have the ability to access it or query it. It really started with like doing exploratory analysis. I’ve got an idea and I want to go test my hypothesis. I need to run some ad hoc queries and get results. And my goodness is going to take me weeks if I have to go to the data engineering team to create pipelines and move data and get it into our data warehouse. And I need to iterate at a much faster speed. So that time to insight was a real driver of early use cases. The other driver was a need for accuracy or freshness I guess I will say because we allow you to effectively skip ETL and we try not to be too dogmatic about this. We’re not saying that ETL is dead or we’re getting rid of ETL. It’s just that we make it optional. And there are going to be cases where it may be advantageous to just connect to your data source and query it rather than moving it. And that gives you some really interesting optionality as you’re doing your analysis.

Matt: And ETL, of course, meaning extract, transform, and load the data. It’s a set of preparations that make the data more queryable and more usable.

Justin: Exactly. So, with the classic data warehousing model pioneered by Teradata and of course Oracle and IBM, it was all about extracting, that’s the E of ETL, your data from the different data sources you have, doing some kind of transformation to normalize it or get it prepared and then loading it into this new enterprise data warehouse.

And that process, that ETL process, ends up taking a tremendous amount of time, particularly human time in terms of creating those pipelines and maintaining those pipelines. Cause you might add a new field in a source database, and now you need to go add that field in your data warehouse, and you’ve got to keep these in sync and so forth. That’s part of the disruption, I guess you could say that we’re offering the market – the ability to skip that process where it makes sense and just query the data where it lives directly.

Matt: Say more about that? Cause I do think that’s one of the transformative capabilities of Starburst. I mean, how do you do that?

Justin: At a technological level, the easiest way to think about our architecture is that we’re a database without storage. That’s the way I explain it to people. For database geeks, they’ll understand the full stack, you know, there’s this SQL parser, cost-based optimizer, query engine and execution engine, and often a storage engine where you’re storing the data. It’s the storage engine piece that we intentionally don’t have. And that’s what gives us a different perspective on really how we design and build the system where we are intentionally reliant on the storage systems that you connect to. And so, we connect to a catalog that you have either a universal catalog — some companies have all their data in one central catalog, and we partner with Alation and Collibra and Glue Catalog on AWS and so forth. Or you’re connecting to the catalog of the individual source systems — Teradata, Oracle, Hive Metastore and Hadoop — and that is effectively how we know where the data lives. And then our engine is going to execute that query, push the query processing down to where the data lives as much as possible to minimize traffic over the network and then pull back what’s necessary to complete the query, execute the join in memory. And back to that point about MPP — that parallel processing is what’s able to give it the performance and scale. Often I have these conversations with customers who maybe are hearing this the first time and they say, “This sounds too good to be true. How can you possibly do this?” It is that MPP aspect that makes this possible in a performant way.

Matt: And in that sense how should I think about where the quote “file system” lives or the data and metadata system that even if I’m not having to deal with the underlying storage, I still need to know the metadata about all the data that I’m trying to access, so I can do a query.

Justin: Different customers have slightly different approaches here. Some leverage a third-party tool, you know, like Alation or a Collibra, which might be a solution. Others maybe are just joining between data lakes and might be leveraging the Hive Metastore. To me, the lasting legacy of Hadoop is really the Hive Metastore. That seems to continue to persist even in the cloud age, if you will. Or, if they’re in an AWS stack, Glue Catalog is a great way of keeping all of your metadata across a variety of Amazon products in one place, we can leverage that we can collect statistics. Collecting statistics is really important because it allows us to optimize the way we execute the queries when we know how the data is laid out and where it lives.

Matt: That’s great. Maybe also so that people that are not familiar with these things, is this a read-only capability or is there a write-back capability? So, I do a query. I can do some analytics. I want to write something back to those underlying distributed data stores. Tell us about that.

Justin: That’s a really important question. And for anyone in the audience — the reason that question is so important is that historically, if we go back to my first startup, in the land of Hadoop, if you will — the early data lakes, you really couldn’t write data effectively. You couldn’t do updates and deletes. It was really designed to be an append-only system. You just keep adding more data to it, but you couldn’t modify the data that existed. And that was a real limiting factor for a lot of use cases. For example, one of the most popular examples is probably GDPR or other data privacy rules that say, look, Matt wants himself out of our database. He doesn’t want us to keep sending him emails. You have to go in and then remove Matt from the database. And that was very challenging to do in a data lake world. And, and that was one of the reasons, quite frankly, that necessitated that you still had to have a data warehouse in your ecosystem. You couldn’t just do everything in a data lake. Now that has changed in the last few years in a very important way on two levels. On both the query and the storage level. And I’ll explain what I mean by that.

So, first of all, on the storage level. There have been new table formats that allow you now in a data lake to make updates and deletes. And they’re really three that are important today. There’s one called Delta, which was created by Databricks. And then later open-sourced. There’s one called Iceberg, which is definitely a fast-mover. And, I would say keep an eye on Iceberg. That was built at Netflix and is used by many of the internet companies today. And then there’s a third one called Hudi, which came out of Uber. And all three of these approaches effectively allow you to do updates and delete. So no longer is this a limitation of a data lake model or a lake house model.

The other piece is on the query engine side, where over the last year or two we’ve added that on the query side. So now you can write data back. You can do updates and deletes in a data lake. You can even create tables in other data sources. We have some customers that use us as part of a cloud migration, where they’re taking data out of a traditional on-prem data warehouse and moving it into a cloud data warehouse and are able to do that through a SQL query engine effectively.

Matt: I’m going to pop this back up for a second to the open-source history here. So it starts out and you’ve got Presto and then I’m curious how it became Trino and then how the Starburst complements and works with the Trino ecosystem. And what are the types of things you’ve built for the commercial product that are complementary to the open source?

Justin: First of all, I’ll just say for me, as I was thinking about starting my second company, open source was an important criteria of the type of business that I wanted to build, because I think there are some really inherent advantages both for the company and customers. The first is, you get the benefit of contributions from a wide audience. I think that really enriches the technology and allows it to grow and evolve at a faster rate than perhaps a single vendor pushing it forward. And what I mean by that is, for example, in the early days the geospatial functions were created by the ride-sharing companies. We didn’t build those. I mean, maybe we would’ve gotten to it eventually. I don’t know, but they built that. So as a result, pretty much every single ride-sharing company in the world now uses this technology. The other benefit is it gives you very broad distribution. It is open source and therefore it is free. Let’s not mistake the fact that it is free. And like anything that’s free, people are going to download it and start using it and use it on a global basis. So, we’ve had customers in Asia Pacific, Europe, Africa, you know, everywhere from the earliest days of the business because of that distribution.

That was one of the lessons, painful lessons for me, actually, I learned in my first business, Hadapt. Although it ran on top of Hadoop, we were selling proprietary software and when Cloudera introduced Impala and that was free and open-source, included with the distribution. So, you know, that was really hard for us because we weren’t getting the same number of looks or evaluations if you will. The last piece I’ll mention on why open source is, I think for customers, it brings the benefit of not feeling locked in to a specific vendor. And I think at least in the data world that has been a historical pain point – where the Oracles and even Teradatas of the world effectively increased prices became very, very expensive and customers fell kind of captive by their vendors. The notion of an open-source project offers customers the freedom to potentially say, you know what, this vendor isn’t adding the value that I want, but I want to continue to use the technology. They have that flexibility. And this is another reason why I think open data formats are really good for customers because then your data is not locked into a proprietary format either.

So that’s a little bit about the kind of why open source. Then you asked the question about sort of Trino and Presto and how we interact with the community today. So, the original Presto was created at Facebook, as I mentioned by my co-founders and the creators effectively left Facebook, joined us and, in the process, created Presto SQL. And so, you actually had two Prestos — a lot of people didn’t know this, but there was Presto DB and Presto SQL. Unless you were really involved in the space, you know, potato/patato, I guess, for, for a lot of folks back then.

Matt: Yeah.

Justin: But, the reality was that the community effectively moved with Presto SQL. That’s where we were investing. That’s where LinkedIn and the other large community players were investing. The name change was more recent. That was a little over a year ago, and that was driven by a trademark issue because PrestoDB was, was the first name. It was created at Facebook, even though it was created by the folks here. It was created while they were employed there. And the way trademark law works, of course, is your employer owns the IP that you create when you’re employed. And so, basically, PrestoSQL had to change its name. So Presto SQL became Trino a little over a year.

Matt: Got it. That’s super helpful. And I think also helpful for the audience. So now we have you know, this open-source Trino and maybe connect the dots between the underlying open-source capabilities and what Starburst is building on top of that.

Justin: First of all, I will say that the open-source aspect of this is still very core to what we do. And my co-founders are deeply involved in the open-source community. And there is a real, I would say philosophical aspect to wanting to make the open-source project a hundred-year project. I think we look at Postgres maybe as a good example of a database created many, many years ago that is still super relevant today. And in order to do that, you have to really have a vibrant community and you have to be making sure that you’re continuously improving it in a meaningful way.

So, the majority of the performance improvements, scalability improvement — those go right into the engine. The engine remains 100% open source. We build our product off of that open source. We do not have our own proprietary fork. some open-source companies do things that way, we don’t. We build directly off of the open source. And what that means is that effectively, when somebody adds a new feature or capability to the open source, our customers are able to pick it up right away because we’re building off of that. But it also means that we’re continuously invested in the success of the open-source project, because the stability of the underlying technology impacts our own stability for our own customers.

So, we invest a lot of time and energy in that and continue to do so both in terms of code quality and testing and code reviews and so forth.

Matt: And that’s a great mindset to have for both the longevity of the underlying Trino open-source movement, and I think it also serves your customers very well. I know this is a simplification — When I think about another company — Databricks is to Spark as Starburst is to Trino, right? And so, in the case of Databricks, they have done some things to supercharge performance to create a managed service and then create a lot of integrations that make it easier to move things in and out of its managed service in the cloud. And then there’s some of these abilities, these commercial abilities that we’ve talked about that kind of wrap around all of that, that seemed to be some of the core things that you get in Databricks that you wouldn’t get naturally, in this underlying Spark open source. Are those the kinds of things that you all differentiate Starburst from Trino on or complement Trino on? Or how do you think about that?

Justin: In many ways. Yes. I think there are probably a little bit of subtle differences to the philosophy. My co-founders are very adamant that we not have different engines, like core elements of the engine. We just don’t do that in a way that Databricks, I think, does in a few areas. So, you’re getting the same core engine on the open source and Starburst. So, that’s maybe one difference. But I think there are a lot of common themes there. I mean, I think really what we’re trying to do is make the technology accessible, useful, and valuable to customers both in terms of the enterprise features and capabilities they need around security or access controls or connectivity to various different data sources — performance as well. We have this notion of materialized views, which is pretty cool, as well as making it just easier to deploy.

We started with a product called Starburst enterprise that is self-managed, meaning customers have to run it and manage it. That’s been very successful, but we just introduced Starburst Galaxy, which is intended to be super easy. And the beauty here of two products, we debated this a lot. Like, are we just pivoting this? Or is this two products? What does this mean? And it is intentionally two products with different criteria. And what I mean by that is Starburst Enterprise is an always will be intended to be maximally flexible to deploy in your environment, whatever you have. So you’re a big bank. You’ve got Kerberos, you’ve got LDAP, you’ve got, Oracle and Db2, and you’ve got all these different things. We’re going to make sure that enterprise works for you within your environment. Galaxy is optimized for ease of use and time to value. It’s kind of the difference between like Linux and your apple iPhone, right? Like iPhone is meant to be useful to even your grandmother, hopefully. That even she can get value out of it. Linux, of course infinitely flexible. And The way we’ve kind of approached those.

Matt: Just to make sure that I and our audiences are understanding Galexy, how similar is the analogy to kind of Mango Classic and Mongo Atlas, where Atlas is the cloud version — it’s a managed service it’s ease of use kind of dimensions to it. Is that a good analogy or not?

Justin: It is. I think it’s probably one of the best analogies. I would say Mongo and, and maybe Confluent are probably our top-two role models in terms of balancing self-managed enterprise product and a cloud product that are similar and different in important ways. To the point about Mongo and that being a great role model for us, we’re lucky enough to have, Carlos Delatorre the former CRO of Mongo as an angel investor very early on. I’ve learned a lot from him over the years. And then, we just hired as our CRO a guy named Javier Molina, who ran sales for that Atlas product specifically. And one of the reasons we were so attracted to him was because he understands that go-to-market motion, and we think that’s going to be really big for us in terms of the market. Today we do very well in the large enterprise. We think that this technology could be applicable to thousands of customers. Not, not just hundreds of customers.

Matt: That is a great hire because that Atlas product from a sort of a standing start four years ago now represents more than half of all of Mongo sales. It’s just incredible to see the team at Mongo in that way. But maybe take us a little bit into the decision to and then launch Galaxy and how that’s additive to both your existing customers and how it opens the door to some new customers.

Justin: I will preface by saying, and some of the audience may know this, we started Starburst as a bootstrap business. We didn’t actually raise venture right away. And that’s important context because, while I loved that part of the company’s history, and I recommend that to any founder who’s able to get a business off the ground that way initially. The one drawback, of course, is you don’t have the capital to go make huge technology bets necessarily. Right? We were funded by revenue. We were a profitable cash flow, positive business. So the moment that we did raise venture, a couple of years into it, that’s when we said, “Okay, we’re going to build this SaaS solution.” So, one part was like, it takes capital to build a SaaS solution, and that was an important trigger. The other motivator though, which kind of gave us confidence that this would work out, is that we were very early and making our self-managed product available on AWS Marketplace. And the reason I mentioned AWS Marketplace is that was a self-service way of buying and consuming our product.

Now it’s not a SaaS solution per se, but it is a self-service way of transacting, deploying via a CFT, and using our technology. What was very interesting to us, is we launched that when we were, I don’t know, 20 people, bootstrap, tiny little company, nobody had ever heard of us. And we did it mostly just because we thought the marketplace was interesting. It wasn’t necessarily any genius idea. Although, it looks maybe genius in retrospect. But what we saw with that was an organic adoption. We didn’t market our marketplace offering. We didn’t push our marketplace offering. We weren’t doing any outbound back then and we saw more and more people start to use it. What was really interesting about that was not only was it growing on its own without us really doing anything to it, also it was a very long tail of customers. And that was what kind of told us. Okay, we’re obviously having a lot of success with Fortune 1000, but there are companies using our stuff that I’ve never heard of before. And that’s super exciting.

Matt: Yeah, that’s awesome.

Justin: And so, for us, that was the signal that there was a market beyond what we were seeing at that point in time.

Matt: I would imagine that is, especially since it was a self-service offering, so, you know, somebody had to have some degree of technical acumen to kind of stand it up. And run it. Were they most often then running it in the cloud, I guess in theory, I could buy it in the marketplace and then operate it on my own desktop, too.

Justin: I think that’s true in theory, but, but you’re right, that it required some heavy lifting on their part. It was a real effort A) to find us and B) to deploy this, to stand it up and manage it all on their own. To us, it was kind of like, imagine how many people might use it if we could make this easy. And that was the motivation for Galaxy.

Matt: Say a little bit more about how it’s been working with, you know, the big cloud service providers to go to market with Galaxy.

Justin: It is actually available on all three major public clouds. And we designed it that way from the start. But, they’re great partners. And look, I’ll preface by saying of course there’s going to be some coopetition and overlap because every cloud provider has an enormous portfolio of products. So there are overlapping points. But at the end of the day, the field organizations, the sellers, just care about driving consumption of those clouds.

And that’s what we do. You know, the more queries you run on Starburst, the more AWS compute or Azure compute or Google compute, you’re consuming. So, they’ve been great to partner with that way. And the marketplaces, going back to that point, turn out to be a great transaction vehicle. I can’t stress this enough for any aspiring entrepreneur. Get your Ph.D. in marketplaces. And by the way, there are a lot of ecosystem partners now that help you with that, like Tackle for example.

Matt: Are you finding, I mean, I’m sure there are differences. Is there naturally better alignment with your products and the kind of customers you’re trying to reach, between the different cloud service providers or is it too early to tell?

Justin: Well, I think we partner with all of them. We enjoy working with all of them. If I was going to maybe single one out just a little bit, I would say that I think Google’s philosophy or approach to the market is interesting to me and well aligned to some of our own fundamental beliefs.

And what I mean by that is I think Google, as the challenger in the market, acknowledges, understands, and embraces that they’re never going to own all of the data in the world. And that’s important at least important, I think for me, and important for customers, because they’re willing to approach the market from the standpoint of not necessarily saying everything has to be in Google or, creating more freedom for customers to basically do different things in different clouds. They’re much more, I guess I would just say, open to the fact that it’s a heterogeneous world, which is a very core aspect of what we believe.

Matt: And so, to that end, do you find that whether it’s in Google or otherwise, that when I deploy Galaxy in somebody’s cloud, and I’m running it in the cloud, that I’m querying data sources that are back on-premise as part of the queries that I do. Or is it strictly the data that’s living in different data repositories or in a data lake in the cloud?

Justin: It can be either one. And that’s part of the power I think for customers is that flexibility, that optionality, that ability to modernize their architecture before they migrate. We’re not saying don’t migrate, but we’re saying we can give you access to everything you want today. And then you can migrate at your own pace, which I think is very powerful. And just to close on the Google point. We just announced a partnership that allows Google customers to leverage big query, to access data in different clouds, different data sources on-prem, etc., effectively extend beyond Google. And I think that’s an important thing to note as well.

Matt: I do think that this whole thing about data and really workload migrations, you referenced it a couple of times. You know, you and I have lived in the cloud and data world for decades now, and it seems like it’s still relatively early innings, but what are you seeing from a customer perspective, especially the enterprise customer, on their, kind of cloud migration journey?

Justin: I will preface by saying it varies. Some are further along in that journey. Some are just getting started. I think one of the biggest things that I find interesting and really try to drill into when I’m talking to customers is to what degree they think they are going to consolidate all of their data into one place. Because what I have seen, and I think this is a risk, so if there are any potential customers listening to this, keep this in mind. Customers have a fantasy, and I can understand why you would like this fantasy of saying, “Oh cool, we’re going to turn off all of these different databases that we have, this total mess that we have on-prem, and we’re going to just get it all into one cloud data warehouse.” And I’m not picking a Snowflake. I’ve heard the same story repeated with every one of the cloud data warehouses out there. My word of caution would be, we’ve seen that movie before over 30 or 40 years, and to the greater extent that you do do that, the more you’re beholden to a particular vendor, which is going to get expensive for you. What I like to remind people is, all these new companies are very charming and attractive today, but Larry Ellison was charming in 1979, and how many of you are still charmed by him today would be my question.

Right? So just be careful in that. Think from a long-term perspective. Create a future-proofed architecture — those would be just some of our pieces of advice.

Matt: That’s good advice. It might be one thing to say I’m going to retire your old employer, you know, Teradata data warehouse in favor of a more modern cloud-based data warehouse. But I do think it’s highly unlikely and ill-advised to think that you’d ever have all your data in one data store to rule them all as it were for all kinds of reasons. But that I think brings us to this data cloud alliance. I note that Google is a part of that, Databricks, Confluence, several others. What was the genesis? What are you trying to accomplish there in service of your customers?

Justin: It’s around trying to create openness, freedom for customers to be able to work in an interoperable fashion across the different clouds that they may participate in. This is another maybe fantasy that I’ll mention. A lot of companies, I think particularly those early in their journey, will say, no, no, no, we’re just doing one cloud. We’re not doing multicloud. We’re just doing one cloud. It’s all going in cloud X. And, the reality is that changes very quickly. One of the fastest ways that that changes is when you make an acquisition. You just bought a new company, and they’re cloud Y, so now your multicloud, whether you want it to be or not. We have a vested interest in trying to give customers choice and the freedom to operate across these different clouds. And I think Google is very forward-thinking in embracing that as well.

Matt: That leads to an interesting question. I mean, I like to think that, infrastructure as a service or kind of the core elements of cloud service providers, was an abstraction layer effectively on top of hardware. To kind of oversimplify it. But is there a new abstraction layer emerging that maybe we could think of as data lakes, data lake houses, cloud-native data warehouses, or how do you think about that layer of abstraction relative to infrastructure, and then relative on top of it to applications?

Justin: Abstraction is such a powerful vehicle I think for application developers, anyone building an architecture. Abstraction gives you a lot of freedom to change the components of course, underneath. For us, what we’re obviously most interested in is being that abstraction layer for SQL-based access to all of the different data sources that you have, so that you have the freedom to change those pieces. Maybe it’s Hadoop and Teradata today and tomorrow it’s S3 and Snowflake — great — so long as your applications, your BI tools, everything that speaks SQL are pointing to Starburst. And then you have the ability to make those changes underneath, around storage and effectively commoditize storage, which is also very powerful for customers. And there is an emerging name, or a category, if you will, that we’re pretty excited about, which is this notion of a Data Mesh, which is really sort of speaking to this idea of decentralized data and creating a mesh that, that sort of works across that. Now that is back to one of the first things you said on this podcast — there’s a sociological component to it. In fact, the creator of this concept is a woman named Zhamak Dehghani. And if anyone’s interested, I encourage you to buy her book. Actually, we’re giving it away for free on our website. But she describes it as a socio-technical sort of movement, if you will. Which is to say it is people, process, and technology altogether. But we think we can be the technology to enable that. The people and process side is very interesting because part of what that enables is the opportunity to decentralize not just access to data, but a decentralized sort of decision-making and ownership of the data. So, this is kind of like a way of putting more power in the hands of the data producers — the ones who are responsible for that data and know the data the best to also participate in the creation of data as a product that can be shared and consumed by others in the organization. So, it’s a really interesting philosophy one that we see certainly gaining a lot of attention, and I think be gaining more and more momentum over time.

Matt: We touched on some of the technological reasons around the why now. Is there evidence of the, why now on sort of these more sociological dimensions and how much has the fact that we all had to live in a digital-only world for a while? And we now believe, I think we all do, that we’re going to be living in a hybrid working world — has that been part of the why now that sociologically people are saying, “Hey, we just gotta change so we can do more of a decentralized approach,” or am I just kind of speculating here?

Justin: I think that’s right. I think the things driving that in my view are, are first of all, just complexity of data sources. We’ve got more data. Everything is collecting data, right? As we’ve digitally transformed, and the pandemic has only accelerated this, we have now more opportunities to analyze and understand and make data-driven decisions. But to do that, it’s just not scalable for everything to always run through one team, one person, one brain. And that’s where I think decentralization is a great way of giving you velocity by delegating and putting more power in the hands of individuals. And I think consistent with that, we operate in an ever more competitive world and companies have to adapt quickly. The speed of adaptation genuinely impacts your top line and your bottom line. So, I think these are some of the things that are driving serious thought around it.

Matt: That’s well said. I have just a couple of fun questions as we wrap up here, but I just wanted to see if there’s anything else that we didn’t cover. That’s important about what Starburst is trying to accomplish.

Justin: I would just say, you know, at the end of the day, what we’re trying to do, and I hope this doesn’t sound cheesy, but we want to do the right thing for our customers. We want to be on the right side of history. And that was one of the things that motivated me to found Starbursts in the first place was that my time in the database industry, up to that point, I met a lot of customers who just felt very trapped, locked in, they weren’t choosing their technology choices. Those choices had already been made and they were stuck with them. They were living with them. Philosophically this notion of freedom is just core to what we’re trying to do. I think you’ll continuously see that in all of our design decisions. We want to be able to support multiple data sources, multiple data formats, be able to operate anywhere. We want customers to be in control, and we think that’s a slightly different perspective than many in the database world at least have historically had.

Matt: I think one other thing that I was curious about is use cases around taking that freedom and distributed, decentralized approach, and then using some of those data sources to help train models from a machine learning perspective. And are you seeing kind of a growth in those kinds of use cases that Starbursts could help unlock?

Justin: Yeah, absolutely. And I always try to be clear that obviously, we don’t do machine learning. We don’t train machine learning models, but I think we’re a very important partner to that process because you need the data to train the model and the more access to data, the better your model is going to be. And so, getting data is the first step to ML and AI. And we think we’re an important part of that.

Matt: We agree. And that’s why we were delighted that, I mean, it was a very strong endorsement of you all being in this enabler bucket for the Intelligent Application 40, and we certainly see and know about those kinds of use cases. A fun question is outside of your company what’s a startup that you’re most excited about that’s related to this broader world of intelligent applications.

Justin: That is a great question. I think Clari is a really interesting example of this. Clari is really the interface that I’m using to understand my business because it ties in all the important aspects of what we’re doing and provides not only a great summarized view, but also predictive analytics about where we’re going to end up. And particularly as you scale, being able to forecast is so critical, especially in the path to an IPO, which we hope will be able to achieve in the next two to three years.

Matt: So. You’ve now been a successful founder, built two companies, Starburst is still a work in process, but you’re doing incredible things. What’s a lesson or two for those in the audience that are either on their own startup journey or considering the startup journey that had been really valuable to you, whether they’re kind of from your first-hand experience or advice from others or a combination.

Justin: Oh man. There’s a lot. I can say there. I think first of all, the advice that I give to any entrepreneur at any stage in the journey, particularly those that are just thinking about maybe being an entrepreneur. I think the single most important attribute is strictly perseverance. You have to have a high pain threshold and a willingness to push through that pain because is not for the faint of heart. It is not easy. I think just some people are built for that. They have the stubbornness, the drive, to push through that, and others get overwhelmed by it and bogged down. So, that’s kind of like a look inside yourself type of thing to evaluate and consider. The piece of advice I will give that I heard myself. I actually asked a now public company CEO founder, “Does this ever get easier?” Because as you’re building, you always think like, okay, at some point, like, I’m just, it’s just going to get easy, right? Like I’m going to be relaxing on the beach, this thing’s going to run itself. And he said, “No, it’s just different kinds of hard.” And that stuck with me because particularly as you scale, every new chapter has been a new challenge and in a totally different way. That’s part of what’s amazing about startups, I think, just from like a personal growth perspective. You are always having to improve yourself, scale to the next level. And so, that really stuck with me. It never gets easier, just different kinds of hard.

Matt: Different kinds of hard. I love that. I don’t know if I’ve heard it phrased that way. So, I really appreciate you sharing that with us, Justin, and yes, you’re always building these new skills for the next phase of the journey, too. And having to let go of things that you did more of so that you can empower others and scale the organization. It has been an absolute pleasure, Justin, visiting with you and incredible what Starburst has accomplished and your role as an enabler of all kinds of data analytics, including those things that go into building machine learning models and intelligent applications. So, thank you very much for taking time with us today and look forward to seeing the continued success of Starburst.

Justin: Thank you, Matt. I sincerely appreciate it. It’s really been my pleasure.

Coral: Thank you for joining us for this IA40 spotlight episode of Founded and Funded. If you’d like to learn more about Starburst, they can be found at Starburst.io. To learn more about IA40, please visit IA40.com. Thanks again for joining us and tune in, in a couple of weeks for Founded and Funded’s next spotlight episode on another IA40 winner.

RunwayML Co-Founder Cristobal Valenzuela on the Intersection of Art and Technology

RunwayML, Cristóbal Valenzuela

In this episode of Founded and Funded, Madrona is launching a special series to highlight some of its IA40 winners, starting with RunwayML, which offers web-based video editing tools that utilize machine learning to automate what used to take video editors hours if not days to accomplish. Madrona Investor Ishani Ummat speaks with Co-founder and CEO Cristobal Valenzuela all about where the idea came from, how he decided to launch a company instead of joining Adobe – and even how TikTok fits into all of this. Listen now to hear all about it.

This transcript was automatically generated and edited for clarity.

Coral: Welcome to founded and funded. This is Coral Garnick Ducken and this week we are launching a special series to spotlight some of last year’s IA40 winners. Today, Madrona investor Ishani Ummat is talking to Cristobal Valenzuela about the web-based video editing tool RunwayML. It all started as a research project inside NYU using an algorithm to stylize and colorize images in Photoshop, but Cristobal now sees Runway as an opportunity to not simply improve how things have commonly been done, but rather leapfrog an entire industry. And the company secured a $35 million Series B in December to work toward that goal. With that, I’m going to just hand it over to Ishani and Cristobal to dive into it.

Ishani: Hi everyone. My name is Ishani and I’m delighted to be here today with Cristobal Valenzuela. The CEO of RunwayML. RunwayML is building a web-based real-time video editing tool with machine learning and last year RunwayML was selected as a top 40 intelligent application by over 50 judges across 40 venture capital firms. We define intelligent applications as the next generation of applications that harness the power of machine intelligence to create a continuously improving experience for the end user and solve a business problem better than ever before. Runway is a story I love — re-imagining creativity with machine learning. And I can’t think of a more interesting conversation to kick off our IA40 spotlight.

Cris, thank you for joining us today.

Cris: Thank you for the invitation. I’m super happy to be here.

Ishani: I’d love to start off with your thesis project actually at NYU. That’s sort of the basis for this company. Take us back to that time. What led you to this idea? Why did you start working on it? And did you know you wanted to start a company?

Cris: So, the short story about Runway is — I’m from Chile, and I moved to New York five years ago. And the reason I moved was at the time, I was just fascinated with things that were coming up in the computer vision world. I’m coming from an econ background and had no experience building deep learning models before, but the things I was seeing specifically around computer vision generative models like five, six years ago, it just blew my mind, and it blew it so much that I just decided to move to study this on a full-time basis at NYU.

So at NYU, I basically spent two years just doing a deep dive into how to really take what was happening, specifically after I would say ImageNET and AlexNET a bunch of really impactful and big milestones in the computer vision world started to emerge, and apply them inside creative and art domains. And the reason was , I think we’re just touching the surface of what it would really actually mean to deploy algorithms inside the creative practice. The reason I wanted to explore those was just, I knew something was happening. I knew something was about to happen, but yet no one was doing it.

So why not just do it yourself? Um, no, I didn’t know if I wanted to start a company, but by the time I was building the thesis, it was more of an organic direction that we took that I realized that my research was way more impactful than I originally thought of. Specifically, when you’re doing research in an academic situation, you’re always constrained, and the bubble is always perfect. You have all the perfect conditions. But when I started applying some of the things I was doing inside school to the outside world, I immediately realized that industry experts, VFX people, film, creators, artists, designers were like, “Hey, I’m interested in this. I want to use it.” And so that kind of sparked the conversation of — “Oh, maybe we should think about this as a company.” And then yeah, it started from there.

Ishani: Was there an aha moment, in that journey as you’re talking to people and they say — “Oh yeah, interesting research, but I don’t actually know how to apply it.” Was there one moment that you can take us back to that said, “Oh, wow. This is actually so significantly bigger and it’s a company, not just a project.”

Cris: I mean, we started the first research projects in school, there were more about taking image segmentation or image understanding models and video understanding models and applying them with creative domains. So how do you take like someone who’s working in Photoshop and help them understand how the software could basically be a bit smarter in terms of understanding what the person is actually trying to do? What the intent of editing and image is and see if you can have an algorithm or a system that assists you on that editing. So, we built a bunch of experiments and integrations in Photoshop and Premiere. And the ideas were very simple. Like, let’s see, for instance, if I can help you just stylize or colorize or edit an image faster by using some very simple algorithms. And again, it was more of let’s see if this is interesting for these creators. And when I realized there was something definitely here, is the reaction when I remember a few tweets around like, here’s a prototype, anyone interested in trying this? And I remember the amount of inbound interest I got from professional photographers, people working in film people working in ad agencies, very organically being just basically, “Hey, I’ve been struggling with this for years can you just help me cut something that took me weeks of work to 10 minutes. I want to learn more.” That’s when we were like, okay, there’s something definitely happening within the scope of creative domains, and so we should go deeper.

I guess there was one moment in particular where I really thought I should try to do it myself. And, so when I was presenting Runway at my thesis at NYU, someone from Adobe was in the panel. And two weeks after my presentation, they basically offered me to join Adobe, to build all the things that we were building at Runway as part of it their new AI team. I was two years into New York as an immigrant, with the perfect dream company offering you the dream job with a visa and the perfect salary – it is just the dream. When I thought about it at that time, I remember my mom was visiting me and she was asking me, “What else do you want? It’s perfect – everything makes sense, rationally. Why would you not take that? Everything you want is there.” But I couldn’t say yes, my gut, my intuition was like, I can’t do it. If I am doing this, if I’m going to build this thing, I need to do it. And I want to have control of how it’s built. And so, the decision of having the offer and having a capacity of jumping in and being like, “Hey, I’m going to take this. This is a safe solution.” Versus, no, I would really want to try and build it on my own even if I fail, I fail, but at least I tried.

So for me, that was the moment where I was like, OK, something happened — either I go and build inside a company or I try to build on my own because I haven’t raised any capital. I’ll try to see if I can sustain living in New York with no money for a couple of months until I figure this out. I think that motivation of like, okay, I’m going to try to prove that I can make the right decision of not taking it, not going to Adobe, was something that I guess motivated us to do it.

Ishani: That’s an incredible story. Can you talk to us a little bit about this technology that underpins Runway? You know, many of the models that you reference and leverage weren’t even around five to seven years ago. We’ve all spent time editing, whether it’s home videos or in Final Cut Pro and the range in between of getting that mug out of the background or even being able to remove the background from an image was such a huge feature in Microsoft PowerPoint that for everyone out there who makes slides on a daily basis and translating that to video seems like an order of magnitude more difficult. Tell us a little bit about the step change in technology that really enabled the core product of Runway to exist.

Cris: Totally. I think there are a bunch of megatrends on which Runway sits today. We’re seeing an emergence of new video content platforms emerging of the last couple of years. And so, the need to create more video has become more obvious for creators, for ad agencies, but also for companies in general. Every company is becoming some sort of media company. They’re creating content all the time. Everyone’s producing their own podcast, their own YouTube shows. The way that software to create content has evolved and has been developed over the last 10, 20 years is, I would say, still based on an old paradigm of how media works. Like, if you open Premiere, if you open Final Cut, those were software made to make ads for TV. And so the limitations and the constraints and the configurations are all set up for like 10 years ago, right? But if you speak with anyone creating content today for YouTube, for TikTok, for Instagram, the volume and the quantity and the type of content is very different. And so that’s, the first megatrend: How do you think about new tools for the next generation of creators. so within that where ML kind of like really come in and where the differentiator of Runaway is that we see a few things that are happening first, the emergence of the web, like the web as a creative medium. I think Figma and Canva have proven this.

The web is such a collaborative space that you need to just be able to build things on the web. If you want to collaborate with more people, if you want to move really fast, if you want to just not be constrained to any limitations from hardware and desktop. I guess, to your question of ML in particular, we build it so in a way that the video platform, the video rendering, the video encoding itself is entirely ML driven. By that, we mean that every single process in that media pipeline that is either tedious, time-consuming or very expensive to do. We can automate via this kind of like pipeline of algorithms. And so, things like you were saying, like removing an object from a background, has been a very tedious process to do historically in video making. It’s a process known as rotoscoping. And it’s been in film and in video for like as early as video was there. Yet, it’s extremely expensive. So, we thought about it. If that’s a primitive principle, for instance, of video-making, how do you make it so it’s accessible? It’s extremely fast. It’s on the web and the way you do it, it’s not a manual, tedious process. It’s automatic – as fast as possible. So, we’ve built it taking those principles of what folks really want in video, simplifying to the core components, using these human-in-the-loop algorithms and then basically helping you make video faster and better. And there’s a lot of other kinds of components of video that we’re automating as well that basically help drive that motion forward to create more video as fast as possible.

Ishani: I love that you frame the company as being built off of megatrends but then focus on the specific use cases. But then, there’s a broad range of use cases here that I hear you talk about. Across whether it’s an individual creator or, you know, a professional photographer. And so it seems quite widely applicable. When you think about some of the research work that you’re doing and the capabilities of making machine learning more accessible to each of those range of end users How do you actually go about picking and choosing the sort of machine learning models that drive it?

Cris: I would say that. Going back to 5, 6, 7 years ago, a lot of the computer vision and ML models started to become more relevant and commonplace. A bunch of things were also built around that time, like the infrastructure to deploy models. And we’ve seen the emergence of ML ops community in general, like tools and systems the monitor, your training process, tools to deploy models to production tools to optimize models to different devices. There’s a lot of things that happen to basically help drive these models into production. And we’ve seen that in like robotics and self-driving cars. Like those algorithms are becoming more predominant than ever before. Basically, because we’ve invested as a community of ML, folds or ML companies on that infrastructure. And so, for us is the realization that we don’t have to build infrastructure ourselves. Like, you can take off-the-shelf solutions to help you deploy the models into production environments, with millions of users in real time, for instance. The core component, I would say it’s not like spending too much time on that infrastructure, given that it’s already been built. It’s more like what’s the unique problem that you’re trying to solve here? If we think about that, there are two ways you can take that approach one is just looking at open source.

The ML community in general has been built a lot on top of open source. And so there’s a lot of ideas that are really interesting. You can borrow them, you can build on top, and you can contribute as well. We do it a lot. We publish. But when it comes to production like getting things and putting them at the level of perfection that your customers really want it is a whole other beast. That requires a different mindset. For instance, going back to the rotoscoping example. Video segmentation is a task that has been approached in very different ways on the research side. But when you speak with someone doing video, even if it’s a professional VFX and filmmaker or some casual creator, the way you think about it is completely different. At the end of the day, as a creator, you don’t really care what model goes behind the scenes. I think a lot of people might want to overemphasize the need of showing you how the algorithm works and demonstrating its capabilities. But if you just focus on the customer itself, people just really want to remove the objects from their backgrounds. And so with that in mind, there’s a lot of that comes from like automation from how do you build a robust segmentation model? How do you build it so it works really well? It all has all of these kinds of constraints, but at the same time, how do you involve the user input in that process? So half of it is research on ML and the other is a lot of just user research. How are you doing this today? How are you actually doing a background removal process? Some people might use Photoshop or some very complicated to use tools. Some other people may use some sort of automation by building their own tools, and you’re trying to really understand what that actually means. So you build a solution that specifically within creative domains is never fully automated.

Cris: I’m a big believer that you’re never going to find a tool in the creative space that does everything for you. That’s just a dream. That’s a Utopia. Nothing in the creative world works like that. So every solution that’s just input here, do nothing because the machine will do it for you.

It’s just a complete mistake and totally would not work. So, for us, it is more about, you have a problem, you have an insight, you need something to be done. Here’s a system that we build on research that helps you, but we also understand what you require, how you work with the device and how you work with that loop that we call.

Ishani: And, you know, you could argue that if a machine was doing all of it, isn’t really creative inherently. Do you lose that aspect? That sort of intangible aspect of creativity? So, much to unpack here. So, you talked about the infrastructure layer. We call those enablers in intelligent applications where there’s this whole system of, the Databricks of the world, but that DataRobots and all these other companies that are out there that are Grafana, Monte Carlo, that sit at the enabler level that create the ability for folks like you, RunwayML, to build endpoint applications much faster and better than before. Some of that’s in the open-source community, as you say. And some of that is actually, company-based but it removes the infrastructure layer from every intelligent application that has to be built. And, being able to capitalize on that, I think has made a huge impact on the endpoint applications like Runway. And then you think about bringing that to the product. So much of what you talk about is around accessibility. You know, new technology adoption – so much of it is related to how accessible that technology has become, and so in the academic sense, this machine learning models and development and rendering and all these sorts of technical terms, don’t feel very accessible to creators and particularly the demographic that you’re targeting. But building it into a, low-code/no-code, video editing tool, it really does.

So, the classic question is browser versus application, and you talked a little bit about why you’re in the browser and how it’s become so much more of a collaborative and creative space. What are the other decisions you’ve made along the way to make the Runway experience — specifically being able to get machine learning into the hands of creators at a product level, more accessible for new users, borrowing from things like the workflow of Final Cut Pro or some of the other tools that are out there. Tell us about those decisions that you’ve made along the way.

Cris: There are a lot of things that come into this conversation. The first one is, we’re always thinking in terms of the company, like the build versus buy. If I want to build and deploy models to millions of users, I don’t have to build a whole backend infrastructure and don’t have to own the instances. You just plug into the whole infrastructure that has already been built. And that’s so good because you can focus on the key differentiators of your company. What are the things that are unique as a product that will help your customers do more?

So, for our customers, what they want is just to create more video faster. And so, for that, we basically take existing primitives from the video space. And so, we’re really close to like professional software for people working in the industry for years to try to understand what are you trying to actually do in your workflow and how could something like an automated system help you, but also open the doors for other folks who would have never of being able to do that thing before, do it as well? And when you think about that, you think about, OK, we need to build on top of the infrastructure. We need to allow the new generation of creators to tap into what making video is. The web becomes such an important aspect of that. Mostly because it democratizes access to complicated and sophisticated tools like professional video in a way that I don’t think we’ve seen before.

There are a few things that are really important. The first one is the need for hardware gets reduced to zero. Like a lot of our users are on Chromebooks, on Windows laptops on iPad. It’s really hard to edit video in any of those devices if you don’t have a powerful or deep-feed, GPU machine. So, for a lot of people, that’s not a limitation if you have that capacity to compute. But if you’re a small shop or a small business, or if you’re a small ad agency or even a big ad agency, you still have that limitation on hardware. The web just like completely reduced it to zero. Basically, you’re connected to our cloud. You have that endpoint. And since we already have that GPU cluster running the models, you’re basically able to access not just one GPU machine, you’re able to access a lot. And so if you want to export hundreds of versions of your video, that’s possible. And I think that the second one really important aspect of the web, and why we decided to build in the web again, building on the accessibility point is collaboration.

When you think about video creation today, you can think about people editing video, like video creators, themselves, video editors. But video encompasses more than just people doing the actual editing. It involves the managers. It involves the viewers and the designers. If you’re building a brand, and you have design assets and files, and someone is building in a video, how you share those assets with that person, or with that team really matters. So video becomes like a central hub of collaboration as well. And the web facilitates that at a rate that’s impossible to do in any kind of environment. And so, for us, it’s considering those aspects as well when deciding how and when to build a platform. And aiming and investing in the web for us has been a long-term goal. A lot of the things we’re doing right now in the video space, on the web hasn’t been done, so we’re working with the Chrome team with the Google team, really closely to work on some of the new standards that they’re developing to make sure editing 4k footage with 10 layers at the same time feels as native as possible. And I think Figma has already proven this in the vector UI design. You can run things natively or even more better than native on the web. And now we’re actually starting to see these in video as well, which is a bit more complex in terms of latency and interactions, but we’re definitely getting there.

Ishani: That’s awesome. You talk about cloud computing as a big enabler again and this collaboration concept. Multiplayer in the web is this next generation of collaboration and you’re right, Figma, Coda, Notion, Canva have made collaboration and multiplayer inherent and I think a lot of the applications that don’t have that multiplayer component are proving to be much more difficult to use, especially within teams and within a remote and hybrid kind of world that we’re entering. Figma and Canva — you mentioned them. They really, to me, started to pave the way to this multiplayer concept — web-based — but also this concept of low-code/no-code and being able to set the precedent for using machine learning, using technology in a much more accessible way for a non-technical user.

Do you think of that as one of the big trends that’s enabled and paved the way for you and Runway.

Cris: So, when we think about it, I guess no code for us on the ML side of things, we actually think a lot about how we take these models, these very complex pieces of software with hundreds of thousands of connections and systems to make them work really well and robust, into really consumable and easy to digest and simple solutions as an interface. Making sure that you build interfaces that are programmable or accessible and customizable. I think in a way, it becomes a commodity like it’s a system that you build, it’s proprietary, you develop it, but your customers are less concerned about the internal aspects of how it works and are more concerned about the output, right? And so, when I think about Webflow for instance, and I think about web designing in general, like Squarespace or those kinds of companies, would build like democratizing, no-code solutions for building websites, you really care about your customers just building really good websites. Right? How CSS and the JavaScript endpoints work on the backend are not really useful for them, unless you’re helping them solve a business use case. And so, you don’t really expose those kinds of things.

Ishani: That’s great, framing it as exposure. I hadn’t quite thought of it that way before, but it does make sense. You’re masking sort of the code and you can expose to components of it where it matters and where it’s a variable that people want to influence. But where It’s not. And you learn a lot of this through user testing, but where it’s not you can mask it. Tell us a little bit about the process for that user testing. I mean, so much of what you’re talking about is really driven by your end user. And it seems like you’re really in touch with who that is and how you learned a lot from them. What does the process for that look like? I think it’s so important as you iterate on early product and early build. And when you launch a new feature, you know, in your case Green Screen, for example, what’s the process you go through for a user iteration and feedback.

Cris: I love that question. I think a few things are important. The first one is a lot of times your users don’t actually know what they want.

Ishani: They just know They have a problem, but they don’t know to solve it.

Cris: Exactly. So, if you ask them the answer to what they want, that will not necessarily be the best solution. That’s the realm of knowledge they have today. In a way, no one was ever asking for an automated rotoscoping solution because no one thought that was possible. When you start doing and developing technologies or start delving deeper into things that haven’t been done before, it’s really hard to do comparisons to like, how has these been working before? Because no one has done it before, so it’s really hard to have a benchmark.

And so, when you ask people, what’s a pain for you in the video space, a lot of people will tell you like, Hey, rotoscoping, extremely painful. So, what do you want? Well, I want a better brush so I can do my mask five times faster. And so, I could be like, great, I’ve listened to you. I’ve built this thing, now you’re working two times faster. Do you like it? And it’s great. I like it. But the moment you mentioned like, “Hey, I can actually automate the whole thing for you. Just literally type a word.” And this is true. We have this as a beta that we are going to release really soon, where you can type. Let’s say you have a shot of a car and a tree. You can type “car.” Then we have a model that understands the object in that video, understands the car, creates the masks for you and extracts the mask immediately. And so, you’re not editing anymore with frames, your editing with words, right?

It’s really hard for our customer to tell you that — “Hey, I want to like this thing.” But the moment you show them to them, they’re like, “Oh, it’s insane. Like I want this. It is not only helping me move twice as fast. It’s helping me move a hundred times faster.” So, a lot of the user research in a way is like listening to your customers and listening to your users, but actually trying to really listen or hear their pain. Okay, what are you actually trying to say when you’re saying these things, this is actually the tool itself is a problem, or it’s more of like, the process is broken. If you have the process that’s broken and you as a product person know that technology, know the skills of your team and what’s possible today, how do you build quick prototypes and solutions that can help you actually figure out if that’s actually something worth investing and building?

Cris: So, we do a lot of that. We listen a lot. We understand our customers. We understand either people who have never used the Runway before. We interview them a lot and we try to distill, okay, what’s the fundamental things that are happening here. And how would we build them with a set of technologies that we’ve been developing over the last couple of years?

Ishani: Right — and from the end-user standpoint. It’s just not in the realm of possibility to augment their workflow so much with automation, you know, maybe incremental baby steps. But as you say, the 100X just doesn’t fall within the imagination of someone using a video tool to take it all the way to, for example, text-based video editing. That’s in the realm of researchers at OpenAI, doing GPT3 work and DALL-E, and all those image processing things. So being able to really distill down a pain point, but then you use your imagination to go from up with a solution.

Cris: And that’s a lot of prototyping as well. Basically, coming up with ideas and you just test those ideas with your customers as quickly as possible before building really robust and technically complex solutions. So, I guess to your point of for instance more on the generative side, something we’ve been spending a lot of time on generative models, deficient models, transform, applies to computer vision. The thesis there is that we’re probably going to start seeing more video content being entirely generated. So, think about stock footage or stock video, right? It was the case before you had to either shoot something or buy that footage from like a Getty Image platform, and that’s a really expensive process, both because the acid itself is super expensive to buy, but also because the asset might never actually be the perfect asset that you want. There’s some things that you want to change the color isn’t right. I want that person, but in a different position. It’s so complicated. And so, we’re approaching the space where you’re actually going to be able to generate those things, generate that stock footage, that footage in general. So, when you ask people, how do you want to create or work with assets, with templates, with custom content, they might ask you like, “Hey, I want a better search for my stock footage library.” But the moment you have Dall-E or other models that are able to generate realistic content, the conversation completely changes. You’re not marginally improving a process. You’re leapfrogging a whole industry. You’re like, okay, this was the way people used to operate.

Now, this technology is enabling you to think in just a completely different way. The questions you’re asking yourself are so different. And so having that is something we’ve always had in mind. And we’re also betting on that, on the long term as well.

Ishani: Incredible. Yeah. That leap from video editing to transformer model augmented video editing is massive, right? Transformative from technology perspective, but massive from it. Just how do I make that leap and requiring the technology, the examples to saying, oh, I can use transformer models in this process. We can talk about transformer models forever. Maybe take us to the moment where that started to make sense for you as a business.

Cris: I think the moment we started seeing this as an interesting research technique was the moment people understood that you can apply it not just to tokens, but to like pixels themselves. We use some of these techniques for our models behind the scenes, but in general, I’m less of a fan of a specific technique because techniques tend to move really fast, and something else will happen. And so, I think it’s important always to like — when you see those trends coming up, see how they can adjust to your product or your needs. But at the same time, don’t fixate too much on specific technique because a new technique might come up that might be better. And the ability to switch and learn from what’s better, I think we’ll always pay off versus like, if you’ve spent too much time developing something and then a new approach comes and you’re unable to adjust. then it’s going to be hard. I mean, the space moves so fast. The ML space is moving so fast that something that just published four months ago has already been changed, so keeping track of that, I think it’s the most impactful thing. I guess on the research side of Runway, we do a lot of different approaches from transformers to more generative stuff from our traditional computer vision as well. Again, always in the aim of like, how do we help you make video faster?

Ishani: That’s a really great insight to be nimble across, you know, a rapidly evolving technology field. And the conversation, even if you just zoom in on transformer models on how large these models have been and how many parameters they’ve been trained on, even over the course of the last 12 months, the chart is absurd, right? And that point of you building a business on top of some of these platform technologies, or what will evolve to be platform technologies, being nimble across the methodology is so, key.

Cris: One hundred percent. Because at the same time, there are a lot of things that are happening specifically where you mentioned if like those hose models themselves that our greater research insights, but try to, productionalize a model that has 2 billion parameters for like a million users. You either have a budget of a million, a million dollars a second, or it’s impossible to do it. Right? So, it’s great. Like fundamentally. It’s moving the field in such an interesting way. There’s new techniques. But again, if you’re thinking about how to put it into a product, that’s a whole different conversation.

Cris: So always trying to balance those things for us is really important.

Ishani: So how do you straddle then the business side of Runway and the research side of Runway.

Cris: We don’t see them as different worlds. It’s part of the same. So, research at Runway, is just applied research to product? As a researcher at Runway, you work really closely with the design team and with the engineering team and with everyone to really figure out if there’s something we can do. There’s a cost, like a literal cost, that needs to be considered, and compute, to have in mind when you are developing that. There’s the feasibility approach — is there something we can actually build in a reasonable amount of time? There’s a performance trade-off and all of these things that you have in mind when you’re thinking about applying those into a product.

Perhaps if you’re a more formal academic context, and you’re just doing research. You’re not constrained by those things. I mean, when OpenAI was building GPT-3 they were not thinking about deploying this for video domains with millions of visitors, they were thinking — this is an idea, let’s see if it works. And then people start building on top of that. Now there’s a lot of like pruning and ideas that can come to make it more efficient, more fast. But it’s still, if you look at OpenAIs for like pricing model for, GPT-3 today’s it is still very expensive to use it. And it’s a language model. So video is way more expensive. And so, we’re less concerned about, how do we push like a field so far where it’s opened all these doors for positive expressions. And we are more of let’s be more pragmatic and like research is a product. It’s the same thing. It’s — just make sure that it works inside our environment where users can actually get value out of it. So that’s how, I guess how we want to think about it.

Ishani: I love that researcher as product. Let’s zoom out a little bit. When we look at the rhetoric around RunwayML, you talked a little bit about this confluence of code and art. And it’s not often that we see companies at this intersection. Talk a little bit about that, conceptually, what it means to you and your customers. One question I’m curious about is, you know, did it make it harder to raise venture funding back in the 2019-2020 timeframe because you are sitting at that intersection and that framing,

Cris: One thing I will clarify is, when I came to school, at NYU I went to art school. I spent two years in an art school, which is working and taking classes in computer science. It’s a unique kind of like arts program inside NYU call ITP. It’s our program that’s been running for 40 years. And it sits at the intersection of like technology arts and design. You can think about as a hacky, hacker space. You can just be there working on whatever you want, any kind of topic that involves technology and art and design and take classes from any department in NYU. And so you’re surrounded by really smart people from all sorts of backgrounds and ideas, and skills and you’re building interesting creative projects- just to just building things because you’re interested in exploring things. When we started the company, we started doing the research inside this program. It was a way for us to just have fun. We just enjoyed doing this. Experimenting with this technology, building our projects and then like showing them in galleries or in spaces or in online places. Seeing what was coming out of it, that’s what drove us. When we started, like seeing that the interest was more than just artists, but like companies and filmmakers and creators, and it was like, Hey, we should actually take this outside of an art experimental approach and productionalize it to make sure that we can deliver on the promise of transforming how content is created.

Was it challenging to raise capital at that time with that kind of like art experimental narrative? I don’t know. It’s difficult for me to benchmark because again, I was like two years in New York coming from a totally different country, culture. So, I didn’t really know at that time what raising actually meant. I was more of like, Hey, we just need to start this company. A bunch of VCs and investors had already started to reach out. So, we built a process — it actually took us like four weeks to raise. It was really fast, I think. I was thinking about the time that I never had a deck. We just showed a demo, and everyone immediately understood how it worked. I guess the advice for me from that time would be definitely to just build demos. Build things more than just decks.

Cris: Now that I look at it, and I started raising a few more rounds after that, it was interesting to see that we’re coming from a background on skills that are not common I would say most like venture-funded companies. Most of the members on our team do have an art practice or a creative background. They are artists themselves our engineers and have studied art as their primary study, and then they became engineers after. And I think that drives a few things. First of all, culture. The culture of Runway is very creative-driven, very altruistic driven, and that sits perfectly with the product we are building. Like we’re really thinking about creativity, thinking about content, thinking and about creative tools. And when you’re an artist yourself, you’re building a way for you. You know, you understand this type of user.

Ishani: You frame it as the intersection of art and technology, art and code. There’s so much opportunity as you’re articulating for the intersection of, you know, technology and X. I think that’s where we’re super excited about the next generation of applications that maybe we haven’t all thought about yet. So, we’re excited to see the success that you’ve had and all the continued progress. You know, building a culture of creativity in a technology company is inherently both easy and difficult.

And so being able to do that and then continuing to scale, it is so exciting for us to see.

Cris: Yeah. And it’s been a great way of attracting really great talent. The intersection of art and technology is something that has grown a lot over the last couple of years. And there’s a lot of interesting and talented engineers and designers and people, in general, sitting at that intersection wanting to really think about how to apply these technologies for art making, creative making. So, Runway has become like that spot where you can just come and help us and build the kind of like reality in a way. And yeah, I’m really excited to continue doing that.

Ishani: Chris, thanks so much for walking us through the business. We’re going to end the series of podcasts with three lightning round questions that have a little bit less to do with your business specifically but more about where you sit in the ecosystem. So aside from your own, what startup or company are you most excited about in the intelligent application space and why?

Cris: That’s a good question. I’m really excited about companies who are verticalizing ML, in kind of like niche domains. Uh, we started using this company called SeekOut for recruiting a couple of months ago. And it’s been so transformative for us, specifically for finding talent. I’m excited about companies like Weights and Biases as well — in terms of like research, how do you make sure that within our problem, you can help your team just move faster by identifying what needs to be done and how you can run experiments just faster. So, any company who is just seeking to like, just think about long-tailed use cases and think about optimizations so you can run with some of these algorithms or these platforms are the companies that I’m excited about.

Ishani: Incredible. And what a great segue to the fact that SeekOut is going to be our next podcast. Okay. Question number two. Outside of artificial intelligence and machine learning to solve real-world challenges, where do you think the greatest source of technological disruption and innovation is over the course of the next five years?

Cris: I guess I’m a bit biased about this, but I would say, from non-domain experts diving into like domain expert fields. The barriers of entry to a lot of technologies have considerably been lower, and so you have people who are able to build on domains that perhaps they’re not their own domains of expertise and bring in insights and thoughts and ways of working and ways of thinking that are completely new. The misfits of those spaces for me is where a lot of transformation will happen. So, I guess for us, it was like, we’re coming from an art background from a creative perspective. We’re changing how video works in businesses, right? We have so many insights and so many ways of thinking about the product and the ecosystem that perhaps people in the industry today are not really thinking of. And that’s just so unique. And such a differentiator that I’m really excited to see more of those people just jumping in between different kinds of domains and backgrounds.

Ishani: Right, this concept of accessibility begets innovation.

Cris: Yes, exactly.

Ishani: Question number three. What is the most important lesson, perhaps something you wish you did better, that you’ve learned over your startup journey so far.

Cris: Oh, well, a lot, perhaps a good way of summarizing all the learning is, I think something I’ve learned, is that in order to just build a great product a great business is the rate of learning really matters. Like how fast you are learning as a company and as a team and as a product, how fast you are learning about your customers, how fast you were learning about the industry, about the competition, about the market, about technology. That rate of learning and how fast you can just do something you’ve never done before. Experiment with it, learn as much as possible and adapt really, really, really, really is important. And it’s something I’ve seen a lot from other companies is perhaps it’s easy to get stuck, uh, and it has happened to us as well, into something that you’ve realized you kind of like, quote know works. But then something happens and you’re not able to adapt. And so, just having that mentality of always learning — learning never stops in every single domain of the company. Always keep on learning as much as possible. And then everything else will come.

Ishani: I love that in the same way. You’re always launching your product; you’re always learning about how to build a company.

Cris: Exactly. Always.

Coral: Thank you for joining us for this IA40 spotlight episode of Founded and Funded. If you’d like to learn more about Runway, they can be found at RunwayML.com. To learn more about IA40, please visit IA40.com. Thanks again for joining us, and tune in, in a couple of weeks for Founded and Funded’s next spotlight episode on another IA 40 winner.

Founder Voices from Madrona’s 2022 Annual Meeting

We just wrapped our 2022 annual meeting, which we were able to have in person for the first time in three years. Madrona has worked with many of our investors for well over a decade, and they span all types of foundations, universities, pension funds, and family offices.

The annual meeting, with about 150 attendees this year, was a much-needed dose of human connection that reminded many Madrona investors why they got into this business in the first place — people and more specifically — great founders. During the day’s events, the audience heard about Madrona’s results, of course, but the stars of the show were the founders and leaders at our companies — and we took the opportunity to check in with them on this week’s episode of Founded and Funded.

Full Transcript – This transcript was automatically generated and edited for clarity.

Welcome to Founded and Funded. This is Coral Garnick Ducken Digital Editor with Madrona Venture Group. We just wrapped our 2022 annual meeting, which we were able to have in person for the first time in three years. Madrona has worked with many of our investors for well over a decade, and they span all types of foundations, universities, pension funds, and family offices.

The 2022 annual meeting, with about 150 attendees this year, was a much-needed dose of human connection that reminded many Madrona investors why they got into this business in the first place — people and more specifically — great founders. During the day’s events, the audience heard about Madrona’s results, of course, but the stars of the show were the founders and leaders at our companies. I thought it would be a great opportunity to check in with some of them on the challenges they face last year and how they were able to overcome these challenges. And we spoke about what they’re focusing on in 2022. And here at Madrona, we’re always looking for and working with new founders. So, I asked them for a piece of advice, they’d share with someone just setting out.

Clari

One of the first companies to present during our 2022 annual meeting this year was Clari. Co-founder and CEO Andy Byrne updated us on his enterprise SAS company that arms chief revenue officers with artificial intelligence that allows them to drive more revenue and boost the predictability and accuracy of their forecasts. And while growth is certainly on the agenda for him in 2022, and he has a plan focusing on expanding value for customers, Andy recognizes that 2021 had some growing pains because of the massive growth the company saw in direct response to the COVID 19 pandemic. Companies wanted visibility into their forecast and pipelines more than ever, and Clari had just the tool. But being ready for that growth and required scale at the flip of a switch is not easy, Andy said

Andy: A lot of things broke, and we had to go about moving from what I would call scrappy startup point solving to scalable machine actual system solving. And that’s really a different mindset shift as you get into the level of scale that we’ve experienced. That was probably our biggest challenge. And the graduation from that sort of scrappy startup to machine actual has been really a joy to experience.

Booster

Coral: Frank Mycroft co-founder and CEO of Booster faced another sort of transition in 2021. Not only did the transition from 2020 to 2021 mean another year of unexpected pandemic restrictions and working in a mostly virtual environment for his team, which is re-inventing cleaner fuel delivery services. But he also had a new addition to the family. The birth of his third child came mid-year. While it was a bit more challenging than he remembered. He said it gave him some new perspective.

Frank: I was expecting the baby, I was not expecting how difficult newborns are. They’re really not self-sufficient, are they? And I had forgotten that. I felt like 2021 was a year where it was easy to have short attention spans. And it was easy to have group think because everybody was reading the same things and on the same Zoom calls. So being very intentional about saying no to things you didn’t want to do and carving out time to be intentional first-principles thinking on your own was really important.

CommerceIQ

Coral: Another company that was very intentional in 2021 was CommerceIQ run by founder and CEO Guru Hariharan. Commerce IQ is an intelligent commerce platform that helps consumer brands like Colgate, Nestle and Kimberly Clark grow their e-commerce business. The company had growth goals, but because the platform is only appropriate for certain verticals, identifying expansion, targets was becoming difficult. But by asking hard questions and digging in, the company is better for it. And it actually just announced a $115 million funding round at an over billion-dollar valuation.

Guru: We had to do some introspection in terms of how we land and expand how we provide more value. We had to go back and do some soul searching. The way we did that was actually going back and asking our customers how they thought this market was going to be evolving over the next few years. And they told us “Look, point solutions are not going to work for us. I don’t expect in the year 2025 or 2030 to wake up to say, ‘I’m going to be looking at a supply chain system, taking an Excel file from there and pushing it out into a retail media system, taking an Excel file, from there and pushing into a promotion or a sales management system.’” They told us that point solutions are not going to work. But at the end of the day, we were a point solution at that point. It pushed us to sort of take a step back and really create the right vision for the company.

This is one of those where just using customer interviews, and the ability to work with customers in a way that we understand their problem, but we were not necessarily listening for solutions from them. So, we understood the problem that point solutions was not going to work. We connected the dots and we said, well, we need to then create a platform. And we went back with a vision that was fleshed out, and we showed it to them, and they said, this is perfect. So, our big learning was going back to the roots and trying to understand from a customer perspective what were the key problem areas, and then going back and actually creating some solutioning around it and then creating the vision for the company. It was a phenomenal experience. And frankly, that was one of the key reasons why we were able to raise a billion-dollar valuation round, because now we are making some significant waves by showing that vision to our customers and to the market.

Rec Room

Coral: It was really fun talking with Rec Room CEO Nick Fajt during our 2022 annual meeting. Rec Room, of course, is the virtual reality world where you can create and play games with your friends. And the metaverse is a huge topic of conversation with Facebook changing its name and both Mark Zuckerberg and Satya Nadella not being able to go through an earnings call without saying the word more than a couple of dozen times each, but Nick launched his company a few years before the pandemic hit, and since December 2020, when Madrona led the series C round, Rec Room has raised $265 million and has millions of player-created rooms. Usage also took off during the pandemic and has continued to grow. Coming out of the pandemic, Nick says he is focused on three big pillars for Rec Room.

Nick: The first is user generated content. Everything in Rec Room is built by players, and we’re constantly looking at ways we can improve the tooling and help people build whatever’s in their imagination. The second area we focus on pretty deeply is building a fun and welcoming community for everyone — what are the ways that we can use our unique reach and our unique platform to help people connect across geographies and across time to make those meaningful connections, make meaningful new friends and make memories with those folks. And then the last area we talk a lot about is being a radically cross-platform app. It’s really something that helps both the user-generated content because it means you can create content on any device and it will go to every device, and it means your devices can get out of the way for the social and the community aspect. For most technology, you really don’t want to connect your device to your friend’s device, you want to connect with your friend. So we take this radically cross-platform approach so we can help people connect regardless of what device they have. So, we’ll be coming to some new and exciting and unannounced devices later this year.

SeekOut

Coral: One of the most recent Seattle-based portfolio companies to land unicorn status is SeekOut following its $115 million funding round. Companies are all facing the great resignations, so recruiting and talent retention are top priorities. SeekOut’s intelligent application pulls data from across myriad sources to find companies the best and most diverse candidates. As SeekOut co-founder and head of product John Tippett looks to 2022, he said the company is focused on scaling and applying its considerable success in recruiting to building the tools needed for internal employee engagement and retention as well. I’ll let John explain.

John: The biggest thing we’re focused on as a company at SeekOut is scale. How do we provide more capabilities to more customers, so they can be more efficient and more effective with their talent as we get into this new world of work? So we’re building out all of our teams and we’re building on new capabilities. One of the things we’re also focused on is how can we turn all the things that we’ve done for recruiting new people into a company to helping you retain, engage and grow your internal employees. And I’ll give you an example of how we got to this. SeekOut’s passive sourcing product has the ability to look at talent insights about any talent pool. So, you could say, what do we know about accountants in Chicago? And when we show that to customers, they say, “this is amazing data — I wish we had the same kind of data for our own employees.” And it’s really based on that insight, we decided we could do this around talent insights for companies so that they could optimize where they’re investing, who they’re hiring, even where they’re building new offices when they eventually get back to that.

A-Alpha Bio

Coral: One of Madrona’s investment themes in recent years has been the intersection of innovation. And at this year’s meeting, we heard from David Younger at A-Alpha bio and Jesse Salk from TwinStrand. And of course, we also had the distinct pleasure of having Dr. David Baker from the Institute of Protein Design give the keynote address during the event. The opportunities coming out of combining the power of data and computer science with life science research seem almost endless. And Dr. Baker actually mentioned during his address that the students in his lab used to want to all become professors, and now they almost all want to start their own companies. So, the opportunity for madrona to help founders fund and build up companies in the space will hopefully be plentiful.

David youngers company, A-Alpha Bio actually spun out of Dr. Baker’s lab. The company combines high throughput, synthetic biology with machine learning to dramatically accelerate the discovery and optimization of lifesaving therapeutics by focusing on antibodies and molecular glues. I will let him tell you in his own words, what they’ll be focusing on for the rest of the year.

David: So, antibodies are protein therapeutic, so they’re made of protein and they function by sticking to other proteins. A-Alpha Bio is the protein, protein interaction company. So antibodies are right up our alley. Everything about them is protein, protein interaction. And so, in that space in 2022, we’re doing a lot of work to build and optimize our own internal antibody library and really go through the workflow of discovering novel antibodies for targets that are otherwise very, very challenging to find the right antibody properties for. So that’s a combination of partnering with leading pharmaceutical companies in the antibody space and also doing some of our own internal antibody discovery and optimization to build our own proprietary pipeline.

In the molecular glue space — molecular glues are small molecules, but they function by bringing together by essentially gluing together two proteins that wouldn’t otherwise interact. And this is an incredibly exciting and relatively new therapeutic modality. And what A-Alpha Bio is able to do very uniquely in this space is identify targets that are suitable for molecular glues. And so, we’ve started to do that with partners. Late last year we announced a partnership with Kymera Therapeutics, who’s one of the leaders in this field, but we’re also starting to build out our own internal capabilities to start programs of our own. So that’s a major initiative for 2022. And then all of this kind of falls under the umbrella of generating a lot of data that we can use to train and validate our machine learning models.

TwinStrand

Coral: Another company with a lot of data and the potential to impact a lot of us profoundly is TwinStrand Biosciences led by founder and CEO Jesse Salk. TwinStrand’s technology is working to utilize informatics to make existing genome sequencers 10,000 times more accurate so scientists and doctors can see subtle changes in DNA that are not only relevant to basic science but particularly to cancer patients. But launching its first product into a pandemic was not the ideal scenario. So, Jessie is looking forward to seeing what the company can do with restrictions lifted.

Jesse: We are really looking to get out in the field, work with more customers, work with more of our clinical and research partners, go to more meetings and generally get an opportunity to spread our wings and use all the sophisticated infrastructure we’ve built the last two years while we’ve been a bit stuck at home. This is my first company — I’m a trained scientist and a physician. So, this is my first time doing this, so it’s been a little bit, challenging to be operating with so many different variables, but I think we’ve done Pretty well. And, you know, part of our technology is about, high accuracy, high sensitivity, and understanding evolution of cancer and cancer cells and so we think we also need to be able to evolve and we’ve done a pretty good job.

Advice

Coral: I promise advice from founders who spoke at our 2022 annual meeting. And I’m going to start here with Jesse because while his may seem straightforward, I think it’s something people often forget.

Jesse: I think you need to have some humility — be very open with what you’re good at and what you’re not good at and what you need to learn, be willing to recognize that there are many colleagues around you who know where you are and are a few years beyond you and are willing to give advice. I learned a lot, and I had tons of support from Madrona, from our other investors, from colleagues and CEOs of other companies. And, just be very comfortable with who you really are and take stock and use others as resources. And I think I’ve tried, to give back and kind of do the same thing because there are certain things, that are not rocket science, but it’s just, you know, you’ve got to learn it and there’s no reason to make everybody reinvent the wheel.

Coral: Next. We have Clari CEO Andy Byrne.

Andy: Take your idea, get with three to five customers that believe in your idea and your vision that they just fundamentally say, “You build that and I will figure out how to get it into my company, and we’ll try to use it and together let’s go build something great.” And that entrepreneur needs to identify who those early adopters are and then you’ve got to go find the person inside that company that’s also saying, “I’m willing to take a risk. I’m willing to turn it on and be a champion internally for you.” So you find those three to five and then you partner together and you co-design and you never, ever, ever give up. And you listen incredibly carefully not with happy ears, with ears that are like, well, if the customer says, “Oh, I would love you to build that.” You need to say, “Well, hold on. Why?”
“Well, because we might use it.”
“Well, why would you use it?”
“Well, because we…”
“Well, why is that valuable?”
And you get down to the depth of knowing, okay, this is actually something that I can monetize. And if you do that level of work of identifying the logos, getting the people in those accounts — three to five of them — and have all this tenacity and the ability to MVP and exceed the customer’s expectation with a product that blows them away that they got earlier than they thought they would. Then you start to get momentum off of your base foundation of customers that become your key marquees that allow you to then build on top of that foundation and start growing incrementally to your next handful of milestones. So that would be my advice to a young entrepreneur who’s starting out and never, ever, ever give up.

Coral: Finally, I’ll leave you with advice from Booster CEO Frank Mycroft.

Frank: You got to sell the product first before it even exists. Take that time you would’ve spent developing it and get out to your customers. Go talk to them even better. When we were starting out, we lived, we literally lived and worked in offices right next to our first customers. You’ll iterate so fast on the idea and you’ll save yourself so much time. And when you finally get to the build part, try to build on the riskiest thing. First, this is not easy for an early entrepreneur. You want to work on what you’re comfortable with, what you know, really what. But if you want to really win, I think you’ve got to figure out the scariest thing, and go work on that first, because if it doesn’t work, you’ll be grateful. You didn’t waste a lot of years doing other stuff before you figured that out.

Coral: Thank you for listening to this special episode of Founded and Funded. Tune in next time, as we launch a series spotlighting our IA 40 winners.

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.