Architecture and design
System design, technology choices and the trade-offs written down before they become expensive.
Architecture · Integration · Technical leadership
Enterprise software engineering,for systems that do not get second chances.
Architecture, integration and technical leadership for government and enterprise systems — with one senior engineer accountable for the decisions.
- Architecture
- System integration
- Technical leadership
What I build
Where the engineering has to hold.
Government portals, financial systems and integration layers — work that has to keep running while the organisation depends on it.
Integration
API gateways and the integration layers that connect systems which were never designed to talk.
Technical leadership
Leading engineering on a programme: standards, reviews and accountability for what ships.
Published work
Products that are live and in use.
Every link goes to the real product or its store listing.
Government
Amanat Hail Platform
Digital government platform for Hail Municipality, Saudi Arabia. Citizen services and municipal operations.
Enterprise
Enterprise Resource Planning
Custom ERP solutions for multi-department organizations.
Enterprise
Financial Management System
Enterprise financial platform with accounting and budgeting.
Enterprise
Enterprise API Gateway
Centralized API management platform for enterprise system integration.
What's included
How enterprise engagements usually start.
Each engagement is scoped individually. Common shapes:
- Architecture reviewAn independent read of an existing system and a written set of recommendations.
- Integration buildDesigning and delivering the layer that connects your systems.
- Platform deliveryBuilding a new system end to end, with the team it needs.
- Technical leadershipLeading the engineering of a programme alongside your team.
How it works
A clear process, with you at every step.
No fixed promises before the facts are known. Timelines and cost come from the agreed scope, and you see progress at every milestone.
Discovery call
We talk through the idea, the users and the constraints. You get an honest view of whether — and how — to build it.
Scope & estimate
A written scope with milestones and an estimate based on it, so you know exactly what is being built.
Design
Flows and screens you can click through and approve before any development starts.
Build in milestones
Development in agreed stages, with working builds you can review as the work progresses.
Release
Final testing, deployment and — for apps — store listings and submission.
Support & growth
Updates, fixes and the next version, under the support arrangement we agreed.
Founder-led
You won't be passed to an account manager. You talk to the engineer who designs your product and answers for it.
Khalid AboubakrFounder & principal engineer
- I lead the architecture, the technical decisions and the quality of what ships.
- When a project needs more hands, I bring in senior specialists I trust — and I stay accountable for the result.
- Healthcare and medical education are my flagship work; government, education and commercial products sit alongside them.
Questions
Before you get in touch.
Do you work with government entities?
Yes — including the digital government platform for Amanat Hail in Saudi Arabia, written up as a case study.
Can you show confidential enterprise work?
Not the screens. Confidential systems are written up as case studies that describe the problem, the decisions and the engineering — without exposing the client's system.
Can you work alongside our in-house team or main contractor?
Yes. Many enterprise engagements are a contribution to a larger programme: an architecture review, an integration layer or technical leadership next to your team. Responsibilities and decision rights are written into the scope.
Can you meet our security, hosting and confidentiality requirements?
Tell me them at the start — where data must be hosted, on-premise or cloud, access controls, NDAs and any procurement rules — and they become part of the architecture and the scope, not an afterthought.
How much will it cost?
It depends on what the product has to do: features, user types, integrations and the systems behind it. After a discovery call you get a written scope and an estimate based on it — not a number guessed in advance.
Who owns the code and the accounts?
Ownership of the code, the store listings and the hosting accounts is agreed in writing before work starts.
Who will I actually be working with?
With me, directly. I lead the project from the first call; when specialists are needed, I bring them in and stay responsible for their work.
Start your project
Tell me about the product you want to build.
Your message comes straight to me. I'll reply personally with questions that sharpen the plan, an honest read on scope, or a clear no if I'm not the right fit.
Khalid AboubakrFounder & principal engineer