How we work together

A clear brief.
A shared way forward.

Know what you are reviewing, what happens next and what your team needs to provide. Our process connects business decisions with visible progress.

Start with a conversation
01

Discover

Get the important questions on the table.

We begin with the business goal, the people using the product and the systems already in place. For an existing website or app, we review the current journeys and content before recommending a change.

What we make clear

  • A practical first-release scope
  • User roles, integrations and dependencies
  • A list of assumptions to resolve

Your part in the process

Bring your current website, a short business brief, examples of the problem and the people who can answer operational questions.

02

Design

Make the direction tangible before the build.

We organise the pages and journeys, then develop screen designs you can review. Work through the core tasks on desktop and mobile so decisions are based on the experience customers will actually use.

What we make clear

  • Page structure or app journey map
  • Working screen designs for key tasks
  • Agreed content and feedback responsibilities

Your part in the process

Review the key journeys, consolidate feedback and confirm who approves the design. Content and product information need an owner too.

03

Develop

Build against agreed milestones.

Development follows the reviewed scope. Features, content and integrations are brought together in a staging environment, with opportunities to check progress. A new idea is assessed for cost and schedule impact before it changes the release.

What we make clear

  • Working milestone demonstrations
  • Forms, integrations and error handling
  • Testing against the agreed user journeys

Your part in the process

Provide approved content and integration access through the agreed secure channels. Review milestones and raise business-rule questions early.

04

Launch & hand over

Finish the operational work around the product.

We check the important journeys, prepare the release and confirm how your team will manage the product. Website migrations include the agreed URL mapping; app releases include the agreed store preparation. External reviews and approvals can affect release timing.

What we make clear

  • Launch and acceptance checks
  • Account, source and editing handover
  • A clear support and maintenance scope

Your part in the process

Confirm account ownership, review acceptance results and agree who will manage enquiries, content and support after launch.

A proposal you can evaluate.

The proposal should make the scope, milestones, dependencies and review stages clear. A timeline follows the actual work; it is not a blanket promise that every website or app can be delivered in the same number of days.

Hosting, licences, third-party services, content creation and ongoing support should be shown separately where they apply. If requirements change, the revised scope should explain the impact before the work proceeds.

Read our proposal and budget guide

Start with the problem you want to solve.

We’ll work through the scope and next steps together.

Discuss your project