What this is and how it's edited

The martech cookbook is a field reference for working martech use cases, organized by outcome rather than by tool. It lives on the web, recipe by recipe. Each recipe names the problem, the data and roles required, the orchestration patterns underneath, and the failure modes from the field.

The seven content fields per recipe (problem, outcome, ingredients, equipment, staff, technique, gotcha) are free to read at Tier 0. They are the whole recipe, written to be used. When a team wants to know what a recipe means for its own stack, the martech workshop is one session that puts that stack on the table and ends with one next move.

Who edits this

The cookbook is edited by Matthew Niederberger, who writes martech therapy. The editorial method is pattern-first: every recipe is composed from named patterns drawn from the pattern list, which is the structural taxonomy beneath the recipes. Patterns are validated when they appear in three or more recipes that survive audit. Until then, they sit in provisional or under-observation status. The status log lives at the top of the pattern list.

Where this sits

The cookbook is a martech therapy property. martech therapy is the publication. the martech workshop is the discovery engagement. martech stack builder is where you map your own stack. The cookbook sits between them as the reference layer, and one account works across all of them.

Licensing

Tier 0 content is published under CC BY-NC-SA 4.0. Attribution required, non-commercial only, derivative works share-alike.

Corrections and contributions

If a recipe lands wrong against your environment, the feedback prompt at the bottom of each recipe is the fastest path to the editor. Recipes get refined; patterns get audited; the status log records what changed.