The workbench file is a map, not a mantra. Wardley Mapping asks a team to lay out the components of a product or business by two dimensions: how visible each component is to users, and how mature that component is in the market. Novel pieces sit near genesis. Repeated but specialized work moves through custom-built and product stages. Eventually, some capabilities become commodity utilities.
That matters because strategy changes as a component matures. A genesis capability may deserve experimentation and proprietary learning. A custom component may justify in-house investment if it creates advantage. A productized component may be bought from a vendor. A commodity utility should usually be consumed cheaply and reliably rather than turned into an identity project.
The digest applies this lens to AI build-versus-buy decisions. Coding tools like Cursor, agent frameworks, retrieval systems, eval harnesses, model routers, observability layers, and prompt-management systems do not all sit at the same point on the map. Treating them as one category called “AI tooling” is how teams overspend in the wrong place.
A practical map starts with the user need at the top. For a software team, that might be shipping reliable features faster. Beneath that need sit capabilities: repository understanding, code generation, test generation, review, CI integration, security scanning, deployment context, incident memory, and human approval. Each component then gets placed on the maturity curve.
The exercise exposes hidden dependencies. A company may think its advantage is a custom coding agent, only to discover the real bottleneck is test reliability, permission design, or codebase architecture. It may also discover that a tool it planned to build is already becoming productized, while a workflow it ignored remains bespoke and advantage-bearing.
The map is especially useful because AI markets move quickly. A decision that was correct in January can be wrong by July if a vendor turns a custom need into a reliable product. Wardley Mapping does not remove judgment. It makes the judgment visible, debatable, and revisable. For frontier work, that is often the difference between strategy and enthusiasm wearing a hat.