Next Generation Biotech

This is a recap of our fireside chat with Dr. Mostafa Ronaghi, SVP of Entrepreneurial Development at Illumina and founder of GRAIL, recently acquired by Illumina for $8 Billion. Watch the full talk at pear.vc/speakers, and RSVP for the next.

Dr. Ronaghi's story
Biotech = data + human need 
Technical founders can become skilled in business
Early indicators of success in early stage and Series A
“Simple” advice for biotech entrepreneurs: commit

Dr. Ronaghi’s story 

As a young boy growing up in Iran, Mostafa Dr. Ronaghi was drawn to biology. He figured he should become a doctor — after all, what other career options were there for someone interested in the future of genetics? But, after shadowing his uncle at a local hospital, Dr. Ronaghi discovered that medicine was not for him. Instead, he would follow his passions into the emerging field of biotechnology. 

In many ways, Dr. Ronaghi was ahead of the curve. Today, opportunities are increasing within the biotech space, as technological advances continue to drive innovations forward. Decades later, the journey has taken him to roles as a researcher, serial entrepreneur, company executive, and inventor. 

Since 2008, Dr. Ronaghi has served as the Senior Vice President and Chief Technology Officer at Illumina, a leading developer of life science tools. He is also a serial entrepreneur, having founded several notable biotech companies including Grail, Avantome, and Pyrosequencing AB. In all, he holds more than 30 patents. 

Dr. Ronaghi earned his Ph.D. from the Royal Institute of Technology in Sweden. It was during this time that he began researching pyrosequencing methods — the groundbreaking DNA sequencing method that he would become known for. 

“I started my PhD program on microbial sequencing. And after one and half years, I came up with the idea of pyrosequencing, which was a novel way of doing sequencing,” he explained. 

He was later offered a role as a principal investigator at the Stanford University Genome Technology Center, and was encouraged to apply for national grants to increase funding. Because he was not a U.S. citizen at the time, Dr. Ronaghi began searching for American co-applicants to collaborate with. In 1998, the search led him to the founders of Illumina. 

Biotech companies are driven by both data and human need 

In biotech, metrics matter. 

Dr. Ronaghi’s technological advancements in gene sequencing have allowed for faster processing and increased accuracy. 

This change has been reflected in the markets as well. His work managed to reduce the cost of genome sequencing by nine orders of magnitude. Only one other industry — the semiconductor industry — has been able to accomplish this. 

“Back in 1990, the cost of sequencing the human genome was more than $3 billion. And we reduced that cost to basically $1,000 within 22 years,” he said. “The genome sequencing is about $500 per genome now, in larger scales. And it’s going to go to $200 in the next few years.”

“This has kind of revolutionized healthcare, the impact is going to be enormous,” he added. 

While much of the daily work responsible for a scientific breakthrough centers around minute details and microscopic particles, it’s important not to lose sight of the emotional, human elements.

When Dr, Ronaghi first started working on the science behind Grail, a healthcare company whose mission is to detect cancer early, the company’s business model was not fully determined yet. But Dr. Ronaghi and his team felt that it was unethical not to bring it to market, considering its potential to save lives. 

Today, Dr. Ronaghi says the technology has improved the survival rate of cancer patients by 20%. 

Technical founders can become skilled in business 

Scientists and researchers shouldn’t be discouraged by the business component of biotech entrepreneurship. Dr. Ronaghi cites his own career as evidence that technical founders can learn. He encourages technical founders to try their hand at business, even if they are used to a lab. 

“I feel that it is much easier to develop the technical founder to understand business than the business founder to understand the technology,” he said. “Especially if you are in a high biotech kind of a space. You really need to understand the technology and the market in depth.”

Illumina’s recent 2020 acquisition of Grail was a test of his new business mindset.

Grail was on track to go public, when Dr. Ronaghi and his team switched course and entered an $8 billion acquisition agreement with Illumina. 

There were a few key elements Dr. Ronaghi considered when evaluating the deal. 

First, they had to calculate the basic financials — when would the acquisition be profitable? 

After justifying the suggested price, they moved on to the less tangible components of the deal — what could Illumina bring to the table?

Dr. Ronaghi realized that Illumina could help Grail scale and further expand the product into global channels. From a business perspective, the deal made perfect sense. 

Early indicators for biotech success in early stage and Series A

As a co-founder of Illumina Accelerator, the world’s first business accelerator focused solely on creating an innovation ecosystem for the genomics industry, Dr. Ronaghi is familiar with a company’s earliest stage. He believes the best indicator of success for an early stage company is the quality of the founding team. 

“When you’re picking a company at the earliest stage, like the accelerator stage, the number one important factor is the team. There is no question,” he said. 

If the team is dedicated, smart, and has the skills to create the proposed technology, then it doesn’t fully matter if the business plan is fine tuned or not. 

For Series A biotech, Dr. Ronaghi has separate rules for different categories:

  • For therapeutics, teams should have a lead compound identified or have pushed a product through clinical trials.
  • For diagnostics, founders should be able to demonstrate that their tests work well and will have an impact on the subject.
  • In the software space, there should be recognizable initial customer traction. 

“Simple” advice for entrepreneurs: commit fully to your idea

Dr. Ronaghi’s advice for entrepreneurs interested in the complex biotech and life science space is relatively simple: commit fully to your business idea, and include others who will as well. 

“I see that a lot of people that are in larger companies, and they want to start a company half time. That’s not going to work. You have to leave your academic job or company job and focus one hundred percent on basically creating something,” he said. 

While this advice could apply to entrepreneurs in most industries, it is especially true for a field that centers around science and technological breakthroughs. Dr. Ronaghi believed that most biotech business plans had a window of opportunity that could easily be missed if the would-be entrepreneur did not quickly execute their plan. 

“If you’re not dedicated yourself, you cannot convince other people to join you,” he added. 

Convincing other talented individuals to join the company is key to the success of any business, Dr. Ronaghi explained. In order to accomplish this, founders should be transparent and keep their team in the loop. They also should be generous — and be prepared to give out enough equity in order to retain a great team. 

Once the team and technology is in place, founders should focus on ensuring customer satisfaction and product market fit before expanding into other opportunities, he concluded.

“I understand your technology has a lot of potential. I don’t want to see it now. I want you to focus on this market and show me that you can actually deliver a fantastic customer experience.”

The future of genomics

What’s next in the world of biotech? 

If Dr. Ronaghi were to make a new company now, it would be related to either of the following topics: 1) the relationship between one’s diet, microbiome, and overall health or 2) single cell biology.

“The reason that I’m picking up food is because that’s the number one environmental factor that the human body is exposed to…  There are a lot of leading scientists these days that believe that 90% of diseases originate from the gut,” he said. 

He views single cell biology as an area that has the potential to unlock other biotech innovations down the line. 

“We have to look at biology at the cellular level or subcellular level. So single cell biology is actually very intriguing. I really think that that’s going to actually open up new frontiers in the way we are looking at medicine.”

How to Get Started

You can read as many articles and books as you want about value propositions, product-market fit, business model design, blue oceans, and everything under the sun about startups, but at some point, you just need to get started.

That’s something that can only be learned by experience. As the saying goes, “A journey of a thousand miles begins with a single step.” Here are the very very first steps that some of our Accelerator ’20 founders took after coming up with their ideas.

