Hiring without a war chest. Hire a generalist, then let revenue and cash decide the rest.

Your first hire is a generalist, not a specialist

The trigger wasn't ambition or a hiring plan — it was a real customer with real needs and no one to serve them. We'd signed our first large account, the support questions were now coming from actual users, and the two of us couldn't field them and build the product at the same time. So we hired the kind of person almost every early bootstrapped company actually needs and almost no one talks about: a generalist who could wear every hat. Junior did customer care, ran demos (so, some sales), helped me on product management, and QA'd the releases. One person, four jobs, and the flexibility to shift to whichever one the week demanded.

I'd strongly advocate for that as the archetype of a first hire. Not a head of sales, not a senior engineer with a specialty — a capable, hungry person who can absorb whatever the business throws up next. It buys you optionality at the exact moment you have the least of it.

Here's the part that complicates the scary-first-payroll story everybody expects. It didn't feel like a terrifying leap. Honestly, it didn't feel that different from bringing on a 1099 contractor, and I never really looked back after making it. The reason wasn't bravado — it was visibility. We had a few large customers and we could see the revenue. The war chest a bootstrapped founder actually needs to make a first hire isn't venture money sitting in a bank account. It's revenue you can see coming, against a salary that comes out of money you already earned. (More on that money, and the founder pay behind it, in paying yourself.)

Sequence by flexibility, not by the org chart

The order matters, and it's not the order a funded company would use. We built the product itself with 1099 contract engineers — Junior was our first real, full-time hire, the generalist. Only after that did we bring on a second full-time engineer. If I were doing it again from zero, I'd sequence it exactly the same way: contract engineers to build the thing, then a full-time generalist wearing many hats to run the business around it, then specialists once the work has clearly outgrown one person.

The logic is entirely about flexibility and fixed cost. Contractors flex with your cash — you can scale the build up or down without committing a permanent salary you'd have to defend in a bad quarter. The generalist, meanwhile, gives you a full-time anchor who can move to wherever the pressure is. Specialization is a luxury you earn later, once the volume in a single function is real enough to justify dedicating a whole salary to it. Hire the org chart too early and you're paying for seats the business can't yet fill.

Lean and remote isn't a concession — it's an advantage

We hired lean and we hired remote, and not because it was fashionable. We often simply couldn't afford to hire locally. Engineering talent in Seattle was expensive, priced by the corporate DNA all around us — Microsoft, Amazon, Boeing, Starbucks and the rest had set the market, and a bootstrapped CRM company was not going to win a bidding war against them. So we went remote, hired engineers in Poland, and were genuinely successful with the people we found there.

It's worth naming what actually happened, because it gets framed backwards. The constraint didn't force a worse outcome — it pushed us toward a better one. If we'd had a war chest, we might have just thrown money at expensive local hires and never built the distributed, high-quality team we ended up with. The bootstrapped limitation made us look in places funded companies ignored, and that's where we found talent we'd have never reached otherwise. The venture world tends to treat lean-and-remote as the thing you settle for. For us it was an edge.

What you sell when you can't sell a lottery ticket

We weren't equity-free — we had an ESOP, so there was real upside on the table if we ever sold, and it kept us competitive when we needed to be. I won't pretend otherwise. But equity was the backstop, not the everyday pitch. Most of the time, what we were actually offering a candidate wasn't a number — it was an opportunity, a genuine challenge, a fun place to work, and a culture that was the foundation of the company.

That's the recruiting reality for a bootstrapped company: you can't out-cash a funded competitor and you can't dangle a unicorn-shaped lottery ticket, so you have to be honest about what you can offer and make it real. The work has to be interesting, the environment has to be one people want to be in, and the values have to be lived rather than laminated. When that's true, you land people the money story alone would never hold. The culture is the offer — which is exactly why we built it on purpose. (That's its own piece: culture on a budget.)

The mistake everyone makes: the premature senior hire

We got hires wrong like every other company does, and our biggest mistakes clustered around one pattern: bringing in a very senior person too early. Sometimes they weren't a cultural fit. Sometimes they were simply the wrong person at the wrong time. And sometimes we hired them before we'd established the processes a growing team needs to actually support a senior leader. We made all three of those mistakes, more than once.

The lesson is one I'd give any founder before they get seduced by a big title on a résumé. When you hire a senior VP, you are not just hiring a person.

For a bootstrapped company that bet is especially expensive on both ends. The salary is your own cash, so a mis-hire burns money you earned. And the disruption lands on a culture you built deliberately and can't easily repair. A senior hire arrives expecting an org and a set of processes that don't exist yet, expecting to staff up a team you can't yet fund, carrying habits from companies that operated nothing like yours. Sometimes that's exactly the jolt you need. Often it's a transplant your body rejects. The discipline is to make that hire when the company has grown into it — not when you're hoping a senior name will conjure the company you don't have yet.

The only rule that matters: revenue and cash

Strip away everything else and our hiring rule was almost embarrassingly simple. If we were growing and we had cash, we invested. If revenue was weak and cash was getting depleted, we shut the plan down. We adjusted hiring decisions against those two numbers and nothing else — not a fundraising milestone, not a competitor's headcount, not what the market said a company our size was "supposed" to look like. We never got out over our skis.

It's old-fashioned, and it works: don't spend more than you make. That one constraint does more to keep a bootstrapped company alive than any clever org design, because it makes the next hire a question the business answers for you. Revenue and cash say "now," or they say "not yet," and you listen. The freedom in that isn't romantic — it's that the numbers, not the hype cycle, decide your headcount. Reviewing those numbers on a regular rhythm is the whole point of running a tight weekly operating cadence: you always know whether you can afford the next person before you ask the question.

So the bootstrapped hiring playbook, in one breath: hire a generalist first, sequence by flexibility, look where the funded companies won't, sell the opportunity and the culture honestly, be slow and careful with senior hires — and let revenue and cash, the only war chest you actually have, decide the rest.