Skip to content
CleanCode

How we work

We run a project in five stages. Each ends with something you can see and judge, so you decide on the next step based on results.

  1. Conversation

    We start with a short conversation about the project's goal, its users and the constraints: deadline, budget, existing systems. If you wish, we sign an NDA first.

    What you get
    An initial view of whether and how we can help, plus a list of questions to clarify.
    Your part
    About an hour for the call and whatever materials you already have.
  2. Workshop and estimate

    We shape the scope: user roles, the key paths and integrations. We split the project into stages and agree what must be in the first version.

    What you get
    A scope description, a schedule and an estimate split into stages.
    Your part
    Time from the people who know the process from the inside.
  3. Design

    We design wireframes, then a clickable prototype of the key screens. Changes at this stage take minutes, so it is the best moment for corrections.

    What you get
    A prototype to click through on desktop and phone, plus the visual design.
    Your part
    Feedback on the prototype, ideally after showing it to a few future users.
  4. Development

    We build in stages and regularly show working parts on a test environment. The code goes to a repository you can access from day one.

    What you get
    A working test version after each stage and visibility of progress.
    Your part
    Testing each version and quick decisions when questions about details come up.
  5. Launch and care

    Before release we check security, accessibility and performance. After launch we monitor the product, fix errors and plan further features.

    What you get
    The product in production, documentation and a plan for further development.
    Your part
    Sign-off before release and feedback from the first users.

The rules we keep to

  • One communication channel

    We agree at the start where we talk and who makes decisions on both sides.

  • Access to the code from day one

    The repository can belong to your organisation. You see every change.

  • Scope changes in writing

    A new idea mid-project is estimated separately before we start building it.

  • Tests before every release

    Nothing reaches users without being checked on a test environment.

Tell us about your project

Tell us what you want to build or verify. We'll come back with questions, a proposed approach and an estimate.

Tell us about your project

Free estimate · NDA on request

What happens next

  1. 1A short call
  2. 2Estimate with a schedule
  3. 3Work begins