***

We presented for Lean Launchpad and horribly failed because we didn’t understand the market. We did our work, and the initial judges of Lean Launchpad later became our first investors.

—William Steenbergen, Founder / CTO of Federato

***

We interviewed over 100 families to deeply understand their journey from when they decided they wanted to start a family, to pregnancy, and beyond.

We then dove deep into studies and literature to identify the drivers of poor outcomes and understand what interventions could be leveraged to address them.

Through this research and input from our mentors at Harvard, we identified the group model of care as a powerful tool for impacting health outcomes.

We then set up our first beta cohort in early 2020 with 3 expecting women and a provider. They met bi-weekly and messaged over a group chat we created for them.

These beta customers are still with us today, over 9 months later, and continue to see June as a resource to support them through the never ending questions & challenges of being a parent!

—Sophia Richter, Founder / COO of June

***

We used Google Forms quite a bit to experiment including whether or not individuals wanted to share notes in a 1-to-1 or group context. We collected nearly 5,000 notes via Google Forms before transitioning to a more functional prototype.

—Sohale Sizar, Founder / CEO of Illume

***

I called every person I knew that worked in data science to understand if they also had the problem. I tracked each of the calls in a spreadsheet and gathered notes. I also called people that were on the OTHER side of the equation (the data owners) to understand their frustrations with the process. The idea evolved quite a bit from these conversations, but it gave me real confidence that this was a ubiquitous issue in almost every company.

—Austin Osborne, Founder / CEO of Spotlight AI

***

Immediately after having the idea to create workflow-ready video conferencing, we built an initial version for use within our professional connection platform and in our team meetings. We were delighted to find that we genuinely enjoyed using our own platform much more than all other alternatives and realized that it had a potential far beyond what we’d initially thought.

—Martin Aguinis, Kamil Ali, and Josh Payne; Founders of AccessBell

***

We started building a website and speaking with early adopters.

—Robert Monaco, Founder / CEO of Exporta Technologies

***

We went to a freight event and stood up on stage to pitch it!

—King Alandy Dy, Founder / CEO of Expedock

Lookback: A History of Pear Demo Day

Sometimes the best ideas aren’t planned at all. They grow organically. That was how Pear Accelerator and Demo Day began.

In 2014, Mar and Pejman invited some talented Stanford engineers to hack in the Pear offices. They also offered their mentorship with no strings attached. That community of hackers became the first ever Pear Garage cohort, which continued into the summer by popular demand from the community.

During the summer, Mar and Pejman thought it might be helpful for the founders to practice presenting their ideas formally, so they decided to host an event and invite their network. 

“It wasn’t like a ‘Demo Day’ or anything else. We just thought it would be great to invite some of our friends to come and provide feedback,” says Pejman. 

So, 40-50 great investors from the likes of Sequoia and Accel crammed into the Pear offices to listen to seven founders pitch. 

“We had handwritten name tags and it was definitely not a sophisticated production with all the bells and whistles, but the teams were great and did their thing,” recalls Lily Johnson from the Pear Ops team. 

Those teams got the attention of TechCrunch however, which ended up publishing an article deeming the event “Silicon Valley’s Favorite New Demo Day.”

That was that. Pear now had a ‘Demo Day’. From then on the team decided to put one on every year, leading to the development of a formal Accelerator program. Demo Day moved into the more spacious Cooley offices. 

Pear Demo Day 2016

Still, Demo Day kept growing. And the Pear team’s visions alongside it.  

“The next year we needed a bigger space, so we were looking at different venues and we really wanted something to still have that Pear touch—not as sterile, or conference feeling. Pejman suddenly said, ‘What about Filoli?’” Lily remembers.

It was a dreamy idea. The historic Filoli Gardens are pristine and meticulously manicured, with 700 volunteers who landscape the entire 600 acres of gorgeous property. 

“I went to many Demo Days—you go and it’s very transactional. I thought, ‘What if we change the scenery, so you can have the same conversations in a nicer environment?’” says Pejman. 

But it was also a bit unorthodox for something like a tech Demo Day. The team wondered if it would confuse investors, or if they would even be able to find the venue, since it was a little farther out from the usual Demo Day locations in Mountain View. 

Ultimately, they decided to go for it. 

“Pear is a special type of VC firm, so I think it resonated with the brand, and it just worked with us and who our team was,” says Lily. 

Pear Demo Day 2017

With that, the big event planning and production process began—always an intensive project.

“It’s like a wedding times two or three, because there are just so many logistics that go into an event of this scale,” says Lily. “It’s such a whirlwind. I remember literally running from location to location.”

Pear Demo Day 2017

Since that first Demo Day in the garden, the event has just kept on growing and growing.

“Last year, we kept sending invites out, and then we started moving past 300 RSVP’s, which is the capacity of the auditorium. I’m starting to get nervous, like ‘Alright. What if everyone shows up?’—which never happens at an event, but in the case that it did, how were we going to fit everyone into this room?” Lily recalls. “Then we got to 600 RSVP’s and it kept climbing. So we were thinking of creative solutions. We ended up reaching out to this rental company and getting chairs that were more narrow, and we were able to fit 500 chairs and it was just an absolute miracle. I remember showing up the day of  and meeting with the equipment rental manager and we were literally going with a measuring tape across the room and just squeezing the chairs together. That was a classic.”

On top of the logistics of producing the event, there’s also the important job of supporting Accelerator founders to be on top of their game for the big day, with hours spent polishing slide decks and rehearsing pitches. 

Pear Demo Day 2017

All the hard work pays off when investors and founders gather to imagine the future together for a few hours. Plus, migrating to the massive lawn terrace from the conference room is always a showstopper.

“The garden, my God, the garden—everybody loves the garden!” Pejman laughs.

Indeed, with the beautiful garden environment, live band, hors d’oeuvres, minibar, and product demo booths, Pear Demo Day has become a righteous, glittering party over the years, far more than a mere networking event. 

“We try to keep it interactive and promote relationship building in a fun Pear-ish way,” says Lily. “The style of Demo Day is a nod to how Pejman has approached everything, where he was thinking, ‘I really want the networking afterparty to feel like an opportunity for people to chat and hang out. I want people to get to know each other, but still have a good time in the process.’”

Pear Demo Day 2018

At the end of the day, in spite of all the glitter, Demo Day is really about something quite simple — getting to celebrate the hard work of Accelerator founders.

“As corny as this sounds, it is always one of my favorite moments: where you just high-five each other and you’re like, ‘Damn, we did it—YES!’” says Lily.

While we won’t be gathering in the gardens this year, that is the spirit of Pear Demo Day that will never change.

How Biotech Company Xilis Successfully Fundraised and Commercialized Their Technology

This case study is about Pear portfolio company, Xilis, founded by David Hsu and Xiling Shen.

Using academic research to help patients
Go commercial, or continue academically?
Pitching a technical product to investors
What’s ahead for Xilis

Using academic research to help patients and make a real impact

Xiling Shen still remembers the moment he bumped into David Hsu in the hallway at Duke University during his first job interview. The two chatted only briefly, but David made an impression. Later, David formally interviewed Xiling for his second interview, and the two discovered that they shared many research interests. 

