Mar 6, 2019 · 1h 3m · y-combinator
Mike Knoop on Product and Design Processes for Remote Teams with Kevin Hale · Y Combinator
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this Y Combinator podcast episode, Zapier co-founder Mike Knoop and YC partner Kevin Hale discuss Zapier's journey from a hackathon prototype to a fully remote, venture-scale automation platform. They share insights on open platform strategy, internal communication tools, and the operational practices required to build and scale distributed teams successfully.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
The partners as informed peer 5.3 Guest teaching 4.3 Guest disagreement 1.2 The partners pushing back 2.1
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 51:45 Knoop flips the question on remote design constraints
Knoop directly challenges Hale's premise by asking what prior belief makes him think designers must sit next to each other to solve problems.
Hardest push from the partners ▶ 51:15 Hale challenges remote design critique effectivenessHale expresses skepticism about remote design critiques, arguing that pointing, sketching, and circulating feedback in person is fundamentally faster and more nuanced.
Biggest teaching moment ▶ 6:18 Knoop explains partnering for retention rather than distributionKnoop reframes how early SaaS platforms scale without distribution power, explaining that partners built integrations because it solved customer churn and reduced their feature backlog.
The partners hold their own ▶ 27:49 Hale shares Wufoo's 15-minute debate ruleHale demonstrates operational expertise by describing Wufoo's rule to pause prolonged discussions after 15 minutes and push them to Friday, resolving 90% of debates automatically.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| Guest Introductions and Backgrounds | 6 | 3 | 1 | 2 | Kevin Hale shares his background founding Wufoo and draws parallels between early form integrations and Zapier's business model. Mike Knoop agrees and elaborates on consumer-scale software trends. | |
| Open Platform Strategy and Early Traction | 5 | 4 | 1 | 2 | Hale asks targeted questions about jumpstarting an open platform and API adoption without initial scale. Knoop explains how offering integration retention value to SaaS partners bypassed the need for an existing massive audience. | |
| Origins at Startup Weekend and Applying to YC | 4 | 3 | 1 | 2 | Craig Cannon and Hale ask about the Startup Weekend demo and handling an initial YC rejection. Knoop details their prototype demo use case and how early paid traction proved the concept. | |
| Transitioning to Full-Time Remote Work | 4 | 4 | 1 | 1 | Knoop explains why Zapier defaulted to remote work after YC due to customer support overload and geographically dispersed early hires. Hale relates with the logistical hurdles founders face. | |
| Resisting Office Norms and Prioritizing Autonomy | 7 | 4 | 2 | 3 | Hale and Knoop compare notes on resisting startup peer pressure to get an expensive office. Both discuss investor skepticism and their shared focus on profitability and personal autonomy over vanity metrics. | |
| Hiring for Remote Work and Organizational Values | 5 | 5 | 1 | 2 | Knoop outlines key candidate traits for distributed teams, such as strong external social networks and defaulting to action. Hale prompts him to clarify why these traits also apply to co-located companies. | |
| Asynchronous Communication and Deep Work Blocks | 6 | 5 | 1 | 2 | Knoop discusses the discipline required to preserve deep work and know when to escalate communication bandwidth from text to video. Hale shares Wufoo's 15-minute debate timeout rule. | |
| Protecting Focus, Team Alignment, and OKRs | 5 | 5 | 1 | 2 | Knoop explains Zapier's 24-hour response expectation on Slack and the use of team-level OKRs to bridge PM, design, and engineering silos. Hale probes into the specific definition and assignment of OKRs. | |
| Team Structure, Autonomy, and Governance | 5 | 4 | 1 | 2 | Knoop details how team autonomy is balanced with standardized interfaces in Jira and cross-team dependencies. Hale questions how teams are formed and staffed over time. | |
| Internal Tools, Slack Etiquette, and Async | 5 | 5 | 1 | 2 | Knoop describes building Async as an internal slow-thinking blog to prevent Slack fatigue and explains their total elimination of internal email. Hale praises the zero-internal-email standard. | |
| Internal Tooling, Hackathons, and Company Retreats | 6 | 4 | 1 | 2 | The conversation covers hackathons, internal tooling, and biannual retreats. Knoop reflects on learning to introduce unstructured time at retreats after previously over-planning every hour. | |
| Remote Design Critiques and Team Interactions | 6 | 5 | 3 | 4 | Hale challenges whether complex visual design critiques can be conducted effectively remotely without in-person sketching. Knoop pushes back with Zapier's 9-box exercise over Zoom and counters Hale's skepticism. | |
| Culture First: Advice for Building Remote Companies | 5 | 5 | 1 | 1 | Knoop summarizes that adopting remote work is primarily a cultural shift toward written communication and autonomy rather than just a tooling change, pointing to large-scale proof points like GitLab. |
Statements from this episode (28)
Hale: Wufoo operated as a fully remote company from its 2006 inception
“And that company appropriately was a no office company. We were all remote all the way back then.”
Hale: Online businesses evolve from web presence to forms to data automation
“It's actually interesting that like, I think the life cycle of people like getting their business online, it's like you start off with like, I need like a presence. It's like, how do I get my stuff out there? And so use like website builders, like by default b…”
Knoop: No single SaaS company is incentivized to build thousands of integrations
“Just because of the dynamics of the explosion and how many tools there are, there's no one player in that marketplace that's going to be incentivized to go build thousands of integrations with everyone else.”
Knoop: Platforms are viable when 1% of revenue could be a business
“I think I'd always, I'd heard the heuristic of like once you get big enough where you could carve off one percent of your revenue and that could be its own standalone business, like you've kind of reached a critical mass that you could actually build a platfor…”
Knoop: Zapier bootstrapped early integrations by offering partners retention, not distribution
“The value we gave to partners was around retention. If they built, they integrated with Zapier, they got access to 50, 60 at the time integrations that were maintained and scaled and were adding more to it, and they got it left for free. So it allows them to g…”
Knoop: Zapier built an app directory and landing pages before the product
“We, so we built our app directory before we built the product. Before we launched in TechCrunch, that whole story was, ah, pre, that, we had been working on Zapier for about five months, I think, at that point. The very first thing we did when we sat down was …”
Knoop: Zapier was rejected by Y Combinator on its first application
“We applied actually twice to YC. We got the email rejection the first time. We applied basically with the prototype from Startup Weekend. So we had no customers, no traction, basically just three dudes from Missouri.”
Knoop: Zapier charged 10 users $100 and 100 users $5 pre-YC
“And then the second time we applied, you know, by that point we had had hundreds of conversations and chat logs and messages from actually a lot of folks in, like, the YC network were even using the product. It was invite only at that point, and we were having…”
Knoop: Zapier had reached $50M in annual recurring revenue by 2019
“And it's like, well, yeah, we have, you know, a hundred, we have like fifty million in ARR, like, yeah, we're a real company.”
Hale: Wufoo remains a top 10 YC exit by equity return
“And I think we're still in, like, top 10 biggest exits for YC still.”
Hale: Wufoo raised only $118,000 total from YC and two angels
“18,000 dollars. YC was 18,000 dollars then, and we raised money from two angels, PB and PG, and it was 50,000 dollars each. And that was it.”
Knoop: Remote employees cannot rely on their workplace for primary social connection
“Your work can't be your family at Zapier or any distributed remote company. Like you, in the past, it's very easy to lean on your work as that, like, social connection.”
Knoop: Remote companies are forced to adopt better management practices much earlier
“The types of things you have to do in order to be a successful remote company make you just a generally better company. They are not unique to remote. However, they, you do have to figure them out earlier.”
Knoop: High quality work requires four-hour deep work blocks, not constant collaboration
“A secondary benefit that I think isn't as obvious is that when you're actually doing your job, like, the best work gets done not when you're, like, sitting next to someone and, like, collaborating all day. There's Like, you have to get into deep work. Even for…”
Knoop: Switch to video when Slack says 'several people are typing'
“If you, like, one of the things I tell a lot of our teammates, if you see that, that's probably a really good signal that you should be, like, jumping on a video call at that point. Instead of wasting, or not wasting, but instead of spending, you know, 10 man …”
Hale: Pausing Wufoo discussions after 15 minutes resolved 90% of issues naturally
“And so for us, we changed the rule to be, like, if you're discussing something for, like, 15 minutes, at that 15 minute mark, just, you gotta stop and go on to whatever the next thing you have to do, like, to get to, like, what you say is default action. And w…”
Knoop: Zapier requires employees to acknowledge direct Slack tags within 24 hours
“In Slack, if you tag somebody in a message, like, at tag them specifically, it's kind of the social norm to be, to acknowledge that within 24 hours. So we have some expectations like that, and the reason we have said 24 hours is because we have folks all acros…”
Knoop: Workers who wait for direction when blocked fail in remote environments
“If you're the type of person who like, as soon as I get blocked, I'm just going to sit here until I'm told what to do next. You're not going to be successful at Zapier or I argue most remote companies.”
Knoop: Zapier's product org has 8 PMs, 8 designers, and 50 engineers
“We've got about seven or eight product managers, a similar number of product designers, and then an engineering org that's about 50 folks attached to that.”
Knoop: Standardize boundaries and interfaces between autonomous teams, not internal processes
“I like to think about there's like the things that are important to be consistent across teams are the interfaces. Like, you need to make sure that the interface between teams is consistent so that both teams know how are you.”
Knoop: Goal setting should be split 50/50 between top-down and bottom-up
“And there's kind of a meet in the middle approach where you kind of want the work that's happening, 50% of it to be kind of top down driven, and I think 50% of it being bottom up. Because in reality, the exec team leadership is never going to have perfect insi…”
Knoop: Written decision artifacts significantly reduce organizational conflict during internal debates
“Like, this is one of the things that's great about writing down our process documentation in Zappi, writing down our decision-making processes, is when it's written down, you have something to debate about. I can go to you and say, hey, can we debate whether t…”
Knoop: Zapier disables Slack notices and actively encourages employees to leave channels
“And very early on, we set the expectation that Slack is not a tool you're expected to keep up with in Zapier. You are free to leave channels. In fact, we encourage it. Kevin Hale: That is fascinating. Mike Knoop: There's a feature in Slack where you can turn o…”
Knoop: Zapier operates with zero internal email across the entire company
“We don't send any internal email.”
Hale: Wufoo spent up to 40% of development time on internal tools
“One thing people were surprised about with us at WooFoo was like, how much time we spent development wise,
On internal tools, actually.
It was, like, almost, like, 30 to 40% of, like, development time was, like, us building stuff for ourselves.
It's why we wer…”
Knoop: In-person retreats build interpersonal empathy necessary for text-heavy remote teams
“Even though we're a hundred percent remote, there is still a lot of value for getting in person.
and we don't like discount that.
you get to build a lot of empathy.
You get to build relationship with folks and it allows you to kind of be, assume best intent …”
Hale: Companies over-optimize for serendipitous chance encounters instead of focused execution
“I actually think a lot of companies or organizations, the group over optimize for serendipity. Like they're like, what about that chance moment? But to me, like serendipity, like we were like some random thing happened, all of a sudden we have a great idea. Li…”
Knoop: Transitioning to remote work requires a cultural transformation, not just tools
“I think it is one of the reasons why it is so hard to add remote onto an existing company is because remote while When you see folks talk about it and ask questions about, it's always very process and tools based. I think the honest answer is that it's more of…”