Rarely from the competitor you're already watching.
You know that one: what they charge, who they sell to, when they cut prices. They've been in the same market for years, with a structure much like yours, solving the customer's problem the same way. They can take share from you, but they won't surprise you.
The threat that surprises comes from someone solving the same need with a different cost structure. They don't compete on your ground: they compete where your rules don't apply.
The uncomfortable question
There's a direct way to find them, and it needs no consultants or market studies:
If someone founded a company today for the sole purpose of taking your customers, and could design it from scratch inheriting nothing of yours, how would they design it?
Not like yours. It wouldn't carry the administrative layers you accumulated because at some point they were needed. It wouldn't have the processes that exist because an old system demanded them. It would automate from the start what you automated halfway and on top of what was already there. It would decide faster, because there are fewer people to consult.
And the second question, which stings more:
Which part of your company exists today only because it was once necessary, and nobody has questioned it since?
The story from the other side of the table
We've been the entrant twice. It's worth telling, because it shows where the incumbent's real vulnerability was.
1994, Colombia. Celumovil. The country was launching mobile telephony, and the owners — in partnership with a North American operator — had to be billing before year's end, ahead of the competition. The contracted provider was a world-class firm in mobile telecom services, with methodology, references and global presence. Their estimate to get billing running: more than twelve months.
SFI had neither that size nor those references. It built the billing system from scratch, from raw call records, with no cooperation from the network's hardware vendors. It went live in four months, in time for the Non-Aligned Movement Summit in Cartagena. Celumovil became the first mobile operator in Colombia able to serve, bill, collect from and support its customers.
The large provider didn't lose on technical capability. It lost because its structure couldn't deliver in four months, and the entire value of the project depended on those four months. Whoever gets there first wins twice.
That same year, in banking. A Colombian bank opened a lobby self-service pilot. The competitors for that contract were backed by IBM, NCR and Unisys: more elegant hardware, more proven, with worldwide support. SFI brought a PC turned into a touchscreen self-service machine, running online rather than in batch — and the banking software the others didn't have.
It won the pilot. The first order was a hundred machines. A year later IBM had added the solution to its portfolio and NCR partnered to resell it.
Twice the player with fewer resources won. Neither time for having better technology: for arriving sooner with something that worked, while the big one followed its own process.
What today's incumbent learns from that
If you're the incumbent, the reading isn't comforting, but it's useful: your vulnerability isn't where you measure it. Not in price, not in the catalog, not in the sales force. It's in how long you take to respond and what it costs you to serve a customer.
An entrant designed today won't beat you on quality — you've spent years polishing it. It will beat you on speed and cost-to-serve, and it will go first for the segment you find expensive to serve and have probably already neglected.
Three signals, in order of severity:
Someone is serving well the customer you consider unprofitable. Almost always the first move: they found a way to make that customer profitable, and they'll climb from there.
Someone delivers in days what takes you months, with fewer people. The difference isn't talent: it's how many approvals and handoffs your process carries.
Someone arrives through a channel you don't measure. They don't show up in your competitive report because that report looks at companies in your industry, and the entrant comes from another.
What can actually be done
Preparing isn't reacting faster once they've arrived. It's knowing in advance which of your processes are vulnerable to that difference, and closing the gap first.
That requires an exercise almost nobody does in peacetime: looking at your own company through the eyes of whoever wants to replace it. What it truly costs to serve each customer type. How many steps and how many people each customer-facing process carries. Which activities exist only because they once were necessary. How long your decisions take, and what delays them.
None of those answers is in a financial statement. And all of them can be built in weeks, if you know where to look.
A question to close on: if you had to compete against your own company tomorrow, with enough budget and none of your inherited constraints, where would you attack first?
---