Home / Services / Enterprise Systems
Systems · .NET · Angular · Enterprise
Enterprise Systems
Internal platforms that a company runs on
The systems nobody sees and everything depends on: back-office platforms, operations dashboards, approval workflows, reporting, and the integrations between whatever you already run. Built at the scale I have carried in banking, government and telecom.
8+ years
on systems with real users and real consequences
5+ ministries
served by one government platform I delivered
Banking core
retail Islamic banking modules in production
Handed over
documented so your team can take it on
Pricing
What a stage costs.
Discovery is fixed. Each module after it is fixed against its own written scope, invoiced per stage, so this never becomes one large irreversible commitment.
Discovery and blueprint
On requestfixed
- Current process mapped as it actually runs, not as documented
- The system's modules, data model and integration points
- Build order, with what pays back first
- A written estimate you can take to anyone
- Delivered as a document you own
Stands alone. If you take the blueprint to another team, that is a fair outcome and it has still paid for itself.
Request this ↗One module, built
On requestone-off
- A single workflow end to end: request, approval, record, report
- Roles and permissions that match how the company actually delegates
- Integrated with the systems that already hold the data
- Audit trail on every state change
- Deployed to your environment, documented for your team
The way to start. One module in production teaches more than six months of planning.
Request this ↗The full platform
On requeststaged
- Every module in the blueprint, in the order it pays back
- One data model and one login across all of them
- Operations dashboard and reporting
- Integrations with ERP, HR, finance or whatever holds the truth
- Staged delivery — each stage usable before the next begins
Priced and invoiced per stage, so it never becomes one large irreversible commitment.
Request this ↗Add-ons — buy with any package or on their own
System audit
On requestfixed
- Architecture, data model and integration review of what you run today
- Where it will break as you grow, with the evidence
- Security and access-control findings
- A prioritised list: what to fix, what to replace, what to leave alone
Useful before spending on a rewrite somebody has already decided on.
Request this ↗Care plan
On requestper month
- Changes, fixes and new reports
- Monitoring, backups and recovery drills
- A named engineer who knows the system
- Quarterly review of what to build next
Internal systems age badly without an owner. This is the owner.
Request this ↗Compare
Side by side.
Whether you are deciding what to build, building the first piece, or building all of it.
| What you get | Discovery | One module | Full platform | Audit |
|---|---|---|---|---|
| Process mapped as it really runs | Included | Included | Included | Not included |
| Costed build plan you can take anywhere | Included | Not included | Included | Not included |
| Something in production at the end | Not included | Included | Included | Not included |
| Roles, permissions and audit trail | Not included | Included | Included | Reviewed |
| Integrated with systems you already run | Not included | Included | Included | Not included |
| Operations dashboard and reporting | Not included | That module | Included | Not included |
| Staged, stop after any stage | Not included | Not included | Included | Not included |
| Review of what you run today | Not included | Not included | Not included | Included |
| Documented for your own team | Included | Included | Included | Included |
Nobody should start at the platform. Discovery then one module in production teaches more than six months of planning, and the price of both is known before you commit to anything larger.
Before we start
What your business needs in place.
Internal systems fail on organisation, not on code. These are the parts only you can supply.
A sponsor with authority
Someone senior enough to settle a disagreement between two departments. Internal systems die when nobody can decide whose process wins, and no amount of engineering fixes that.
The process as it actually runs
Including the spreadsheet somebody keeps on the side and the step everyone skips. Building the documented process rather than the real one is the classic way an internal system goes unused.
Access to the systems that hold the data
ERP, HR, finance, the old database. Read access and a test environment at minimum, and the name of whoever administers each one.
Time from the people who will use it
A few hours from two or three real users, early. Systems designed only with management input get built correctly and used reluctantly.
A decision on data residency
Where the data may physically live, and who may see it. In Saudi and Egypt this is often decided for you by the sector, and it changes the architecture — so it is settled before, not after.
Terms
How the money and the risk are split.
No retainer to start a conversation, and no invoice for work that never got delivered.
Half to start, half on delivery
Balance falls due when the work is done and handed over. Not delivered, not charged.
Fixed price, not an estimate
The number holds unless you change the scope. If I misjudged it, that is mine.
The clock starts at handover
From the day I have everything on the list, not from the day you pay.
One round of revisions included
Then hourly, quoted before anything starts. No surprise invoices.
You own everything at the end
Code, accounts, assets and credentials. Nothing is held hostage.
Proof
Delivered at the scale that breaks things.
Banking, government and telecom — where a bug has consequences beyond a refund.
Strategy 360
A flagship platform for managing strategic initiatives across government organisations, delivered in close work with more than five Saudi ministries.
iFIN
Core development on one of the leading digital retail banking suites — backend services in .NET and Oracle, for global Islamic banking clients.
Redbull Mobile KSA
Leading the team behind the digital channels and the internal operational tools that run behind them.
redbullmobile.sa ↗Development Manager
Running delivery, architecture and engineering teams on production systems at enterprise scale, today.
What you get
What a stage delivers.
Each stage ends in something in production, not a document about it.
An operations view
The real numbers, live, so decisions stop waiting on somebody exporting a spreadsheet.
Approvals that leave a trail
Who requested, who approved, when, and what changed. Because someone will eventually ask.
Reporting your finance team trusts
Reconciled against the system that holds the truth, not re-keyed from it.
Documentation your team can use
Architecture, environments and access, written for whoever maintains it after me.
What you send
The handover, in one list.
Send it in one go and the clock starts.
- The process, written or drawn, however roughly
- Who does what, and who approves what
- Sample data or real forms — even photographs of paper ones
- Access to the systems it must read from or write to
- Any compliance rules that constrain the design
- Roughly how many people will use it, and from where
How it runs
Six steps, and you see each one.
-
01
Map
Sit with the people doing the work and record the process as it really runs, including the workarounds.
-
02
Blueprint
Modules, data model, integrations and build order, written down and priced.
-
03
First module
The one that pays back fastest goes to production first, with real users on it.
-
04
Integrate
Wire it to the systems that already hold the truth, so nobody types anything twice.
-
05
Stage by stage
Each module usable before the next begins. You can stop at any stage and still have something working.
-
06
Handover
Documentation, environment access and training for whoever maintains it. Then the Care plan, or your team.
Scope
What this is not, and who it is not for.
These are quoted separately, so the price above stays a price.
- Licences for ERP, database or BI products
- Hardware and infrastructure procurement
- Business process consulting beyond what the build needs
- Data entry and historical data cleaning
- Training beyond the handover sessions
- Regulatory certification and audit sign-off
Right fit, wrong fit
Saves a call that would end in no.
A good fit
- A process runs on spreadsheets and email and has outgrown both
- Two systems hold the same data and disagree
- You need an audit trail because someone will ask
- You want it staged, not one irreversible commitment
- Arabic interfaces and RTL are a requirement, not a nice-to-have
Not a fit
- Nobody senior is willing to own the decisions
- You want a product demo rather than a build
- An off-the-shelf product would obviously do the job — I will tell you if it would
- The requirement is a certification, not a system
After launch
After handover.
An internal system without an owner degrades quietly: reports stop matching, an integration silently fails, nobody updates the dependency with the security advisory. The Care plan puts a named engineer on it who already knows the design.
Questions
The ones people actually ask.
Should we build or buy?
Buy, whenever something off the shelf fits — I will say so, and the discovery is where that comes out. Building is right when the process is genuinely yours, when integration is the hard part, or when licence cost per user outgrows the build inside two years.
Can you work with our existing team?
Yes, and it is usually the better arrangement. I take the architecture and the hard parts, your developers take the volume, and the handover happens continuously instead of at the end.
How do you price something this open-ended?
Discovery is fixed. Each module after it is fixed against its own written scope. You are never asked to commit to the whole programme up front, and you can stop after any stage with something that works.
What about our data leaving the country?
It does not have to. The architecture follows your residency rules — on-premise, a local region, or a hybrid where only what is allowed to leave leaves. Decide it before the design, not after.
Who maintains it when you are gone?
Your team, if you have one — the handover is documentation, walkthroughs and access, not a zip file. If you do not have one, the Care plan covers it until you do.
Tell me what you have, and I will tell you what it takes.
The app, the market and the deadline is enough to get a straight answer on scope, price and timing — usually the same day.