Content roadmap
The publishing system, in the open
Most companies treat their content plan as internal. Publishing ours keeps us honest about cadence, makes gaps visible, and lets readers tell us what is missing.
Where we are
The library today
16
Published articles
4
Topic clusters
24: 2 · 25: 9 · 26: 5
Published per year
6/8/2
Awareness / consideration / decision
Structure
Four clusters, each with a pillar
Every article links up to its pillar and across to at least one sibling, and every cluster links into the product page it supports. Sixteen well-connected articles are easier to rank and easier to maintain than sixty orphaned ones — though structure only helps once the individual pages are worth reading.
Procurement process
PillarThe procurement process, end to end
SupportingRequisition vs purchase order · Approval workflow design · Three-way matching · Procurement policy
Informational — buyers learning the operating model
Spend control
PillarSpend analysis guide
SupportingMaverick spend · Tail spend management · Procurement KPIs · Contract renewals
Informational shading into commercial
Buying software
PillarHow to choose procurement software
SupportingWhat is procurement software · SaaS procurement checklist · AI in procurement
Commercial — active evaluation
Suppliers and sourcing
PillarSupplier onboarding checklist
SupportingRFI vs RFQ vs RFP · AP automation basics
Informational — operational how-to
How we write
Rules that apply to every piece
An answer above the fold
Every article opens with a short, quotable answer to the question in the title. It serves readers scanning for a definition and it gives answer engines something accurate to lift.
Question-shaped headings
Headings are phrased the way people ask, not the way marketers write. Whether that improves retrieval in ChatGPT, Perplexity, or Gemini is not something anyone can measure precisely from outside — we do it because it also makes the page easier to skim.
Specific over comprehensive
A 900-word article that answers one question completely beats a 3,000-word article that covers everything vaguely. Length follows the question.
One internal link per section, minimum
Cluster to pillar, pillar to cluster, both to the relevant product page. Links are placed where the reader's next question naturally arises.
Structured data on everything
Article, BreadcrumbList, Organization, and FAQ markup where it genuinely applies — never stuffed to chase a rich result.
AI as a research and drafting aid
Used for outlining, finding gaps against competing pages, and repurposing published work into social and sales assets. Not used to generate publishable drafts unedited.
What's next
The queue
| Target | Piece | Format | Stage |
|---|---|---|---|
| Q4 2026 | Procurement maturity model | Pillar | Awareness |
| Q4 2026 | Purchase order template and worked example | Tool | Awareness |
| Q4 2026 | Multi-entity procurement: consolidating three ledgers | Article | Consideration |
| Q1 2027 | Benchmark report: mid-market approval cycle times | Report | Awareness |
| Q1 2027 | Switching from spreadsheets: a migration guide | Guide | Decision |
| Q1 2027 | Two more customer stories (manufacturing, professional services) | Story | Decision |
Missing something you would find useful? Tell us and it goes into the queue.