Dec 23, 2021 · 24m · saastr
The Secrets to Scaling Zapier to 500 Employees from Employees Themselves with Zapier CEO Wade Foster
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
Zapier co-founder and CEO Wade Foster shares twenty practical scaling lessons gathered directly from the company's earliest employees, outlining foundational strategies for pragmatic engineering, intentional hiring, adaptive culture, and sustainable startup growth.
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 →
Jason as informed peer 0.0 Guest teaching 0.0 Guest disagreement 0.2 Jason pushing back 0.0
speaking balance: gold is Jason, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 21:56 Rejecting conventional industry playbooks
Wade delivers his most contrarian takeaway, arguing that following established best practices only yields average outcomes and companies must intentionally break rules.
Hardest push from Jason ▶ 19:45 Critiquing premature corporate practicesIn a solo monologue format with zero host pushback, the closest analogue is Wade pushing back against premature corporate reporting and complex tooling in early startups.
Biggest teaching moment ▶ 3:38 Six-month organizational solution shelf lifeWade imparts one of the presentation's most direct counterintuitive frameworks, explaining why high-growth organizational solutions naturally degrade every six months.
Jason holds their own ▶ 14:07 Engineering scalability lessonAs a solo presentation without a host to demonstrate domain mastery against, this moment highlights Wade's technical insight into how shared codebases slow down scaling engineering teams.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Jason as informed peer | Guest teaching | Guest disagreement | Jason pushing back | Why |
|---|---|---|---|---|---|---|
| Zay's Lesson: Building Scrappy and Durable MVPs | 0 | 0 | 0 | 0 | This is a solo keynote presentation by Wade Foster with no host dialogue or interaction. Wade explains how early employee Zay built an MVP for templates that lasted four years. | |
| Vicky's Lesson: Navigating the Six-Month Shelf Life of Startup Solutions | 0 | 0 | 0 | 0 | Wade presents lessons from Jordan and Vicky regarding adapting to rapid organizational growth and building solutions with a six-month shelf life. There is no host involvement. | |
| Paolo's Lesson: Connecting All Employees Directly to Product and Support | 0 | 0 | 0 | 0 | Wade discusses Paolo's insight on all-hands customer support and Stephanie's lesson on being someone others want to work with. No host dialogue occurs in this monologue. | |
| Steve's Lesson: Anchoring Shared Values While Evolving Operational Mechanics | 0 | 0 | 0 | 0 | Wade relays lessons from Ben, Steve, Linz, and Joe on putting people first, keeping values constant while shifting mechanics, and setting explicit six-month plans for hires. | |
| Rob's Lesson: Taking Transparent Ownership of Mistakes and Course-Correcting | 0 | 0 | 0 | 0 | Wade walks through Andrew's focus on hiring for values and Rob's experience navigating a broken profit-sharing program transparently. There is no host participation. | |
| Justin's Lesson: Establishing Clear Code Ownership and Modular Architecture | 0 | 0 | 0 | 0 | Wade discusses Statwonk's outcome-based metrics and Justin's lessons regarding code sharing and clear architectural ownership. The format remains a solo address. | |
| Danny's Lesson: Recognizing the Equal Value of Individual Contributor Paths | 0 | 0 | 0 | 0 | Wade covers Jesse's lesson on avoiding premature complexity, Danny's view on valuing individual contributors, and Cooksey's insight on engineering management churn. | |
| Micah's Lesson: Focusing on Business Fundamentals Over Premature Complexity | 0 | 0 | 1 | 0 | Wade presents Micah's lesson warning early-stage startups not to 'play business' before finding product-market fit, alongside advice from co-founders Mike and Brian. | |
| Wade's Lesson: Breaking Conventional Rules to Become an Outlier | 0 | 0 | 1 | 0 | Wade concludes with his own advice to break standard SaaS rules to become an outlier, followed by a final recap to the SaaStr audience. |
Statements from this episode (18)
Zapier scaled entirely on cash flows following a $1M seed round
“We raised about a million in a seed round, but beyond that, we've scaled the company with cash flows and our balance sheet.”
Zapier grew to 500 employees largely without a sales organization
“Also, we've largely done this without a sales organization, which also makes us somewhat unique.”
A four-year-old CMS MVP still powers 20,000 Zapier templates today
“He built this system over four years ago, and today it, ah, works with 20,000 different Zapp templates. And it's largely that same MVP he built four years ago.”
No-code platforms help founders rapidly build high-quality, durable MVPs
“The great news with a lot of no-code solutions, things like Airtable, Webflow, even Zapier itself, allow you to build things not just quickly, but also with quality. And so it's easier than ever to build these MVPs and actually have them go the distance for yo…”
High-growth startup organizational solutions typically break down after six months
“When you're in the high growth stage, solutions to org problems are gonna have around a six month shelf life. Don't be tempted to overthink that first version, and also don't be tricked into thinking that it's going to be one and done. Instead, build mechanism…”
Over-indexing on future problems often leaves current operational challenges unsolved
“Often if you over-index on a year or two from now, you'll find that the solutions to your problems Don't actually solve the problems you have today, and so by all means, think about what's coming next, but make sure to really understand the problems you're fac…”
Zapier required every employee across all functions to handle customer support
“For a long time, we asked every single one of our employees, no matter what function you worked in, to do some support, and what this meant is that all of our folks really understood the product that we were building and what was special about it, and they als…”
Scaling companies must constantly evolve their operational mechanics while preserving values
“Steve shares, keep the values, but change the mechanics. Companies change constantly, whether it's your code base, your org chart, your systems and processes, your go-to-market motion, all these things are going to change and evolve over time. So your organiza…”
Developing distinct sub-team cultures prevents employee isolation as startups scale
“Now, it's all great to have, ah, you know, shared values, shared purpose, shared mission, but as your org gets bigger and bigger and bigger, it can start to feel a little more lonely, and so one of the things that Linz's team done is they've branded the suppor…”
Adding headcount without clear role definitions slows down startup execution
“It can be tempting to want to throw more bodies at problems and say, ah, if we just had one more person, if we just had 10 more people, we might be able to solve this. But if you don't have a clear perspective of how they're going to help, you're going to end …”
Zapier's core values established at 20 employees successfully scaled to 500
“Some of those things that we thought through at 20 people have scaled with us to 300 to 500 and have ripple effects over where we've gone. Those sets of core values have really helped us be intentional about where we're taking the company. If you contrast the …”
Zapier enforces mandatory code reviews only for the riskiest software changes
“So one of the things we've done over time is said, you know what, we're gonna put in infrastructure to make sure code review's happy against some of the riskiest changes, and then we find another path to production for other types of changes.”
Sharing code without clear ownership slows engineering teams past 64 developers
“And what started as a thing that helped us go fast, quickly as the engineering org grows from eight to 16 to 32 to 64, now becomes the very thing that slows you down over time.”
Rapid organizational scaling frequently outpaces an early employee's management capabilities
“As your organization grows, and if it grows faster and faster, your org growth might outpace an individual's ability to grow. And that's okay. So it's important to make sure each of your early folks really understand that there is a path for them inside your c…”
Multiple Zapier engineers had over four different engineering managers in one year
“There was multiple folks that had over four engineering managers in one given year.”
Startups under 20 employees should focus entirely on product, sales, and support
“Micah shares, don't play business until you have to. Especially when you're quite young, when you're less than 20 people, ah, it's really hard to have, to do everything that bigger organizations can do. You're gonna hear a lot from a lot of great folks today w…”
Scaling startups stagnate unless non-founders are hired to drive product innovation
“If your founding team is the only ones that are thinking about innovation, and they're now focused on scale, what you can find is that innovation starts to stagnate. So it's really important in your organizations to bring in other folks that are thinking about…”