What Filip Kaliszan learned building Verkada to $3.5B

Executive overview

Most founders over-build before launching. Verkada shipped early because they had no choice — limited runway forced customer contact that reshaped the entire product roadmap.

The company grew from a Raspberry Pi prototype in a living room to a $3.5B security platform by staying close to customers, hiring for culture, and treating each new product line as a self-contained startup team.

Limited runway is a forcing function: ship early, let customers rewrite your roadmap.

From CourseRank to Verkada: founding lessons

• CourseRank reached ~7,000–8,000 Stanford undergrads as a class project before acquisition
• Key early lesson: delegate based on actual strengths, not assumed expertise
• Chegg acquisition taught him M&A diligence and how brutally hard integration is
• Joined Chegg at 80 people; spent years integrating acquired product teams
• Integrating acquisitions fails when team dynamics are ignored — product fit alone is not enough

Choosing the right problem

• Gave themselves 12 months to explore ideas before committing to Verkada
• Criteria: large market, real pain, meaningful spend — video security was $15–20B annually
• School safety infrastructure refresh became a powerful early demand driver
• Shared ideas widely — customers, investors, friends — to test what resonated

Building and shipping the first product

• First prototype: Raspberry Pi cameras assembled in a living room, ~60–70 units
• Distributed to friends to surface real-world problems (bandwidth, multi-camera scaling)
• First manufacturing order: 250-camera minimum; five pallets arrived in Filip's garage
• Limited funding removed the temptation to delay — forced a launch before "ready"
• Customer feedback revealed a significant gap between what the team wanted to build and what customers valued

Scaling new product lines

• Access control had false starts when founding engineers got pulled back to core product
• Solution: isolate the team physically (the basement), give them autonomy, make them ship
• Self-sufficient pods — "startup within a startup" — became the repeatable model
• In-office culture is deliberate: physical products require hands-on testing and daily dog-fooding

Culture and leadership at scale

• Biggest mistake (2019, ~200 people): didn't act decisively on misconduct — caused team confusion about values
• Lesson: when someone doesn't fit the culture, make the change immediately
• Past ~50 people, your team no longer knows who you are — you must actively communicate it
• Tactics: small-group lunches, frequent all-hands, intentional touchpoints across the org
• Deliberate office design (floor-specific snacks) nudges cross-team collisions

Persistence as a founder skill

• The startup journey is cyclical — good periods and bad periods repeat at every stage
• Store energy and positivity during good times; you will need it when things turn
• External shocks (Covid, market shifts) are inevitable — execution with a level head is the differentiator
• Core advice: spend thousands of hours building things; skill compounds like any other craft