Why Your First Idea Is Probably a Feature, Not a Company

2 days ago
5 min read

A pattern that shows up in almost every student pitch competition is the founder who has thought carefully about a single moment in a user day, has designed a clever solution for that moment, and is now pitching the solution as the company itself.

The solution is often genuinely good, the team has clearly done real work, and the audience nods along because the problem is recognizable. The trouble is that the thing being pitched is almost always a feature inside a larger company rather than a company on its own, and the founders cannot see this from where they stand because the work has felt like building a startup the whole time.

This piece is about why first ideas tend to be features rather than companies, how to tell the difference before you have spent a year on the wrong scale, and what to do when you find that your idea needs to widen into something bigger.

What makes something a company rather than a feature

A company is a self sustaining organization that can address a meaningful customer need across multiple dimensions of that need, while a feature is a single capability that addresses one dimension. The difference matters because a feature can be built into many companies, and the value of building it alone is bounded by the size of the moment it serves, while a company can grow into adjacent moments over time and compound its value in ways that a feature cannot.

The clearest test is to ask whether the thing you are building solves enough of the customer problem that the customer would willingly pay for it without also paying for something else that does the rest of the work. If the answer is no, you are looking at a feature, since features depend on being attached to something larger in order to feel complete, and a customer who would only pay for your product as part of a bundle is telling you that the standalone version is not yet a business.
The other test is to ask whether the thing you are building has a natural path to expansion within the same customer life, since a company has room to grow with the customer while a feature reaches its ceiling quickly.

If you cannot imagine the next three products the company would build for the same customer once the first product is working, the original product is probably a feature, and the absence of a natural expansion path is a quiet signal that the scope was too narrow at the start.

Why founders pick features without realizing

The reason founders pick features without realizing is that features are easier to imagine than companies, since features are concrete, demonstrable, and easy to describe in a sentence, while companies require holding a larger and more abstract idea in your head for a long time.

Magnific.com

The first idea a founder has tends to be the one that fits inside a slide deck cleanly, and slide deck friendly ideas are disproportionately features rather than companies.
A second reason is that founders often pick features because they themselves experienced a specific annoyance and want to fix it. Personal annoyance is a useful starting point, since it usually points at a real problem, but the annoyance is by its nature a single moment, and a company shaped entirely around that moment tends to inherit the narrowness of the original observation.

The better path, once you have noticed the annoyance, is to widen your attention to the larger context in which it sits, because the context is usually where the company actually lives.

How to widen a feature into a company

Widening a feature into a company is a specific kind of work, and although it sounds vague, the process is more concrete than founders expect.

The first step is to spend real time with the customer for whom your feature would be useful, not in the form of a survey but in the form of a long conversation, and to ask them about the entire workflow that contains your feature. The workflow is usually wider than the feature, and inside that wider workflow there are usually three to five other moments that are similarly annoying, similarly served by inadequate tools, and similarly underserved.

The second step is to ask which of those moments share enough underlying logic that a single product could address all of them. The company you eventually build will be the one that addresses several connected moments rather than one isolated moment, because the connections between the moments are what produce the compounding that makes a company more valuable than its individual features.

The third step is to test the wider scope by describing the company to a few potential customers and watching their reactions. A customer who lights up at the description of a wider product, even though their original need was narrower, is telling you that the wider scope is worth pursuing, because the customer is seeing possibilities that the original narrow product would not have unlocked.

When to keep the feature small

There are situations in which a feature is genuinely worth building as a standalone product, and it is honest to acknowledge them. Some features are large enough on their own to support a real business, particularly in categories where the customer is willing to pay a high price for a single capability, or in categories where the feature is so universally needed that the volume of customers makes up for the narrowness of the offering.

In these situations, the feature is not a hidden company waiting to be widened, it is a real business that happens to have a narrow scope, and the right move is to build it carefully rather than to artificially expand it into something larger than it should be. The honest distinction is whether the scope is small because the founder has not yet seen the larger company underneath or because the small scope is itself the right size for the business, and the difference usually becomes clear after a few customer conversations.

What to do with the realization

If you read this far and realized that your current idea is probably a feature rather than a company, that is useful information rather than disappointing news. Most strong companies start out as feature ideas in their founders minds, and the work of widening them is part of how founders develop the judgment that produces durable businesses.

The realization is an opportunity to spend the next month doing the wider customer conversations rather than the deeper product building, and the conversations almost always produce a richer picture of the company than the founder originally had.

If, after the conversations, the wider company is still not visible, the right move is sometimes to wait and pick a different problem, since not every feature can be widened, and forcing the widening when the underlying material does not support it tends to produce companies that feel patched together rather than coherent.

A closing thought

The difference between a feature and a company is one of the harder things to see when you are inside your own first idea, and the founders who recognize the difference early tend to build companies that grow well, while the founders who do not tend to spend a year building something they will later need to widen anyway. Talk to the customer about the wider workflow, look for the connected moments, and trust that the company underneath your feature is usually visible if you are willing to look beyond the moment that first caught your attention.