Value and portfolio strategy
We score competing initiatives on expected value, technical risk, dependencies and evidence quality — then turn the result into a sequence that leadership can defend when capacity or priorities shift.
Capabilities
Design the decision, the system and the path to adoption.
Gartner found that 80% of CEOs expect AI to force an operational overhaul. Most know the change is coming — what they lack is a practical route from that conviction to a system their organisation can run, trust and improve.
Our point of view
A control that arrives after the build is a tax. The same control designed in is a shortcut.
Risk tiers, evaluation sets and review paths decided during design tell a team what it may ship without asking. Decided afterwards, they become a queue. Same controls, opposite effect on delivery speed.
AI and data product delivery
We take one consequential workflow and build it to production: retrieval, agent orchestration, evaluation harness, human review path and the cost model that decides whether it should exist.
Architecture and governance
We design the data contracts, evaluation sets, logging standards and risk tiers that let a team ship a second and third system without renegotiating approval each time.
Adoption and operating models
We redesign the roles, rituals and incentives around the new system, then train the people who will own it after we leave. If adoption depends on a change-comms deck, the design is wrong.
How engagements run
Three shapes, and what each one leaves behind.
Most work starts with framing. Some framing engagements end with a recommendation not to build, which we consider a successful outcome and price accordingly.
Framing
3 to 6 weeksA named decision, a value envelope, an evidence threshold and a build-or-stop recommendation. Runs on interviews, data inspection and working sessions with the people who own the outcome.
You keep Decision brief and sequenced options
Build
3 to 6 monthsOne workflow taken to production with its evaluation harness, controls and operating path. We work inside your team rather than alongside it, and your engineers own the repository from week one.
You keep Running system and evaluation suite
Embed
Ongoing, part-timePortfolio governance, architecture review and enablement while your team takes over. Deliberately tapering — the measure of success is that the retainer becomes unnecessary.
You keep Owned capability and reusable patterns
Fees are day-rate or fixed-scope depending on the shape. We will give you a number in the first conversation rather than after a discovery phase.
Start a conversation
Where is complexity slowing a decision?
Tell us what is changing, where the difficulty sits and what a good outcome would look like. We reply within two working days.