Governance · Change · Implementation · KSA
The real job is rarely what it says on paper: find the actual problem underneath the official one, build what's missing — and make sure people actually use it.
Governance & Implementation
Taught me to model systems and find the variable that actually matters. A physicist doesn't describe what they see — they ask what governs it. That habit never left.
Taught me structure, risk architecture, and how governance fails in practice. Rules are not bureaucracy — they are the operating system of organisations. When they're wrong, everything built on top of them is fragile.
The only lawyer in a holding of eight companies — construction, manufacturing, healthcare, logistics, retail. Procurement, licensing, inspections, acquisitions — usually all at once, with no team and no second opinion down the corridor.
My own consultancy since 2017, for businesses that need legal and operational cover without an in-house department. Manufacturing, construction, technology — including the legal and reporting structure of a UAE-registered entity.
Since 2025 — designing and implementing IP and data governance inside a software company, from zero documentation to a working system. It confirmed what every earlier role suggested: most IP problems are governance problems, and most governance problems are systems problems.
None of it was a detour. Each layer exposed the limits of the one before — and project delivery is where they all converge.
A software development company had no IP governance whatsoever. No chain-of-title. No asset registry. No policies. No awareness among developers that what they created had legal and commercial value. The brief was: draft IP policies.
What I found was that policies would be useless without the underlying system. The real problem wasn't legal — it was architectural and cultural. Developers didn't understand why it mattered; management saw IP as a legal formality, not as something the company actually owned and could lose. So I reframed the task and built two governance systems in parallel.
IP governance: a work-for-hire policy framework covering AI tool usage, open-source compliance, and SBOM tracking; an IP identification matrix across nine asset categories; a 16-module IP Management Center with traffic-light OSS classification, asset registry, and accounting integration; a contractor and client agreement suite built for real chain-of-title integrity; and a visual system map designed for developer onboarding, not for lawyers.
Data governance: the full regulatory package — processing policies, data protection regulation, incident management with a 24/72-hour notification structure, transfer procedures, anonymisation and destruction frameworks, and an external processor agreement built to banking-sector standards.
Knowledge base: practical guides written for how developers actually read — not for legal audiences. Throughout, the system was benchmarked against the practices of major Russian technology companies, and in several areas reached comparable levels.
* Confidential engagement, 2025 — ongoing. Client details withheld by agreement.
A holding company needed a high-value government infrastructure contract. The tender landed on a Thursday evening; the deadline was Monday, the documentation wasn't ready, and the internal consensus was that it couldn't be done.
I put the package together over the weekend, coordinated across departments, and represented the company personally at regional and federal procurement offices to execute the agreement on time.
* Confidential engagement. Identifiers withheld.
As the sole legal function for a diversified holding of eight operating entities — construction, manufacturing, healthcare, logistics, retail — I managed the full spectrum of legal, compliance, procurement, and regulatory operations simultaneously. Not sequentially. At the same time.
The practical challenge was not legal knowledge — it was architecture. How do you build a system that handles eight entities with different regulatory profiles, different operational rhythms, and different risk structures — without constant firefighting? The answer was to design internal workflows that reduced dependency on reactive legal support and gave the business faster, more independent operational decision-making capability.
Saudi Arabia is a long-term professional direction for me.
My connection with the Kingdom began personally, through genuine interest and respect. Over time, it became more than admiration. It became a serious professional orientation.
What draws me to Saudi Arabia today is the scale of practical transformation taking place across technology, institutions, services, infrastructure, and human capability — and the discipline required to turn ambition into systems that work.
This is the kind of environment I want to prepare for carefully.
My background is strongest where structure, people, technology, and adoption meet: project governance, change implementation, AI-enabled workflows, IP and digital assets governance, documentation systems, and operating processes.
I am not looking at Saudi Arabia as a place to approach casually. I am learning Arabic, strengthening my project management foundation, and building a clearer professional profile because I believe any meaningful place in another country should be earned through value, respect, lawful work, and contribution.
My goal is simple: to become useful in the right environment — especially where complex ideas need to become practical systems, and where implementation matters as much as vision.
If you are building or improving a governance, implementation, PMO, AI adoption, or digital assets process —
and my background seems relevant — feel free to reach out with the context, the organisation,
and the problem you are trying to solve.
I respond best to substantive professional enquiries with a clear role, project, or business need.