Skip to content

How we work

A defined process from requirements to ongoing support

Our delivery process is organised around six stages and scaled to the size of each project. The aim is to build systems that operate predictably and remain maintainable after deployment.

  1. 01Initial assessment
  2. 02System definition
  3. 03Development
  4. 04Testing
  5. 05Deployment
  6. 06Maintenance
Illustrative process sequence. Stages and review points are agreed for each engagement.

Delivery stages

Stage 1

Initial assessment

Before any development begins, we review how the requirement currently works and what the system must account for.

  • Operational requirements
  • Users
  • Information sources
  • Existing systems
  • Integrations
  • Intended outputs
  • Access requirements

Stage 2

System definition

We define the workflow, data structure, business rules and acceptance criteria before development begins.

  • Workflow
  • Database structure
  • Information fields
  • Business logic
  • User permissions
  • Integration requirements
  • Technical scope

Stage 3

Development and configuration

We build against the agreed scope, with regular review points during implementation.

  • Applications
  • Databases
  • Interfaces
  • Workflow automation
  • Notifications
  • API connections
  • AI-assisted functions where appropriate

Stage 4

Testing

We test the system against normal use and against the conditions that usually cause operational failures.

  • Normal use cases
  • Incomplete information
  • Error conditions
  • Routing rules
  • Permissions
  • Integration failures
  • Notification delivery
  • Reporting

Stage 5

Deployment

We deploy the system to the agreed cloud or production environment and provide concise technical or user documentation.

  • Deployment to the agreed environment
  • Configuration of production settings
  • Access and permission setup
  • Technical or user documentation
  • Handover to the client

Stage 6

Maintenance

Where agreed, the system remains under a defined support arrangement after deployment.

  • Monitoring
  • Defect correction
  • Workflow changes
  • Updates
  • Technical support
  • Incremental improvement

Agreements

Work is governed by a written agreement

Material projects are governed by a written agreement or statement of work defining the scope, payment terms, confidentiality, intellectual-property treatment and responsibilities of each party.

Most engagements begin with a short initial assessment, so the scope and the first delivery stage can be agreed before development starts.

Describe your requirement