Skip to content
Condictor Studio
Process / project map

Five stages. You always know what comes next.

Rather than one large leap into the unknown, we make five deliberate decisions. Each stage ends with a concrete result and your choice: continue, adjust or stop.

5 stagesvisible progressa decision after every stage
See the process in a minute

Process

01

Distillation

We organise the starting point: materials, content, data and processes. We separate what has value from what only creates noise.

02

Brief

We agree on one direction: who we build for, which problem we solve and what we deliberately leave out of this iteration.

03

Plan

We turn the direction into an executable route: architecture, data, sequence of work and milestones that can be accepted separately.

04

Delivery

We build working parts of the product and give them to you to use during the project-not just at the end.

05

Verification & iteration

We test the real production result: speed, accessibility, SEO, forms and post-launch operation. Then we fix what measurement reveals.

No fine print

How to read this process

01

A result after every stage

You do not wait for the final. Every stage leaves a document, decision or working part of the product.

02

A shared decision, not a guess

Before the next step, you see the material, share feedback and consciously decide whether to continue.

03

You can stop the project

The outputs are yours. You can stop without losing the material already created.

No fine print

Stages in detail

01

Distillation

An inventory with decisions: keep, change, merge or remove.

We organise the starting point: materials, content, data and processes. We separate what has value from what only creates noise.

What happens along the way

  • We review the existing site, documents, spreadsheets, tools and team workflow.
  • We identify assets that cannot be lost: data, ranking content, references and brand voice.
  • For migrations, we sketch redirects before a single address disappears.
What you receive
An inventory with decisions: keep, change, merge or remove.
Usually takes
3 days-2 weeks
Exit gate
Every important item has an owner and a clear decision. Nothing uncertain is hidden for later.
02

Brief

An approved brief with goal, scope, information architecture and success measures.

We agree on one direction: who we build for, which problem we solve and what we deliberately leave out of this iteration.

What happens along the way

  • We explore several directions rather than committing to the first idea.
  • We define audiences, value proposition, tone, scope and what is out of scope.
  • We agree success criteria and constraints that guide future decisions.
What you receive
An approved brief with goal, scope, information architecture and success measures.
Usually takes
1-2 weeks + your review time
Exit gate
You approve the direction before planning. Every important decision is written down, not left in meeting memory.
03

Plan

A technical plan with estimates, risks and completion criteria for every milestone.

We turn the direction into an executable route: architecture, data, sequence of work and milestones that can be accepted separately.

What happens along the way

  • We design architecture, data model and boundaries between modules.
  • We divide scope into small, verifiable pieces with contracts and dependencies.
  • We allocate parallel work in advance so contributors do not touch the same files.
What you receive
A technical plan with estimates, risks and completion criteria for every milestone.
Usually takes
A few days-5 weeks
Exit gate
We know what is built, in what order and how we will know it is ready. Only then do we start building.
04

Delivery

Tested code, a version to review and an up-to-date decision log in your repository.

We build working parts of the product and give them to you to use during the project-not just at the end.

What happens along the way

  • We deliver milestone by milestone, with regular room for your feedback.
  • AI assistants work in parallel only on separate modules and agreed contracts.
  • Authors do not approve their own code: every change gets cross-review before merge.
What you receive
Tested code, a version to review and an up-to-date decision log in your repository.
Usually takes
2-6 weeks for the first scope
Exit gate
Every milestone works on key paths and passes tests and independent review.
05

Verification & iteration

A QA report with evidence, a safe release and a backlog for the next iteration.

We test the real production result: speed, accessibility, SEO, forms and post-launch operation. Then we fix what measurement reveals.

What happens along the way

  • We measure on the production build and test accessibility, forms and redirects end to end.
  • Every finding gets evidence, priority and an owner-nothing is put on a ‘someday’ list.
  • After release we observe the project after one day, one week and one month.
What you receive
A QA report with evidence, a safe release and a backlog for the next iteration.
Usually takes
2-4 days per QA round + release
Exit gate
Results must meet the thresholds in the brief. Open blockers or a missed criterion stop publication.

We work in five stages. Each one produces a visible result and ends with a decision: proceed, adjust direction, or stop. This prevents the project from turning into an open-ended promise.

1. Discovery and distillation

We collect the available materials, systems, processes, and constraints. We separate facts from assumptions, identify gaps, and define the problem worth solving. The outcome is a shared starting point, not a slide deck.

2. Brief and scope

Together we establish the business goal, users, required data, integrations, risks, budget frame, and the first useful stage. The gate is your written acceptance of the direction.

3. Plan

We prepare the architecture, data model, milestones, estimates, and acceptance criteria. We make dependencies and decisions explicit before implementation begins.

4. Implementation

We build in small, reviewable milestones. Each has a defined outcome, tests, and an independent review. New scope returns to planning instead of silently extending the delivery.

5. Verification and launch

We verify functionality, performance, accessibility, technical SEO, security appropriate to the risk, and the production deployment. The outcome is a working, documented system with a defined support path.

What you control

At each gate you can continue, change direction, or stop with the artefacts produced so far. We do not hide uncertainty: if a smaller pilot is the sensible next step, we propose it. If a requirement cannot be confirmed, it remains an assumption until it is tested.

Start with the project brief, or contact us with a short description of the situation.

We deliver repeatably because we work as a pipeline - we don't improvise.

Fill out the brief