Working together

A clear scope.
An informed decision.

Every project starts with the job you need to get done. You receive the build, cost, responsibilities and intended timeline in writing before you commit.

The process

From the first conversation to a working system.

  1. 01

    Understand the job

    We look at the current process, the people using it and where they get stuck.

  2. 02

    Agree what to build

    You get the scope, cost, responsibilities and intended timeline in writing.

  3. 03

    Review it together

    You see the build and test the important journeys before anything is published.

  4. 04

    Launch with a clear handover

    We check the public journey and agree support, monitoring and who handles exceptions.

Before committing

A useful proposal answers these questions.

What problem are we solving?

The current process, the people using it and the outcome that makes the work worthwhile.

What is in the build?

Agreed deliverables, supported connections, what you need to provide and what is outside the scope.

What happens after launch?

Hosting, monitoring, support, supplier subscriptions and ownership of day-to-day decisions.

The commitments, in plain sight.

Project payments

50% up front and 50% on completion.

Monthly service

A six-month minimum, then rolling with 30 days’ notice.

Warranty

A 30-day warranty from go-live.

Your materials and the build

Your own materials remain yours. Once paid for, the agreed build is supplied under a perpetual licence. Reusable underlying tools have separate terms.

Supplier costs

The quote identifies applicable subscriptions, AI usage, messaging, payment fees, total payable and tax treatment.

Scope and timing

The date depends on the agreed build, content, access and any integrations. Changes to scope are agreed before additional work.

Read the full terms alongside your written agreement.

First conversation

Bring the problem. We can work out the brief.

Show me what happens now, where the work gets stuck and the software you already use. An anonymised example is often more useful than a long specification.

You can start with the free six-question roadmap, or simply describe the issue in an enquiry.

Start with the problem

What would make your working week easier?

Tell me what happens now and what you want to improve. You do not need a technical brief.