bhavin parikh

growth, profit, and consequences: what founders should know about the rise in tech layoffs and what we’re doing to prevent them here

founders have big dreams when they start a company. they dream of changing the world and creating jobs. they dream of building a fast-growing enterprise used by millions or, in some cases, billions. they don’t, however, dream of laying people off. but unfortunately, that happens all too often.

in the past year, a number of companies i admire—including moz, treehouse, and buffer—have had to make layoffs. hoping to shed light on the issue, those companies chose to be open about their cuts and published articles here, here, and here about their struggles. three businesses making layoffs may not seem like a big deal, but they represent only a small portion of the layoffs that happened last year. and with most layoffs going unannounced, the truth is we still have only a small glimpse of how widespread the problem really is.

at magoosh, a startup based in the bay area, we’re vastly aware of the uptick in layoffs happening around us. but rather than shutting our eyes and waiting to see what happens, we’ve made it a priority to understand why cuts happen and actively work to avoid them. taking a cue from moz, treehouse, buffer, and others who have written on the subject, i’d like to share our own thoughts on layoffs: what we’ve learned about why they happen, how we approach risk-taking at magoosh as a result, and how we implemented our own layoff-preventing practices.

by having more open conversations about layoffs, it’s my hope that we can promote more understanding around them and collectively start making better business decisions at the intersection of risk-taking, growth, and hiring.

layoffs can happen for a number of reasons. every company is different, after all. so, let’s focus on one prevalent reason that has widely affected companies in the tech space.

startups, especially silicon valley venture-backed startups, are encouraged to chase growth. growth can take the form of more users, more revenue, or more of something else.  the hope is that high growth (often unprofitable growth) will lead to more funding which will lead to more growth and so on. at some point the company, usually after it has a very large user base, will focus on profit with the thought that high growth at first could lead to more long-term profit. but there’s a natural tension between growth (i.e. market share) and profit, and it’s a tension that has existed long before the dot-com bubble in the early 2000’s. in fact, the harvard business review published an article on the subject as far back as 1975.

vc firms have investors who are expecting a 6x return on their investment over a period of 10 years. in order to achieve that level of success, vcs need some of their companies to achieve massive outcomes (100x or higher), given that most of their portfolio companies will fail or return very little. because of this, vcs are incentivized to invest in startups that aim for big growth—startups that are willing to lose money month-over-month in order to grow the top line faster.  when founders take vc money, they are implicitly promising they will chase growth, not profit.

targeting growth (over profit) can be a smart approach for many companies, especially companies in a winner-take-most market. for example, facebook, twitter, snapchat, and the like would not have reached their levels of success if they focused on profit early on. however, most companies are not facebook, twitter, or snapchat. and most companies don’t realize what they’re getting into with the growth-before-profit approach. too many of these companies—energized by silicon valley’s seemingly free-flowing cash and pervasive “growth at all costs” message—end up chasing growth (to get that next round of funding), when in reality they should be focused on nailing down their value prop and developing a path to profitability.

the growth-focused approach can be painful when it doesn’t work—and for most startups it doesn’t. every founder anticipates some level of failed experimentation (“this product might fail, that’s fine”), but what they don’t usually think through is the people side of the product. in other words, when you raise a lot of money and hire a lot of people to build a product and then it fails, you’re not only faced with dropping a product, you’re faced with laying people off.

example: when failed experiments lead to layoffs

i’ve looked up to moz since the early days of magoosh (2011). i’ve read many blog posts, especially the ones by their founder rand, on how to approach content marketing and how to approach building a company.  moz and rand have played a big part in magoosh’s growth and my own growth.

so, in late 2016, i was sad to learn that moz was announcing layoffs. from their ceo, sarah bird:

this is the gut-wrenchingly painful part. the hardest part of my job is asking people who have put their hearts and souls into moz to part ways. to align the organization with this strategic shift, we will be asking about 28% of mozzers to leave. they are a part of the moz family and it is heartbreaking that they will not be working alongside us in the future.

moz had raised $29m to-date, a small early round, then $18m in 2012 and another $10m in 2016. while i don’t know the specifics, i suspect they raised the $18m round based on the success they had up to that point, and on a big future vision of becoming more than an seo company—eventually becoming the leading provider of tools for all inbound marketing. this was a big experiment and a big risk. and after four years, they realized the risk didn’t work out the way they hoped, which led to laying off 28% of their staff.

running a startup is a constant exercise in risk assessment. sometimes big risks pay off and sometimes, as in moz’s case, they don’t.  and the truth is that those layoffs—while difficult—were likely the right decision for moz in the long-term. moz’s experience is just one example of what many startups go through. it’s why many layoffs happen and will continue to happen. so, what can companies do? are layoffs an inevitable consequence of taking risks?

at magoosh, we approach business and risk-taking differently. we raised a small round of capital to get us off the ground at the beginning, and since then we’ve made it a point to spend only the money that we have, using funds from our most-successful product lines to expand into new product lines and markets. it’s made us a stronger company and it’s insulated us from the rising tide of layoffs throughout the bay area, while allowing us to still take calculated risks.

so, what do our business decisions look like in action? below, i’ve outlined some scenarios that many companies face. then, i explain how a vc-backed growth-focused company would approach each scenario and compare it to how we would approach that same scenario at magoosh.


scenario 1: launching one (or several) new product lines

magoosh is an online test prep company, and we periodically add prep products for new exams. for instance, we recently launched an mcat prep product for aspiring doctors, and we have plans to add more exams in the future. let’s see how the approach to adding exams differs.

vc-backed approach:

  • identify the exams the company wants to pursue and focus on those that have very large market sizes.
  • build a model for the growth trajectory of those exams and determine how much capital is required and do some light validation (e.g. surveys, etc.).
  • launch and build as many exam products as possible, staying within the capital constraint, and hire people to work on those products.