“I just remember…sometimes, you just feel like it’s love at first sight,” Xiling jokes. 

“As an academic junior faculty, you’re focused on publishing papers. But when I was talking to David, he asked ‘How do you think about how to help patients?’ and that suddenly opened a door—that’s where you really make an impact. 10 or 20 years down the road, do you really want to be remembered for how you published this many papers that probably no one reads anymore?”

The conversation also convinced Xiling that he had to move down to Duke. There, he and David worked together over the next three years. They focused on the big question of how to use patient-derived models of cancer as a potential diagnostic tool. 

Patient-derived models of cancer are created by growing small versions of tumors taken from tissue donated by patients.

“Patient-derived models of cancer are great for research or discovering new tools for discovering new drugs. The problem is, they’re not very useful in a clinical setting,” says David. “The main reason is that a lot of these models take too long to make, so I can never use them in real time to guide patient care. I don’t have time to grow these models to do all this testing.” 

That was where Xiling fit in, with his biomedical engineering research and expertise in organoid formation. The two developed “micro-organosphere technology,” a microfluidic-based method of growing miniature organoids. David saw that this new technology had the potential to be used as a diagnostic assay in real time to guide patient care.

“I’d been doing patient-derived models of cancer for a decade, and until we started making these droplet organoids, I never felt that there was going to be a patient-derived model of cancer that I could potentially use clinically as a diagnostic tool,” says David. “I’ve worked with cell lines, regular organoids, patient-derived xenographs. Because of the limitations, they were never going to be able to be used from a clinical perspective, and there’s plenty of companies who have tried and it’s been very difficult. 

Go commercial, or continue academically? How to evaluate and make the decision

With the discovery, David and Xiling faced two options: continue researching academically, or try to create a company around their new technology. The two ultimately decided that they could develop the technology faster by commercializing. 

“When you work in an academic lab, sometimes there isn’t that urgency. When we’re running the lab, we have 20 other projects to do—so, sometimes we lose our focus because we go on other tangents, depending on what piques our interest,” says Xiling. “From a company standpoint, you have to meet deadlines, you have timelines.” 

Understanding which path is right to pursue requires understanding the differences in the two “worlds”. Academia is a publication-focused model of research, thus novelty is more important, and it’s okay if the research works, say, 70-90% of the time, as long as it produces groundbreaking knowledge. 

For research that is intended to be commercialized, the technology obviously needs to work 100% of the time and meet market needs. There is heavy emphasis on quality control and product development, which often cannot be done in academia. Moreover, these are not the typical kinds of projects that graduate students pursuing publication will want to work on anyway. 

Xiling often warns junior students and postdocs eager to pursue entrepreneurship not to go out to investors prematurely, when a technology is not ready for commercialization. As with starting any company, the fundamental proof of concept needs to be complete before raising any funding. You need to collect feedback to shape and focus your technical idea and effort.

“The typical mistake is you develop a product for an imaginary customer, or you develop something where there’s no path into the clinic because of the regulatory or reimbursement reasons,” says Xiling.

Students can also be tempted to start a company around a solution they’ve discovered that is only an incremental improvement.

“People think, ‘Hey I can do this 30% better.’ But, you’re not going to replace the existing product for doing 30% better,” Xiling says. 

It is also important to realize that technology development is only a small part of getting a company to succeed. 

“70% is about all the other things—operating, marketing, sales, BD…” says Xiling. 

Academics can also underestimate the importance of management in building a successful company. 

“You don’t become a professor because you are good at managing, but that’s very important. Managing talent and managing companies is certainly a lot different from managing an academic group,” says Xiling. 

David and Xiling have found success by hiring the right people.

“Getting the right people dedicated to tasks where they can play to their strengths—I think that’s the most important thing,” says Xiling. 

Pitching a technical product to investors

Mar and Nils asked Xiling and David if they might be interested in pitching their product at Pear Demo Day — a week and a half before the day. 

“I remember we ordered the t-shirts,” Xiling laughs. “And we came up with the name, Xilis, not because I’m ego-centric, but David was just like, ‘Oh that looks good.’ The other option was like ‘Davis’ — David’s name with my name.”

At first, David and Xiling were resistant to practicing their pitch, despite Mar and Nils offering to help.

“We had a little arrogance, because you know, we’re faculty. That’s our job, presenting thoughts to an audience, and we love it,” Xiling said.

“Nils wanted us to practice all the time, but we were like, ‘We don’t have time to do this thing,’” David laughs.

In the end, the two admit that the practice was quite helpful. 

“Even if you’ve been presenting for such a long time, you’re talking to your peers. It’s very different to talk to a lay audience and really get them to understand why this thing is important—which was so self-evident to us,” says Xiling. 

The practice also showed in the results. Prior to Demo Day, Mar had already introduced Xiling to a few VC’s, but the conversations had not gone anywhere. After the presentation, investor interest flooded in within 9 days. Xiling and David flew back out to the Bay Area on a Thursday night and returned to Duke on Monday with term sheets in hand. 

“Pear provided an opportunity to hammer out 80% of the questions we got from investors,” says Xiling. “No matter how much you prepare or think about something, nothing can replace getting real-time feedback.”

Through practicing with Mar and Nils, and then through the real live experience of meeting with different investors. David and Xiling were able to continuously refine their pitch and understand the common themes of what investors cared about and how to communicate effectively with them.

The first important learning: explain your product as clearly as possible with crisp messaging.

“Since we’re in the field, why the technology is important is very self-evident to us. We wouldn’t normally spend so much time explaining that in academic presentations,” says Xiling. “But to the lay audience, you have to be mindful of any jargon coming out of your mouth, and you have to make it clear.”

The second important learning: have an explicit explanation of your go-to-market strategy.

Academic founders have often thought very deeply about their technology, but haven’t spent as much time thinking about their exact customers and how they will go about gathering them.

“For us, we were thinking, ‘This is helping patients,’ and that’s what we had always thought about. But for investors, they’re asking, what is your plan? What’s the first product? What’s a second product? Who do you have as customers? What’s the timeline? It has to be very spelled out, the exact steps and how much investment you need,” says Xiling. “We were not even thinking about a lot of those questions. But thinking back, those answers could definitely have been better thought out or better spelled out, more deliberate.” 

Xiling also recommends really thinking through what kind of company you are building. 

“I think in general, there are two types. One is the transformative, paradigm shifting type—high risk, higher reward. The second is more incremental, but you have a faster go-to market and could potentially be profitable as a private company,” says Xiling.

“For VC, especially Silicon Valley VC’s, they want the first type of the company—they’re going out to make 100x returns. So, kinda understanding what the investor is looking for and going after the right type of investors is important.”

Finally, it’s absolutely critical to have the right team. 

“At the end of the day, it’s about the execution. Do you have a good balance of leading technical people, but also experienced business people? You want to have a team that has the right business experience in the intended market, so that investors feel the investment is more de-risked. I think that’s probably the biggest challenge for most academic teams. It’s often the piece that would increase their attractiveness significantly.” 

What’s ahead for Xilis

Xilis is currently focusing on conducting clinical trials and in talks with big pharmaceutical companies, as well as getting on the path to becoming CRIA certified. 

