How Adam Young went from 5 employees to 100+

Simple. Not easy.

That's the honest summary of scaling a company from a handful of people to more than a hundred. I've done it and I've watched plenty of other founders do it, and the pattern is remarkably consistent: the growth itself isn't the hard part, because the hard part is that the company you built stops working three separate times along the way, and each time you have to rebuild it while it's still running.

I'll walk through how that played out for me, with real numbers where I have them and honest ranges where I don't.

Where it started

I founded Event Tickets Center in 2006 as a college side project. No venture money. No board telling me what to do. Just a small team and a market growing underneath us. The secondary ticketing market is a real industry, one analysts generally size somewhere in the $15-30 billion range globally, and we were up against StubHub, Vivid Seats, and SeatGeek with a fraction of their resources.

Bootstrapping shaped everything about how we grew, because when you can't hire your way out of a problem with someone else's money, you get very careful about who you hire and when, and every headcount decision has to come out of actual revenue. That constraint hurt at the time. Looking back, it was the best discipline I never asked for.

Later, building Ringba, I ran the same playbook, and I wrote about the marketing side of that journey in The Pay Per Call Revolution. But the people side, the part nobody writes books about, is what this article is really for.

It's not one scaling problem. It's three.

Here's what most founders get wrong about growing from 5 to 100 employees. They treat it as one long climb. In practice it's three separate rebuilds, and the systems, org chart, and communication norms that work at each stage actively break the next one.

At 5 people, the company runs on osmosis. Everyone hears everything. There's no org chart because there's no org, decisions happen in one conversation, usually the same day, and the whole thing is fast and fun and completely unscalable, though you don't know that yet because you've never needed it to scale.

Somewhere between 10 and 20 people, osmosis dies. Not gradually. It just stops working one week, and suddenly two people are solving the same problem without knowing it, or a customer issue sits untouched because everyone assumed someone else had it. You're forced to build your first management layer, wanted or not. Leadership research puts the practical span of control at 5-9 direct reports before communication breaks down, and in my experience the lower end is closer to the truth once your people are doing complex work.

The second rebuild hits between 20 and 50. Now your managers need managers, or at least real written processes, because "ask Adam" no longer scales. Founders either learn to delegate outcomes instead of tasks here, or they become the bottleneck that caps the company.

The third rebuild is 50 to 100+, and it's less about people than infrastructure: HR systems, compensation bands, actual onboarding, legal review. The company becomes an institution whether you like it or not.

Each rebuild felt like starting over. Because it was.

Why does 5 to 20 hurt the most?

Because it's the stage where you lose the version of the company you fell in love with. You go from doing the work to managing the people who do the work, and nothing in your founder experience prepares you for that. Most founders resist it six to twelve months longer than they should.

I certainly did. I liked being in the details, knowing every customer issue and every line of the product, and promoting your first managers means accepting that things will be done differently than you'd do them, and sometimes worse, at least at first. The alternative is trying to personally supervise 15 people. That fails for everyone, every time.

What got me through it wasn't complicated. Promote from within first, because your early employees already carry the culture and culture is the one thing you can't hire. Write down how decisions get made before you need it; a one-page document beats a hundred Slack arguments. Set a weekly rhythm of short, structured check-ins and keep them boring on purpose, since boring is what consistency looks like. And accept that your own job description changes completely, because fighting that is the most expensive mistake at this stage.

None of this is glamorous. It's mostly just showing up and doing the unglamorous thing again next week.

The costs nobody budgets for

Recruiting is the first surprise. Replacing or hiring a mid-level employee commonly runs 50-100% of that role's annual salary once you count sourcing, onboarding, and ramp-up time, and those SHRM-cited figures match what I've seen. Hire a $90,000 employee badly, part ways after eight months, and you've quietly burned $50,000 to $90,000 with nothing to show for it. Do that three times in a year and you've lost a senior salary to bad hiring alone. Ouch.

Compliance is the second. Crossing 50 employees in the US triggers a new tier of obligations, since FMLA coverage kicks in and historically the ACA employer mandate did too, which means real HR expertise, legal review of your policies, and administrative overhead that simply didn't exist at 40 people. Founders consistently underestimate this. I budgeted for the salaries. I didn't budget for the infrastructure around them.

The quiet lesson: headcount is never the whole cost of headcount.

What revenue do you need to support 100 employees?

If you're bootstrapped, you realistically need annual revenue somewhere in the $10-50 million range depending on your margins, because payroll alone for 100+ people often runs $6-12 million per year, and unlike venture-backed companies you can't run that headcount at a loss. So revenue per employee becomes your governing metric. No way around it.

This is why bootstrapped scaling is slower but sturdier. Every one of our hires had to be justified by the business, not a pitch deck. When the market tightened, we never had to do the panicked layoffs our funded competitors did, because we'd never hired ahead of reality in the first place.

Track revenue per employee quarterly. If it's falling while headcount rises, you're hiring on hope. Hope is not a funding source.

Where to start if you're at 5 right now

Don't plan for 100. Plan for 20. Figure out who your first two managers will be, write down your decision-making process on a single page, and open a spreadsheet that tracks revenue per employee starting this month, because the third rebuild will take care of itself if you survive the first one. If you want more of the specifics behind how I think about this, I write regularly at adamyoung.com.

FAQ

Did Adam Young raise venture capital to scale Event Tickets Center? No. The company was founded in 2006 as a college side project and bootstrapped past 100 employees without outside venture funding, competing in a secondary ticketing market generally sized at $15-30 billion globally.

At what headcount should a founder hire their first manager? Usually somewhere between 8 and 15 employees. Span-of-control research suggests 5-9 direct reports is the practical ceiling, and founders who wait past that point almost always become the bottleneck.

How much does a bad hire actually cost? Commonly 50-100% of the role's annual salary once you include sourcing, onboarding, and ramp-up time. For a $90,000 role, budget $50,000 or more in real losses if it doesn't work out.

What changes legally at 50 US employees? FMLA coverage applies, and historically the ACA employer mandate did as well. Plan for meaningful HR and legal overhead starting around employee 40, not employee 50.