External website; opens in a new tab.

How the work happens

A useful solution starts with listening.

Tell us what you need to achieve. We’ll compare sensible options, explain the work and agree a clear scope before you commit.

Build philosophy

Existing first. Bespoke last.

  1. Use

    Choose a proven existing product when it meets the need.

  2. Configure and integrate

    Make established tools work together before replacing them.

  3. Automate

    Remove stable repetitive work with controls and a fallback.

  4. Extend or build

    Build custom software only when the remaining gap justifies its ownership and operating cost.

Project sequence

Clear decisions at every stage.

  1. Discovery

    Define the outcome, users, constraints, current state and who can approve decisions.

  2. Recommendation

    Compare sensible routes and make limits, dependencies and ownership visible.

  3. Scope

    Agree inclusions, exclusions, acceptance, access and change control before delivery.

  4. Build or configure

    Work in reviewable stages with the smallest practical privilege and data exposure.

  5. Validate

    Test the agreed result, failure handling and handover evidence.

  6. Hand over

    Transfer knowledge, document assets and remove or retain access only as agreed.

Written boundaries

We agree what’s included, what isn’t, and what “done” looks like before work starts.

Approved decisions

Access and important decisions require a customer who is authorised to approve them.

Portable outcome

The result includes the ownership, documentation and exit evidence appropriate to its level.

Ownership and handover

Understand what stays customer-owned, how delegation works and what an exit pack should contain.

Read the ownership model →

Next step

A good first conversation should make the decision clearer.

Tell us what you are trying to change and what is getting in the way. We will help identify the next useful step.

A useful agreement, not hidden assumptions

We agree scope, revisions, customer inputs, the total price and acceptance before work. AI assistance and protected-data restrictions belong visibly in the project agreement. Engineering checks, delivery permission and customer contractual acceptance remain separate.

How we quote · Service documents · Practical handover guide