Skip to content
ES, EspañolEN, English
Tell us about your project

00Diagnosis

First we understand. Then we quote.

In one or two weeks we review your goal, what already exists and its risks. You get a document with what we found and the approach we recommend.

It is the first phase of our method and you can also hire it on its own. If you go ahead with the project, its fee is credited against the proposal.

Request a diagnosisBook a conversationSee the full method

At a glance

Duration
1–2 weeksIndicative: we set it in writing before we start.
Your time
1–2 meetingsPlus read access to what already exists.
You get
A diagnosis document
Fee
Depends on the scopeCredited against the proposal if you go ahead with the project.
01When it helps

To decide with information

Common situations, not client cases.

  • You are about to build something new and don’t know what it involves.

    You leave with the scope, the risks and an order to build in.

  • You inherited a system and nobody quite knows its state.

    You leave with an inventory of what exists, whose name it is in and what to address first.

  • You want to change suppliers without losing control.

    You leave with a list of what to recover: repository, access, domain and infrastructure.

  • You have a proposal and want a second technical opinion.

    You leave with an independent reading of the scope and of what is still undefined.

02What we review

Four questions, in writing

Each diagnosis is adjusted to your case; these are the starting areas.

Goal

  • What the system has to achieve, and for whom.
  • Which constraints apply: deadlines, budget, team, regulation.

Current state

  • What exists today: code, infrastructure, integrations and documentation.
  • Whose name the repository, domain, hosting and access are in.

Risks

  • What could fail or block the project.
  • What depends on a single person or a single supplier.

Options

  • Which paths exist and what each one involves.
  • Which one we recommend, and why.
03How it works

From the first email to the document

  1. 01

    We agree the scope

    You tell us the context and we send in writing what we will review, how long it takes and the fee.

    YouYou accept the scope.

  2. 02

    We talk

    One or two meetings with the people who know the problem and the system.

    YouYou give us read access to what exists.

  3. 03

    We review

    We analyse what exists and weigh the options. When something is unclear, we ask.

    YouYou answer specific questions.

  4. 04

    We hand over the document

    We go through it with you, point by point, and answer your questions.

    YouYou decide the next step.

04What you get

A document that is useful even if you don’t continue with us

Written for both leadership and the technical team. Dated, with its sources and with what is still to be confirmed.

Diagnosis document

Version 1 · delivery date

  1. 01Summary for leadershipWhat we found and what we recommend, on one page.
  2. 02Problem mapGoal, constraints and who is involved.
  3. 03InventoryWhat exists and whose name it is in, if something is already built.
  4. 04RisksRanked by impact, with what to address first.
  5. 05Options and recommendationWhich paths exist, what each one involves and which one we suggest.
  6. 06Next stepWhat a proposal would need, if you want one.
Structure of the document. The content depends on each case.
05Afterwards

You decide what comes next

You continue with us

We send a proposal with scope, exclusions, milestones and cost. The diagnosis fee is credited.

What a proposal looks like

Your team runs it

You keep the document to use with your team or another supplier.

You decide to wait

If what we find says it isn’t worth building now, that is a result too. The document is there when you pick it up again.

06Questions

About the diagnosis

Proposed answers, pending approval.

  • It depends on the scope. We tell you in writing before we start and, if you go ahead with the project, it is credited against the proposal.

  • Yes. Then the diagnosis focuses on the goal, the constraints and the options to build it.

  • One or two meetings with the people who know the problem, and read access to what already exists. We don’t ask for admin passwords for a diagnosis.

  • Yes. We can sign it before we receive any information.

07Next step

Shall we start by understanding the problem?

Request a diagnosis
Book a call

Online booking is not available yet.

What happens next

We reply with questions about the context and, once it is clear, with the scope and fee of the diagnosis in writing.