How do we position against a platform our buyer already owns?

You beat a platform your buyer already owns by changing the question from which product is better to which job is going unfinished. The platform wins a feature comparison every time, because it only has to be good enough and it's already paid for. Your opening has to name one job it handles badly, put a number on what that costs every month, and answer the roadmap question out loud before the buyer asks it.

That's a harder argument than the one most growth-stage companies prepare for, and it's a different one from positioning against a much bigger competitor. Size is an asymmetry you can turn into a liability. Ownership is something your buyer already chose, already paid for, and would have to admit was incomplete.

Why doesn't our usual competitive positioning work here?

Most competitive messaging assumes a bake-off. Two vendors, one shortlist, a scorecard somewhere. Write the comparison page, win the columns, take the deal.

When the buyer already runs on the platform, there's no bake-off to win. The platform is the default, the budget is already committed, and your product has to justify a new line item next to something the team has been trained on for years. The real alternative you're up against is doing nothing, which costs the buyer no money, no political capital, and no integration work.

This is the same mechanism behind weaker products winning more deals. The better product loses to the easier decision. When the easier decision is already installed and running, the gap widens.

How do we answer "doesn't the platform already do that?"

Concede the overlap immediately, then narrow. The honest answer is usually yes, a version of it, and buyers can tell when you're dodging. Every second you spend arguing that the platform's module doesn't really count is a second you're not spending on the job it genuinely handles badly.

The narrowing has to be specific enough to be checkable. "More flexible" and "purpose-built" are the words every adjacent vendor uses, which makes them worth nothing to a buyer comparing three of you. Name the workflow, the frequency, and the failure. A claim like "their module handles the standard case and routes the exceptions to a queue your team works by hand, roughly 400 a month" gives the buyer something to verify internally, and verification is what moves a deal.

Once you've named the job, the Three Questions Test does the rest of the work. Why change, why change now, why change with you. The platform-adjacent version of that middle question is the one founders skip, and it's the one that decides the deal.

What do we say when they ask if the platform will just build it?

Answer it on the page, in your own words, before a competitor answers it for you. The roadmap objection kills more adjacent deals than any feature gap, and refusing to address it reads as if you haven't thought about your own risk.

Platforms build for the average of their installed base. That's the correct strategy for a company serving thousands of accounts across every size and configuration, and it's exactly what creates your opening. The consequence for your buyer is that the platform's version arrives built for the median customer, on the platform's timeline, and configured the way the median customer needs it. If your buyer sits outside that median, waiting has a price.

Put the price in months and money. A buyer weighing an announced roadmap item against a working product needs to know what the wait costs, and most adjacent vendors leave that number blank. Filling it in is the whole argument.

Does naming the platform on our homepage help or hurt?

Naming it helps. Naming it as a logo instead of as the alternative is where companies lose the thread, and we have numbers on how common that is.

We scored 302 healthcare software homepages on the 19-signal Brand Signal Score and published the results as the 2026 Healthtech Messaging Index. Health IT is the clearest example of the pattern because nearly every company in it sells next to a platform the hospital already owns, but the failure travels to any market with a dominant suite vendor.

36 of the 302 companies name a major platform somewhere on the homepage. 32 of those 36 still score a flat zero on Alternatives Acknowledged, the signal that measures whether a page tells the buyer what they'd use instead. The platform appears as an integration badge and never appears as the thing the buyer is actually choosing between.

The six-point spread between those last two rows travels with a stronger page overall rather than proving one signal causes the rest. Read it as a marker: the companies willing to name what the buyer would otherwise do tend to have done the harder positioning work everywhere else too.

A logo wall says you connect to the platform. It doesn't tell a buyer why they'd add you to it. Those are separate jobs, and only one of them wins a deal.

How do we position without sounding like a feature?

The adjacency trap is letting the platform's name become your identity. Once your first line is built around who you integrate with, you've told the buyer to file you under accessories, and accessories get cut in the first budget review.

The fix is owning language the platform doesn't use. When your category name, your description of the problem, and your proof all come from the platform's vocabulary, you've agreed to be measured on the platform's terms. Companies that get recommended own a frame of their own, which is the practical difference between a visual identity and a narrative identity.

This is where Solution-Centric Marketing does the most damage. A page that leads with capabilities invites a feature-by-feature comparison against a suite that has more features than you ever will. Leading with the problem, named precisely enough that the platform's version obviously doesn't cover it, moves the comparison onto ground you can hold.

What do we change first?

Four changes, in this order, and the first two cost nothing but a decision.

1. 1Name the real alternative on the homepage. Write the sentence that says what a buyer does today without you, including the option of keeping the platform module and absorbing the gap manually. If that sentence isn't on the page, the page is arguing against a competitor the buyer never considered.
2. 2Answer the roadmap question in public. One paragraph, honest, with the cost of waiting in months and money. Burying it doesn't stop buyers from asking it, it just means they ask someone else.
3. 3Move the integration logos below the argument. Keep them, because they answer a real procurement question. Stop letting them do the work your positioning should be doing.
4. 4Run the Cover-the-Logo Test on the result. Hide your name and hand the page to someone outside the company. If they can't tell whether they're reading you or the platform's own product page, the narrowing hasn't happened yet.

None of those are copywriting tasks. Each one requires a decision the leadership team has to make together about which job you're claiming and which you're conceding, and that decision is the thing a rewrite can't manufacture. That's the work a Magnetic Messaging Framework documents once so the answer stays the same in the deck, on the site, and in whatever your team writes next week.