Substantial versus Imitative Engagements

Imagine two proposals arriving on the same desk. Both carry the same price, both name the same team, and both use confident language about delivering value for a customer's AI work. Read quickly, they seem interchangeable. Yet one may leave the customer with something real, while the other leaves a stack of slides. Before deciding which engagement deserves trust, you need a way to look past the proposal's wording and see what the work actually produces.

The diagnostic for this purpose is called the document-versus-code test. Its job is to show you what an engagement delivers, not how it describes itself. This article walks through the single question the test asks, how to apply it, and what separates the two possible answers.

Notice that the test asks one question, and it is about one thing: the primary artifact. The word primary matters. Most engagements produce several outputs along the way, such as notes, meeting summaries, and drafts. The test does not ask about those side products. It looks at the thing the engagement was fundamentally built to deliver. Find that one artifact, then classify it as either a document or a deployment. Everything else in the engagement is supporting material for that main output.

Because the test focuses on the primary artifact rather than on the sales pitch, it cuts through presentation. A proposal can describe a deployment in impressive detail while the work it actually delivers is a set of planning documents. The artifact is what the customer is left holding at the end, so it is the right thing to inspect.

The test also sets aside features that often seem important. The price, the staffing, and the wording of the proposal do not settle the question. The source specifically identifies these as features that can match across both kinds of engagement, which is why the test looks at the delivered artifact instead.

The test works because every engagement has a primary artifact, and that artifact falls into one of two categories. The engagement is the container, the primary artifact is what it delivers, and the artifact is either a document or a deployment. The classification then tells you whether the engagement has substance. An engagement whose primary artifact is a deployment is substantial. An engagement whose primary artifact is a document lacks substance, and it sits on the imitative side of the split that gives this article its title.

Read the diagram from top to bottom. You begin with the whole engagement, narrow it to the single primary artifact, and then ask the one classifying question. The answer routes the engagement to one of two outcomes. Notice that the path never asks how large the engagement was, how senior its staff were, or how expensive it was. Those features can be identical for both outcomes.

The test becomes clearer when you trace an engagement forward through time. Take the same starting point: two firms hired to help a logistics company use AI to route its delivery requests. Watch what each firm leaves behind and what is still usable once the consulting period ends.

A deployment is the primary artifact of an engagement that has substance. The source describes it through three characteristics that appear together. Each is developed below, and the final one, durability, is the practical test of substance.

A document is the primary artifact of an engagement that lacks substance. The source gives examples: a slide deck, an architecture diagram, a roadmap, and a strategy paper. Each of these is a non-executable output. Each describes something without executing it.

Documents are not worthless in themselves. The concern is narrower. A document, by itself, does not carry substance, and it is typically filed away after some time. Once that happens, the engagement has produced nothing the customer can operate. The distinction is about what remains usable, not about whether the writing was careful or the thinking was sound.

Read the diagram column by column. The left column holds the forms a document commonly takes, all of which describe something without executing it. The right column lists the conditions that a deployment satisfies. The diagram summarizes the source's categories, so use it as a quick reference rather than a full substitute for the reasoning above.