Stop asking what to post. Build a story inventory.

Teams invent content on a Thursday afternoon while valuable raw material has been discarded since Monday: a customer objection, an unexpected result, a founder decision, a photograph from the field, a product detail, one sentence from a review. A story inventory turns the job from invention into collection and selection.

Six shelves

Customer questions — what people ask before buying, during delivery and after the result. A repeated question is proven demand for an explanation.
Customer language — exact phrases from calls, reviews and emails, which reveal what customers notice without prompting.
Proof — results, rebookings, route clicks, leads, coverage, introductions, time saved, before and after, always with context.
Process — the choices and details that affect quality, without exposing anything confidential.
Founder beliefs — the industry assumptions you accept, reject or see differently, attached to the experience that produced them.
Field notes — observations from visiting customers, testing products, travelling, speaking, solving a real problem.

The minimum viable version is one shared document, six headings, and under every item: source, date, the exact detail, and why it might matter to a customer.

Collect before you package

One customer sentence may later become a homepage line, a LinkedIn opener, an answer to an objection in an FAQ, a question for three more customers, a proof point in a proposal, or the premise of a longer article. The inventory preserves that optionality.

A thirty-day rhythm

Week one, listen: ten customer questions and five exact phrases. Week two, inspect the work: photograph five details and explain why each affects the result. Week three, gather proof: three outcomes with their source and commercial context. Week four, form a point of view: three beliefs supported by what you collected.

What strong proof looks like

Not "nine million impressions" but "nine million impressions and 280 leads for bikes above eight thousand euros, delivered remotely with no ad spend." A commercial result, a customer context and a delivery constraint.

Put ownership close to the work

Give customer-facing colleagues, founders and delivery teams a five-minute capture habit. The person nearest the evidence should save it; a writer or strategist finds the meaning later. This also makes founder-led writing far easier, because the founder responds to a living archive instead of summoning insight on demand.

Measure whether it improves the business, not the reach: prospects repeating your language, sales calls starting further along, useful replies from ideal customers, teams reusing stories without the founder re-explaining them. The best content calendar starts behind you, in the work already done and the proof already earned.