And like any startup, team building is an ongoing process.

“We are kind of a unique company in terms of being very interdisciplinary. Engineering, biology, clinical, and of course then adding business people, software, hardware… so we’re really focused on building a team that has complementary skills. Right now, the next hiring priority is continuing to hire the right business expertise.”

From Software Engineer to CTO

Cathy Polinsky, former CTO at Stitch Fix, chatted this week with Pear associate Harris, who leads our talent initiatives. This is a recap! Watch the full talk at pear.vc/speakers.

It starts as an obsession. You play with your first coding language, and you’re hooked. You keep learning new languages and building cool things with your new skills. You’re doing this in an exciting environment with enthusiastic mentors who support you.

Cathy Polinsky, former CTO at Stitch Fix, was lucky enough to grow up this way. In the 80’s, Cathy’s mother was a teacher, and Apple personal computers had arrived at school. Cathy’s mother thought the technology was interesting and bought one for their home (before they had a VCR!).

Cathay learned her first programming language, Logo, and went on to learn basic programming. Computer science was so new then that there wasn’t formal education for it in school, but growing up in Pittsburgh meant that Cathy was able to go to a summer camp at Carnegie Mellon.

“We did algorithms in the morning and more hands-on programming in the afternoon with robotics and maze solving problems, and I just really got hooked and knew I wanted to study it after high school,” said Cathy.

Sure enough, Cathy did just that, and went on to a thriving computer engineering career. In this fireside chat with Pear, she looks back at her career and highlights the building blocks she gained from each role to help future engineers make decisions about their own careers.

“A career is made in hindsight, not while you’re on that path. While you’re on it, it might not feel straight, but you can in retrospect see this arc of where you’ve come from. I’d say I have a little bit more of a clear arc than most, but I know many other people who have had different paths that have gotten there or to some other destination that they have been really excited about.”

Laying the groundwork as a software engineer scaling early Amazon
Hands-on, non-stop building at an early stage startup
Moving into management and people skills at Yahoo and beyond
Cathy’s Career Advice
Cathy’s Advice On Hiring
Tactical Hiring Tips

Laying the groundwork as a software engineer scaling early Amazon

Like many young graduates in computer science today, Cathy’s first job out of school was as a software engineer at a fast-growing company — Amazon, in 1999, right before the dotcom crash.

“I thought I’d missed the interesting times at Amazon. I thought I’d missed the early stage startup. Little did I know, I was living the interesting times. It was a gritty time. I was there during the dotcom collapse and all my stock was underwater,” Cathy recalls.

Things were still early enough for Cathy to grow fast with the company (she had a door desk when she started!). Amazon was in the hundreds of engineers then, and everyone was brilliant, but the rapid pace meant that the environment was a bit chaotic. The code base was a mess for example, with little documentation.

“It was an amazing time where I learned how to be an engineer being in a company that was scaling so fast. I learned a lot about how to hire people earlier than any other job I would have gotten,” says Cathy.

At Amazon, Cathay had the opportunity to learn from the tech giants. She developed solid, rigorous ground for her career learning to ship things at scale and having to think through everything from interview process to database and schema design, to hardware constraints and automation and testing.

But in addition to engineering skills, Amazon helped Cathy to gain a deep appreciation for the growth mindset — a mindset that serves her even today.

“Jeff [Bezos] never wanted to be written in an article and have Amazon in the same sentence with any other early stage dotcom company. He only wanted to see himself with the giant companies that were out there. I’d say that I was much more of a voice of growth and opportunity as a leader at Stitch Fix in the sense of: ‘How can we invest more, and how can we grow more?’ and making sure that we were keeping our eyes always on the long-term.”

Hands-on, non-stop building at an early stage startup

Cathy soon got the startup itch and wanted to see what early startups were like, so she went and joined a 13-person startup in San Mateo.

At first, with only two years of work experience at a scaling company, the early startup environment felt quite different. Cathy was surprised to learn that there were no automation suites and other big tools she took for granted at Amazon.

“But, I wrote way more code there than any other place, and I got to wear more hats and I got to go to a pilot customer and be involved when we were doing discussions about name changes and logos,” says Cathy. “You got to interact with people that weren’t just tech and be much more involved in the company on a different scale .”

Cathy also experienced the pain of building great products that didn’t work out.

“The company never really got off the ground. We only had two pilot customers, couldn’t get sales. There was a recession going on. It was heartbreaking when we closed the door to feel like I put so much of my blood, sweat, and tears into building something that I was really proud of.”

It was valuable first-hand experience in understanding that a successful company was not just about building a great product, but also about building the right thing and checking in with the market for early feedback.

Moving into management and people skills at Yahoo and beyond

After the startup heartbreak, Cathy turned back to big company world, though she “wouldn’t recommend to anyone to overcompensate that strongly,” she laughs.

At Oracle, Cathy realized she missed the fast pace of earlier companies, and sought to move into management. A friend pointed her to a position opening up at Yahoo.

Cathy ended up being offered her choice between two roles there — an engineering management role and an engineering lead role. She decided to try management and never looked back, going on to lead engineering at Salesforce after Yahoo, and on to the C-suite at Stitch Fix.

One of the first lessons Cathy learned in her first management role at Yahoo was to stay out of the code. The engineering manager she inherited the role from said that she regretted being so hands-on and jumping in too quickly to fix bugs or help her team with the solution.

“I really took that to heart. If I’m jumping in to heroically save the day, I’m not actually working on the fundamental issues that are going to help the team be successful in the long run. That has really influenced how I spend my time and how I look at the role,” says Cathy.

That is, transitioning into a management role means focusing your attention more on the people issues rather than the tech issues.

“I’d say that I choke often — that I would have been better off being a psychology major than a computer science major,” Cathay laughs. “Dealing with people in some of these large organizations is much more complex, and not deterministic in any way. You never know if you’re doing it the right way or not. I think that I’ve spent more sleepless nights thinking about people issues than I have about technology issues.”

In all the companies Cathy has been in, it’s been key to treat every single tech production incident as a learning opportunity.

That’s because if you’re shipping software, it’s inevitable that you are going to break something eventually. So, the question software engineers should be thinking about isn’t “How do we avoid breaking things?” but rather, “How do you make sure you don’t have the same problem happen again, and how do you make sure that you learn from it and get better and have other people around you learn from it, so they don’t have the same mistake that you had?”

Cathay is a fan of blameless postmortems.

“We get in a room and we do a postmortem of what happened, but the only rule is you can’t point fingers at anyone. You don’t name any names. You’re not trying to get anyone in trouble. If you can really approach any problem with that open mindset and learning, then you will make sure that you uncover all the problems in the areas and you won’t have the same problems again.”

Cathy’s Career Advice

  • There’s no wrong answer to big tech vs. join a startup vs. start my own company.
  • Take the roles where you’re going to learn the most.
  • Follow your passions.
  • If you are interested in something that’s different than what you’re doing today, just tell people that. People will see you differently and think of you when opportunities arise when you tell people what you’re passionate about.
  • Don’t worry about where you’re going to be 10 years from now, but have an idea of what you want to do next.
  • If you don’t know what you want to do next, talk to a lot of people.

Cathy’s Advice On Hiring

Anytime you can, hire someone smarter than you.

