Warning: Standing up too quickly can make you dizzy
summary
Panelists warn that scaling without processes breaks things and give concrete fixes: an Akamai outage example where root access changes deliver the wrong site content, tracking days sales outstanding and collections prevents six‑figure hits, and use Carta for cap table to avoid legal mistakes. Advice: avoid Kickstarter promises that force deliveries, invest in onboarding so sales hit quota in ~90 days, expect leadership turnover and hire HR by ~35–50 employees (or engage a consultant sooner). Focus on unit economics before pouring on growth.
AI-written summary · about
chapters (4)
related talks
29mNavigating the chaos of scaling
01h 00mThings I Wish I'd Known
43mPreparing your software engineering teams for times of financial uncertainty
45mThe Small Fish in a Big Pond: Working with Large Clients
25mScaling Up, Not Out: Managing Enterprise Demands in a Growing SaaS Startup
26mBeat the curve how to stay fast at scale
25mKeeping Your Startup Heart While Scaling Up
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer