Discovery and scoping

Know what you are investing in before the build begins.

We turn the important unknowns into decisions: who the software serves, what it needs to do, how it fits the business and what the first useful release should include.

What the work includes

What the work includes

Understand the current work

Map the critical workflows, users, documents and systems. Identify exceptions and constraints with the people who handle them.

Test the uncertain parts

Use prototypes, technical checks or data samples where they answer a material question. Choose the method around the uncertainty.

Define the delivery basis

Document the proposed scope, priorities, acceptance criteria, dependencies and assumptions behind the estimate.

What you take away

A shared picture of the problem

The critical workflows, users, dependencies and constraints we have reviewed.

A recommendation

The proposed approach, options considered and the trade-offs behind the recommendation.

A basis for delivery

A prioritized scope, acceptance criteria and assumptions for estimating the next stage. The depth of each output is agreed before the engagement starts.

Working together

Expect a recommendation. And a team that follows through.

We do the homework

We do the homework

We review your existing software, documents and workflows before asking you to explain everything again.

We make the recommendation

We make the recommendation

We bring options, trade-offs and a proposed way forward. You decide the business priorities with the context to judge them.

Testing is part of our job

Testing is part of our job

Our team checks the implementation against the agreed rules and critical scenarios. Your team validates that it fits the business.

We plan for actual use

We plan for actual use

Migration, access, training, rollout and ongoing ownership belong in the plan from the beginning.

Questions before we start

Can we bring an existing plan or system?

Yes. Share the context you already have. We review it and use the important gaps to shape the next conversation.

How are scope and price agreed?

We define the work, dependencies, responsibilities and acceptance criteria before committing to a delivery scope. Where material unknowns remain, we recommend the next step to investigate them.

Bring the problem. Let’s work out the next step.

An idea, a plan, or software that needs to change — tell us where you are and what you want to achieve.

Let’s talk