Skip to main content
Delivery

Start with a priority. Build the common foundation.

A phased delivery model covering configuration, integration, data migration, testing, training and controlled rollout.

A delivery project with its phases, owners, deadlines and documents
Delivery pathway

Six controlled phases

Each phase ends with something the city can review: a decision, a configured service or documented evidence.

1

Discover

Services, users, data, systems and the obligations each one carries.

2

Design

Target journeys, the entity model and who is responsible for what.

3

Configure

Interfaces, workflows, rules and document templates.

4

Integrate

Identity, registers, payments and the legacy systems already in place.

5

Pilot

Data migration, testing, training and acceptance on a real service.

6

Operate

Rollout, support, measurement and extension to the next service.

Shared responsibility

What the city provides, what the delivery team produces

A delivery only holds its schedule when both sides know what they owe. These are the inputs and the outputs, named at the start.

01

From the city

Service owners, the current procedures, forms and templates in use, integration owners, sample data and the staff who will run the pilot.

02

From the delivery team

A solution blueprint, configured workflows, integration mappings, a migration plan, test evidence and training materials.

03

Reviewed together

Every phase closes on a document or a working service the city has seen, not on a status report.

Delivery principle

Configuration over fragmentation

Visual editors for data, interfaces, workflows and rules let the implementation team refine a service alongside the people who run it, while the platform core stays standard.

01

Business users

Describe the procedure, the deadlines and the documents they already work with.

02

Implementation team

Configures entities, forms, workflows and rules in the visual editors.

03

Platform core

Stays standard, upgradeable and shared across every configured service.

Start narrow

One service, mapped end to end, before you commit.

Discovery workshop · Current procedures · Systems to connect · A realistic path to pilot

Book a Demo

Plan a discovery workshop

We take one municipal priority, map the journey, name the systems it must connect and set out what a pilot would take.