The competitor that takes a piece of your market this year will not show up in the competitive section of your board deck. You benchmark against the funded incumbent, the name everyone in the category knows. That is the competitor you can see, which is exactly why it is not the one to worry about.
The one to worry about is eight people you have never heard of, running a fleet of agents, shipping the roadmap you presented last quarter, faster than you can build it, with nothing to defend.
The short version
The most dangerous competitor in your category is no longer the funded incumbent. It is the small, agent-native team: eight people who fit in one conversation, carry no legacy product to protect, and produce what eighty people used to thanks to the agent stack. They have no coordination tax, no architecture they cannot rewrite, no customers they cannot break, and a cost base low enough to survive on revenue that would not cover your floor. The instinct to dismiss them as too small is the same instinct every incumbent had before losing a segment. The CEO move is not panic but a specific exercise: ask what eight people starting today with no legacy would build to attack you, and why you cannot.
For how defensibility shifts when features are cheap, see Any Competitor Can Clone Your Feature in a Week. For the economics that make tiny teams viable, see The Product Budget Is a Compute Budget Now.
Why small is now a weapon
For most of the history of software, small meant under-resourced. A tiny team could not match an incumbent's output, so it survived in niches the big company ignored. Scale was an advantage on its own terms. More people meant more output meant a wider moat.
That arithmetic inverted. Three forces did it.
No coordination tax. Eight people share one context. There is no cross-team dependency, no quarterly planning cycle, no review board, no translation layer between the person who understands the customer and the person who writes the code. Your roadmap crosses six teams and four reviews before it ships. Theirs is a conversation and a commit. Speed is not about working harder. It is about the absence of friction, and small teams have almost none.
No legacy to defend. Every decision you make is constrained by what you already sold. The contracts you cannot break, the architecture you cannot afford to rewrite, the customers who will churn if you change the thing they depend on. These constraints are real and they are heavy. The eight-person team has none of them. They start from the current state of the art and build forward with no weight. Your legacy is an asset on the balance sheet and an anchor on the roadmap.
Capital efficiency that used to be impossible. The agent stack lets a handful of people produce what a department used to. That changes the economics of who can compete. A team that small can survive on revenue that would not cover your office lease. Which means they can profitably take a segment you consider too small to bother defending, establish themselves, and expand into your core from a position you let them have.
The dismissal that kills incumbents
When you first notice a team like this, every instinct says dismiss them. They do not have enterprise features. They do not have your brand. They do not have your compliance certifications or your reference customers. They are not a real threat.
That is the precise sentence incumbents say before they lose. Not because the small team magically acquires all of those things overnight, but because they do not need them to start. They take one segment that you serve poorly because it was never your priority. They win it completely. They use that beachhead to build the features and credibility they were missing. And by the time they have enough to threaten your core, they also have customers, revenue, and momentum, and you are reacting instead of leading.
I have been on both sides of this. I have been the small team taking a segment a larger competitor thought was beneath them, and I have run the larger org that had to decide whether a tiny upstart was worth taking seriously. The pattern is consistent. The danger is always underestimated at exactly the moment it is cheapest to address.
The exercise
You do not respond to this by trying to out-hire them. You cannot, and headcount is not the lever anyway. You respond by thinking like them on purpose.
Run this exercise with your product leadership, once a quarter. Imagine eight people start a company today, with no legacy, the current agent stack, and the explicit goal of taking a piece of your market. Answer three questions honestly.
What would they build first? Not your whole product. The one wedge that is most underserved by your current offering. That wedge is almost always a segment you have quietly deprioritized, a workflow you support badly, a customer type you treat as secondary.
Why can't we build that? The answer will usually be some mix of coordination tax, legacy constraint, and priority, not capability. That gap between "we could" and "we don't" is your exposure.
What do we do about it? Decide deliberately. Either defend the segment by removing enough of your own friction to move at speed where it matters, or cede it consciously and protect the moats that scale actually gives you: distribution, data, trust, switching cost. What you cannot afford is to leave it undecided, which is the same as ceding it without noticing.
The plain version
Your scariest competitor is small, fast, and unburdened, and you will be tempted to ignore it because it is small. That temptation is the trap. Eight people with the current tools can ship your roadmap and take your underserved segments before you finish the planning cycle to respond.
Block ninety minutes with your product leadership this month and run the eight-person exercise on your own market. The segment you would attack if you were them is the segment someone else is about to attack you in.
If you are an incumbent trying to figure out which segments to defend and which to deliberately cede, that prioritization is one of the sharper conversations in product leadership right now. Find me on LinkedIn.
Further reading
Also on Medium
Full archive →Frequently asked
Why is a small team a bigger competitive threat now than a funded incumbent?+
Three reasons: no coordination tax (eight people fit in one conversation while your roadmap crosses six teams and a planning cycle), no legacy to defend (they start from the current state of the art with none of the architecture, contracts, or customers you cannot break), and extreme capital efficiency (the agent stack lets eight people produce what eighty used to, so they survive on revenue that would not cover your floor).
Isn't a tiny team easy to dismiss because they lack enterprise features and brand?+
That dismissal is exactly how incumbents lose. The small team does not need your whole feature set to start; they take one underserved segment, win it, and expand. By the time they have the features and brand to threaten your core, they also have the customers and momentum. 'Too small to matter' is the last thing many incumbents say before they lose a segment.
What is the 'eight-person competitor' exercise?+
A planning exercise where you ask: if eight people started today with no legacy and the current agent stack, what would they build to attack us, which segment would they take first, and why can't we do that? It surfaces the parts of your strategy that depend on inertia rather than advantage, and it usually points straight at a segment you are quietly underserving.
How should a CEO respond without overreacting?+
Do not try to out-headcount them; you cannot, and that is not the lever. Identify the segment a lean team would attack, decide whether to defend or cede it deliberately, and remove enough of your own coordination tax that you can move at a comparable speed where it matters. The goal is to compete on the dimensions where your scale is an asset, not a liability.
Does scale stop being an advantage entirely?+
No, but it changes form. Distribution, data, trust, and switching cost are still real advantages of scale. Headcount and breadth of features are no longer advantages by themselves, because a small team can match the features and moves faster. Scale wins when you convert it into the durable moats, and loses when you rely on it to simply out-build.
Comments (0)
Sign in with LinkedIn to leave a comment.
Sign in with LinkedIn