Mode · I · Pre-decision counsel

Before the decisions.

Independent counsel for the people whose call this is, through to the operators to shape and deliver the strategy itself.

The evidence for AI is uneven, and the practices for deploying it in complex systems are not settled. Cost structures, failure modes, and operating disciplines are still being learned in production.

The dominant pressure on consequential AI decisions today isn’t examination; it’s the hype cycle and the pace it sets. Commitments are made in good faith, at the pace asked of the people making them, often before the second-order effects can be properly examined.

Consequence & Co. is engaged for the examination that comes before sign-off: by veteran engineering leaders who have built and operated technology businesses at scale, and recognise the patterns from prior structural shifts. The work does not presume adoption is right. It tests whether the benefit is real, whether it survives the organisation’s actual complexity, and whether proceeding, narrowing, waiting, or stopping is the defensible decision.

When clients engage us before the decisions.

Typical briefs:

  • We’re being asked to approve a major AI or technology investment, and want the case behind it stress-tested before we sign off.
  • We’re forming a leadership position on AI and want to know what it could actually gain us, and where the real risks sit, before we commit to a direction.
  • We’ve been told we’re “behind on AI.” We’d like to know whether that’s true, what the actual gap is, and what’s worth doing about it.
  • We’re committing to a multi-year vendor relationship and we want the cost trajectory and lock-in implications properly modelled.
  • We have an AI strategy or major change programme on paper, and we want the assumptions checked before the board signs it off.
  • We’re considering a build vs. buy vs. adopt decision and the internal recommendations are conflicting.
  • We want the controls, safeguards, and governance defined before we proceed, not after a regulator or auditor asks the question.
  • We operate in a complex or highly regulated industry and do not accept that generic productivity claims will survive our constraints.
  • We’re piloting agentic tooling and want credible evidence before deciding whether to roll it out more broadly.

What the engagement looks like.

A defined-scope engagement, scoped to the brief. We meet the people who need to be heard, read what needs reading, examine what needs examining, model what needs modelling. The deliverable is a written assessment (findings, named risks, a clear recommendation, the reasoning behind it) supported by working sessions to make sure the people who need to act on it understand it.

Many of these engagements stand alone. Some continue: into shaping the strategy itself, into delivery through the Co when the work calls for hands rather than counsel, or into a remediation engagement if the assessment surfaces material issues with what’s already in flight. Some end with a recommendation to engage a different kind of firm entirely. All four are normal.

When the evidence supports proceeding and the engagement extends into delivery, the Co takes on the technical heavy lifting: engineering practices, guardrails, policies, and ways of working proportionate to the actual use case and its consequences.

Engagement shapes Talk to us about a pre-decision engagement