Skip to content

How a project with us works

Seven stages from first conversation to support. Every stage ends with something you can review, and nothing starts without a written scope.

The seven stages

  1. 01

    Discover

    We listen: your business, your users and what success looks like.

  2. 02

    Scope

    We write down what will be built, what will not, and how we will check it.

  3. 03

    Design

    Layouts and flows you can review before any code is written.

  4. 04

    Build

    Working software in reviewable steps, not a big reveal at the end.

  5. 05

    QA

    Testing on real devices and browsers, accessibility and speed checks.

  6. 06

    Launch

    A planned release with a checklist, redirects and monitoring in place.

  7. 07

    Support

    Fixes, updates and improvements after launch, agreed in writing.

Timelines, payments and ownership

These depend on the project, so they are agreed in writing in your proposal before any work starts.

  • Timelines

    The proposal sets a timeline for each stage, based on the scope and on how quickly feedback and content can be provided.

  • Payments

    The proposal states how payment is arranged for your project, so you know what is due and when.

  • Ownership and handover

    The proposal states what you own and what is handed over when the work is complete.

How we communicate

We aim to reply to every enquiry within one business day, subject to feasibility. How we communicate during a project is agreed in your proposal; email, phone and WhatsApp are all available.

Confidentiality: if you need confidentiality terms before sharing details, mention it in your first message and we will discuss it.

Questions about the process

Do I need to know what I want before I contact you?
No. A short description of the problem is enough. The first stages exist to turn that into a clear written scope.
Will I see the work before it is finished?
Yes. We build in reviewable steps, so you see working software along the way and can steer it.
Can I change my mind during the project?
Changes are normal. We agree how they are handled in the written scope, so a change never comes as a surprise.

Start with a conversation

Start a project