An outsourcing tender arrives. Sixty pages, four weeks to respond, a portal, a weighting matrix, a clarifications deadline. Somebody on your team clears a fortnight and starts writing.
You have already lost, and you lost about nine months ago.
The document is the end of the process
By the time a buyer publishes a requirement, they have decided what the problem is, roughly what the solution looks like, what it should cost and who is plausible. The document is the written form of decisions that were taken long before, in conversations you were not part of.
Which is why the criteria so often feel like they were written for somebody else. They were. Usually for the incumbent, or for whoever has been in the room while the buyer was still working out what they needed.
If your language is not in the requirements, you are answering somebody else's question and being scored on how well you answer it.
What the year before actually looks like
The sequence varies, but the shape rarely does.
- Something changes internally. A new CX or operations leader arrives, a board sets a cost mandate, a service failure becomes visible enough to need an answer.
- A review gets commissioned. Sometimes formal, often not. Someone is asked to find out what the options are.
- The informal market scan. Peers, analysts, LinkedIn, two or three providers they already know, whoever has published something intelligent on the specific problem.
- The shape of the solution settles. Onshore or offshore, one site or several, what is in scope, what good looks like. This is where the deal is actually decided.
- Procurement arrives. The shape becomes a document, the document becomes a process, and the process is designed to defend a decision that has largely been made.
The window is stages one to three. By stage four you are being written into or out of a specification. By stage five you are providing competitive tension for somebody else's preferred option.
The signals that sit under each stage
All of this is visible if you are watching for it rather than waiting for a portal notification.
- A new CX, operations or customer service leader appointed — new leaders review supplier arrangements, and they do it early
- A contract approaching its renewal window, where the term is discoverable
- An announced technology or transformation programme that changes the operating model
- Expansion into a new market, product line or channel
- Visible service pressure: complaints volumes, regulatory attention, press
- Merger, acquisition or restructure, which consolidates supplier lists
- A public review of onshore, offshore or hybrid delivery
What being early actually means
It does not mean calling a stranger and asking whether they are reviewing their outsourcing arrangements. It means being a name that is already in their head, attached to a specific problem they recognise, before they start writing anything down.
That is a content problem before it is an outbound problem. Most providers in this market sound identical on paper: scale, quality, flexibility, partnership, transformation. If a buyer cannot tell four providers apart, the only lever left is rate, and rate is an argument you win by being cheapest rather than by being right.
The providers who get into the conversation early are the ones who have said something specific and useful about the thing the buyer is currently worried about. Not a capability statement. A point of view, ideally one their own operations people actually hold and could defend in a room.
The uncomfortable implication
If this is right, then responding to more tenders is not a growth strategy. It is a way of staying busy while your win rate stays where it is.
The work that changes the number is unglamorous and slow: knowing which accounts matter, watching the things that happen before a review, having something worth saying when you reach them, and reaching them while the problem is still being defined rather than after it has been priced.