Skip to main content

Digital Platforms

Design and delivery of the operational systems an organisation runs on -- portals, registries, case management, dashboards and the web and mobile products built on top of them.

Problem framing

What tends to bring people here

  • Work happens in spreadsheets that nobody owns

    Critical processes run on files passed between people, with no audit trail, no validation and no single version of the truth. The cost shows up as reconciliation effort and decisions made on stale numbers.

  • An existing system cannot follow the process

    The software was bought or built for a workflow the organisation has since outgrown, so staff maintain a parallel manual process beside it and the official record drifts from reality.

  • Every new requirement means another disconnected tool

    Point solutions accumulate, each with its own login, data model and support arrangement, and nobody can answer a question that spans two of them.

  • The system works until it is used at scale

    A pilot that served a handful of offices stalls at national rollout, because concurrency, data volume and intermittent connectivity were never part of the original design.

  • Nobody can safely change it

    There are no tests, no environments and no deployment process, so a small change carries the same risk as a large one and the system slowly freezes.

What we deliver

Concretely, what you receive

  • Solution design and technical specification

    Data model, service boundaries, integration points, access control model and non-functional requirements, written so a second team could build from it.

  • Production web application

    A deployed system with role-based access, validation, audit trail, reporting and the operational tooling required to run it.

  • Mobile or offline-capable client

    Where field use demands it, a client that works with intermittent connectivity and reconciles cleanly when it returns.

  • Administrative and configuration tooling

    The screens that let the organisation manage reference data, users and workflow rules without a developer.

  • Migration from the existing system

    Extraction, cleaning, mapping and reconciliation of existing records, with a documented account of what could not be migrated and why.

  • Handover documentation and training

    Runbooks, architecture notes and the walkthroughs an internal team needs to operate and extend the system.

Typical engagements

Shapes this work takes

  • new platform

    Build a platform that does not yet exist

    Discovery through to production for a process currently run on paper, spreadsheets or a system being retired.

  • modernisation

    Replace a system that has stopped fitting

    Incremental replacement of a legacy application, keeping it running and migrating capability and data in stages rather than by big-bang cutover.

  • data solution

    Add reporting to an operational system

    Layer decision-support and reporting onto a platform that already holds the data but cannot answer questions about it.

  • architecture review

    Assess a platform before committing to it

    Independent review of an existing or proposed system against maintainability, security, integration and scale.

Engineering approach

How we go about it

Methods

  • Discovery before design

    Start with the process as actually performed, not as documented. The gap between the two is usually where the requirements are.

  • Thin slice to production early

    Take one narrow path end to end -- including deployment, access control and reporting -- before broadening. It surfaces integration and operational problems while they are still cheap.

  • Incremental replacement over big-bang cutover

    Where a system is being replaced, run old and new together and move capability across in stages, so there is always a way back.

Standards

  • Accessibility as a build requirement

    WCAG 2.2 AA treated as part of the definition of done rather than a remediation exercise, because public-facing systems are used by people with the full range of access needs.

  • Auditability by default

    Who changed what, when, and on whose authority, recorded at the point of change rather than reconstructed later.

Patterns

  • Explicit domain model

    A data model that names the organisation's own concepts, so the system can be reasoned about by the people who own the process.

  • Separation of operational and analytical paths

    Reporting reads from a shape designed for questions, so analysis cannot degrade the performance of day-to-day operations.

  • Configuration over redeployment

    Reference data, workflow rules and permissions changeable by the organisation, so routine change does not require an engineer.

Competencies applied in Digital Platforms
  1. Domain and data modelling

  2. Service and API design

  3. Role-based access control and audit

  4. Offline-first and intermittent-connectivity clients

  5. Reporting and decision-support interfaces

  6. Accessibility and multi-device delivery

  7. Data migration and reconciliation

  8. Automated testing and deployment

Platforms we deliver on

  • TypeScript
  • React
  • Next.js
  • Node.js
  • PostgreSQL

Related work

Confidential enterprise clientEnterprise

Enterprise Financial Management System

Replacing spreadsheet-driven finance with one system: budgeting, enforced approval workflows, reporting, document management, and loan tracking with automatic interest calculation.

Problem
The organisation ran its finances on manual processes and spreadsheets. Records were fragmented, reporting was late, audit trails were weak, the same data was entered more than once, approvals stalled, and there was a standing risk of losing files outright. Nothing enforced an approval sequence, and finding a specific piece of information took longer than it should have.
Outcome
Fewer manual errors
  • digital platforms
  • integration
Confidential enterprise clientEnterprise

Fleet Management System

Vehicle, trip, driver, fuel and maintenance management with GPS and telematics integration, a mobile app for field workflows, and analytics built for fleet cost and reliability decisions.

Problem
Vehicle booking and allocation were manual, availability was hard to see, maintenance tracking was weak and fuel records were missing or incomplete. Trip approvals were inefficient, drivers and vehicle assignments were hard to follow, and reporting could not answer the questions that actually drive fleet decisions: which models fail most, which cost most to maintain, which vendors are reliable.
Outcome
Visibility of the fleet
  • digital platforms
  • integration
  • data ai

Have a process that has outgrown its tools?

Tell us how the work is done today and where it breaks. We will tell you what we would build, what we would not, and roughly what it involves.