How we engineer it

1. Phase 1

   Discover

   We map the process as it actually runs, not as the policy says it should.

   • Interviews with the people who do the work
   • Your forms, spreadsheets and emails as evidence
   • The exceptions, and who resolves them

   You get

   A process map with its states, rules and roles, in your language

2. Phase 2

   Model

   We turn the map into a data model, permissions and integrations.

   • Records and how they connect
   • Roles and what each can see and do
   • Which systems to connect, and which way data flows

   You get

   A working prototype on the platform foundation, with your own examples

3. Phase 3

   Build in increments

   One process at a time, each one usable on its own.

   • A demo at the end of every increment
   • Your people test with real cases
   • One backlog you can see and reprioritise

   You get

   Increments accepted by your team, ready to use

4. Phase 4

   Go live

   Your data moves across and your people are ready on day one.

   • Data migrated and reconciled with you
   • Training by role, using your own records
   • A parallel run where the stakes call for one

   You get

   The process running on the platform, with support from day one

5. Phase 5

   Evolve

   The platform keeps pace as the business changes.

   • Administrators own everyday changes
   • Improvements shipped as small increments
   • New processes join the same data model

   You get

   A platform designed to evolve as your business changes

Timings depend on scope and integrations; you'll have a dated plan after discovery.