The distinction that decides the case
Adjudicators separate two things that practitioners tend to conflate: advanced skill in a widely available technology, and knowledge specific to an organisation's proprietary systems, methodology, or accumulated practice. Deep expertise in a commercial ESB product is generally the former. Knowledge of how a particular firm's canonical data model, reconciliation logic, and failure-recovery patterns interlock is the latter.
A defence built on the first category struggles. A defence built on the second — with documentary support — is considerably stronger.
Documenting proprietary methodology
Middleware consultancies accumulate genuine proprietary assets: internal accelerators, policy-as-code frameworks, reference topologies, migration playbooks, and canonical schema libraries refined across dozens of engagements. These are documentable, version-controlled, and demonstrably not available on the open market.
The evidentiary task is to show the consultant's specific fluency in those assets — commit history, authorship of internal standards, delivery of internal training, and the length of time required for a comparably skilled outside hire to reach equivalent productivity.
Quantifying the replacement burden
One of the most persuasive forms of evidence is an honest, specific estimate of onboarding time. If bringing an experienced external integration architect to full productivity on a client's estate takes nine months of supervised exposure, say so, and explain what makes it nine rather than three: undocumented legacy protocol dialects, regulator-specific reconciliation rules, or bespoke transformation libraries.
Vague assertions of criticality carry little weight. Specific, quantified operational reality carries a great deal.
Keeping the claim consistent across filings
Inconsistency is a recurring problem for consultancies filing across many beneficiaries. If a role is described as requiring rare proprietary knowledge in one petition and as a routine staffing backfill in another, both claims weaken.
Maintaining a single internal taxonomy of roles, each with a stable description of required knowledge, prevents that drift and makes every filing easier to prepare.