A lot of people have a hard time doing that. They think, “Oh, they have more experience, or they’re smarter than I am, what am I needed for?” You will never ever fail if you were hiring people that are smarter than you and know more than you.

Extend outside your network and find people who are going to push you.

I have worked in a lot of companies that focus on hiring within your network and telling the great track record they have for internal referrals. As a woman engineer, I think that’s really dangerous. I think that you have only a specific network of people and if you continue to hire people in your network, you’re only going to see people who look exactly like you and you’re not going to push yourself and get diverse opinions around the table. You’d be better off really trying to extend outside your network and finding people who are going to push you and bring different experiences to the table than you have in your own. That’s something that we were really intentional about at Stitch Fix — making sure that we were reaching out into diverse networks and seeing people that were different than the people that we already had.

Follow the structure of what you set out to do — don’t rush.

One of the challenging hires was not someone who worked directly for me, but was one level down, and was a referral from someone in the organization. We did a rush job hiring and leaned on the referral, but really did not show up living the values that we had as a company. We started to see some things that didn’t show up the way that we would expect for someone of their level. When we did a debrief on what happened, we realized that we hadn’t done reference checks and we hadn’t really done a full check on: ‘Is this person a good fit to the values that we had?’ It was a pretty big miss that we hadn’t followed the structure of what we had set out to do and really caused a lot of friction across the team because of it.

It’s critical to understand what you need for the stage of your company.

In the early days, Amazon would rather hire someone that had a couple of amazing interviews and a couple of bad interviews than someone who was mediocre across the board. They wanted to see someone who really excelled in a specific area, even if it meant they had holes in other areas. I like that sense of playing to someone’s strengths, especially as a larger company, you can take more liberties in that way.

It’s harder in an early stage company… you have funding for three hires. You’re going to need to hire some real generalists who like to build things, who can also answer phones and do hiring and operations and the like. Thinking about those first hires as generalists who are interested in getting to wear a lot of different hats is important. It’s kind of fun for the people who do it, to get to build things from the early stage.

Then you have to think about how you scale it. Because at some point, those people are probably not going to be happy after you get to a team of 100 where they’re not the best at any of those things. Either they scale, and they still know everything and are this amazing person that can jump in anywhere and add value, or they get really dissatisfied that they can’t really play the same role that they had before.

As you’re scaling things out, you’re hiring more narrow generalists of, “Hey, we really need someone who understands AWS deployments, or we need someone who really understands this mobile technology stack,” or whatever it might be.

So, if you’re really thinking about building and scaling with the business, as the business scales, you have to think about what stage you’re in and know that what works before is not going to be the thing that’s going to be successful after you get to 50 or you get to 100.

Tactical Hiring Tips

  • Take home interview questions and pair-programming interview questions are a good way to see what people are going to do in their day to day. You don’t work by yourself — you work in a team and so seeing how people work with a team is good.
  • Have candidates interview with non-technical team members and solve a problem together. It’s important for technical people to be able to talk with nontechnical folks. At Stitch Fix, this practice has enabled a much higher EQ team.
  • Have inclusive language in your job description and list fewer requirements to be more welcoming to women. Avoiding bro-like or gendered language is of course the obvious thing to do, but what might be less obvious is that long requirements can rule out certain populations of people! Men will tend to apply anyway despite not meeting all requirements, and women will tend to filter themselves out because they don’t have nearly enough of the requirements on this list.
  • Sit in on every debrief. You don’t necessarily need to meet every candidate, but you should listen carefully to candidate discussions and guide your team. “There were times where someone would explain the interview and then have a strong assessment on whether we should hire the person or not. I would listen to their rationale, but not agree with the outcome based on their assessment, so we could talk about that and dig in. Sometimes there were some things that changed the way that they thought about the interview, for example, something like, “They weren’t very confident in their skills.” We would ask, “Why did you think that?” And it could just be a passive word choice that they used, and someone else points out, “They’re actually really confident over here — and is that really a job requirement that you need?”

Hello, World!

Welcome to the Pear blog!

There’s a lot of startup content out there, so we thought we’d introduce ourselves and explain what we hope to accomplish here.

Our Manifesto: we love 0 to 1.

We believe it’s the most exciting stage of a founder’s (very long) journey.

We know — it’s also the messiest, most confusing, hardest part of the journey. There’s not as much information out there about this stage, partially because of how messy it can be. It’s hard to use tactics, because everything changes so quickly this early.

Most founders think it sucks and want to get out of it as fast as possible.

We want you to get through it as fast as possible too, of course, but our greatest joy in this work comes from helping you do just that—because we’ve been there ourselves!

Our content is intended to:

  1. Put founders first. This content is for you.
  2. Clarify and break down different parts of the murky 0 to 1 journey.
  3. Help you develop the frameworks you need to solve your company‘s unique problems at this stage.

We hope this blog becomes a valuable resource to you during this scary and thrilling stage of building a category-defining company.

In the process, we also hope this helps you get to know us—what we care about, and how we think—a little better as well. 

Design Thinking Q&A with Bob Baxley

As we move into the last days of summer, with the world still very much uncertain, we highly recommend giving Bob Baxley’s Pear talk on conditions, constraints, and convictions a watch at pear.vc/speakers.

Bob shares three Cold War stories of magnificent innovation — reminders of the amazing things humans have accomplished and can still accomplish even in trying times.

Below, find insights from the Q&A session for thinking about conditions, constraints, and convictions for our own times.

When are constraints good for creativity, and when are they bad?
What can founders do to help creative teammates be most creative?
How do you figure out which problems to solve and which to defer?
What signals can you look for to indicate that you need to engage the creative side more, versus getting it done?
How do you find inspiration for design during the initial brainstorming phases?
How can we think about current pandemic conditions of not being able to see each other?

Q: Constraints may have boosted Dr. Seuss’s creativity, but it seems that a lot of conventional wisdom also suggests that having too many constraints can be bad for creativity — how do you reconcile this?

I think the question is getting at two different kinds of constraints. One is a resourcing constraint and the other one is defining the problem space. Trying to do too much with too few people is a different challenge. That’s really a question of prioritization, so I’ll leave that aside.

As a creative professional and somebody who’s been designing software products and leading teams for three decades, the worst thing you can do is to give me a lot of space and a lot of time. Every creative I know, we’re master procrastinators. We will always put off finishing the thing. If we have a big, giant open field, we don’t quite know how to get started. I’m a big believer in a well-defined problem space.

I like making sure that you have to show progress on a steady basis. With my teams at Apple and now ThoughtSpot, the team has to show me work basically every 48 hours. We are constantly looking at work. It keeps people from getting too caught up in their own heads and wandering off in the wrong direction, and it keeps us together as a team. It reduces a lot the emotional, creative pressure on people.

Structure’s the difference between an empty field and a baseball diamond. You can’t have a game if you don’t have the diamond. You can’t make progress if you don’t have the diamond. You’ve got to have some boundaries to make progress and a ton of amazing art.

If you really go back and you look at Chopin’s Preludes are Bach’s Goldberg Variations, there’s a ton of different, great artistic achievements that were set up as a technical problem that the artist was trying to solve. They go into the work that way. Most artists don’t just show up at the canvas and see where it goes — like they’re trying to accomplish something.

