Ali Hussain, co-founder and CEO of Tabs (AI and agents for finance and accounting), shares 10 lessons on scaling drawn from growing Latch to 500+ people (1 in 10 new U.S. apartments used their smart locks) and building Tabs to 150+ people.
Learning to scale at Latch
Scaling was driven by a young, high-slope team operating on belief; the turning point was seeing tens of thousands of locks ready to ship in a new warehouse, realizing the product would reach users nationwide.
The hardest lesson came from a mission-critical failure: locks stopped working at 11 p.m. in a 500-resident building, locking people out — teaching that deployment and operations muscle matters as much as product.
Preparing to scale: go slow to go fast
Before writing code, spent ~6 months talking to hundreds of finance professionals to find the root pain; investors initially called it a “boring problem,” but seeing Zip, Ramp, and Koopa create unicorns in adjacent finance tooling confirmed the opportunity.
Deep ICP work — understanding exactly who buys and why — unlocked faster market entry despite early mistakes.
Savor the early days: the transition from 0 to brand recognition happens faster than expected, and daily work changes fundamentally once the organization functionalizes past ~30–50 people.
Building a founding team that scales
First 8–10 hires must augment the founder’s gaps: technical founders need sales/operations counterparts; diversity of thought and skill set is the litmus test.
Co-locate the first 10 people (e.g., in New York or SF); remote hiring early on weakens the culture and velocity that set the company’s trajectory.
Growing leaders internally
Use “pod leads” as a low-risk trial for management: give ownership of a workstream for 3–6 months, then bet heavily on those who crush it.
Promote from within — insiders know the product, culture, and processes best.
Two traits separate future leaders: (1) belief and optimism in themselves and the company (contagious), and (2) strategic perspective that could change the company’s course — not waiting to be told what success looks like.
How the CEO role evolves
Early stage: do everything (sales, support, ops, marketing).
Middle stage: hire domain specialists; stay deeply involved in some functions.
Late stage: with great hires, the CEO becomes “redundant” in execution — shrinking tactical scope to focus on direction, decisions, and rallying the org.
Scaling founder knowledge
Documentation and perfect onboarding are unrealistic early on; rely on direct mentorship — founders teach early hires, who then cascade knowledge and become the best trainers.
Operate on data: every team has 2–3 must-hit KPIs; quarterly sense-checks ensure time allocation matches highest-impact priorities.
Driving impact as the org grows
Defer the “what” and “how” (tactics, feature choices, spend allocation) to domain experts who are closer to the ground.
Own the “why” and “where” (strategy, direction): be decisive, consistent, and avoid decision fatigue; mandates must be clear and the org rallied behind them.
Resist pressure for 12-month roadmaps in fast-moving markets; roadmaps should reflect highest customer impact, product-market fit signals, and technology shifts.
Most common scaling mistake
Over-investing in long-term planning creates strategic rigidity; embrace uncertainty in the long term while concentrating all calories on short-term customer impact and flexibility.
AI’s role in scaling
AI mandates across every function democratize tooling: post-sales builds on product, marketing and support automate workflows — no longer gated by engineering capacity.
In an AI-abundant world, defensibility comes from touching the metal and building hard, differentiated things; conviction on what makes you inevitable matters more than ever.
