Domain model and workflows
Entities, states and approval rules captured from your departments, implemented as explicit workflows rather than loose status fields.
Service · Enterprise
Commission us to build the large internal systems many departments depend on: case management, operations platforms, approval workflows and staff portals. We design for complex permissions, auditability and integration with the software you already run.
SSO and SCIM provisioning
Every change written to an audit log
Integrations with retry and reconciliation
Deliverables
Entities, states and approval rules captured from your departments, implemented as explicit workflows rather than loose status fields.
Role-based and attribute-based access control covering who can view, edit and approve each record, including delegation and segregation of duties.
Single sign-on through SAML or OpenID Connect with your identity provider, plus SCIM provisioning so joiners and leavers are handled automatically.
An append-only record of who changed what and when, with before and after values, searchable by auditors.
Connectors to finance, HR, CRM and data platforms through APIs, events or file exchange, with retries, idempotency and reconciliation reports.
Early decisions
A modular monolith for most internal systems, splitting out services only where teams or scaling needs genuinely diverge.
Whether roles are enough or record-level rules based on department, region or ownership are needed, which affects every query.
Synchronous APIs, event streams or scheduled batches, chosen per integration by latency need and the other system’s capabilities.
Operational reports inside the application versus a separate warehouse for analytics, protecting transactional performance.
Which rules administrators may change without a release and which stay in code, trading flexibility against testability.
Engagement
We work with each department to document workflows, approval chains, data ownership and compliance obligations.
The domain model, access rules and integration contracts are designed and reviewed with security and data owners.
Modules are released to departments in sequence, each wired into identity and audit from its first day.
We support go-live for each department, load data from previous tools and pass operations to your IT team.
Fit
When SaaS products force you to bend a core process, a custom system can encode it faithfully.
One system with clear ownership replaces copies of data drifting apart across tools.
Regulated organisations must show precisely who did what, and when.
Alternatives
If the system centres on accounting, procurement and stock, ERP work fits better.
Open registerMulti-tenant products for external customers need SaaS architecture and billing.
Open registerBuilding on an existing Salesforce org may beat standing up a separate system.
Open registerInternal systems seldom fail on features; they fail when the wrong person sees or approves something. We design the permission model early, enforce it in one place and write tests proving each role sees only what it should.
Adding auditing after launch means some history is lost for good. We record changes at the data layer from the start, including who acted, on whose behalf and through which interface.
An integration that silently drops records is worse than one that stops. Every connector we build logs its outcome, retries transient failures and produces reconciliation reports comparing counts and totals between systems.
Launching to every department at once concentrates risk. We release modules to one group, fix what they find and then widen the rollout, keeping identity and audit foundations shared throughout.
Every enterprise system acquires a small group of people who keep it running day to day: they fix a wrongly assigned case, reopen a closed approval, bulk-update records after a reorganisation and answer “why can’t I see this?” questions. We give them a proper admin console with bulk actions, a permission explainer that shows which rule granted or denied access, and impersonation that is itself written to the audit log.
Imports deserve the same care. Departments will keep sending spreadsheets, so uploads validate every row, show a preview of what will change and reject the whole file cleanly rather than half-loading it. Long-running jobs report progress and can be retried safely, which saves your IT team from database surgery after a failed load.
FAQ
We model them explicitly, centralise checks in one policy layer and test them against a matrix of roles and records, instead of scattering conditions across screens.
Yes, through their supported APIs, middleware or file interfaces. Each integration is designed with retries and reconciliation so failures are visible and recoverable.
Your team or ours. We document the architecture, runbooks and permission model, record significant choices as decision records, and run handover sessions where your developers ship real changes under our review. If you prefer, we provide ongoing support with agreed response times, a maintained dependency upgrade schedule and a backlog of improvements requested by departments.
We index for real query patterns, paginate every list, archive closed records to cheaper tables and move heavy reporting to a read replica or warehouse rather than the transactional database. Load tests seeded with several years of projected volume run before each major release, so slow screens are found in staging instead of by staff.
Related services
Well-documented APIs that other teams use to integrate with the new system.
Open registerThe wider programme of process change around a new internal system.
Open registerHosting internal systems behind Entra ID with Microsoft 365 integration.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.