Some of the best things founders build are projects, not businesses. The trouble starts when they can't tell which one they've got, and pour three years of business effort into something that was only ever going to be a project.
A project is something worth doing. A business is something other people will keep paying for. They overlap, but they're not the same, and an idea can be a genuinely good project and a hopeless business at the same time. I've watched founders defend the quality of the thing they made as if that settled the question. It doesn't. The work can be excellent and the business can still not exist.
Here are the three signs I'd look for. None of them is fatal on its own. All three together, and you're probably building a project and calling it a company.
Sign one: you're the only one who has to want it
In a project, your wanting it is the whole point. You build it because you want it to exist, and if no one else ever uses it, you've still succeeded on your own terms. That's fine. That's what a project is for.
In a business, your wanting it is close to irrelevant. What matters is whether someone with no connection to you wants it badly enough to pay, and then to pay again. The question isn't "is this good?" It's "who, specifically, reaches for their wallet, and why."
The tell: when you describe the idea, you talk about how much you'd use it, how it solves your problem, how you couldn't believe nothing like it existed. Listen to how much of your case rests on you. If the idea collapses the moment you remove yourself from the customer list, it's a project.
Sign two: the money is a someday, not a mechanism
A business has a mechanism — a specific answer to "how does money come in", concrete enough that you could draw it. This person, in this situation, hands over this much, for this reason, on this rhythm. You can name them.
A project has a someday. Revenue is a thing that will happen later, after it's built, after it's good enough, after people see it. "I'll figure out monetisation once I have users" is the sound of a project. It's not that the answer is wrong. It's that there's no answer yet, and the absence is being treated as a detail rather than the central question it is.
The tell: ask yourself to describe the first ten dollars. Not the millionth — the first ten. Who pays it, for what, and what made them. If you can describe the product in detail but the first ten dollars goes blurry, the money is a someday.
Sign three: it gets better by you adding, not by the market pulling
Watch where the energy comes from. In a project, every improvement comes from you — your taste, your next idea, your sense of what it should become. The roadmap is a list of things you find interesting. It grows because you keep feeding it.
In a business, the market pulls. People ask for things. They use it in ways you didn't intend. They complain about the right things, which is its own kind of gift, and the roadmap starts writing itself out of what real users need. The thing develops a gravity that isn't yours.
The tell: if you stopped adding to it tomorrow, would anyone notice? Would anyone be annoyed it wasn't getting better? In a project, the only person who'd miss the next feature is you. In a business, someone else is already pulling.
Why this distinction is worth the discomfort
Calling your idea a project feels like a demotion. It isn't. It's information — and it's the cheap kind, available before you've spent the year.
"The danger isn't building a project. The danger is building a project with a business's expectations bolted on."
The runway, the cofounder, the round you mean to raise, the identity you've staked on it being a company — when the project doesn't behave like a business, you don't conclude it was a project. You conclude you've failed, and you double down, because admitting it was a project all along feels worse than burning another six months.
A project that knows it's a project can be wonderful. A portfolio piece, a tool you love, a thing you're proud of, the seed of something that becomes a business later when the market shows up. What it can't be is the thing you quit your job for on the assumption it was already a company. The whole bet depends on knowing which one you're holding — and the signs are visible long before the bank balance makes it obvious.
If you read the three signs and felt a flicker of recognition, that flicker is the cheapest market research you'll ever get. It's also the same thing as confusing enthusiasm with validation — the project is what enthusiasm builds when no one checked whether the market was there.
Want more like this? Rick writes about the go/no-go decision, founder counterintuitions, and the business of building ventures worth building.
All writing