How we work

Six stages, from first conversation to optional support. Each ends with something you can review, so decisions are made with full information.

Project stages

  1. Discovery

    A conversation about what you need, the people involved and the constraints.

    We ask about the problem, current tools, timing and budget range. If something isn't a good fit for us, we say so early.

    You receive: A short written summary of what we heard

  2. Scope and proposal

    A written proposal with deliverables, exclusions, price and timeline.

    Assumptions are listed so nothing is implied. Larger projects may start with a paid discovery phase to make the estimate reliable.

    You receive: Proposal and, on acceptance, an agreement and Statement of Work

  3. Design and planning

    Structure, interface designs or technical design, depending on the project.

    You review the plan before significant development starts, so changes are cheap.

    You receive: Approved designs or technical plan

  4. Development and implementation

    Building in increments, with a preview or demo you can try.

    Progress is visible throughout. Changes to scope are handled through a short written change request.

    You receive: Regular demos and a shared progress view

  5. Testing and handover

    Testing against the agreed acceptance criteria, then launch and handover.

    We test on real devices and data where possible, fix issues found and hand over code, credentials and documentation.

    You receive: Working system, documentation and a handover session

  6. Ongoing support, where agreed

    Optional updates, monitoring and improvements on a defined monthly scope.

    Support is never assumed. If you prefer to manage things yourself or with another provider, the handover makes that possible.

    You receive: A support plan with clear scope and response times

Documents you'll see

Every engagement is backed by clear paperwork, adapted to the project size.

  • Proposal

    Scope, deliverables, exclusions, price and timeline in plain language.

  • IT Services Agreement

    The framework terms: responsibilities, payment, intellectual property, confidentiality and data protection.

  • Statement of Work

    Project specifics: objectives, milestones, acceptance criteria and pricing.

  • Change request

    A short form to agree any change to scope, cost or timing before it happens.

Ready for the first conversation?

Discovery starts with a short message. No commitment until you accept a written proposal.