When a platform giant ships your feature

There's a specific email I get a handful of times a year. Apple or Google or Microsoft or whoever just announced a feature that does roughly what the founder's product does, and the founder writes to me with the same opening line. This validates the problem, right. They want me to confirm it. They want me to tell them the giant entering the space proves the market is real and they should keep going. I almost never can, because the giant shipping your feature usually doesn't validate anything, and the framing itself is how founders avoid the harder conversation they need to have.

Start with what the giant actually brings. They bring distribution that you can't match, on the order of hundreds of millions of devices that already have their product installed and updated. They bring a price point of zero or close to it, because the feature is bundled into something the user is already paying for. They bring trust that took decades to build. They bring a UX team that will iterate on the feature long after launch. They bring an integration with the rest of the platform that you can't replicate because you aren't the platform. Any one of those is a meaningful disadvantage. All of them together is a different category of competition than the one you signed up for when you started building.

What founders mean when they say this validates the problem is that the giant's product team, with all of their research and their resources, also concluded the problem was real. That part is true. The problem is real. The conclusion founders draw from it, which is that the market is therefore good for them, doesn't follow. A market being real and a market being a good place for a small team to compete are two different things, and the giant's entry is evidence for the first while being strong evidence against the second.

The instinct that follows the announcement is almost always the same. Expand scope. The founder decides the answer is to do more, to add the things the giant won't do, to build the version that's for serious users or for teams or for some specific industry. Sometimes that works. Usually it's a dodge in new packaging. The expanded scope is harder to build, harder to explain, and still has to be sold against a free thing that does the basic version well enough for most people. You haven't solved the competition problem. You've added complexity to a product that now has to justify itself against an even higher bar.

The honest move when a giant ships your feature is to ask a different question. Not is the market real. The market is real. The question is whether the small slice of users for whom the giant's version will never be enough is large enough, reachable enough, and willing to pay enough to support a business. Sometimes the answer is yes. The slice is usually professional users with specific needs, or teams with workflow requirements the giant won't touch, or industries with compliance constraints the giant doesn't care about. When you can name that slice precisely and you have evidence that they're willing to pay for the better version, you have a path forward.

When you can't name the slice precisely, the answer is usually that the giant just took your business. That's a hard sentence to write and a harder one to accept. Founders often won't accept it for at least six months, during which they'll keep building, keep telling themselves the giant's version is bad, keep watching their growth flatten, and keep avoiding the conversation about what to do next. Those six months are the expensive part. The pivot itself, when it comes, is rarely what costs you. The avoidance is.

There's a version of this where the giant's announcement is actually good news, and it's worth naming. If you were building a thin product that solved a painful problem and you were waiting for the market to mature, the giant entering can validate the timing and pull adoption forward across the whole category. In that case the giant's version becomes the on-ramp and your version becomes the upgrade, and you do well because the rising tide is real. That outcome requires you to already have something the giant's version structurally can't be, which is a high bar and not the default situation.

When the announcement comes, give yourself a week to feel however you feel about it. Then sit down and answer the precise question. Who specifically won't be served by the free thing. Why specifically. What evidence do I have. If you can answer all three with specifics, keep building. If you can't, the work in front of you isn't to expand scope. It's to figure out what you're going to do next.

This connects to a question I answer in depth: How do I know if my startup idea is worth building and What should I build next as a solo founder.