Analysis and scope
We gather goals, workflows, users and technical constraints. We define priorities, missing information and expected results, clearly separating the initial scope from later work.

A good digital project makes its choices explicit. We analyse the context, define the scope, test assumptions and build in stages, with clear results and responsibilities.
Many projects start with a feature request and only discover constraints during development. An external system does not provide the expected data, a process has exceptions or content is not yet available. Bringing this information into the analysis phase allows us to make a more realistic proposal.
Our method adapts to the project: a website, a web app and a migration need different checks. The common principle is to make goals, dependencies, acceptance criteria and decisions visible. We use the stages needed to reduce uncertainty, without adding steps for their own sake.
Focused approaches to organising information, training and technology decisions.
Each stage produces information or tools that help the next one.
We gather goals, workflows, users and technical constraints. We define priorities, missing information and expected results, clearly separating the initial scope from later work.
We design the structure, interfaces and data model. Where useful, a prototype or technical experiment tests a risky step before development expands.
We build the agreed features and connections to external systems. Checks and reviews are chosen according to the complexity and impact of the changes.
We check the main user journeys, error handling and operating conditions. We prepare the release with everyone involved and plan any migrations, training and rollback procedures.
Real use brings new information. We organise fixes, maintenance and new features around shared priorities and defined support agreements.
A useful estimate explains what it covers and the assumptions behind it. The availability of data, content, system access and user involvement affects the schedule just as much as development.
If a new need emerges during the work, we discuss its impact and priority before including it. This keeps the project manageable and helps decide what to deliver, postpone or rethink.
Our method, step by step ↗Answers to help you decide whether this is the right direction for your project.
It depends on the complexity of the process and the information available. A focused request may take a few discussions; a system with many integrations needs deeper checks. We agree on activities and outputs before starting.
Yes, where dependencies allow it. We define a usable first scope and separate later developments. Some activities, such as a migration, require coordinated preparation.
We assess their effect on functionality, timing and costs and agree on priorities. Documenting changes prevents the project from shifting without an informed decision.
Your goal, an example of the current process, the tools you use and approximate deadlines. If you already have a specification or workflow map, let us know so we can agree on an appropriate way to share it.
Describe the result you want to achieve. Together, we can establish requirements, priorities and next steps.
Let’s define the project ↗