What to do when a giant enters your market

Guide · Founder · 5 min read · last verified 2026-07-27

An incumbent entry is the day a company many times your size announces a product in your category: the platform adds your feature, the giant ships the adjacent module, and the press writes the obituary for every smaller vendor in the space. It is an incident to be worked, not a verdict to be accepted. The first discipline is separating the announcement, which is loud, from the change in buyer behaviour, which is measurable — and which, in the early weeks, is often smaller than the press cycle suggests. Often, not always: that is a tendency, and the entire point of what follows is to find out which case you are in rather than guessing from the coverage.

Work it as an incident, not a verdict

Founders tend to experience an incumbent entry emotionally before they experience it commercially — the panic usually arrives well before the buyers do, because the announcement lands on you in a morning while its effect on buying behaviour, if any, unfolds over quarters. Incident discipline counters that asymmetry. Open a log. Date the entry. Record what was actually announced versus what was shipped, which are frequently different things and different dates. Put decisions on the record with the evidence that justified them. The goal is to make every response a considered move rather than a reflex, because reflexes in this situation skew expensive.

Measure before you meet

The strategy meeting held in announcement week runs on adrenaline and secondhand takes. Schedule it after the measurement instead. What to pull, concretely: whether the giant now appears in the buyer questions you actually compete on; whether the answers to those questions have changed in substance or only in cast; and whether the questions themselves are shifting — new comparison questions naming the giant alongside you are a leading indicator worth more than any headline. If you keep a locked benchmark of your question set, this is the moment it pays for itself: the before-picture already exists, taken when nobody was frightened, and a Magrios re-scan against it turns "everything changed" into a specific, sourced list of what changed and what did not.

Read the deltas coldly

Three readings recur, each with a different response. The first is announcement-only: coverage everywhere, category answers barely moved. This has been the early-stage pattern often enough to check for first — though it is an observation about how these events tend to unfold, not a law, and answer surfaces keep shifting as engines and content change. The response is vigilance, not surgery: keep the watch, skip the repositioning. The second is adjacency: the giant now appears for broad category questions but not for the specific jobs your buyers hire you for. The response is to deepen your grip on those jobs and let the giant hold the generic ground. The third is direct overlap: the giant is being named in your core comparisons and recommended for your core use cases. This is the serious case, and it earns the full counter-position below. Knowing which case you are in changes everything about the next quarter — which is why the reading precedes the meeting.

Where giants structurally underserve

Size buys distribution and trust, and it bills for them in depth, speed, and focus. Depth: your category is the giant's roadmap line, staffed by one team among hundreds; it is your entire company. Speed: their release trains, review layers, and platform obligations set a floor under how fast they can respond that a focused company can undercut. Focus: their version of the product must serve their platform's average customer, so demanding segments and awkward edge cases tend to get the generic treatment. These are structural tendencies, not guarantees — each one is a hypothesis to verify against evidence from your own market, by checking where the giant's documentation goes thin, which buyer questions their material does not answer, and what their actual ship cadence in the category has looked like. Where the tendencies hold, they are durable, because they follow from what makes a giant a giant.

Write the counter-position from evidence

The counter-position is not a manifesto about passion or nimbleness; it is a short document in which every claim is checkable. The questions where the record shows you answering better. The segments the giant's own material visibly does not address. The depth comparison a skeptical buyer can verify from public sources in ten minutes. Built that way, it arms three fronts at once. Sales gets it as a battlecard built from AI answers, because reps are likely to start hearing the giant's framing repeated back to them in deals — and those repetitions should flow back through the loop described in what sales should tell marketing about buyer questions, since what buyers echo tells you which of the giant's claims are actually landing. Content gets a priority list: the exact questions where the entry threatens your position. And leadership gets calm, which is not a soft benefit; teams take their temperature from the founder in these weeks.

One boundary keeps this article honest: if the giant publishes a comparison page naming you directly, that is a narrower situation with its own decision tree — see what to do when a competitor publishes a comparison against you. The entry itself is the broader event; the comparison page is one move inside it.

What not to do in the first month

Do not reposition in panic; a position changed under fire, before measurement, reads as confirmation that the giant was right to come for you. Do not announce a feature race you cannot ship; the announcement buys a week of comfort and costs a year of credibility. Do not snipe publicly at the giant; punching up in public mostly advertises the fight, and the fight advertises the giant. And do not go quiet with customers — many of them read the same coverage you do, and silence lets the press cycle answer their questions for you. A short, factual note about what the entry does and does not change for them beats any amount of internal composure.

Keep the watch running

An incumbent entry is a process, not an event. The giant's presence in your category's answers will keep shifting as their content lands, as buyers react, and as engine behaviour changes — all three move independently, none of them on your schedule. Put the giant into your standing competitive scan and read it quarterly, the discipline covered in how to track competitor AI visibility over time, with named escalation triggers: appearance in your core comparisons, displacement from a question you previously held, their claims surfacing in your deals. Companies do survive incumbent entries — the pattern worth copying is procedural, not heroic: measure what changed, position where the structure favors you, and re-measure on a schedule the press cycle does not set.