A global automotive manufacturer put its Cisco Enterprise Agreement out to bid in March 2025 — licenses, maintenance and support, with the option to consolidate hardware and network installation services under the same partners. Services delivery across roughly seventy North American locations, on a renewal worth tens of millions annually. I carried the services technical response.
Seventeen working days, and the first two mattered most
I was brought onto the pursuit late on a Friday morning. Clarifying questions were due to the client by two o’clock Monday.
What went back was a structured question set — license inventory, three-year projections by product category, planned platform migrations with timelines — written to scope the renewal rather than describe it, along with the agenda for the Monday working session.
A question set is not a formality. It is the last chance to find out whether the thing being bid on is the thing that will have to be delivered, and the difference between those two is where a services engagement goes wrong. The same instinct as reviewing a statement of work before it becomes an engagement, arriving under a deadline instead of a process.
The differentiator was not North American
Intelligence early in the pursuit reframed the bid. The client was consolidating a long partner list down to a subset with broader capability, rather than replacing an incumbent — breadth, not displacement.
What made the answer different from a regional competitor’s was the group’s parent company in the client’s own home country: its certified engineering bench, and its large-scale fabric, campus automation and wireless references, fed into the vendor questionnaire directly. A regional partner could not have answered those questions at all.
That is what a global affiliate is actually for, and it is rarer to have used one than to have one. The post-quantum program and the orchestration proof of concept came out of the same relationship from the other direction.
It was a loss, and the debrief was worth more than most wins
Four bidders survived first screening. Two of them priced at a loss, and the ones left standing were already doing on-site support.
Four weeks later the team was at the client’s North American headquarters anyway, and the account stayed live past the bid it was supposed to have ended with.
What the client said it wanted from a partner
That meeting is the part I kept, because it is a client stating plainly what it takes to be one:
- Proven capability in plant-floor networks, industrial wireless and multi-network environments.
- Experience with high-pressure change windows, where plant downtime is the constraint and the window is not negotiable.
- Security designed into the infrastructure rather than layered onto it.
- A segmentation and private-cellular strategy.
- Multi-vendor across Cisco, Palo Alto Networks and Juniper, rather than a single-vendor conversation.
- Partners who challenge the thinking with outside insight rather than take orders or sell product.
Every one of those sat inside the practice I ran, which is why the meeting rather than the bid is the part of this that belongs to me. The plant-floor and industrial-wireless half of it is older than that — Nissan and Georgia-Pacific and the Vistakon line integration are the same problem twenty years earlier, surveyed on site with the lines running.
Why a loss is on the record at all
Because a record that only carries wins is a sales document. The useful question about a pursuit is not whether it closed but whether the work was right, and the evidence here is that the client took a meeting with a firm it had just declined to hire.
Outcome
Not selected. The relationship opened anyway — a partnership session at the client's North American headquarters four weeks later, and a live account after that.