Skip to content

Methodology

How we work: a defined process, in six phases.

Building custom software without a clear process leads to surprises. These are the six phases we follow, what we do in each, what you receive and what we need from you.

Phase 01

Discovery

Goal: Understand the problem, the context and the business objectives.

What we do

  • We talk to the people who live with the problem every day.
  • We review the processes, tools and data involved.
  • We identify objectives, constraints and risks from the beginning.

What you receive

A shared view of the problem and of what is to be achieved.

What we need from you

Access to the people who know the process and to the relevant information.

Phase 02

Specification

Goal: Define what will be built and what stays out.

What we do

  • We turn needs into concrete requirements.
  • We bound the scope and prioritise it by its value to the business.
  • We agree how we will check that the result is what was expected.

What you receive

A scope and a set of requirements agreed in writing.

What we need from you

Review the scope and decide the priorities.

Phase 03

Architecture

Goal: Design the solution before building it.

What we do

  • We choose technical approaches suited to the requirements and to your environment.
  • We design the modular structure and how it connects to your systems.
  • We anticipate aspects such as security, data and future extensions.

What you receive

A design of the solution that can be reviewed and discussed before construction starts.

What we need from you

Information about existing systems and about technical or business constraints.

Phase 04

Development

Goal: Build the solution in modules.

What we do

  • We develop in independent modules that can be tested and changed separately.
  • We share progress so you can see and comment while it is being built.
  • We handle scope changes explicitly.

What you receive

Functionality you can see and comment on during construction, not only at the end.

What we need from you

Answer questions and give feedback promptly.

Phase 05

Quality Assurance

Goal: Check that the solution works before delivering it.

What we do

  • We test each module and the whole.
  • We validate the result against the agreed requirements.
  • We fix what is detected before delivery.

What you receive

A solution validated against the agreed scope.

What we need from you

Take part in the validation with real use cases.

Phase 06

Delivery

Goal: Put the solution into operation and leave it ready to evolve.

What we do

  • We deploy the solution in the agreed environment.
  • We hand over documentation on how it is built and how it is used.
  • We agree how it will be maintained and evolved afterwards.

What you receive

The solution in operation, documented, and a clear path for its evolution.

What we need from you

Confirm acceptance and the next steps.

What to expect

What you can expect as a client.

Beyond the phases, these are the conditions under which we commit to working.

  • Clarity about the scope

    You will know what is being built, what stays out and how it will be validated, before development starts.

  • Transparent communication

    Clear information about progress and decisions. Frequency and channel are agreed at the start.

  • Visibility during construction

    You will see the result as it progresses, so the course can be corrected early.

  • Managed changes

    If the scope changes, it is reviewed explicitly before continuing.

  • Documentation and continuity

    The solution is delivered documented and with a clear path for evolution.

  • Timelines and budgets

    We do not give fixed timelines or budgets before we understand the problem. We estimate them once the challenge is understood and the scope defined, that is, after the first two phases.

FAQ

Frequently asked questions about how we work.

Do I need to have the technology or the scope defined before getting in touch?

No. It is usual to start with a problem or a need. The scope and the technical decisions are defined together in the first phases.

What happens if the requirements change during the project?

It is normal for that to happen. Changes are reviewed explicitly, assessing their impact on the scope, before they are incorporated.

Can you work with the systems we already have?

Yes, integrating, extending or evolving them is part of our services. First we review their state to decide the best approach.

How is the progress of the project communicated?

We share progress regularly and show real functionality during development. Frequency and channel are agreed at the start.

Let's start by understanding your challenge.

The first phase is a conversation. Tell us what you need to solve.