Q: What can we, the founders, do to help our creative teammates be most creative and set the right constraints without setting too many?

In all designed problems, what you’re trying to do is help the person to understand the problem. Don’t get prescriptive about the solutions. Try to make sure we’re trying to accomplish the same goal, and then evaluate the design solution in the context of the goal.

A story I tell is: at a company I was working at years ago, we had a homepage. There was a link on the page, and the product manager said “Bob, you have to make that link blue.”

I said, “Why do we have to make a blue?” They said, “Just make it blue.”

We got in this debate about it being blue. I said, “No, I don’t want it. That’s going to ruin the aesthetic of the page.” And they said, “Well, I want it” and went behind my back and made it blue.

Then we had a heated discussion in the hallway. I eventually said, “What was it you were trying to accomplish by making it blue?”

Turns out, people couldn’t see it. And I said, “Oh, so it wasn’t prominent enough?” And the product manager said, “Yeah. It wasn’t prominent enough.”

I said, “Okay, great. Well, we’re professional graphic designers. We have 15 ways to make it more prominent, one of which is making it blue. What you did is you leapt to a solution, and you didn’t really present the problem to us.”

For founders and executives, I spend most of the conversation trying to get them to more specifically narrow down our understanding of the problem and to make sure that we’re on the same page with the problem. The benefit of doing that is that when you find the right solution, everybody will agree.

I often get questions about how to resolve creative conflicts between different design solutions. I always say — that means you haven’t agreed on the problem. Because if you had a shared understanding of the problem, the solution would be obvious.

Q: How do you and your team tend to figure out which problems to solve and which ones to defer or ignore?

Here’s another story, about my friend Steve.

When Steve was getting ready to work on Keynote for the first time, Steve went to Roger Rosner, who was the VP of engineering responsible for iWork. Roger asked, “How should we think about Keynote? We got to compete with PowerPoint. There’s already these other presentation packages. What should we do?”

Steve said, “Roger, there’s three things with Keynote. One is it should be really difficult to make ugly presentations. Two, you should focus on beautiful cinematic transitions. And three, you should optimize for innovation over PowerPoint compatibility.”

I use those as examples of strong tenets. Each one of those statements, for example, if we just take the last one, optimize for innovation over PowerPoint compatibility — you could imagine the thousands of hours of debate that the product team would have had if they didn’t have clarity on which side of that debate to be on.

Steve just said, straight off the bat, make it difficult to make ugly presentations. That’s a whole set of things to take out of the way. So, we get beautiful cinematic transitions, which to this day is the hallmark of Keynote and why I can’t stand using Google Slides or PowerPoint. That’s a very clear direction.

I think a lot of times when you’re trying to figure out what to do, do you really have clarity around the tenets? Because if you have that clarity, the priorities fall out much quicker.

Q: What signals do you look for in your own work that indicate you need to engage on the creative side more deeply versus buckling down and getting it done?

This is an interesting question we’ve been dealing with internally at ThoughtSpot. When does something pivot from being exploratory creative work to execution mode? It’s always a delicate balance, and it’s a little bit like being a parent. When do you give your kid that extra thing to go do? When do you let them go further, versus when do you stay closer to them?

There is a point with almost every project where the team has some sense of, “No, this is really what we want to go do.” I can’t give you a rubric for how to judge that, but you can usually feel it in the room. The debates are becoming more and more myopic and you don’t seem to be making the same level of progress. There seems to be general agreement that this is the thing we want to go do. At that point, you have to pivot into execution mode. There’s a point where you just have to sit down and finish the thing.

As a creative, I enjoy working in both those modes, because it’s emotionally draining to sit in that level of uncertainty of wondering what we’re doing. There’s a point when it’s actually really rewarding to put all that uncertainty behind you and just go and finish the dang thing.

We tend to do that with deadlines. We sign up for some sort of commitment. Maybe there’s a company event that you have to have a demo ready to show. Maybe you have to give a presentation like this. You sign up for different kinds of commitments, and then you can use that commitment as a forcing function.

Q: How do you find inspiration for design during your initial brainstorming phases?

In terms of software, I spend a lot of time just looking around in the world. I’m the annoying guy at the deli that asks to look at the point of sales system. How does the Clover UI actually work? I sit and chat with people about self-checkout at Safeway and how it sucks and why it sucks. There are software products everywhere, so there’s tons of inspiration to be found just looking around the normal world.

Q: We have a lot of new constraints these days — one of which is that we’re not with each other. What are your thoughts on our current conditions, and where do you see it going?

I’m on the side that says there’s no great reason to go back to the office. I always try to get my team to separate the idea of working from anywhere from the idea of the lockdown. Imagine your kids are still going to school, and imagine you can go work at the Starbucks, and you can go see your friends for lunch. You can work from Hawaii if you want. How does that feel?

Most people say, “Oh my God, that feels awesome” — so, it’s not the working from home thing, it’s the lockdown. The lockdown is not something within our control, as individual companies or individual citizens. So you have to parse those two.

I firmly believe that we can make this work, and I think there are some unique benefits to working from anywhere. The fact that we can do things like this company events with a few hundred people from around the globe — we wouldn’t have done that in the past. If we had, it would have been a huge deal, and it would cost us an enormous amount of money.

You’ve got to dance with the constraints, and stop thinking about what you’ve lost by not being in the office, and start thinking about what you’ve gained — because you’ve gained a lot.

Pear is Partnering with Gatsby!

Community is one of our top values at Pear. We believe deeply in the power of deep, authentic connections — it’s how founding partner, Pejman, went from being a rug salesman to a tech investor, after all.

Since the early days, we’ve devoted a lot of energy into nurturing a vibrant community of high-caliber founders, and we know how much work it takes. That’s why we’re excited to announce our new pre-seed partnership with a company seeking to empower the superheroes who do this important work: Gatsby.

Like all of the founders we back, Zach Rivkin is someone who deeply understands the problem he’s working on. As Joe Lonsdale’s Chief of Staff at 8VC, Zach had a hand in helping to manage Joe’s network. One of the most meaningful ways of nurturing relationships is to host intimate events, and Zach quickly became very familiar with the painful process of pulling such gatherings together.

“Let’s say there’s someone visiting from out of town, and you want to have a dinner with them, and maybe eight other people in your network. Who should you invite? How do you send those invites out? How do you figure out the seating chart? How do you track people’s dietary restrictions? How do you collaborate on this with other people in your team? There are lots of these small little things. I’d be back and forth all the time with the admins and executives trying to figure out how to work through these problems. And if these things break, it’s really bad!”

Image for post

As someone with a front row seat to innovation, Zach thought, why don’t we actually try to use technology to fix these annoying workflow issues?

Back in August, Zach had met his first cofounder, Michael Zuccarino: an engineer at Pinterest with a deep passion for building indispensable products. The two had already been building on the side for fun and loved working together. They then brought in creative technologist, Chris Zelazo, from Pinterest to complete the team as their third cofounder. Michael and Chris first worked together on a project for Apple to rapidly prototype a new feature in the Pinterest app, which was demoed and presented at WWDC ‘19.

