Run it yourself in four minutes. Or have us verify it in five days.

• The ranked plan — every tool with a verdict, sorted so the first phase is what pays for itself fastest
• The keeps, with the reason for each. Usually about half the stack, and the reasons are the useful part
• Costed sequencing: what to do first, second and not at all, with the payback on each
• Where the answer is infrastructure, a modelled range rather than a single number — cloud economics do not survive being flattened into one figure

It is paid, and it is credited in full against your first build — so if you go on to engage us, it cost you nothing in the end, and if you do not, you paid for five days of work and got five days of work.

Two limits on the credit, stated before you pay rather than after: it runs for 90 days from delivery, and it is one per client. An unexpiring credit is a liability with no bound on it, and ninety days is long enough to be a real option without becoming a deadline you did not ask for.

It is priced as expertise rather than as a share of the build it precedes, because reading your invoices and telling you which three of twenty tools matter is the part that is hard. We do not sell it as a place in a queue: we take three starts a month — a First Win or a build, counted the same — not because we could not take a fourth, but because every engagement is reviewed by one person and the fourth is where that attention goes thin. If the month is full we will tell you which month is not.

We also do not run slashed-price anchoring on this. It is the visual language of a discount-code site, and it invites you to conclude the real value was never the higher number.

• A mutual NDA before you send anything

  Signed first, not alongside. If we have not signed, do not send us an invoice export.

• One named recipient

  A single person receives and works on your data, named in the NDA before it is shared. Not a team inbox, not a shared drive with the door left open.

• Raw exports deleted within 30 days of delivery

  Your invoices, expense reports and app inventories are destroyed once the plan is delivered. Only the derived plan is retained.

• Used for your plan and nothing else

  Not for benchmarking, not for training anything, not to inform a pitch to anyone else. It produces your plan and then it is gone.

If any of these is ever relaxed operationally, this page, our trust page and the underlying policy change together. They are one source, rendered twice.

• Invoice exports, or a finance report of software spend for the last twelve months
• An SSO or app inventory export if you have one — this is what finds the subscriptions nobody is tracking
• Seat counts where they are not on the invoices
• Renewal dates, if you know them. They decide sequencing more often than savings do

Roughly an hour of gathering. If you cannot get the SSO export we still do the work — it just means the shadow-spend question stays open, and we will say so in the plan rather than estimating around it.