Working together / From conversation to handover

Start with the problem.
We’ll work out the approach.

Tell us what you want to accomplish, what’s already in place, and what’s getting in the way. You don’t need a finished specification to start a conversation.

  1. Understand what needs to change.

    We’ll talk about who will use the work, what success looks like, and what’s already in place. Bring any deadlines, integrations, budget considerations, or problems you’re running into.

    Starting point

    A shared project brief.

  2. Agree on a practical plan.

    We’ll put the work, deliverables, pricing, and responsibilities in a proposal. If we need to investigate an idea or existing system first, we’ll agree on that step before planning the build.

    Before we begin

    A written proposal.

  3. Review working progress.

    You’ll see progress during development and have opportunities to give feedback. We’ll keep open questions, tradeoffs, and next priorities visible as the work takes shape.

    As the work develops

    Work to review.
    Clear next steps.

  4. Launch with a clear handover.

    Before launch, we’ll review what’s ready and confirm who owns the accounts and infrastructure. We’ll hand over the documentation and agree on any ongoing help.

    Ready to run

    Launch readiness.
    Ownership and documentation.

Before work starts

Clear expectations.
On both sides.

  • Deliverables and how we’ll review them.

    The proposal describes the work and how we’ll check it. We review working progress together so decisions can be made before the handover.

  • Your inputs, access, and decisions.

    We agree on the content, system access, and decisions needed from your side, along with who can provide them. These dependencies help shape the plan.

  • Price, payment terms, and third-party costs.

    The proposal sets out the price and payment terms. Hosting, software subscriptions, and other third-party costs are discussed separately so you know what is included.

  • How we’ll handle changes to the scope.

    If the work changes, we discuss the effect on cost and timing before moving ahead. We agree on any revised scope before continuing.

  • Launch, handover, and any ongoing support.

    We agree on the launch steps, handover, and documentation the work needs. Any ongoing support or further improvements are scoped separately.

We quote against the agreed scope and approach, and discuss the effect of changes on cost and timing before moving ahead.

Start a conversation

What would you
like to change?

A rough idea or an existing system is enough to start.

Talk through your project