magoosh approach:

  • identify the exams that we want to pursue, focusing not only on those that have a sizeable market, but also those that could quickly be roi+.
  • validate demand for these exams by building an audience first, before potentially building a product. this validation can take 6-9 months.
  • only create products for the exams for which we successfully built an audience.

tradeoffs:
the vc-backed approach can lead to faster growth since the products are created earlier. if there’s a first-mover advantage, then the benefit of faster growth could be significant, and as we discussed before, faster growth can also help the company raise their next round of funding. however, if many of the new products are not successful, the vc-backed approach could lead to significant lost capital and could result in layoffs for the people hired onto some of the new teams.


scenario 2:  developing a new growth channel—outbound sales

at magoosh, we recently decided to experiment with outbound sales. we had seen some indication of market interest based on inbound group purchase requests and believed this channel had more potential. let’s see how the approach to experimenting with outbound sales could differ:

vc-backed approach:

  • determine the potential of outbound sales and then hire an individual or several individuals to grow revenue, depending on capital available.
  • continue pursuing outbound sales for 2-3 years even if it’s losing money, that is as long as there is some positive signal. if it pays off then it could pay off in a big way and grow top-line revenue in the meantime.

magoosh approach:

  • identify outbound sales as an opportunity and potentially hire a contractor or intern to pursue it rather than hiring someone full-time.
  • if we decide to hire someone, explicitly let them know that this is an experiment so there’s more risk in this role than there would be in other roles, and look for a more significant positive signal before hiring others onto that team.

tradeoffs:

if the outbound sales is successful, the vc-backed approach will almost certainly lead to faster growth. and some experiments need time in order to demonstrate a return, so the magoosh approach of hiring a contractor or intern may not provide enough time to assess whether outbound sales was successful. the magoosh approach, however, leads to lower capital expenditure and provides more clarity on the uncertainty of the future of the role. the vc-backed approach could lead to layoffs if the new channel is not successful.


in both of the scenarios above, the vc-backed approach can lead to faster growth, and if successful,  is likely better overall. our company’s approach protects against lost capital and layoffs, meaning it’s better in the failure case (which, in the world of start-up experiments, is the most likely outcome), as it can still lead to profitability. and even though our approach can mean slower growth, we think of it as a long-term approach worth carving out time for.

for what it’s worth, our approach hasn’t kept magoosh from attaining high-growth or profitability. we became cash-flow positive in 2012 and continue to grow quickly year-over-year, even achieving a top 100 place on the inc. 5000 in 2016.

perhaps, some might say, we could have achieved that more rapidly if we had employed a vc-backed approach to growth, but i believe making time to build a risk model to mitigate the chance of layoffs was the right move for us in the long run. and i believe if more vc-backed companies acted as if they were chasing profitability, even if in reality they were chasing growth, they could mitigate their own layoffs because they had at least created some artificial constraints for themselves. constraints are difficult to abide by, though, so at magoosh we’ve developed our own framework to keep us on track.

over the years, we’ve developed a framework for how we approach risks, especially as they relate to people. when a manager wants to hire for a new role, we go through the following questions:

  • what’s the expected benefit of this role?  estimate which metrics will move, by how much, and by when.

  • is the work experimental in nature? if yes, what happens if the experiment doesn’t work out?

  • what is the time-frame for this role? what will this person be doing in 6 months, in 1 year, in 2 years? if the person’s work/project will end or will no longer be a company priority, what will we do? should we hire a contractor instead?

these questions help us understand the expectations and risks associated with each role. we then try to communicate these expectations and risks to each candidate (aligning with our value of communication > efficiency). we realize this approach can make it harder to fill positions. because we’re upfront about the potential risk in our temp and experimental roles—while they may not actually be that risky in reality—people might turn down those roles in favor of full-time positions elsewhere that they perceive as being less risky. we’re comfortable with that trade-off, though. if the experiment doesn’t work out for any reason, we know the person opted into the risk.

our approach has its own issues. while we try to take risks, our risks are generally smaller than those of the companies that have raised a lot of capital. this means we’re less likely to see the massive 100x successes. for now, it’s a tradeoff we’re comfortable with, as we believe it’s an approach that works best for our company and our team.


now that you’ve read all about our approach to risk-taking, layoffs, and hiring, i need to make one thing clear: we’re not so naive to think magoosh is immune from layoffs. we recognize that for any number of reasons—changes in the market, the end of the gre as we know it—could lead us to make our own tough cuts. that will always be the reality. but i believe the existence of layoffs—the fact that they will always happen in business—is not a good enough reason not to take steps to minimize their potential. if we didn’t at least try, we would not be doing right by our employees or our company.

i’ve shared what we’re doing; now i’d love to hear from you as well. if you’re using other tactics at your company, or disagree with any of those we’re using here, please leave a note for me in the comments. let’s continue to make this an open discussion, so that we can all—magoosh included—get better at understanding, preventing, and addressing layoffs.

 


 

thanks to aj shankar (everlaw), joel gascoigne (buffer), tawheed kader (toutapp, now marketo), andrew cronk (re-factor) and greg mcverry (review talent feedback) for reviewing and providing feedback on this article.

 


 

header image designed by mark thomas

author

  • bhavin parikh

    bhavin sets the vision and strategy for magoosh, along with whatever else needs to be done. with a bs/ba in economics and computer science from duke university and an mba from the haas school of business at uc berkeley, he’s on a mission to change the way people learn and how they think about learning. years ago, bhavin played on several nationals-level ultimate frisbee teams. today, he’s our resident gelato connoisseur.