Open for enterprise and government engagements

Software that must not fail

Independent engineering for government, healthcare and enterprise systems — twelve of them, nine written up in full on this site.

Work delivered across Saudi Arabia, Egypt, the United Kingdom and the wider Gulf, for government, healthcare and enterprise. Nothing claimed on this page is something you cannot go and check.

Track record

What has actually shipped

Every figure below is countable from the case studies on this site.

12
Systems in production
Nine of them are documented as case studies on this site, with their constraints and the decisions behind them.
7
Sectors delivered in
Government, healthcare, medical education, education, media, e-commerce and enterprise.
4
Countries and regions served
Saudi Arabia, Egypt, the United Kingdom, and GCC-wide enterprise work.
10+
Years building enterprise software
Independent delivery alongside a Senior Technical Lead role at _VOIS.
47
Technical articles published
Across ten subjects, from software architecture to security engineering.

Background

A decade, and where it went

Enterprise systems since 2013, delivered independently alongside a Senior Technical Lead role at _VOIS (Vodafone Intelligent Solutions).

The salaried role, and the independent work

The salaried role is Senior Technical Lead at _VOIS (Vodafone Intelligent Solutions). Alongside it sit the twelve systems in this portfolio: two government portals in Saudi Arabia, medical education and clinic systems in the United Kingdom and across Europe, a teacher app, a news platform and an online store, and an ERP, a financial platform and an integration gateway across the Gulf. Nine of them are written up in full.

Every write-up records the same things: the sector, the region, how long it ran and how many people were on it. They range from five months to sixteen, and from solo delivery to a lead with four engineers.

Where the work has been

  • 🏛️ Government Digital Transformation

    Municipal service platforms, citizen portals, and administrative systems for Saudi government entities.

  • 🏥 Healthcare Technology

    Medical examination platforms, clinic management solutions, and patient portals serving healthcare providers.

  • ⚙️ Enterprise Operations

    Resource planning, financial management, and integration platforms for multi-department organizations.

  • 📚 Educational Platforms

    Student management systems, e-learning platforms, and educational administration tools.

Selected work

Open it, then read how it was built

Three of the twelve carry both a public address and a full write-up — open the system on one side, read the engagement and the architecture on the other.

The eMRCOG platform homepage, showing its MRCOG preparation curriculum and question bank.

EMRCOG Education Platform

Large-scale Moodle-based e-learning platform preparing doctors for the MRCOG postgraduate qualification from the Royal College of Obstetricians and Gynaecologists

Large-scale Moodle-based educational platform for MRCOG exam preparation. Serving thousands of doctors across Europe preparing for the Royal College of Obstetricians and Gynaecologists qualification.

Sector
Medical Education
Region
Europe-wide (UK-based, serving international medical professionals)
Duration
12 months initial + ongoing maintenance and feature development
Team
Lead technical architect + support engineer

The SmartFRCS candidate dashboard, showing study mode, exam history and progress statistics.

SmartFRCS Platform

Healthcare · International (UK-based certification)

Medical examination platform for Royal College of Surgeons fellowship candidates. Automated assessment and progress analytics.

Duration
12 months + ongoing development
Team
Solo developer (full-stack)
The Hail Region Municipality portal at amanathail.gov.sa, showing its Arabic homepage and e-services navigation.

Amanat Hail Platform

Government · Hail, Saudi Arabia

Digital government platform for Hail Municipality, Saudi Arabia. Citizen services and municipal operations.

Duration
14 months
Team
Lead developer + 3 engineers

How the systems are built

Built for the real world

Six positions, each one taken on a project you can read about here.

  • Where the data sits is decided first

    Public-sector and healthcare work starts with residency and audit, not with a framework. The Hail platform runs on cloud infrastructure inside Saudi Arabia and logs access for government review because that was a requirement of the brief, not a hardening pass afterwards.

  • The handover is part of the build

    Documentation and knowledge transfer are written while the system is being built, so your team can run and extend it without me. Decisions are explained in language the people who have to live with them can act on.

  • The old system is a constraint, not an obstacle

    Most of this work begins with systems nobody can switch off. The municipal platform reached its legacy data through an adapter layer with standardised interfaces, so the old system kept serving while the new one took the load.

  • Plan for the day the load is not average

    The EMRCOG platform is busiest on the days an exam board opens registration. Capacity follows that calendar in advance rather than reacting to it, because the peak was known before it arrived.

  • Build so the next change is small

    The Hail platform was split into modular services and a configurable approval engine specifically so the next department could be added without reopening the rest of the system.

  • Built for the person who is not comfortable with software

    A citizen portal is used by people with very different levels of technical confidence; a study platform by clinicians working through it in whatever fragments of time they have. Both were tested with those users and simplified until the common task was short.

