What we are asked before the first meeting.

We do not publish the level of our security clearances. That is standard practice in this sector and part of the confidentiality commitment itself. We work on programmes that require the handling of sensitive information, and we share the detail of our clearances in the first conversation, once there is a contract or programme framework that justifies it.

Yes. Where a programme requires Spanish or EU nationality for assigned personnel, we verify this at assignment and confirm it in writing before work starts. No profile joins a programme without meeting the requirements set by the authority or the client.

On our own systems, under ISO 27001 and the Spanish National Security Framework at Medium level, or directly on the client's systems where the programme requires it. We do not use third-party services that the client has not authorised to store or process programme information.

By default, intellectual property in the deliverables belongs to the client. This is set out in the contract before work starts, together with the treatment of documentation, software and any tooling developed during the project. We do not reuse one client's deliverables on another.

We do not export equipment. Where a project involves technology or components subject to export control or dual-use regulation, we work within the client's licensing framework and with the relevant authority, and we adjust team composition and information handling to whatever that framework requires.

The team is ours. If a programme needs a highly specific profile we do not have in-house, we propose it to the client and obtain approval before bringing that person in, under the same clearance and confidentiality conditions as the rest of the team. We never subcontract without the client's knowledge.

Three factors, in this order. First, the clearance level the programme requires: where personnel clearance is needed, the timeframe is set by that process and is outside our control. Second, how specialised the profile is: a systems engineer with aeronautical certification experience does not join on the same timeframe as a development profile. And third, the size of the team and whether it joins at once or in phases. In the first conversation we review these three points against your case and give you a specific, committed timeframe rather than a generic estimate.

A generalist consultancy sells you hours. We deliver evidence under the standard your programme demands, and we stand behind it in front of the authority. The difference shows up at the design review, not in the proposal: we know which document is needed, in what format and with what traceability, because we have delivered it before on air, naval, land and space programmes.