The tiny companies doing big numbers have a habit your managers should copy

Stan, a Toronto and Los Angeles company that sells an e-commerce platform to creators, passed US$30 million in annual recurring revenue with fewer than 30 people. It is now at $40 million with 60 people, close to $1 million in revenue per employee, and it has turned down venture money. Its co-founder Vitalii Dodonov told The Logic this month that people wrongly believe that to grow a business, “you need to increase the number of people.”

He isn’t alone. The same piece profiled Halo Eye, a four-person automotive imaging company whose founder estimated the team’s output would have needed about 20 people at his last company. And Stripe reported in May that solo founders started 63% of the C corps formed through Atlas in the second quarter of this year, the highest share it has seen.

Most of my readers don’t run a one-person company and don’t want to. But I think the tiny companies have worked out a habit the rest of us should copy. It has to do with the order in which they ask questions.

By the numbers

63%

of new Stripe Atlas C corps in Q2 2026 had a single founder

They ask a different first question

When a 100-person company gets busier, the first question is usually “who do we need to hire?” A manager sees the queue growing, writes a job description and waits two months for a person who then needs another two months to be useful.

A solo founder can’t ask that question. There’s nobody to hire, or no money to hire with. So the first question becomes “how do I stop doing this by hand?” They write the process down, hand the repetitive part to software or an agent, and keep the judgment for themselves. Only when that runs out do they think about a person.

That order is the habit worth copying. Hiring isn’t bad. Stan went from fewer than 30 people to 60 as it grew, and Stripe’s data shows the best multifounder startups still earned 53% more by month 24 than the best solo founders. Teams matter. The point is that the tiny companies hire after they have squeezed the manual work out of the job, so each new person spends their time on work only a person can do.

Stripe’s numbers point the same way. Its top-decile solo founders were about twice as likely as the median to build AI-native products, and by year two those AI-native startups had roughly twice the revenue of the others. The founders who did best also stayed close to customers. Nearly 30% of top-decile customers came back the next month, against 8% for the middle of the pack. A tiny team doesn’t have the layers that keep a founder away from the people paying the bills, so feedback lands fast and gets acted on the same week.

Before and after

The usual order

• Queue grows
• Post a job
• Wait months for a hire
• New person does the manual work

→

The tiny-team order

• Queue grows
• Write the process down
• Hand repeat work to an agent
• Hire for what's left

I learned this building something by myself

I built Track Raider, a music discovery and set-building web app for DJs, on my own. When you’re the whole company, you notice every task that eats an hour, because there is no one else to hand it to. You get ruthless about which parts of the job need you and which parts just need doing.

That is a very different feeling from running a company with a payroll. In a bigger company, manual work hides. It sits in someone’s afternoon. Nobody writes it down because it has always been done that way, and nobody questions it because the person doing it is busy, and busy looks productive.

The one-person company makes that cost visible. I think every manager should spend a week looking at their team’s work as if they were the only person available to do it.

What a 100-person company can take from this

You don’t need to shrink. You need your managers to think like the founder of a four-person company when they plan.

Make “can an agent do the repetitive part?” the step before every job post. Before a role gets approved, the manager writes down the five tasks that eat most of the week in that role and marks which ones are repetitive enough to hand off. Sometimes the answer is still “hire.” Often the answer changes the job description, because the person you need now is the one who reviews the agent’s output and handles the exceptions.

Give one person a whole workflow. In tiny companies, one person owns a process end to end, so they see the waste. In bigger companies, a quote passes through sales, finance and operations, and no one sees the full path. Pick one workflow and make one person responsible for all of it, with permission to change it.

Write it down before you automate it. A solo founder’s process lives in their head until they hand it to software, and then it has to be on paper. The same is true for your team. If a task can’t be written as steps, an agent can’t do it, and neither can a new hire without months of shadowing.

Measure output per person, not headcount. Halo Eye’s founder put it simply: they plan to get “a whole lot more done with each person.” That is a better goal for a department than “grow the team by four.”

Before you approve the hire, ask what a four-person company would do with that queue.

Where the tiny-team model breaks

There are limits, and pretending otherwise would be dishonest. Small teams carry real risk when one person is out sick or leaves. Customers who pay a lot of money often want a named person they can call. And the tiny companies doing well tend to be selling software, where the product scales without people. A services firm or a manufacturer will never run like Stan. Agents also need someone to watch them. A four-person company with a dozen automations has made a choice to spend part of every week reviewing what those automations did. If nobody at your company has that time set aside, adding agents just moves the mess somewhere harder to see.

That’s fine. What carries over is the order of the questions. A 200-person distribution company that asks “what would a four-person team do here?” before every new hire will end up with people spending their days on judgment calls and customers, and fewer of them spending their days retyping orders.

What to do this week

1. Pull up every open job posting and every role you plan to approve before the end of the year.
2. For each one, ask the hiring manager to list the five tasks that will take most of the new person’s week.
3. Mark which of those tasks are repetitive and rules-based. Those are candidates for an agent with a person reviewing.
4. Rewrite any job description where more than half the tasks are on that list, so it describes the judgment work that remains.
5. Pick one workflow that crosses three departments, name one owner for it, and ask them to write the steps down by next Friday.

Sources

• These AI startups are making millions with tiny teams (The Logic, August 5, 2026)
• Solo founding is at an all-time high: Top performers have these traits in common (Stripe, May 28, 2026)