How Zapier built a 200-person fully remote company from day one

Executive overview

Most companies treat remote work as a perk bolted onto an office culture. Zapier built the opposite: a fully distributed team from the first hire, out of necessity, and discovered that the disciplines remote forces on you make any company better.

The core insight is that remote doesn't fail because of tools — it fails because of culture. Defaulting to async written communication, empowering autonomous decision-making, and being explicit about process are habits that must be set from day one, not retrofitted.

Remote work succeeds or fails on culture and written communication, not on tools.

From hackathon to platform

• Zapier prototyped at Startup Weekend 2012, with PayPal, Twitter, and Highrise as the first three integrations.
• Applied to YC twice; first rejection motivated the team to get traction before reapplying.
• Launched on TechCrunch with three engineers fielding three days of live chat — all requests for unsupported apps.
• Built an open platform out of necessity: couldn't hire enough people to build integrations internally.
• Early partner value proposition was retention, not distribution — partners could say "yes" to customer integration requests by pointing to Zapier.
• Partners promoted Zapier in help docs and sales calls, which seeded strong SEO and word-of-mouth early.

Why remote became permanent

• First remote hire was a college friend in Chicago they couldn't convince to relocate.
• One co-founder was already flying back and forth to Missouri — remote was a natural experiment.
• Around eight or nine people in, after the first company retreat, the team concluded remote was not an experiment but a better way to run the company.
• Investors pushed back; some turned Zapier away purely because of the remote model.
• Profitability made it easy to resist that pressure: hard to argue with the results.
• Remote attracts people who value autonomy — Zapier screens for this, but also screens out people who rely on work as their primary social network.

Hiring and culture for remote

• Hire for defaulting to action: past examples of taking initiative without consensus are a strong signal.
• Past remote experience is a useful proxy but not required; there is a learning curve.
• Tell candidates their work can't be their family — they need a social network outside the company.
• Over-communication must be explicitly taught: sharing status updates to an empty Slack channel feels awkward but is critical.
• Written communication and autonomy are the two most important cultural values to set early.
• Starting remote from day one is an advantage: everyone is in the same boat, so norms are easier to establish.

Communication architecture

• Default in co-located teams: interrupt someone and get full-bandwidth conversation.
• Default in remote teams: silence. The gap must be managed deliberately.
• Bandwidth escalation ladder: deep work → Slack/text → video call → synchronous conversation.
• Signal to escalate: "many people are typing" in Slack means get on a Zoom call instead.
• Rule: if a Slack thread runs more than 15 minutes, pause it and revisit at the weekly Friday sync.
• Friday syncs resolve ~90% of tabled discussions before they're even raised — most issues dissolve overnight.
• Slack tag etiquette: @-mentioning someone carries a social expectation of acknowledgment within 24 hours.

Async and internal tooling

• Async: internal blog built in-house after outgrowing P2 (a WordPress plugin). The heartbeat of the organisation.
• Every employee writes a Friday update — what they worked on that week — posted to Async.
• Async has a curated default feed so employees see posts from direct reports and key colleagues, not everything.
• No internal email. Slack for real-time work talk; Async for final work, decisions, and documentation; Quip for long-form wikis.
• Slack channels: employees are encouraged to leave channels freely; leave/join notifications are turned off to remove social pressure.
• Zapier builds many internal tools as Zapier apps — a direct feedback loop that surfaces product gaps.
• OKR tracking is built into Async, with annotations linking OKR updates to related posts.

Product and design process

• Product teams are long-running, staffed with a PM, designer, and engineers sharing a single OKR.
• Shared OKRs prevent us-vs-them friction between engineering, design, and product.
• Leadership sets annual direction; teams break it into monthly check-ins and own execution.
• Teams have autonomy over their own processes; consistency is only required at the interfaces between teams (handoffs, JIRA conventions, shared observability).
• Design critique runs Tuesday/Thursday cadence on Zoom: show work Tuesday, iterate 48 hours, show again Thursday — forcing fast feedback loops without sacrificing deep work.
• Nine-box sketching exercise: fold paper into nine boxes, sketch nine ideas in two minutes each, then remix. Run over Zoom with participants holding sketches up to camera and posting photos to Slack.
• On design Zoom calls: ask participants not to mute, to encourage spontaneous feedback.

Serendipity and cross-team connection

• Pair (now trio) buddies: a Slack bot randomly pairs or triples employees for a 30-minute no-agenda call.
• Company retreats twice a year — the primary mechanism for building in-person empathy and relationships.
• Retreat formats have included hackathons and team breakouts; most recently added unstructured afternoon sessions after employee feedback.
• Unstructured time let cross-team groups self-organise around shared interests — worked better than expected.
• Hackathon projects are curated to have a credible path to customer value, avoiding the "built and abandoned" trap.
• Serendipity is overrated as a strategy; structured async visibility into what colleagues are working on solves most of the same problems.

Advice for starting a remote company

• Remote is a cultural shift first, a process and tools choice second.
• Founders starting remote have an advantage: no existing culture to fight.
• Set values around autonomy and written communication from day one.
• Write everything down — decisions, status updates, rationale. Ephemeral Zoom conversations don't scale.
• Hire people who can get unblocked independently and find productive work when waiting on others.
• Large fully remote companies exist (GitLab, Invsion, Automattic) — proof it's possible at scale.