Approach

How we work, and what we refuse to do.

Both practices run on the same small set of commitments. They are the reason engagements land, and they are also the reason we turn work down.

Principles

01

Business before technology

The first conversation contains no product discussion. If we cannot describe your commercial model back to you accurately, we have not earned the right to propose anything.

02

Diagnosis is paid

Free discovery is shallow and commits neither side. A paid assessment is defensible, useful on its own, and lets us tell you honestly when there is nothing worth building.

03

Adoption is the deliverable

A system nobody uses has produced nothing, whatever shipped. We design around the existing way of working rather than asking people to change to suit the build.

04

Measured commercially

Engagements are judged on revenue, conversations, retention and time recovered — not on features delivered or activity performed.

05

Senior people, small teams

The people in the discovery conversation design and build the work. There is no handover to a delivery pool after the sale.

06

Client separation is absolute

Knowledge gained in one engagement never surfaces in another. Where practices share infrastructure, client data does not.

What we decline

Being explicit about this saves everyone time, and it is usually more informative than a list of services.

Engagements priced on hours

We price against business impact. Hourly pricing rewards the wrong behaviour on both sides.

Competing on cost

We are not the cheap option and will not become it. If price is the deciding factor, we are the wrong firm.

Guarantees before feasibility

Numbers promised before anyone has examined your market are a sales tactic, not a commitment.

Systematising judgement

Some things should stay with the partner. Part of the assessment is identifying what must not be automated.

Rebuilding what works

Most firms own more capability than they use. Replacement is usually the largest hidden cost in this work.

Work that should not exist

If the assessment concludes you should not build, we say so and stop. That is a successful assessment.

We would rather lose an implementation than deliver one that should never have been built.

Start with a conversation

Tell us how your firm originates work today and where you think it leaks. That is enough to establish whether there is anything here worth doing.