Company of One, in Practice

A company of one is a business that questions growth. Not one that can’t grow — one that asks, at every fork, whether growing is actually the right move, and often decides it isn’t. The measure of success isn’t “bigger.” It’s better, more durable, and small enough that one person can own the whole thing.

If the phrase sounds familiar, it’s because of a book. Let’s start there, because the idea deserves its citation — and then let’s talk about the part the book leaves for you to solve.

The Company of One book, briefly

Paul Jarvis’s Company of One made the case that staying small can be a deliberate strategy rather than a stage you’re supposed to outgrow. The short company of one summary: growth is not inherently good; it’s a tool, and like any tool it has costs. More revenue can mean more staff, more overhead, more complexity, and less of the freedom you started a business to get. Company of One (Paul Jarvis) argues you should grow only where growth genuinely serves the outcome you want — and resist it everywhere else.

That reframing did real work. It gave a lot of people permission to stop apologizing for not scaling. If you want the argument in full, read the book — this essay won’t reproduce it, and it certainly won’t link you to a pirated PDF. Buy it; it’s worth it.

The half the idea leaves to you

Here’s what a philosophy of “question growth” can’t do on its own: it can’t finish your work for you.

The book makes the case for staying small. It’s mostly quiet on the daily mechanics of how — and the mechanics are where staying small actually lives or dies. Because the same decision that gives you freedom (no team) also removes your safety net (no team). When you’re the whole company:

• There’s no designer to hand the rough thing to.
• There’s no ops person to maintain the system you set up.
• There’s nobody to own the parts you’d rather not.

That assumption — that there’s a team behind you — is baked into most software, most templates, most tools. And it quietly costs a company of one the one resource it can’t buy back: hours.

The reasons for staying small only hold if the tooling does

This is the practical heart of it. The reasons for staying small — keep the margin, keep the decisions, keep the craft, keep your time — are all real. But every one of them is undone by unfinished tools.

A half-built template that breaks on real copy? That’s an afternoon. A subscription that does a fraction of what you need? That’s a monthly tax and a workaround. A tool abandoned by its maker at version one? That’s a migration you’ll do alone. Staying small doesn’t fail because the strategy is wrong. It fails because the operator drowns in the maintenance of things that were never finished.

So the missing chapter of every company-of-one plan is the same: you need things that are finished when you find them, because there’s nobody to finish them for you. That’s not a mindset. It’s a supply problem. (And it’s why restraint isn’t decoration — it’s the requirement.)

Company of one, solopreneur, lifestyle business

The words overlap. A solopreneur is the person; a lifestyle business is the shape; a company of one is the philosophy — growth questioned, size chosen. Underneath, it’s one decision: stay small on purpose, and take the responsibility that comes with it seriously.

Where Merchant of One comes in

Merchant of One exists because of the book, not in competition with it. If Company of One makes the case for staying small, Merchant of One is trying to supply the missing half: the finished tools that make staying small survivable.

A course on restraint. Template packs used on real client work. A few small tools that remove a chore. Each one built because it was needed, used until it was dull and reliable, and only then sold — buy once, yours forever, revisions free. Not a fake product. Finished work from one person who still does the work.

That’s company of one, in practice. If you’re living the philosophy and tired of unfinished tooling, browse the tools.