The magic moment happened when these three builders aligned on the Gatsby vision: build a powerful technology system to serve the administrative workers who manage high-stakes, complex relationships and their related workflows, such as intimate event planning.

Image for post

You might be wondering why a good tech solution doesn’t exist yet, especially in such a tech-forward industry. We like it when our founders have some ideas:

“I think admins are somewhat trained to always make it look like everything is working seamlessly behind the curtain,” says Zach. “Also, I don’t think a lot of people ask admins for their opinions on what could be done better. It’s framed as a very execution oriented role as opposed to strategic, but I view a lot of this administrative work as highly strategic.”

We love that Zach has empathy for his users in spades.

“These admins are super powerful in a way that most people overlook. Their executives rely on them. They have tons of context and knowledge in their head, because they see everything going on. They own the keys to the castle and determine who gets meetings and who gets pushed forward.”

Indeed, we agree with Zach — it’s time to supercharge those powers with technology. We’re thrilled to be partnering with 8VC to back this incredible team.

How To Actually Be Helpful to Early-Stage Founders

This post is an excerpt from longtime startup mentor and Pear Operating Partner Touraj Parang’s onboarding session for Pear Accelerator S20 mentors — handpicked industry experts who we personally match with each founder in the cohort. Interested in being a mentor? Reach out!


Build the Foundation: Get to Know the Team On a Very Personal Level
Establish a Heartbeat
LISTEN LISTEN LISTEN
Be a Good Coach and Look to the Future

By now, “let me know how I can be helpful” is such a cliched offer to founders in Silicon Valley that it’s become a Twitter meme. Being helpful to founders is often framed as a means to “network” in the Valley, or to become a successful angel investor, but the best mentors, like Touraj Parang, do it out of true love for the founder journey.

Touraj began “mentoring” as an entrepreneur in the mid-2000s via getting together with other entrepreneurs and sharing best practices. After selling his startup, he began angel investing, and being helpful was a natural thing to do for the founders he invested in. Over time, he shifted to simply advising without investing for the love of it.

“I personally like to know: what are the latest technologies or what are people thinking about? How are they trying to solve these tough problems? I take satisfaction in being able to help other entrepreneurs achieve their dreams, paying it forward. Lots of people mentored me and helped me, and so I feel like that’s the way Silicon Valley works.”

Especially at ground zero, companies can barely look like companies. It’s a different ballgame from mentoring more advanced companies. Touraj draws on his hard-earned years of wisdom to share best practices for mentoring founders at the earliest stages of a startup.

Step 1 — Build the Foundation: Get to Know the Team On a Very Personal Level

Most early-stage founders are struggling to answer very similar questions or challenges:

How do we grow the team? Who do I need to hire? What do I look for in a new hire? Is it how much culture matters? How much of a stickler should I be about culture if I need someone now?

How do we find that product market fit? What is really even my core value proposition? Who is my customer? Do I sell to bigger customers and a more expensive product or to smaller customers with a cheaper product?

“A lot of these questions are very much existential. It’s just picking a direction and not knowing which way to head,” says Touraj.

Fundamentally then, mentoring an early-stage entrepreneur is almost like being a therapist. Your role is to help founders figure out what their values are and who they want to be in the context of their company.

There’s no right answer to these questions, and that’s why it’s so critical to know the team on a very personal level.

So, before you even get into the idea, the market, the competitive landscape and all the other fun things about the business you’re working with — really get to know your founders.

“You really want to try to see the world as much as you can from their point of view. Because then you can actually help put things in a language that they understand or motivate them in a way that they would really click with it.”

What is their background? What have been some past challenges or extraordinary achievements that they have had? What are their personal aspirations and ambitions? Try to probe into their areas of strength and what they consider to be their weaknesses, individually and as a team.

Understand what success looks like to your mentees. Capture their initial goals, even if they are vague, and start from there. Though many similar challenges come up with early stage founders, the founders themselves are likely all very different.

“I try to level set initially and understand, ‘Where are they coming from?’, and then be responsive to where they are, and meet them where they are, rather than just having uniform advice for everybody. I try to be very mindful and personalize the guidance I give.”

Step 2 — Establish a Heartbeat

Part of building a solid personal foundation with your mentees is to establish a rhythm of the relationship. Whether it’s a weekly or biweekly meeting, put it in the calendar right off the bat. Hold that slot in your calendar and make sure your mentees put it in their calendar and stick to it.

Once everyone gets busy, it can be very easy for the weeks to go by and lose that thread. While it’s understandable that the meeting may need to be moved occasionally, do all you can to hold your mentees accountable to showing up for the meeting, and make sure that you do your share and stay available as well.

Step 3 — LISTEN LISTEN LISTEN

Once you’ve established the basics, the key skill to being a successful mentor is to be patient and practice being an active listener.

Active listening to me is not only hearing what the person is saying, but then asking questions to get to the deeper layers of what they’re struggling with,” says Touraj. “It’s engaging in a dialogue and withholding advice until you understand the root cause and what the objective is that you’re trying to achieve in that conversation.”

When a founder first comes to you with a complaint about a situation, the root cause of that complaint is often not clear. Sometimes founders struggle because they’re not clear on what goal they need to achieve. Sometimes they know their goal, but they don’t know how to achieve it. Some founders are very detail oriented but have a hard time of going higher up and looking at the big picture. Some founders are so academic and big picture that they don’t really see the operational steps necessary to get where they want to go.

You want to create a space for open dialogue so that you can get a clearer picture on the situation.

Get into that mode of investigative work. Part of that is nudging them by asking probing questions.”

Some example questions Touraj suggests:

  • What do we learn from this outcome?
  • What hypotheses are we trying to validate?
  • Are there other solutions to the same problem?
  • What you’re putting your efforts into — is that the highest priority?
  • Do you have resources to be successful? If not, what do you need and in what order?

Note that through all of this, your role is NOT to tell your mentees what to do. Remind yourself to address the assumptions, rather than making assertions. Try to stay away from ‘You need to go do this.’

“It’s good for founders to know your role is not to provide answers, but to be a thought partner, to be a sounding board. Let them draw the conclusions. Once you clarify the assumptions and the goals, they can come up with how to get there and sometimes they come up with it much better than you could.”

If the founders are hitting roadblocks or feel stuck, a helpful approach is to suggest options. You might say, ‘In other companies I have seen, these are some of the things that others have tried. Which one sounds good to you?’

Touraj notes that newer entrepreneurs can be hesitant to open up about their problems.

“They feel like because Pear is an investor or potential investor in the next round, they always have to give the happy talk and seem confident,” says Touraj.

“You have to make them comfortable and say ‘Look, it’s okay. It’s okay if you have challenges. We have all had challenges, and it’s actually a good sign that you have challenges and you’re seeking help, rather than trying to white-knuckle it and then fail.’ They need to feel that they’re not being judged in any way, and that really, as a mentor, you’re here to help, you’re not a secret agent of the VC firm.”

Step 4 — Be a Good Coach and Look to the Future

When you’re working with early-stage founders, remember that you are also working with future leaders. As such, for maximum impact, go beyond the therapist role and take on a coaching mentality.

“It’s about seeing what skills we can give them, so that they become great entrepreneurs and leaders as their startup grows. I try to encourage a lot of reflection and self improvement,” says Touraj.

