Skip to main content

Our Process

A Clear Process. From First Conversation to Final Delivery.

We approach projects through structured planning, thoughtful design, careful development, and clear communication at every important stage.

Explore the Process
Illustrative project plan. Stages adapt to each project.

Project Journey

Know What Happens at Every Stage.

Six stages, each with a clear purpose and a clear part for you. Not every project uses every stage in the same way.

  1. What happens
    We learn about the business problem, your goals, your users, and the initial requirements.
    Your part
    Share context, priorities, and any existing material.
    Typical outcome
    A shared understanding of the problem and what success looks like.

    Every project starts here. For a small project this can be one focused conversation.

Working Together

You Stay Informed at the Important Moments.

How often we meet and which tools we use are agreed with each client. These are the moments that always involve you.

Requirements & decisions
You help clarify needs and priorities, and make the key decisions.
Reviews & feedback
Designs and deliverables are reviewed at agreed milestones.
Changes & scope
New requests are discussed and assessed before the agreed work expands.
Delivery & handoff
You receive the deliverables, documentation, or access set out in the agreement.

Quality

Careful Work Doesn't End When the Interface Looks Finished.

Before delivery, the work is checked in the ways that suit the project. Which checks apply depends on what is being built.

Careful checks reduce problems; they cannot promise software with no defects.

Before delivery

  • Functional testingAll software
  • Responsive checksWebsites and apps
  • Accessibility considerationsAll interfaces
  • Code reviewWhere applicable
  • Integration checksConnected systems
  • Deployment or handoff preparationEvery project

Expectations

Clarity Before Work Begins.

Ownership, revisions, support, timelines, and commercial terms are set in each project's written agreement.

How is the project scope agreed?

Through a short discovery followed by a written proposal that sets out deliverables, responsibilities, and assumptions. Work starts once both sides agree it.

How are revisions handled?

Reviews happen at agreed points. The number of revision rounds is set in each agreement rather than being open-ended.

What happens when requirements change?

Changes are discussed and assessed first. If they affect scope, time, or cost, that is agreed in writing before the work changes.

How is progress reviewed?

At the milestones set in the plan, where you can see and comment on real work rather than status reports alone.

Who owns the final work?

Ownership of code, designs, and other deliverables is set out in the agreement for each project.

Is ongoing support available?

Support and maintenance can be arranged separately. What is included depends on the agreement.

What affects the timeline?

Mainly scope, the number of integrations, content readiness, and how quickly decisions and feedback can be given.

Have a Project in Mind? Let's Talk Through It.

Tell us what you are planning. We will explain how the stages would apply to your project.

Explore Our Services