Enterprise Software
Internal systems built for the organisation around them
We build and replace the software your operation runs on, working within the constraints that matter in an established organisation: existing systems of record, access control, audit requirements, and the fact that the current system cannot be switched off on a given Friday.
- Typical timeline
- 3 to 9 months, phased
- Migration
- Parallel running, staged cutover
- Deployment
- Your cloud or on-premise
(01)Overview
What this covers
The internal systems that run established operations are usually a mix of a core platform nobody wants to touch, several tools bought for one department, and a layer of spreadsheets holding the gaps together. It works, because people make it work. The cost shows up as duplicated data entry, reports that disagree with each other, onboarding that takes months, and changes that are quoted in quarters.
Our work here is replacement and consolidation under real constraints. We integrate with the systems of record you are keeping rather than arguing for a clean slate, model the permissions your organisation actually has rather than a simplified version, and build the audit trail that your finance, compliance, or security function will ask for before approving anything.
Migration is planned as its own body of work. Data is profiled before it is moved, the new system runs in parallel with the old one on live data until the outputs reconcile, and cutover happens in stages with a tested path back. We would rather extend a parallel-running period than put a department in a position where there is no way to retreat.
(02)Capabilities
Capabilities
Scoped against your existing landscape and the governance it operates under.
- 01
Internal platforms and portals
Operations consoles, partner and customer portals, case management, and scheduling systems, built around the work your teams do rather than around the structure of the database underneath.
- 02
Legacy replacement and migration
Data profiling, mapping, and reconciliation, with the new system running alongside the old one on live data until the outputs agree. Cutover is staged by department or region with a tested rollback path.
- 03
Integration with systems of record
Connections to ERP, CRM, finance, HR, and warehouse systems using supported interfaces. Where a system exposes nothing usable we build a documented adapter rather than writing against its database directly.
- 04
Access control and audit
Role and attribute-based permissions, single sign-on against your identity provider, delegated administration, and an append-only audit log covering who changed what, when, and from where.
- 05
Reporting and reconciliation
Reporting built on a single defined source for each figure, so numbers agree between departments. Reconciliation jobs surface discrepancies against upstream systems rather than leaving them to be found at period close.
- 06
Operational readiness
Deployment automation, environment separation, backup and restore testing, monitoring and alerting, and the documentation your internal IT function needs to accept the system into support.
(03)What you get
What you receive
A system your own IT function can accept into support, with the documentation to back it.
- The platform deployed in your cloud account or data centre, with infrastructure defined as code
- Source code in your repository, with dependencies and licences documented
- Architecture, data model, and integration documentation written for your internal engineers
- A migration record covering data mapped, transformations applied, and reconciliation results
- Role and permission matrix, audit log specification, and backup and restore procedures
- Administrator and end-user training sessions, recorded, plus a defined support period after cutover
(04)Process
How we work
Phased delivery with a reversible step at every stage. Nothing is switched off until its replacement has been reconciled against it.
- 01
1.Current state review
Two to four weeks. We document the systems in use, the data they hold, the integration surfaces available, and the processes that depend on them. You receive a written review with a target architecture and a phased plan with costs.
- 02
2.Foundations and first integration
Environments, identity integration, permission model, audit logging, and the first connection to a system of record. This phase proves the constraints are satisfied before significant functionality is built.
- 03
3.Phased build and parallel running
Functional areas are delivered in sequence, each running alongside the existing process on live data. Discrepancies are reconciled and signed off by the owning department before that area is considered complete.
- 04
4.Staged cutover and support
Cutover proceeds by department or region, each with a tested rollback path. Training is delivered to administrators and end users, then the system moves into a defined support period before transferring to your internal function.
(05)Technology
Technology
Chosen to fit your existing platform commitments and the skills of the team that will own the system.
- Application
- TypeScript
- Next.js
- Java
- Python
- Data
- PostgreSQL
- SQL Server
- Oracle
- Kafka
- Identity
- Microsoft Entra ID
- Okta
- Keycloak
- SAML and OIDC
- Platform
- AWS
- Azure
- Kubernetes
- Terraform
(06)Questions
Questions we are asked
Can you work alongside our internal IT team?
Yes, and in most engagements that produces the better result. We work to your standards for architecture review, change control, and security approval, and we plan for your team to take the system into support. Where your engineers want to be involved in the build, we pair rather than deliver in isolation.
How do you handle migration from a system we cannot switch off?
By not switching it off until the replacement has been proven against it. We profile and map the data, run the new system in parallel on live data, and reconcile the outputs until the owning department signs off. Cutover then happens in stages, each with a rollback path that has been tested rather than assumed.
Can this be deployed on-premise?
Yes. We deploy to your cloud account or your own data centre, with infrastructure defined as code either way. Where data residency or network isolation requirements apply, they are established during the current state review and shape the architecture rather than being retrofitted.
What about our security and compliance review?
We expect it and plan for it. Access control, audit logging, encryption, and data retention are addressed in the foundations phase, and we produce the architecture and data flow documentation your reviewers need. It is considerably cheaper to satisfy these requirements in the design than to retrofit them before go-live.
What does support look like after cutover?
A defined support period follows each cutover, covering defect resolution and operational questions, with response times agreed in advance. After that, organisations either take the system fully in-house with the handover documentation or keep a retainer for changes and second-line support.
Other services
Start a project
Start with a current state review
A documented review of the systems you run today, a target architecture, and a phased plan with costs you can take to an internal approval process.