Judgement

Decisions, and what they cost

Four problems these systems ran into, and what was done about each one.

  • Medical EducationEurope-wide (UK-based, serving international medical professionals)

    The constraint

    Handling massive traffic spikes during RCOG exam registration windows and mock test periods

    What was done

    Implemented auto-scaling infrastructure with predictive scaling based on exam calendars, plus aggressive caching layers

    See the full context
  • Medical EducationEurope-wide (UK-based, serving international medical professionals)

    The constraint

    Ensuring assessment integrity with anti-cheating measures for high-stakes mock examinations

    What was done

    Implemented question randomization, strict time limits, browser lockdown features, and activity monitoring

    See the full context
  • GovernmentHail, Saudi Arabia

    The constraint

    Integration with legacy municipal systems

    What was done

    Built adapter layer providing standardized interfaces to legacy data

    See the full context
  • GovernmentHail, Saudi Arabia

    The constraint

    Meeting national government security requirements

    What was done

    Security architecture aligned with NCSC guidelines and regular penetration testing

    See the full context

Working together

How I work

Five stages, with what you are holding at the end of each one.

  1. Discovery

    What exists, who uses it and what it has to comply with — before any code. On the municipal work that meant reading the systems that could not be switched off; on the citizen portal it meant sitting with residents while they tried to use it.

    You receiveA written problem statement, the real constraints, and a scope you are able to say no to.

  2. Architecture

    The decisions that are expensive to reverse get made and written down first: where the data lives, how the system is split, what the audit trail records, which parts have to keep working when one of them fails.

    You receiveAn architecture note and the key decisions behind it, in language a non-engineer can review.

  3. Delivery

    Small teams and honest reporting. Across the engagements written up here the team was anywhere between one person and a lead with four engineers, and the work ran between five and sixteen months. You are told when something slips, at the point it slips.

    You receiveWorking software you can use on a staging environment, matching the scope that was agreed.

  4. Production

    Going live is a milestone, not the end of the work. Monitoring, backups and the recovery procedure are in place and tested before launch rather than assembled during the first incident.

    You receiveA running system with monitoring, backups and a recovery path that has actually been rehearsed.

  5. Handover and support

    Documentation and training so your team can run the system, and a support arrangement for the times it still needs me. Two of these platforms have stayed under continuing development since their first release.

    You receiveDocumentation, a team that has been walked through it, and a named route to reach me.

Scope

What you actually get

Four kinds of engagement: building the system, designing the architecture, reviewing a decision somebody else has to make, or leading the team that does the work.

Custom Software Development

End-to-end development of enterprise applications.

  • Full-stack web application development
  • API design and implementation
  • Database architecture and optimization
  • Third-party integrations

System Architecture & Design

Strategic technical planning and architecture design.

  • Scalability planning
  • Microservices architecture
  • Cloud infrastructure design
  • Security architecture

Technical Consulting

Expert guidance on technology decisions.

  • Technology stack evaluation
  • Process optimization
  • Digital transformation roadmap
  • Code review and auditing

Technical Team Leadership

Hands-on technical leadership for development teams.

  • Team mentoring and coaching
  • Agile process implementation
  • Technical decision-making
  • Quality assurance standards

Writing

Written up rather than claimed

Forty-seven articles across ten subjects, from software architecture to security engineering — the reasoning behind the work, in public.

Fit

Where I help, and where I would not

Worth knowing before you write. Being told no early is cheaper for both of us.

A good fit

  • Government, healthcare or another regulated domain, where data residency and an audit trail are requirements rather than features.
  • A system that has to keep running for years and eventually be handed to your own team — not a prototype to demonstrate once.
  • Existing systems that cannot be switched off and have to be integrated with rather than replaced.
  • Work that needs the architecture settled before the code: how the system is split, where the data lives, what it has to comply with.
  • An in-house team that needs technical leadership, review and mentoring alongside the delivery.

Not the right fit

  • Marketing sites and brochureware. Design-led studios do that better than I would, and will do it faster.
  • Work where time to launch has to outrank security, auditability and the cost of maintaining it afterwards.
  • A fixed price and a fixed scope agreed before anyone has read the systems the work has to live with.
  • Engagements where documentation and handover are treated as extras to be dropped if the schedule tightens.

Next step

Tell me what must not fail

The more specific you are about the constraint, the more useful the first reply will be.

Write what the system has to do, what it has to comply with, and when it has to exist. You will get a reply within a few business days — either an honest read on the problem, or a clear no if this is not the right fit.