About Us
Our Approach — How We Run the Engagement
Every EuroShield engagement begins with the same question, and the question is not technical.
What decision is this engagement supporting, and who is making it?
The decision defines the scope. The decision-maker defines the voice, the evidence standard, and the deliverable structure. A report prepared for an investment committee is not the report prepared for a regulator. A brief prepared for a plant manager is not the brief prepared for a board. An engagement that cannot answer this opening question precisely has not yet been scoped — it has been sketched.
We will not proceed to scope until the question is clear. This is the single most consequential discipline in our practice, and the one most commonly skipped in the market we operate in.
How We Scope
First, we declare what the engagement will and will not do. Every proposal carries an explicit scope-inclusion list and, as often, an explicit scope-exclusion list. Work outside the defined scope is not performed under implicit extension; it is either added as a formal variation or declined. This protects the client from surprise billing and protects the engagement from scope drift that degrades the deliverable.
Second, we quote against the scope, not against hours. For the majority of our engagements — diligence, readiness reviews, FEED reviews, commissioning oversight, regulatory preparation — fixed-fee pricing is appropriate and offered. For genuinely open-ended work (incident response, live red-teaming, restructuring-grade review), time-and-materials is more honest and is disclosed as such.
Third, we tell the client when they should not buy. If the decision does not require the advisory, if an internal team can deliver to the required standard, if a peer firm is better placed on the specific mandate, we say so. A declined engagement is a longer relationship than an oversold one.
How We Staff
Every engagement carries a named senior signatory — partner-level or equivalent — with operational experience in the domain. That signatory is not a title on the cover page. They lead the engagement, attend the decision points, sign the deliverable, and remain reachable through the post-delivery period.
Behind the signatory, we staff lean. A mid-sized engagement typically runs with the signatory, one senior specialist (OT, DC, AI, embedded, or financial-technical depending on mandate), and a supporting analyst. Larger engagements add discipline leads — mechanical, electrical, controls, cyber, regulatory — but do not add layers of review. The signatory sees the work, not a summary of it.
We do not staff by headcount optimisation. The team that arrives at the first meeting is the team that delivers the final report.
How We Analyse
Evidence-linked findings. Every material finding is traced to a named artefact — a document reference, an interview note, a test result, a configuration file, a telemetry sample. Findings that cannot be evidenced are flagged as such, not asserted as fact.
Calibrated uncertainty. We document what we know, what we inferred, and what we did not have access to. A finding with a confidence qualifier is more useful to a decision-maker than a finding without one. Confidence is declared, not implied.
Consequence-class framing. Risks are categorised by consequence — regulatory, operational, safety, financial, reputational, commercial — and by their coupling between classes. A cyber risk with a safety consequence is not the same artefact as a cyber risk with a commercial consequence, even if the vulnerability is identical.
Counter-factual testing. For recommendations, we ask what would need to be true for the recommendation to be wrong — and include that reasoning in the deliverable. The client reads the argument, not only the conclusion.
How We Deliver.
How We Work Alongside Other Advisors
Most of our engagements sit in a broader advisory ecosystem — lawyers, accountants, consulting firms, EPC contractors, certification bodies, investment bankers, and existing internal teams. We are explicit about our role and our boundaries in every such engagement.
We coordinate actively with counsel, particularly on contract, regulatory, and incident-response matters. We do not provide legal advice.
We coordinate with transaction advisors, auditors, and accounting firms. We do not conduct financial audit.
We hand off cleanly to systems integrators, EPC contractors, and operating teams at engagement close. We do not compete for their scope.
We cooperate with internal teams rather than replacing them. Our role is to provide what internal teams cannot provide — independence, cross-disciplinary integration, or specialist depth — not to duplicate what they already do well.
What We Do Not Do
We are specific about the work we decline, because that specificity is what protects the work we accept.
The list is deliberate. Every item on it is a business we could technically enter. Each one is a boundary we maintain because crossing it would compromise the independence, the judgment, or the senior-signed standard that defines the firm.