A few months ago we lost a bid.

A logistics company, field-based workforce, frontline-heavy operation. The kind of organization where the work happens in trucks and on routes and in the hands of people whose names never appear in a boardroom. We knew that world. We had done deep operational work with a similar company; different service, same structural DNA. Frontline workforce, compliance-driven, schedule-dependent, thin management layers between the people making decisions and the people doing the work.

We did not get the engagement. They went with a firm that had more direct experience in their specific industry.

I spent some time sitting with that. Not to relitigate the decision, but because losing well means asking an honest question: what did we leave unsaid?

The Label Problem

When a prospect asks for industry experience, they are not really asking about your resume. They are asking something deeper and more reasonable than that: do you understand our world? Do you know what it feels like to manage a workforce that starts at five in the morning? Do you understand the compliance pressures, the safety culture, the gap between what the policy says and what actually happens on the route?

That is a fair question and it deserves a real answer.

Where it gets complicated is when industry experience becomes a label rather than a lens. When the question stops being “do you understand our operational reality” and starts being “have you worked with a company in our specific sector.” Those are not the same question, and the difference matters more than most procurement processes are designed to catch.

The firm that wins on the label may understand the industry. They may also understand it so well that they know exactly how it has always been done. And sometimes, that is precisely the problem.

What We Had and What We Did Not Say Clearly Enough

Here is what I know now that I wish I had said more directly in that room.

We had worked with a private security company. Field-based workforce. Frontline-heavy. Route and schedule dependent. Operationally driven by compliance, safety, and accountability structures that had to function at the ground level, not just on paper. Managers stretched thin across large geographic areas. Frontline employees who had seen initiatives come and go and had learned, reasonably, to wait and see before they changed anything.

The operational DNA was nearly identical to the logistics company sitting across the table from us. The uniforms were different. The trucks were different. The problems; adoption, governance, role clarity, the gap between strategy and what actually happens in the field were the same.

That did not get translated correctly. We talked about the work we had done and did not draw the line explicitly enough between their world and ours. I left that connection for them to make, and that was my mistake.

When a prospect is evaluating risk, they are not going to do that translation work for you. That is your job and if you leave it undone, the label wins every time.

The Adjacent Experience Problem

There is a version of industry experience that is genuinely valuable. Deep sector knowledge, regulatory familiarity, understanding of the specific compliance environment a company operates in. That matters and we do not dismiss it.

What we have learned to do is bring that knowledge in deliberately. When we engage with a new sector, we identify an industry expert whose job is to pressure-test what we build. Not to run the engagement, but to stress-test it against the realities of that specific world. To ask the questions an insider would ask. To catch the assumptions an outsider might miss.

That is a more rigorous model than pattern-matching from a prior engagement in the same sector. It combines outside perspective; the ability to see what insiders have normalized, with real-world validation from someone who knows the territory. You get both. Most firms offer only one.

That model only lands if you explain it clearly, specifically, and early, not as a defense of your resume, but as a demonstration of how seriously you take the question the prospect is actually asking.

What I Would Do Differently

If I walked back into that room today, I would not argue against the instinct to want industry experience. It is a reasonable instinct. I would speak directly to what sits underneath it.

I would say: you want to know if we understand your world. Here is what our work with a field-based operation looked like. Here is where the operational reality matched yours. Here is where it diverged. Here is how we account for the gap. Here is the person we bring in to make sure we are not missing something specific to your sector.

Then I would ask them a question in return: the firm you are considering that has direct industry experience; do you know whether their last engagement in your sector actually stuck? Not whether they delivered a strategy. Whether the business ran differently eighteen months later.

That is the question that reframes the conversation. Not to win an argument, but to make sure we are all talking about the right thing.

The Question Underneath the Question

Industry experience is shorthand for trust. The prospect wants to know that you will not waste their time learning their world on their dime and that is fair.

The answer is not to defensively list your credentials. The answer is to demonstrate, specifically and early, that you already understand more about their world than they expected. Always be honest about where you are bringing in reinforcement and why that model produces better outcomes than familiarity alone.

We lost that bid. I think we could have won it if we had done a better job of that translation. That is the learning. Not that industry experience does not matter, but that adjacent experience, clearly translated, is more valuable than most prospects realize and more valuable than we made it sound in that room.

The question worth asking before your next engagement is not who has worked in our industry, but who understands the problems we are actually trying to solve, and who has the track record to prove they can make the change stick.

Those are not always the same firm.

That is the conversation the Clarity Call is for. Not to sell you an engagement, but to help you figure out whether what you are dealing with is an industry problem or an adoption problem and what the difference means for who you actually need in the room.

Thirty minutes. You talk, we listen. No invoice for the conversation.

Just an honest answer to the question that should have been asked before the last engagement started.

Book Your Clarity Call at knewlynk.com/business_process_consulting