TechFides — June 2026
There is a simple test for whether a government modernization project was sovereign, and it is applied at exactly one moment: when the vendor leaves. If the system keeps running because the government's own people can run it, the project was sovereign. If it degrades because the knowledge walked out with the contractor, it was a dependency dressed up as a deliverable.
Most engagements fail this test, and they fail it by design. The vendor's commercial interest is in being needed next year, which is precisely the opposite of the government's interest in being capable on its own. Capability transfer is how that conflict gets resolved — but only if it is written down.
Why "transfer" has to be contractual
Every vendor says its solution builds local capacity. Almost none commit to it in a way the government can enforce. The word "transfer" in a sales deck is an aspiration. The same word in a contract, with named deliverables and a close-out condition, is an obligation.
The difference is everything. A transfer that is merely promised happens when there is time and goodwill left at the end of a project — which is to say, rarely. A transfer that is written into the engagement, with a plan and a date, happens because the contract is not closed until it does.
What transfer actually requires
Real capability transfer is more than handing over passwords and a manual. For a government to genuinely own a platform by close-out, the engagement has to produce:
- Trained operators — the agency's own staff running the system in production before the engagement ends, not watching a demo of it.
- Open, interchangeable technology — a stack the government's team can extend, replace, or maintain without the original vendor, because there is no proprietary lock-in to trap them.
- Documentation that serves operation, not marketing — the runbooks, the architecture, the decisions, written for the people who will keep the system alive.
- A written transfer plan in the contract from day one, with the close-out defined as the moment the government's team owns it.
When those four are present, the vendor's departure is a milestone, not a cliff.
Why this is the heart of sovereignty
Sovereignty is often discussed as a question of where data sits. That matters, but it is incomplete. A government can host every byte inside its borders and still be wholly dependent — if the only people who understand the system work for a company in another country.
True sovereignty is the combination: the data inside the perimeter and the capability inside the institution. The first without the second is hosting. The second is what lets a government actually run its own mission. Owning the hardware is necessary. Owning the know-how is what makes it sovereign.
The same commitment at every scale
A small city standing up an inspection system and a national ministry standing up a customs platform have the same exposure: the day the contractor leaves. The transfer plan is what protects both. The complexity differs; the principle is identical — by close-out, the institution's own people own the platform.
If a vendor cannot put capability transfer in the contract, with a plan and a date, ask why. The answer is usually that they intend to be needed next year. A sovereign engagement is built to make itself unnecessary. Own the platform — and make sure the contract says so.
Your mandate. Our operating model.
Sovereign digital infrastructure for the agencies that run a nation's missions.