Content a committee uses: one asset per role and stage

In a sale that takes months, B2B content marketing has one job: help each member of the buying committee do their part of the decision. A company buys only when several people say yes, and each of them needs something different to say it.

So the test of a piece of content isn't how many people saw it. It's whether a buyer used it in a real decision: forwarded it to a colleague, quoted it in a meeting, stopped asking a question because the answer was already on the page.

At Veloria, seven people must agree before dispatchers get English lessons. Ten generic blog posts a month ("Why English matters") may bring traffic, but none of those seven will decide anything with them. Views, downloads and search rankings are side effects. They can all grow while no deal moves.

In a committee sale you rarely talk to everyone. Usually one person inside the client, the champion, carries your case to the others. At Veloria that's Pavlo from HR and learning. He doesn't read blogs; he needs material he can forward without explaining it again.

That changes how you write. A forwardable piece:

• answers one colleague's question on its own, without a call to explain it;
• is short enough to read between meetings (one page beats a long guide);
• uses the reader's terms: costs and dates for finance, shift hours for operations;
• carries no claims Pavlo would have to defend without proof.

If the champion has to retell your pitch in his own words, every retelling loses detail and confidence. Give him pages that speak for themselves, and he spends his credibility on pushing the deal, not on translating it.

Each member of the committee has their own worry, so each needs their own asset. One brochure for everyone answers nobody's question well.

For Veloria:

• HR and learning (Pavlo): a program outline with outcomes: what people will be able to do at the end, such as handling a carrier call, and how that's checked.
• The budget owner: a one-page cost and payback sheet: price per lesson, monthly cost, what's measured and when to decide.
• IT security: a data note: what's stored, where, for how long and who sees it, answering their questionnaire before they send it.
• The users (dispatchers): a sample lesson with a real tutor on a real carrier call. Trying it calms a nervous learner more than any promise.
• Operations (Stepan): a schedule built around the shifts, inside the outline.

Start from the committee map, then write one asset per person on it.

A committee moves through stages, and the useful content changes with them. Sending everything on day one buries the piece that matters now.

1. Is there a problem? Early on, people aren't sure they need anything. A one-page self-check helps: how often does a carrier call or a customs form go wrong at the dispatch desk?
2. Which option? While they compare, the program outline and a sample lesson do the work: what people will learn, and what a lesson feels like.
3. Can we approve it? At the decision, the committee needs to justify and sign: the cost sheet, the data note, a draft contract and a pilot plan.

For Veloria the pilot plan is concrete: 12 dispatchers, 2 lessons a week for 4 weeks, 96 lessons at 800 UAH = 76,800 UAH, credited to the contract if they sign. That line belongs on the cost sheet.

At the decision, the committee stops asking "is this interesting?" and starts asking "can I defend approving it?" Each approver needs the paper that lets them say yes inside their own process.

• The budget owner needs the cost and payback sheet, with the paid pilot credited to the contract, so the first spend isn't a gamble.
• IT security needs the data note, so their review is short.
• Legal needs a draft contract early. Last year Veloria's safety-course purchase stalled for three weeks because legal got the contract last.

What doesn't belong here: early-stage pieces such as the self-check (they already know they have a problem) and general articles about careers and English, which help nobody approve anything.

The rule: at each stage, ask which person is about to act and what they need in hand to act.

A cost sheet is read by someone whose job is to spot weak numbers. One unsupported claim makes the whole page suspect.

Before a line goes in, ask: who measured this, where, on whom? If you can't answer, cut it. "Corporate English raises productivity by 40%" found online fails the test.

Cut as well:

• guarantees nobody can keep, such as "fluent English in three months";
• digs at competitors ("unlike other schools, we care"): they prove nothing and sound defensive;
• case studies with no real client behind them.

Keep what you can show: the price (800 UAH a lesson, invoiced quarterly), the pilot terms, how progress is checked. And state plainly what you don't have: Klasna has no logistics clients yet, and the pilot is how it proves results on Veloria's own people. Honesty about a gap reads stronger than a number nobody can trace.

A common habit is to gate content: hide a guide behind a form so every download becomes a lead. In a committee sale this rarely pays off, and asking for too much data creates a second problem.

Data minimisation is the rule: collect only what you will actually use, for a clear purpose. To send a guide you need a work email at most. A personal phone number or a birthday has no business purpose here, and holding data you don't need is a risk under data-protection rules in the EU and Ukraine.

There is a sales cost too. A buyer who meets a long form either leaves or types something fake, and Pavlo can't forward a page his colleagues must register to open.

Better: keep the assets that help a committee decide (outline, cost sheet, data note) free to read and forward, and ask for contact details only when someone wants a call or a pilot.

A PDF that Pavlo forwards can't be counted in a dashboard, so measure content where it does its job: inside the deal.

Signals that an asset worked:

• the champion forwarded it, and colleagues reply about its contents;
• the budget owner's questions now refer to lines in the cost sheet, and she has set a date to review the pilot;
• IT security comes back with fewer questions, because the data note answered them;
• the deal moves to its next step sooner than the last one did.

Also ask the champion: "Which page did you actually use inside?" One honest answer tells you more than an open counter. Opens, likes and compliments on the design say nothing about a decision.

How it fits together: content serves a committee, one asset per person, timed to the stage, honest enough to forward, measured by deals. Next lesson: reaching companies that don't know Klasna yet, with outbound that respects consent.