There is a simple test for any strategy, assessment, or roadmap deliverable:

Could a different firm execute this without the firm that wrote it?

Most cannot, and usually not by accident.

How deliverables become non-portable

Rarely through an explicit clause. Through omissions that each look reasonable:

  • Recommendations stated at a level of generality that requires the author to interpret them
  • Findings without the evidence trail that produced them
  • Metric definitions described in prose but never specified — no grain, no source field, no exclusions
  • Effort estimates without the assumptions behind them, so nobody else can re-estimate
  • Diagrams delivered as images rather than editable source
  • A roadmap of workstreams with no acceptance criteria for any of them

Each omission is defensible individually. Together they mean the document is a prompt for a conversation with its author, not a specification anybody could build from.

What portable actually requires

Definitions precise enough to implement. For each metric: business definition, grain, source system and field, calculation including exclusions, and a proposed owner. If a competent engineer cannot build it from the document without asking a question, it is not specified.

The evidence, not just the conclusion. What was examined, what was found, what could not be determined and why. A conclusion without its evidence cannot be re-derived or challenged.

Assumptions stated separately from findings. So that when an assumption proves wrong, the affected conclusions can be identified rather than the whole document losing credibility.

Editable source for everything. Diagrams, models, workbooks. An image of a data model is a picture of a specification.

Acceptance criteria for the recommended next step. Objective and testable. Without them, "done" is a negotiation.

Why a supplier would offer this

The obvious objection: portability makes it easier for the client to leave.

Yes. And it changes what the supplier is competing on. A firm whose position depends on being difficult to replace has an incentive to keep the client dependent rather than capable — and that incentive shows up in a hundred small decisions about what to document and what to keep in someone's head.

A firm that hands over a genuinely portable specification is betting on being the best option for the next phase rather than the only one. That is a harder position to hold and a better one to buy from.

What to ask before signing

"At the end of this, could we take the output to another firm, or to our own team, and have them build it without you?"

The answer, and how comfortable the answer is, tells you most of what you need to know.

Practical check

Before accepting the final deliverable, give one section to a competent person who was not involved and ask them to restate the requirement, evidence, assumptions, and acceptance test. If they need the original author to translate it, the specification is not portable yet.

Every 360° Enterprise Intelligence Blueprint is written to be portable — it is a specification the client owns, not a proposal they are locked into.