One morning the company whose platform you build on ships your core feature, free, baked into the operating system. If that feature is what you sell, the floor seems to drop. I have been on the other side of that morning. The move that saved the quarter was to read the launch as proof the category was real, then argue the whole product on the one part of the problem the free version leaves unsolved.
If you market a product that lives inside someone else's ecosystem, this is a structural risk rather than a freak event. The platform watches which third-party features people love, and eventually it copies the popular ones into the system where they cost the user nothing. Your pricing page starts competing with a toggle in Settings. Given a long enough timeline it happens to any feature people love, so the only variable you control is what you do in the two weeks after.
In September 2025 it happened to a client of mine. YouMail is a consumer app that stops spam calls and robocalls. Apple's iOS 26 update shipped Call Screening, a built-in feature that answers unknown callers, asks who they are and why they are calling, then hands you a transcript so you can decide whether to pick up. That sits close enough to the core of what YouMail sells that the first reaction across the team was to treat it as an extinction-level event.
Read the launch as validation
The panic had it backwards. A platform does not build a feature into a billion phones on a whim. For a small app that had been explaining the category one ad at a time, that is awareness you could never buy.
A platform shipping your feature is the cheapest market validation you will ever get. Apple just taught a billion people the category exists.
So the first move was to name the platform's version precisely and mark the gap between it and ours. Every reactive positioning exercise I have run since begins in the same place: with where in the problem each product does its work, well before anyone opens a feature list.
The feature list is the trap
The instinct when a rival ships is to build a comparison table and drop a green check in every row you win. It feels productive and it is a trap. A feature grid invites the reader to count checkmarks, and an incumbent carrying a whole operating system can keep adding rows long after you have run out. Play a counting game against Apple and you lose it on a long enough timeline.
The axis that does not move under you is where the problem actually gets solved. Apple's screening acts at the phone: the call arrives, the device intercepts it, the caller answers questions, and you still read a transcript and make the call. The positioning we chose placed YouMail earlier in the path, so the message was that a bad call is stopped before the phone rings at all.
Compete on where the problem gets solved. The platform solves it at the surface. You solve it at the root.
One caution matters here, and it is the difference between good positioning and a claim you cannot back. What the app does under the hood, how aggressively it filters, what it draws on to decide, belongs to engineering and legal, and has no place on a landing page. So the language stayed in the register of positioning. The message became that the call is stopped earlier. Whether that maps cleanly to a specific technical mechanism is exactly the thing you do not assert on a marketing page you cannot substantiate.
The same move, three times in six months
The response was one idea sharpened across three passes as it met more real traffic, and the shape of those passes is the reusable part.
The first pass, in September, was just the argument on paper. One line carried it: the platform asks unknown callers to stop and explain themselves, and YouMail's positioning was that the call never reaches you to begin with. There was a comparison, but it led with that depth contrast, and every row restated the same thing in a new costume rather than opening a checkmark race.
The second pass, in October, turned the argument into a landing-page brief. The language tightened to a single verb contrast a cold reader could hold in their head: the platform silences the call, the app stops it. The design job was to make that legible on one screen, the polished built-in version on one side and the deeper version on the other, so the difference registered before anyone read a word of body copy.
Cold traffic never reads the middle
The December page followed a sensible shape: a hero, a few middle sections explaining the problem and the fix and the mechanics, a short setup note, and a closing value section. It read well on its own. Then it went in front of cold Meta traffic, people in the discover-and-engage phase who had never heard of the app and did not yet have the problem consciously in mind. The read after the first flight was blunt. The hero worked and the final section worked. The middle did nothing.
A cold visitor does not read a page, they skim the first screen, feel something or feel nothing, and leave. The careful middle, the interference fix, the walk-through of how the filtering made its decisions, was all written for a person already shopping for a solution.
Cold traffic never read the middle of the page. The comparison had to move to the top or it did not exist.
So we cut the middle and promoted the comparison. The depth contrast that had been sitting three sections down moved directly beneath the hero, because to a stranger that contrast is the entire pitch. The teaching sections did not get thrown away. They moved to the pages a warmer visitor actually reaches, where a reader who is already interested will happily read the mechanics. The cold page kept the hero, the promoted comparison, and the payoff, and nothing else.
The honesty that makes positioning hold
There was one operational wrinkle worth naming, because how you handle it is itself a positioning decision. On newer iOS, a user who switched on the platform's screening while also running a third-party filter could find the built-in setting sitting in front of the app and getting in its way. The tempting move is to stay quiet about it. We did the reverse and put the short setup step right on the page, plainly stated, no spin. Showing a prospect exactly how to make both things work earns more trust than any row in a comparison table. Positioning that survives contact with a real user is positioning that does not depend on the reader staying in the dark.
Run it yourself when the platform copies you
You do not need this exact story to use the pattern. Any time a category incumbent ships a native version of what you sell, the same five moves apply.
- Read the launch as validation. The incumbent just certified your category and taught its whole base that the problem is real. Absorb that awareness instead of bracing against it.
- Find the depth gap. Map where in the problem the built-in version stops working and where yours keeps going. Build the story on that axis, since it is the one the platform cannot cheaply copy back.
- Reframe before you compare. Lead with how deeply the problem gets solved, so the reader weighs substance rather than tallying boxes you can eventually lose.
- Lift the contrast above the fold for cold audiences. If a stranger has to scroll to learn why you are different, you have not actually told them.
- Retest against the coldest traffic you buy. What a warm visitor needs on a page will quietly mislead you about what a cold one will ever read.
This is the competitive edge of the wider system I lay out in the growth operating system. The same YouMail engagement produced the web-funnel rebuild I cover in the app-store-tax story and the acquisition work in the full case study. The Apple response is the reactive front of all of it. When a platform ships your feature for free, the win is a clearer answer to where the problem actually gets solved, put in front of the coldest reader you have, quickly.
If a platform just shipped a native version of what you sell and you are deciding how to respond, this is the kind of positioning work I do. Let's talk.