Proof before proposal

Buying strategy has always worked in a strange order. You describe a problem. A firm sends a proposal describing how it would think about the problem. You agree a fee, often for weeks of work. Only then do you see the thinking, and by that point you have already paid for most of it.

The proposal is a promise about work that does not exist yet. It is judged on the firm's name, the team's CVs and how well the slides describe a method. None of that tells you whether the work will be right for your decision.

The firm is not being dishonest. Until recently it had no practical way to show its work before you bought it. That changes when the heavy lifting of research, modelling and drafting takes days rather than weeks. Real work can come first, and the proposal can come after.

We would rather reverse the order. Solve one real problem in front of you, then talk about the next. Proof before proposal.

The way we do this is the 72-Hour Strategy Bootcamp. It takes one problem your team would scope in weeks and works it to a decision memo your leadership signs, with a fixed scope and a fixed fee.1Show source for note 1 You see the Strategy Twin being built, the evidence ledger filling up, the options being red-teamed and the gates being signed. You leave with a working strategy and a starter Twin.

If you continue, the Bootcamp fee is credited to an Engine Sprint. If you do not, you have a signed decision on a real problem and a clear view of how we work. Either way, the thinking came before the commitment.

For teams not ready to commit even that far, the Strategy Readiness Scan is free and takes 30 to 60 minutes.2Show source for note 2 It gives an AI diagnostic and one insight you did not have. It is a small proof, but it is proof, not a sales form.

We say strategy1 turns weeks of strategy work into days. That is a claim, and claims about speed are cheap. “AI is fast” is easy to say. We would rather show it, which means measuring it in a way a sceptical buyer can check.

So we publish a number with a method behind it. The Compression Index is a specialist's baseline time divided by strategy1's time for the same deliverable.3Show source for note 3 An index of 5 means we took a fifth of the time the specialist estimated. That is an illustration of the arithmetic, not a target and not a result.

The method is where the honesty lives:

• The baseline is written first. An independent specialist estimates the same scope in writing before we start. No baseline, no index.
• Our time is all our time. Agent runs, strategist work, human review and Domain Fellow sign-off all count.
• Like for like. If the specialist's estimate covered more than we delivered, we cut the baseline to match, or we do not publish an index.
• Waiting time is treated the same. Time spent waiting for the client is excluded on both sides, or on neither.
• Outliers stay in. We report the slow cases as well as the fast ones, per engagement first and then as medians per engine and per quarter.

Each index is published with its baseline document, anonymised, and the acceptance record. The point is that someone who does not trust us can still check the arithmetic.

A method is defined as much by what it refuses as by what it counts. We will not show a target dressed as a result. We will not show an average across work nobody can inspect. And we will not show a case count beyond what is published.4Show source for note 4

That has a cost, and we accept it. No case is published yet: a case goes live only with its baseline and the client's written permission. A case is counted only when four things exist: a written baseline from an independent specialist, dated before work started; a deliverable the client or the specialist accepted; our time record for the same scope; and the client's written permission to publish, with an anonymisation pass reviewed by a Strategy Partner. Internal demos, estimates we wrote ourselves and work the client has not accepted do not count.

Until a case clears those steps, it stays off our site. We would rather launch with a published method and no figures than with figures that cannot carry the weight a buyer will put on them.

An index measures time, not quality. A fast wrong answer is worse than a slow right one, because it arrives with more confidence. So every published case will also show who validated the output, the red-team findings and what the work could not do.

Scope matters too. Our deliverable may be pre-feasibility where a specialist would deliver detailed design, and we state the scope on every case. A blueprint is not bankable engineering.5Show source for note 5 Yield simulation, grid studies and protection design still need licensed engineers. Saying so is part of the proof, not a disclaimer at the bottom of it.

The same discipline sits inside every deliverable. Each key figure carries a confidence grade: A, B or C.6Show source for note 6 Every strategy ships with the conditions under which it fails. A buyer should be able to check the thinking, not only admire the speed.

The simplest version of all this is a challenge. Bring a problem your team scoped in weeks. Watch us solve it live.

If the work holds, you will have seen the evidence, the gates and the signatures on your own decision, which is a better basis for the next step than any proposal we could write. If it does not hold, you will know quickly, and you will know why. That is what proof before proposal means: you judge the work, not the promise of it.