Perspectives · Strategy · Gulf markets

How to Win a Tender in an Industry You've Never Worked In

On cross-domain methodology transfer — and why deep expertise in your domain is sometimes your competitor's liability

In 2025, we at Futad competed for a design-phase procurement contract with an aviation catering company in Qatar. We had never designed a uniform. We had no fashion background, no garment experience, no relationships inside the aviation catering sector. Our competitors were established fashion consultants with domain credentials we could not match.

We won. And the reason we won is worth understanding — because it applies to every cross-domain entry problem, and the GCC market is full of them.

The Brief Behind the Brief

The stated brief was uniform design. The actual problem was operational disruption. The client needed to fit uniforms to over a thousand employees across culinary and operational teams. The existing process required 13 minutes per person for manual measurements. Across that workforce, the cumulative cost — in time, scheduling disruption, and operational coordination — was enormous.

Our competitors read the brief as written: design better uniforms. We read the brief as a symptom: there is an operational efficiency problem disguised as a design brief.

We proposed volumetric body scanning. One scan per employee, completed in under a minute, producing a precision 3D model that fed directly into the design process. Measurement time dropped by 92%. Estimated operational disruption avoided: 70 days.

Deep expertise in a domain means you’ve learned to solve its problems the way they’ve always been solved. That can be an advantage. It can also be a constraint.

Why Domain Expertise Can Be a Liability

This is a pattern I’ve observed across multiple tender situations: domain experts solve domain problems with domain tools. Fashion consultants approach a uniform brief with garment methodology, fabric knowledge, and design process. All of that is legitimate. None of it addresses the underlying operational problem because fashion consultants are not trained to look for operational problems in a garment brief.

Deep expertise narrows the aperture of problem recognition. It is enormously valuable inside the aperture. Outside it, the expert sees what they expect to see.

We had no expectation. We had a systems methodology: define the actual constraint before selecting the intervention. Applied to a domain we had never worked in, that methodology found a problem the domain experts weren’t looking for.

The BMW Principle

The specific technique we used on that tender — importing ergonomics logic from automotive manufacturing into garment fitting — is an example of what I call cross-domain reference importing. The precision 3D body measurement methods used in BMW’s automotive ergonomics research for driver fit optimisation had no obvious connection to aviation catering uniforms. Except that both problems are, at their root, the same problem: fitting a physical object to a human body at scale, with precision, at minimum operational cost.

Once you see it that way, the automotive methodology is not an analogy. It is the solution.

Cross-domain reference importing only works if you have two things: a systems-level understanding of the problem (not a domain-level one) and exposure to enough adjacent fields to recognise where the solution already exists.

What This Means for Market Entry

If you are entering an industry where you have no domain history, the temptation is to acquire credibility by imitating what established players do. To learn the domain language, recruit domain talent, build a domain track record.

That strategy works, slowly, with significant capital. There is a faster one: find the problem the domain experts aren’t solving because they can’t see it from inside the domain. Build the solution from your methodology, not theirs. Win on the dimension where your outsider perspective is an advantage, not a liability.

The credential you need is not a history in their industry. It is a documented track record of finding the hidden constraint. That is what we walked in with. It was enough.

You don’t need domain history to win in a new domain. You need the methodology to find what the domain experts have stopped looking for.

About this essay

Written from Mirsab’s years at Futad Advertising in Doha, which he co-founded in 2018 and left in 2025. The projects, clients and results described are Futad’s. First published on Mirsab’s blog on 14 March 2026. Republished from Mirsab’s blog with light edits for accuracy.

Partner with us

Think it through with us.

If an essay here describes a problem you are working on, tell us about it. The first conversation is about the problem, not the technology.

Start a conversation