Is Your Business Actually a Feature of Someone Else's Product?

There is a question that kills more software startups than bad code ever will: is your business actually a feature of someone else's product? If you are building on top of another platform, the platform owner is watching what works, and anything that works well enough eventually gets absorbed. Founders call it getting sherlocked, after a 2002 incident that gave the practice its name. It has been happening every year since. Here is how to know if you are next, and when being a feature is actually the smart play.

What it means to be a feature, not a product

Being a feature means your entire product fits inside someone else's roadmap as a line item. A product has its own surface area: its own data, its own workflow, its own reason to exist if every platform vanished tomorrow. A feature has none of that. It patches a gap in a bigger product, which means its lifespan is decided in a meeting you will never attend. The gap you found is real, the users love you, the revenue is growing, and none of it matters, because the platform can close the gap whenever the spreadsheet says it is worth closing.

The sherlock test: three questions

The name comes from 2002, when Apple released Sherlock 3) with features that cloned Karelia's Watson, a $29 app Mac users loved, and Watson's market evaporated. Ever since, founders ask the sherlock test before building on a platform:

1. Does the platform already own the pieces? If they have the distribution, the data, and the user interface, your product is glue, and glue gets absorbed.
2. Is your core feature one quarter of work for their team? If a small team at the platform could ship your main feature in three months, assume they will, eventually.
3. Would their users rather have it native? If the honest answer is yes, you are a waiting room, not a destination.

Answer yes to all three and you do not have a moat. You have a countdown.

Famous absorptions everyone forgot

The pattern repeats so reliably it has a season. Every June, Apple announces new system features and a wave of indie apps quietly die; the practice is so routine the community tracks it annually. When iOS 7 added a built-in flashlight in 2013, an entire category of flashlight apps, some with enormous download counts, became obsolete in a single keynote. The apps were not bad. They were features of the operating system, temporarily sold separately. The same story plays out on every platform with enough users: browsers absorbed password managers and reading modes, social networks absorbed scheduling tools, marketplaces absorbed analytics dashboards.

When being a feature is the right strategy

Here is the part the doom posts skip: sometimes being a feature is exactly the plan. If you know the platform will need what you built, you can build it deliberately as acquisition bait, price your time accordingly, and treat the company as an eighteen to thirty-six month project instead of a forever business. Calendar tools, email plugins, and analytics add-ons have all sold well to the platforms they patched. The mistake is not building a feature. The mistake is building a feature while telling yourself, your team, and your investors that it is a product. That self-deception is what turns a decent exit into a shutdown blog post.

Before you commit a year, run the idea through the free Reality Check. It asks directly who has to say yes for the business to work, and a platform that could simply absorb you counts double. And if you are still hunting for a problem worth solving, the Opportunity Finder looks for pain that does not sit inside someone else's roadmap.

FAQ

How do I know if my product is really just a feature?

Ask what is left if the platform ships your core function for free tomorrow. If the honest answer is nothing, you are a feature. If you still have data, workflow, or a community they cannot copy, you might be a product with a risky integration.

Can a feature grow into a real product?

Yes, by expanding surface area faster than the platform cares to follow. Features become products when they own data the platform does not, serve a niche the platform ignores, or become a system of record. The window is usually a few years, not forever.

What actually happened to Watson?

Apple shipped Sherlock 3 in 2002 with web search features cloned from Karelia's Watson, bundled free with Mac OS X. Watson, a paid app, could not compete with free and built in, and its market collapsed. The term sherlocking has described platform absorption ever since.

Should I avoid building anything a platform could copy?

No, because platforms can copy almost anything and that logic paralyzes everyone. Instead, price the risk: shorter time horizons, faster monetization, an exit mindset, and a second act planned. Awareness is the whole difference between a strategy and a surprise.