We have seen a marked increase in the number of startups being built outside traditional technology hubs such as Silicon Valley. We’ve also experienced firsthand how startups are building seamless distributed teams spread across many geographies. The conventional wisdom has been that it is a significant inhibitor for a startup to have team members based out of multiple geographies or fully distributed. Many mainstream venture investors have historically been loathe to invest in such companies. And this has been for a good set of reasons.
We posit that it is time to change these beliefs. We’ve reached a tipping point where the advantages of building a distributed team can offset the inherent challenges. Further, the ability to execute rapidly with a distributed or remote team can provide a startup with significant competitive advantages over those limited to one region.
We are beginning to see breakout examples of this trend. InVision has built out a billion-dollar business with 700 employees and zero offices. Popular, high-growth SaaS products such as Automattic, Buffer and Gitlab have been built by engineers spread across many cities. Companies such as Atlassian, Freshworks, and Algolia (originated from Australia, India, and Europe respectively) have leveraged remote offices since their early days and are now prominent in their respective market segments globally. With skyrocketing costs and high employee turnover in the SF Bay Area, we are seeing many startups from here open offices in more stable locations with tech talent availability. At Emergent Ventures, we meet multiple early-stage startups with distributed or remote teams every week and have invested in several of them.
Just as the Cloud had a proverbial 10X multiplier effect on the technology ecosystem by exponentially reducing startup costs, we believe that distributed teams — by removing the location barrier to team growth — are the next game-changer for the startup world. When done right, distributed teams can be faster to set up and scale can cost less to run and can be more resilient and available. Distributed teams are also a great way to overcome regional talent barriers and immigration constraints.
We have seen a marked increase in startups with truly distributed teams in recent years. The snowball is now building up. The advent of the Internet and video conferencing tools provided the necessary backdrop for distributed teams to be successful. Yet, those are not exactly recent developments. Here are reasons we believe startups with distributed teams are taking off now:
- Collaboration Tools tipping point (The Slack effect): Collaboration tools such as web conferencing and cloud-based software development environments have existed for years. However, these are now reaching a level of usage and familiarity, where executing with distributed and remote teams is more seamless. Dev teams now communicate primarily using Slack, and collaborate using tools such as Atlassian, Github, and Trello. Cloud-based Docs and Sheets are staple for product management teams. Online whiteboarding solutions replicate a key element of in-person meetings for creative teams. Increasingly larger B2B sales are being done remotely using tools such as Zoom and Uberconference. And global business deals are being negotiated and sealed over Whatsapp and WeChat!
- Necessity: Tech talent is getting extremely tight and expensive in startup hubs such as Silicon Valley and New York. Public tech companies in these locations can offer potential employees interesting work, high compensation (including liquid RSUs), a globally recognized brand, and sometimes great lifestyles too. Early stage startups can offer few of these, so hiring in these locations is not easy. Further, employee turnover can be high in an environment with numerous high-quality alternatives. Yet, having a presence in places such as San Francisco/Silicon Valley provides significant deal-making advantages across M&A, partnerships, and fundraising, along with global reach and credibility. By having the right presence in a deal-making hub with other employees spread over multiple geographies, startups can potentially have their cake and eat it too.
- Specialization: Software is eating the world. Tech is going deeper into industry segments. Consequently, more startups are building products in places that have talent with domain expertise in vertical or functional areas. Examples include AI startups in Montreal, Robotics companies in Pittsburgh, SMB SaaS companies in India, and industrial IoT startups in Germany and France. These startups often tap tech deal-making hubs such as Silicon Valley or New York as they get to market, and their teams are thus distributed from early on. Similarly, some places have built a talent pool and reputation in a specific functional area. A great example is the Greater Salt Lake City area in Utah (aka Silicon Slopes), which became an effective hub for building remote software sales teams and is now thriving as a home to many successful software startups
- Remote Hiring: With AI-driven recruiting platforms and SaaS HR tools, hiring, onboarding and managing remote talent has become more seamless in recent years. Services such as Terminal are enabling companies to achieve hyper growth by accelerating the build out of distributed teams outside of Silicon Valley while handling everything from recruiting to office management.
Distributed teams are not for every startup — at least not yet. And there are certainly some fundamental challenges that only a few have demonstrated they can master. Shaping the culture of a startup in its early days can be an order of magnitude harder with a distributed team. Team communication can be a challenge in the absence of nonverbal cues. Some have found that distributed teams may not be able to move as fast as a dozen early startup employees cranking away, ‘locked’ for days in the proverbial Silicon Valley garage. Motivation and morale can be hard to sustain in a virtual environment. Training and onboarding acquire a new set of challenges. Some functions can be harder to execute well in a fully distributed structure, e.g. creative pursuits that rely on brainstorming and serendipity. And for teams spread across the globe, conference calls and other synchronous communication may be limited to a few inconvenient hours of the day.
Getting it Right
Over the years, we have observed several practices shared by successful distributed teams that help them overcome the inherent challenges of the model. This can be the topic of an entire book (or at least a blog post of its own), however, here are some of the big ones:
- Successful distributed teams focus on frequent communication. They heavily use messaging apps, written communication and video. Some even have video feeds open between multiple locations all day, by default. Maturation and adoption of technologies such as AR for team collaboration will make this even more frictionless. High achieving distributed teams come together for periodic face-to-face meetings and retreats. For startups that are spread over distant time zones, email and asynchronous communication can often be better than over-reliance on instant messaging
- The role of team and location leaders is critical a distributed team structure. For startups with two or more offices, having experienced leaders that trust each other be in charge of each office often correlates with success
- Leaders at these companies foster practices that help reduce social distance. They often have a low tolerance for organizational politics. They build consistent hiring practices that heavily leverage cloud-based assessment tools. They filter new hires for a disposition of low supervision needs, high organizedness, high communication, and high resilience. They often manage even local teams as if they were remote
- Successful distributed teams also emphasize higher advanced planning and superior project management. Work is organized in small to mid-sized sub-teams
Once a startup has the distributed team engine going, it can optimize the location of each hire for:
(Talent Availability X Employee Retention X Speed to Scale) / Cost
Distributed Team Models
There isn’t a generally accepted definition of a “distributed team”. For instance, if two out of a team of ten people are based in different locations, then it would likely be seen as a core local team with some remote members. When does a team go from being a core+remote to distributed? Our opinion is that if the ratio of remote members to total team size is greater than a third then it begins to have the dynamics of a distributed team. We include teams with two or more offices or locations in our definition of distributed teams.
Based on our observation and study of distributed teams, we classify them into a few different structures and models. We have not come across widely accepted nomenclature describing these models and will take the creative license to suggest names for them as we reflect on the key dynamics for these models. Distributed team setups that we see most frequently include:
Hub and Spoke model: In the Hub and Spoke model, there is a clear core or headquarter location, which often houses some of the leadership. There are one or more “satellite” locations with team members focused on specific functions or needs, e.g. software development, data wrangling or inside sales.
This structure has been used by larger corporations for a long time. It is now increasingly used by early-stage startups to build product away from the noisy and expensive tech hubs. Some startups use this model to tap into specific competency areas, such as Montreal for AI or Pittsburgh for Autonomous Vehicles. This model is also seen where startups with a high-touch field sales model add regional sales offices to be closer to the critical mass of customers. Our own decision of making Xpand a bi-coastal team early on was driven by the decision to be close to our two core customer segments — financial services and technology.
Reverse Offshore model: This is an important variant of the Hub and Spoke model, and has the team focussed around two core geographies. The primary location is often focused on building the product and its delivery/operations, while the other is focused on selling the product.
The genesis of the traditional offshore model was with larger corporations offshoring certain functions, primarily as a cost-saving measure. In that format, the core team is close to the customer base, and parts of product development seen as non-core are often offshored.
Many startups are now reversing the traditional offshore model, where they start in a location suitable for building a high-quality product, but not in close proximity to the target customer base. These startups then establish a go-to-market team in their target market. Israeli enterprise software and security startups pioneered this model over the past couple of decades. We are now seeing high-quality B2B software companies emerge out of India, Europe and elsewhere. Freshdesk and Criteo are examples of this model, where they ‘offshored’ part of their go-to-market teams to the US after building product elsewhere.
Polygon model: In this model, a startup begins with a central seeding location. Over time, it expands to other locations that are equally important, with no clearly defined headquarter. Each of these locations is ‘full-stack’, has a cross-section of important functions, and is relatively self-sufficient.
Amazon’s recently announced move to a three headquarter format (Seattle + New York City + Arlington) aligns with this model. Atlassian is another example where the founding vertex was Sydney, and other equally important vertices were developed in SF and Ireland. This model can work well with a configuration where different businesses or product lines are managed out of different offices. We believe this model is better suited to growth-stage startups and large corporations. Early-stage startups benefit from a clearly identified central node that can drive decisions and agility.
Truly Distributed model (“Beans” model): In this model, team members are spread across cities and countries. Often there is no formal office at all. The number of locations such a startup has members in could approach the number of its team members. The emergence of this model is the culmination of extensive usage of seamless collaboration tools and maturation of remote hiring/management practices.
Buffer is an example of this model, where a team of 79 members is dispersed across 50+ locations. Locations are not organized by strategic competency and team members contribute from wherever they want to work.
In recent years, we’ve been seeing a surge of startups with this model. Many successful fully distributed startups we’ve seen are focused on consumers, developers or SMBs as customers. Those focused on larger Enterprise customers and/or with a complex technology core have so far been underrepresented here. But this may change as the distributed team model becomes more mainstream and remote collaboration tools evolve further.
This model is not easy to pull off. But those who are able to get this right in the early days of a startup have a significant competitive advantage in our opinion. We expect to see many more successful startups emerge with this model, especially in combination with the Hub and Spoke model. One format we are seeing frequently has a small central leadership team based in San Francisco or Silicon Valley, with rest of the team working remotely from anywhere in the world.
As you may have already concluded, each distributed team setup has its own benefits and shortcomings. Different structures lend themselves well to different evolution points in a team/startup’s trajectory. As you think about your team’s structure, evaluate how it aligns with your company’s competitive advantages, focus segment, and customer base. Key factors to consider are around optimizing cost structure, attracting and retaining the right type of talent, taking advantage of certain tax benefits, developing proximity to customers, and access to future financing, strategic partners and potential acquirers. The distributed team model brings its own challenges, but there are known strategies and tactics around team building, conflict resolution, creative co-development, and driving goal alignment for the different types of distributed teams. We hope to cover some of these areas in future posts.
We welcome your feedback and look forward to learning about your experiences of building distributed teams.
Deb Bardhan is an entrepreneur and early stage investor based in Silicon Valley. He is the co-founder and CEO of Xpand, an enterprise SaaS startup, tackling the problem of employee onboarding with customers like Allianz, ING, Tata. He’s also an Entrepreneur-In-Residence at Pre-Hype and co-founder and board member of the Wharton Alumni Angels. He can be reached via LinkedIn.
Anupam Rastogi is a venture capital investor and advisor based in the San Francisco Bay Area. He has been associated over two dozen startups and growth-stage companies from around the globe. Anupam focuses on SaaS, AI and Smart Mobility investments at Emergent Ventures. He can be reached via Linkedin or Twitter
All image rights owned by respective authors and used under Creative Commons