Talk about your next project
Rohirrim executive brief

The lesson

Use third-party data to show a gap, then argue that the cause is different from what the reader assumes and name each cause in its own heading.

The move

The essay opens with a pilot the reader will recognize, then cites The Hackett Group: 49% of procurement teams piloting generative AI and just 4% at production scale. It states its claim directly: "That is not really an AI problem. It's an architecture and readiness problem." After "How Pilots Actually Die," three sections follow, "Failure Mode #1: The Tool Was Never Built for the Workflow," "Failure Mode #2: The Data Environment Can't Carry the Weight" and "Failure Mode #3: Results You Can't Defend When It Counts." It closes with "What the Teams That Scale Do Differently" and "The Other 96%," which brings in the product and a demo offer.

Why it works

  • Our readOpening with a stalled pilot and a renewal date nobody wants to discuss lets the reader see their own situation before any claim appears.
  • Our readCiting outside studies such as Hackett and the ProcureCon CPO Report backs the gap with sources other than the brand, so the argument is harder to dismiss as a sales pitch.
  • Our readNumbered failure-mode headings let a skimmer collect the whole diagnosis, and a reader can disagree with each cause separately.

What not to copy

Don't copy the procurement statistics, the AMAC example or the Sections L and M proposal details, which belong to Rohirrim's market. Keep the order of the piece: a recognizable failure, a sourced gap, a restated cause, numbered failure modes, then what the winners do.

More from Rohirrim

More executive briefs

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.