Understand the need
Output: a shared scopeWe start with something concrete: a task, a file, a journey or a recurring difficulty. We clarify the users, constraints and available access.
You know what we are building, why we are building it and what you will receive at the end.

We start with something concrete: a task, a file, a journey or a recurring difficulty. We clarify the users, constraints and available access.
The proposal defines deliverables, exclusions, timing, the total fee and any third-party services. A structure or journey is presented where the project calls for it.
Work follows the agreed scope. Representative examples are used to check the expected behaviour. One feedback cycle allows the deliverables to be refined before handover.
You receive the items in the proposal: files, access, documentation and practical guidance. Any ongoing maintenance or future changes are covered by a separate agreement.
Describe the current task and what should become easier.
A website, a tool, a file or an initial idea: any starting point is useful.
A deadline, a budget, the intended users or a technical constraint to account for.
A few lines are enough to begin. We will define the right scope together.