Skip to content

01 / Case Study

01Cowork Document Engine

Brief → strategy → assets → deliverable. On-brand, every time.

Stop asking an LLM to “make me a deck.” Run intent through a pipeline; let the templates handle form.

A multi-stage Claude Cowork pipeline that turns raw requirements into briefs, POVs, decks, and reports — each rendered onto pre-built branded templates so output stays consistent without sacrificing strategic depth.

Problem

Generic AI output kills strategic deliverables.

Senior marketing deliverables — briefs, POVs, decks, executive reports — require strategic thinking, brand consistency, and a defensible point of view. Asking an LLM to “make me a deck” produces whatever it dreams up: off-brand, off-strategy, and impossible to ship to a client.

The real cost isn’t the LLM — it’s the senior strategist’s time spent fixing AI output to make it presentable.

Strategic Approach

Separate intent from form.

Intent is captured upfront — in a brief, in a strategy session — using skills, instructions, and data files that define what we’re trying to accomplish. Form is fixed in advance via pre-built branded templates that live in the same folder structure.

The output isn’t an LLM hallucinating a deck. It’s a pre-strategized payload rendered onto a template. That’s defensible work product.

How It Works

A four-stage pipeline.

Inputs (requirements, source documents) enter Claude Cowork. Stage one builds the brief. Stage two runs a strategy session against the brief. Stage three generates the supporting assets the deliverable needs. Stage four renders everything onto the branded template — deck, POV, brief, or report.

I use this for briefs, POVs, deliverable documents, and decks.

Demo

See it in motion.

Simulated, zero-token — feels live, costs nothing, can’t be abused.

Loading demo…

Outcomes

What it changed.

  • Deliverables land on a pre-built branded template stored in the same folder structure, so briefs, POVs, reports and decks come out consistent and on-brand by construction rather than by review.
  • Separating intent — the skills, instructions and data files that define what I’m trying to accomplish — from form means every output follows a deliberate brief → strategy → assets → deliverable flow instead of whatever a single prompt dreams up.
  • It carries real work product, not demos: briefs, POVs, deliverable documents and decks.