Enterprise
Large organizations where nothing is greenfield, and a new system is judged by what it integrates with, not what it replaces.
The context
Enterprise work starts inside systems that already run the business. The finance ledger, the HR record and the identity directory are fixed points that a new platform is built to fit between. Most of the engineering is integration, migration and access control rather than new features.
What makes it hard
Conflicting systems of record
The same employee exists in the directory, the HR system and the ledger under three different keys. Which record wins is a business decision before it is an engineering one.
Cutover against a running business
A core system may expose one nightly file drop and no API at all. It cannot be switched off while its replacement is tested. Both run in parallel, and reconciling them is the real work.
Gates between finished and live
Security review, vendor onboarding and a change advisory board sit between a finished feature and a live one. A design that assumes weekly releases fails at the first quarterly window.
Users who did not choose the system
An internal platform lands on people whose job did not change when it shipped. Anything slower than the spreadsheet it replaces gets routed around, and the data goes with it.
How we help
- The first work is a map of what already exists: the systems of record, the keys they disagree on, and the integrations nobody documented.
- Integration is designed as a contract with a version and an owner, rather than a point-to-point connection one person understands.
- Migrations run with the old system still live, and reconciliation is a report that either balances or does not.
- Release planning starts from the change window the organization actually has, not the one the team would prefer.
- Runbooks, environments and access sit with the internal IT team from the first release.
- SAP, Oracle or Dynamics already holding the system of record
- Single sign-on through Active Directory or Entra ID, with Nafath where citizens sign in
- ZATCA e-invoicing clearance inside the order and billing path
- Personal Data Protection Law residency, retention and subject access rules
- National Cybersecurity Authority controls as a pre-launch review gate
- Change advisory approval and quarterly release windows
Related services
Tell us what you are building.
Send the outline and we will come back with an honest read on scope, sequence and what it takes to run it in production.