Narrow your niche until revenue per employee funds the next hire

Narrow the product before you add people

You are deciding whether to broaden the product or narrow it before adding headcount. The answer is cash: narrow until revenue per employee can fund the next hire. Neural Frames had $5M ARR, a 12-person Berlin team, and was profitable. That worked out to roughly $415K ARR per employee.

Slower growth is a deliberate choice when it keeps the bank balance readable. Profit is an accounting line; cash is what pays payroll, and burn is what empties it. A bootstrapped founder reads that balance daily, so the product decision has to show up in collections, not just in a roadmap.

Pick one use case where the buyer already has a job to do and a budget to pay. Choose the task that appears in your support queue, sales calls, and churn notes. If the buyer has to explain why they need it, the use case is too broad. If the buyer can describe the job in plain language, you have a candidate. A narrow use case should make demos, support, pricing, marketing, and refunds simpler.

Done looks like a product page that names the task, the input, and the output without explaining a platform. Neural Frames initially targeted a wider AI animation market before shifting to musicians. It chose a narrow music-video use case instead of competing as a general-purpose AI video tool. More than 40,000 musicians used the platform, and they made over 2 million videos.

Make the buyer and price do the work

Name one buyer who can say yes without a sales team. The buyer should be a role, not a company size. A role has a recurring job, a budget owner, and a way to say no. A company size is a label that changes the sales motion. The finished state is a support inbox where the same role asks the same question. Adding another buyer before the current buyer has paid spreads support, marketing, and product work across competing jobs, and it hides whether the current job is worth doing.

Submagic launched in early 2023 with a product focused exclusively on subtitles, a single narrow use case. After launch, the team deliberately ignored requests for a mobile app and dozens of features, preserving its narrow product focus. It used a small remote-first organization centered on product, marketing, and support, with no sales team.

Set one price that covers the cash cost of serving the buyer. The price should cover support time, payment processing, hosting, and founder time, not just gross margin. If the price depends on a discount, a trial, or a custom quote, it is not one price. You know it when the checkout page has one plan, not a pricing matrix. Submagic delayed paid ads until eight months after launch, when they became profitable, and the delay reflected bootstrapping discipline. Sleek, a solo-founded AI design tool, hit $10,000 MRR within weeks of launch while spending no money on marketing.

Let the per-employee number decide the next hire

Require a revenue-per-employee target before adding features or people. The target should be a cash number, not a vanity metric. Compare the next hire's fully loaded cost to the cash the current team already produces. If the current team cannot cover the added cost, the product is not narrow enough. The test is a written rule that compares salary, benefits, and tooling against collections. Submagic generated $8M ARR in 36 months while employing 15 people and remaining self-funded, for roughly $615,000 revenue per employee. Neural Frames had never raised outside capital, and it grew 6x year-over-year.

Add the next hire only when the target covers the added cost. The next hire should remove a bottleneck that the current team has already proven is worth paying for. If the bottleneck is unclear, the hire is a guess. The hiring note should say the current team produces enough cash to cover it. If the number is short, narrow the product further before widening the org chart.