Avaro Partners

Our approach

Five steps, in this order.

We reverse the usual order: where the market builds first and hopes for use afterwards, we begin with the work and build from there.

Figuur 01Where the order diverges

The usual order

Technology
Build
Launch
Hope for use

Our order

01Understand the work
02Baseline
03Define adoption
04Build
05Measure again

The provable difference sits between these two points

The steps differ less than the order does. The difference sits in what happens before the build, and in the fact that measurement happens at both ends.
  1. Diagnose

    Understand how the work runs today and record the baseline.

    We observe the work as it runs now: which steps people take, where decisions are made, what gets left undone. At the same time we record where things stand today, because without that starting point there is no way to tell later whether anything changed.

    DeliversA picture of the work and a recorded starting point.

  2. Prioritise

    Establish where AI delivers the largest relevant improvement.

    Not every bottleneck is an AI question, and not every AI opportunity is worth the trouble. We weigh the opportunities against each other on return, feasibility and support, and pick a few. The rest we deliberately leave alone.

    DeliversA reasoned investment decision instead of a long list.

  3. Define adoption

    For us, adoption is not the closing stage but the starting point — it determines what we build.

    Before anything gets built, we establish who will use it, how the work changes as a result, and what has to be true for it to hold. If it turns out here that people will not use something, we do not build it.

    DeliversA sharp brief for the build, with the conditions attached.

  4. Implement

    Design, direct and deliver, with established engineering partners.

    We determine what has to be built, direct the build and watch the connection to existing systems. Delivery happens with established engineering partners; we remain accountable for the outcome.

    DeliversA working application, embedded in the work.

  5. Measure again

    Compare against the baseline and decide the next step.

    After delivery we measure the same points as at the start. Only then can anyone say whether the intervention made a difference, and where the next gain sits.

    DeliversA reasoned answer to the question of what it returned.

From insight to something people actually use.

An engagement should not get stuck in analysis. Within six weeks we work towards a first concrete application that is used in practice — provided scope, access and the necessary decisions allow for it.

How an engagement starts

Every engagement starts with the diagnosis. It is a bounded first product: affordable, short, and meant to remove the barrier to starting. What follows depends on what the diagnosis turns up.