Engagement process

Nothing is built until you have approved the design.

Three meetings, each producing a document you keep. Published in full, because the most useful thing a prospective client can know is exactly what they are agreeing to.

See pricing

Before implementation

Three meetings, three documents.

01

Discovery

30–60 minutes · Our delivery lead, with you and your process owners

  • Current state: how the process runs today
  • Future state: what it needs to do instead
  • Pain points and where work is actually lost
  • Business and industry context
  • Priorities and sequencing

OutcomeA mutual NDA and a completed requirements questionnaire.

02

Fit-gap review

30–60 minutes · Our architect and delivery lead, with your decision-makers

  • Your problems walked through with the architect directly
  • Module-to-requirement mapping
  • Requirements mapped against systems you already own
  • Solution design context and constraints

OutcomeAn engagement proposal with a defined success path.

03

Design sign-off

30–60 minutes · Our architect, delivery lead and solution designer, with your team

  • Presentation of the end-to-end process flow diagram
  • Wireframes and mockups where the interface matters
  • Data migration approach, if you are moving off another system
  • Deployment plan and go-live checklist

OutcomeAn approved technical specification that implementation is built against.

After approval

From approved design to go-live.

  1. 01Solution designRequirements analysis, process flow diagrams, and the technical specification your team signs off before anyone writes code.
  2. 02Build and testingImplementation against the approved specification, with a standing development cadence and internal QA throughout.
  3. 03UATStructured user acceptance testing with training walkthroughs, tracked findings, and a change-management path for anything new.
  4. 04User trainingEnd-user manual, admin manual, and developer documentation, so the system survives staff turnover.
  5. 05Go-liveProduction deployment against a readiness checklist, test data removed, and a formal project handover.

What you keep

Twelve documents, yours at handover.

These are yours at the end of the engagement, whoever maintains the system afterwards.

Scope

What happens when scope changes.

Requirements change during delivery. That is normal, and the process accounts for it rather than pretending otherwise.

  1. 01We explain the coverageWhat the approved proposal included, and how the new requirement differs from it.
  2. 02We confirm the differenceBefore any estimate is produced, both sides agree on what is genuinely new.
  3. 03We issue a revised estimateThe additional work is quoted and approved in writing before it starts.

Work outside the approved scope is never absorbed silently and then billed at the end. If we have not quoted it and you have not approved it, we have not built it.

Book a walkthrough

See what your system could look like.

Thirty minutes, online. We will cover:

  • How your process runs today, and where time is lost
  • Example builds close to what you need
  • Which tier fits, and what it would cost

We use these details only to prepare for your walkthrough. Privacy policy