What is a zero-employee company, and what does it take to run one?

The term describes a structure, not a size or an industry. It says nothing about revenue and nothing about ambition. It says only that nobody is employed.

Is a zero-employee company the same as a solo business?

Not quite. Every zero-employee company has at least one person — the owner — so it is solo by definition. The difference is that a solo business is usually limited by one person’s hours, and a zero-employee company is limited by one person’s attention instead, which is a much higher ceiling.

A solo consultant who does everything themselves is limited to what they can do in a week. A zero-employee company can process a thousand leads overnight and present its owner with the three worth calling. The owner’s week is spent on decisions rather than throughput.

It is also worth saying what it is not: it is not a company that used to have staff. This is a greenfield structure, describing businesses that start this way. The two situations have almost nothing in common operationally.

What do you need before you can run one?

Three things. Software that holds the business — customers, orders, workflows. Agents covering the functions that repeat. And a set of thresholds that decide what stops for you. Without the third, you have automation running unsupervised, which is how a small business creates a large problem.

The software matters more than people expect. Agents with nowhere to put their work produce activity rather than a business: emails sent, no record of who was contacted or what was promised. The application is what turns agent output into a company that has state.

The thresholds are the part most founders under-specify. A useful starting set: any discount over a fixed percentage, any refund, any spend above a number you would notice, anything published in the company’s name, and anything a customer could hold you to.

Can a zero-employee company grow?

Up to a point, and then it usually hires. Volume scales well because software does not run out of hours. Complexity does not: the more distinct judgments a business requires per week, the more the owner becomes the bottleneck. That ceiling is a good reason to hire, not a failure.

The signal to watch is the morning queue. If it takes fifteen minutes, the structure is working. If it is taking two hours and growing, the business has outgrown one person’s attention and the honest answer is to hire someone, narrow the business, or raise the thresholds and accept more risk.

Most zero-employee companies never hit that ceiling because most small businesses are mostly repetition. But the ones that do should treat it as information rather than defeat.

What does it cost to run one?

Software subscriptions, model usage, whatever tools the business needs, and any percentage a platform takes from your revenue. The absent line is payroll, which is usually the largest cost a small company has. What replaces it is your own attention, which is limited and worth accounting for.

The percentage line is the one to examine before committing to any platform, because it is the only cost that grows as the business succeeds. A subscription becomes proportionally cheaper as revenue rises. A share of customer payments does the opposite, and the crossover arrives sooner than most founders expect.

The cost nobody budgets is the morning queue. Fifteen minutes a day is around sixty hours a year of founder attention spent on approvals. That is cheap compared to managing people, and it is not zero, and a plan that assumes zero is a plan that breaks in the first busy month.

Where newc0 fits

newc0 builds this structure on purpose: an application the founder owns, an agent workforce covering sales and outbound, customer support, marketing and content, and back-office operations, and an approval gate holding everything binding or irreversible. The canonical definition is in the glossary.