One way to do this is to train your mentees on best practices that you have found useful in your own life or in the organizations you have worked in. Although Touraj was an entrepreneur, many of the processes and frameworks he shares come from his experience at larger organizations like GoDaddy.

Touraj also works to hold his mentees accountable to their own goals.

“When we are meeting, I always make a point of writing down every goal, or every statement they make saying that they will go and do certain things. In my next meeting, I refer back to those and make sure to see whether they were done and if not, why not, so that they get this habit of accountability — if they say something, if they commit to something, they’ll follow through with it.”

In setting their own goals, however, founders may not be stretching themselves or taking enough risk. A good coach will figure out exactly how far they might need to push a founder. The best coaches help their protégés achieve things they didn’t know they were capable of.

“I think one of our jobs is to encourage founders to be bold, to experiment. And that it’s okay to fail and to learn as long as you learn from it.”

Zero to IPO in a Downturn

This is a recap of our partner Ian Taylor’s April 27th fireside chat with Matthew Prince, founder and CEO of Cloudflare. Watch the full talk at pear.vc/speakers, and RSVP for the next.

Cloudflare was born in 2009 during the Great Recession, and recently went public last year. As we continue to make our way through the economic downturn caused by COVID-19, we’re looking to Matthew Prince, Co-founder and CEO, for insights and advice on starting a company during hard times.

What a recession teaches you
Don’t start a company with your friends
Figure out your unfair advantage in hiring

What A Recession Teaches You

As many have said before, some of the greatest companies have come out of recessions. Matthew’s business school classmates included the founders of Rent the Runway, ThredUP, and Tough Mudder. Matthew thinks there are two reasons for that.

“If the economy had been roaring, and if everything had been going really well, I’m not sure that Michelle and I would have ever taken the risk to start a business. At some level, adversity makes you start to think about other paths that you can take,” says Matthew.

Michelle, Matthew’s co-founder, had completed her MBA summer internship at Google. Traditionally, if interns did well over the summer, they could expect an offer to return after their MBA. That year, the recession meant that Google was not making offers to anyone.

The second reason great companies come out of recessions is that recessions force a frugal attitude.

“At some level, your job as the founder of a company is to not run out of money. There are lots of ways to not run out of money. You can generate tons of revenue. You can raise a whole bunch of money. But one of the best is just not to spend a lot, and to be really frugal with the resources you have,” says Matthew.

Building a company during a time of crisis made Matthew and Michelle incredibly cognizant of every dollar they were spending. It also forced them to focus on pushing forward instead of getting caught up in unnecessary details or wasting time running up and down Sandhill Road.

“We basically pitched one venture capitalist who we thought was the right initial investor. We had a relationship with another VC firm that didn’t typically do early stage deals as well,” said Matthew. “But we didn’t optimize.”

Matthew continues: “We said, ‘Yeah, okay, you’ll give us a couple million bucks,’ which seemed like a huge amount of money at the time. We basically did the deal on handshake. In retrospect, we could own a lot more of the company. The biggest slug of equity we gave up was in that first round, but it just so doesn’t matter if these things are successful.”

Don’t Start A Company With Your Friends

Matthew Prince’s first company was an anti-spam product, and he co-founded the company with his friends from junior high school — they’d all had lockers next to each other.

“That is about the worst possible way you can choose who your co-founders are,” Matthew says emphatically.

While his co-founders were great people that he respected, the big problem was that there was no diversity in their skill sets.

“If there aren’t natural divisions that make it clear whose job is what, then when you get to hard decisions, you end up spending all your time just fighting over what the right answer is and you don’t actually get anything done. If you then resort to hierarchy where I say, “Well, I’m the CEO, therefore this goes, that doesn’t make the other people feel really good, because they could have just drawn different straws and been reordered in different ways. So we fought like dogs,” Matthew recalls.

Though Matthew and one of his co-founders are close friends again nowadays, there was a point where they didn’t speak for several years after the experience.

It is a far better strategy to look for complementary co-founders.

“If you’re starting a company, there’s this huge surface area that you’ve got to build a team to cover. With your founding team, you want it to be like a Venn diagram where there’s just enough overlap that you guys can communicate. But mostly you’re just trying to cover as much surface area as possible.”

In those early days of Cloudflare, Michelle focused on process and operations; Matthew focused on vision, marketing and sales; and Lee focused on tech.

“I remember early on, one of the things that really mattered to Michelle — she was like, ‘I want to be on the board.’ I went to Lee and I was like, ‘Do you want to be on the board?’ He was like, ‘Why on earth would I want to be on the board? I just want to write code.’”

It made for a strong, foundational group, and Matthew believes it’s a crucial set up from the beginning.

“One of the questions that we get all the time is, ‘Gosh, how did you guys split up responsibility?’ I try not to say this when someone asks it, but immediately my thought is, you have the wrong co-founder. Because if it’s not 100% clear from day one, it’s only going to get harder every day that passes.”

Figure Out Your Unfair Advantage In Hiring

Recruiting is always the hardest thing you have to do as an entrepreneur, and it’s likely the biggest challenge you’ll face when starting a company during a recession. Workers are less palatable to taking on risk during hard times.

Still, it’s the one thing you as the CEO cannot “fire yourself” from.

“Companies are just collections of the people who join them, so there’s almost nothing that you can do that’s more important than just making sure you’re getting really, really, really high quality people,” says Matthew.

The two characteristics that Cloudflare tries to hire for are curiosity and empathy. Matthew defines empathy as the ability to be a good listener and the ability to change one’s mind when they hear facts that are different from what they might have assumed.

In the tough early days when nobody’s heard of you, the mindset you need to take when recruiting is to think about what you can do that gives you an unfair advantage.

For one of Cloudflare’s early hires, that meant figuring out visas.

Matthew found one of his first programmers simply scrolling through LinkedIn. They were looking for a candidate who was a low-level C and assembly programmer, and they found a profile of a person who had an incredible resume for exactly that. However, the candidate was currently working as a front-end HTML web designer.

Matthew saw an opportunity. He reached out to the candidate, pointing out that he seemed underemployed. It turned out that the candidate was a French citizen who wanted to be in the United States, and his current firm was the only one that could sponsor his visa.

Matthew offered to transfer the visa to Cloudflare, where the programmer would be able to write C and assembly. The candidate immediately accepted.

After that hire, the team went and found a great immigration attorney, and continued the strategy of looking for people who were underemployed on some kind of visa. They would then transfer those candidates’ visas over.

“You can say ‘We’re going to all make a ton of money,’ but that’s what every startup says. You have to figure out ways to get people to have a span of control of things that they really love to do, or have a mission and a purpose which really resonates,” says Matthew.

“It took us a while to figure out that Cloudflare’s mission was to help build a better Internet, but once we did, people were like ‘Yes! That’s why I work here, I like coming in and solving the hardest problems on Internet-level scale.’”

Matthew and his co-founding team made sure to be relentlessly fair to those first employees. Though half of Cloudflare’s original 8 employees eventually went on mostly to start other companies, they all came to join the team on the floor of the New York Stock Exchange when Cloudflare went public.

“It’s pretty amazing, we wouldn’t have gotten to where we were without them, so it was great to be able to celebrate there with them,” says Matthew.