How to build a B2B content plan

A content plan that starts from the questions your sales team answers every week, gets an engineer’s knowledge onto the page and is measured by what it does for sales.

· 13 min readUpdated: Content

Short answer

A B2B content plan takes the questions your sales team answers most often and the reasons deals are lost, and orders them by buying stage and by the reader’s role. Knowledge comes from expert interviews, each piece is written from a short brief, and success is judged by enquiries and how often sales uses it.

A sales engineer opens the inbox and, for perhaps the tenth time this month, answers the same question: “Does this product work at high temperatures, which certificates does it have, how long does a sample take?” The answer goes out in different words each time, but with the same information. Over the same period, the company blog has published a trade fair announcement and a holiday greeting. A B2B content plan starts by connecting those two things: the question a customer asks becomes an answer that is written down on the website and can be found. In this article we explain, step by step, how we plan a B2B company’s blog posts, guides, product and application pages, case studies, newsletter and LinkedIn posts.

The topic list comes from the sales team

When people ask how to put a content plan together, our first suggestion is to listen. The first source is the sales team’s inbox. Gather the replies written to customers over the last three months, notes from pre-quote meetings, technical support records and sample requests. Put every question in one table: the question in the customer’s own words, the role of the person asking, how often it comes up and how it is answered today.

The second source is lost deals. The “reason lost” field in the CRM is often a single word, and the most common word is “price”. Five minutes with the salesperson usually turns up something else behind it: the lead time was unclear, a competitor had the certificate that was asked for, the technical team was never convinced the product would fit their existing line. Each of these is a content topic. A page that explains production and delivery, a page that brings certificates and test reports together, a guide that answers compatibility questions.

Keyword research comes after this list. The questions tell you what to write; search data shows which words people use for the same question. We explained how to combine the two lists in what is B2B SEO.

One product, four readers

In B2B, the buying decision is never one person’s, and each role asks a different question:

  • User: the person who will use the product on site. Is it easy, how is it maintained, what happens when it breaks down?
  • Technical evaluator: an engineer or quality manager. Dimensions, standards, test results, fit with the existing system.
  • Purchasing: lead time, payment terms, continuity of supply, comparison with other suppliers.
  • Management: risk, return and whether the supplier will still be there years from now.

Write these roles as rows and the buying stages as columns: noticing the problem, researching options, comparing suppliers, deciding and using. Put each question from the topic list in the cell it belongs to. Filled cells show the questions already answered; empty cells show the gaps. You don’t need to fill every cell; close the gaps that slow sales down most first.

Which question suits which format

The format is chosen after the topic:

  • Product and application pages: where the technical evaluator looks most. Technical data, standards and how the product is used for which job belong here. Most sales questions belong on these pages rather than in a blog post; we covered how to build them in what a company website needs.
  • Guide: a long, lasting resource for the stages of noticing the problem and researching. “Which material for which environment”, or “the measurements to check when choosing”.
  • Blog post: one answer to one question. Short enough for a salesperson to add as a link to an email.
  • Case study: for the comparing and deciding stages. A real project, told with the customer’s written permission; without permission, the sector, the problem and the fix are described without naming the customer.
  • Newsletter: for existing customers and open quotes. It carries new content to the people sales is already talking to.
  • LinkedIn: a distribution channel. The content lives on the website; a short summary and a link are shared on the company page and on the expert’s own profile. We explain how to fit these posts into the month’s plan in our guide to building a social media content calendar. To put experts sharing from their own profiles on a voluntary footing, see our guide to employee advocacy on LinkedIn.

The knowledge is in the engineer’s head

The hardest part of B2B content marketing is getting the knowledge from the person who has it; the writing is the easier half. Engineers and product managers don’t set time aside to write, and they shouldn’t be expected to. This is the workflow we use:

  1. The writer reads the brief and sends the expert five or six questions in advance.
  2. A 30 to 45 minute interview with the expert, recorded with permission.
  3. The writer drafts from the interview, keeping the expert’s sentences and examples.
  4. The expert reads the draft for technical accuracy only; style is the writer’s job. One round of corrections is enough.

The questions that work in an interview are usually these: “What’s the first thing you say when a customer asks this?”, “What is most often misunderstood?”, “When would you not recommend this product?”, “What’s a mistake you’ve seen on site?” The answers to the last two are information that never appears in a brochure and that readers trust most.

Google’s guide to helpful, reliable, people-first content suggests asking who created the content, how and why; and the first letter of E-E-A-T in the search quality rater guidelines stands for first-hand experience. Putting the expert’s name and role under the article shows readers, too, where the knowledge came from.

A brief template

Before each piece is written, a half-page brief is filled in:

Field What to write
Goal What will change once this is published? For example, the salesperson will answer this question with a link from now on.
Reader Which role, at which stage.
Question answered One sentence, in the customer’s own words.
Target search phrase The main phrase and close variants, if there are any.
Sources The expert to interview, technical documents, standards, test reports.
Internal links Which pages will lead to this piece, and which pages it will lead to.
Format and length Product page, guide or blog post.
Next step (CTA) What this reader can reasonably do at this stage; download the data sheet, ask for a sample or book a technical call.
Distribution Who sales will send it to, and how it will be announced in the newsletter and on LinkedIn.

If the “question answered” line can’t be written, the piece isn’t ready yet.

A realistic cadence and a simple calendar

Choose a cadence the team can keep up for a year. A piece that needs an expert interview depends on the expert’s calendar; two new pieces and one update a month does more than a weekly plan that is published for three months and then stops.

A spreadsheet is enough for the calendar. Columns: title, question answered, role and stage, expert, interview date, draft, expert approval, publish date, announced to sales, and next review date. Plan three months at a time and review once a month. For ongoing work, we put progress in the Monday report instead of a separate meeting: what was published last week, which interview is waiting, what is needed from the expert.

Here is a row template you can copy into your own spreadsheet; the first row is only an example.

Title Question answered Role and stage Expert Interview date Draft Expert approval Publish date Announced to sales Next review date
Example: Which material for which environment “Is this product right for our environment?” Technical evaluator, researching options Product engineer Month 1, week 2 Written Pending Month 1, week 4 On publish day, with the link Month 4, week 1
The path of one piece of content: from sales questions to the brief, the expert interview, publishing and measurement 1 Sales questions 2 Topic list 3 Brief 4 Expert interview 5 Writer’s draft 6 Expert approval 7 Publish 8 Announce to sales 9 Review 10 Measure The path of one piece of content: from sales questions to the brief, the expert interview, publishing and measurement 1 Sales questions 2 Topic list 3 Brief 4 Expert interview 5 Writer’s draft 6 Expert approval 7 Publish 8 Announce to sales 9 Review 10 Measure
Figure: each piece goes from the questions the sales team receives into the topic list, is written from a brief and an expert interview, is published and announced to sales after expert approval, and is then reviewed and measured by what it does for sales.

Updating and pruning old content

Every piece has a review date in the calendar. On that day, three questions are asked: is the information still correct, is the product still sold, is there another page covering the same topic? Depending on the answer, the piece is updated, merged with a similar one or removed. The address of a removed or merged page is redirected to the closest current page.

The same Google guide lists changing the date of pages to make them seem fresh, when the content has not substantially changed, among its warning signs. An updated date goes on only when the content really changes. Pruning belongs to the plan as much as publishing does: technical information that is out of date costs a customer more than missing information.

Measurement: what it does for sales

A view count doesn’t tell you whether a B2B piece works; a technical page may be read by a few of the right people each month, and that is enough. We look at three things:

  • Assisted enquiries: was this content read before a form or quote request came in? The key events attribution paths report in GA4 shows which channels start, assist and close the path to a key event. Complete it with a “how did you find us” field in the CRM and a single question the salesperson asks in the first call.
  • Use in sales: how many times a month does the sales team send this link? Is the same question asked less often by email?
  • Reasons lost: after the content is published, does the same reason for losing a deal appear less often?

These numbers are small and move slowly. Ask for the same measure when you bring in outside help with content; in how to choose an SEO agency we explained why work measured by the number of articles misleads.

Common mistakes

  • Starting from a keyword list. Topics people search for but that never touch sales get written, and the salesperson’s question stays unanswered.
  • Counting company news as content. Fair and greeting posts have their place, but a plan isn’t made of them.
  • Waiting for the expert to write. The draft waits for months. Hold an interview and let the writer write.
  • Putting everything on the blog. If technical information belongs on a product page, it should live there; the blog post links to it.
  • Publishing without telling sales. If the salesperson doesn’t know the content exists, they keep writing the same email.
  • Writing once and leaving it. Content without a review date carries wrong information within a few years.

We run the content plan together with expert interviews, writing and distribution as part of our content service.

Common questions

What is a B2B content plan?

A B2B content plan is a written list showing which questions a company will answer for its customers, in what order, in which format and with whose knowledge. The topics come from the questions sales answers most often and from the reasons deals are lost. Each is tied to a role and a buying stage, written from a brief, and carries a publish date and a review date in the calendar.

How often should a B2B company publish content?

As often as the team can keep up for a year. Pieces that need expert knowledge depend on the expert’s calendar; two new pieces and one update a month usually does more than an intense plan that stops after a few months. What matters more than frequency is that each piece answers a real customer question and that the sales team uses it.

How do you get content out of engineers who don’t want to write?

The engineer doesn’t need to write. The writer prepares the brief, sends the expert a few questions in advance and holds a recorded 30 to 45 minute interview. The writer drafts; the expert reads only for technical accuracy. The expert’s name and role go on the article, so readers can see where the knowledge came from.

The first thing to do this week is small: ask the sales team for the five longest replies they wrote to customers in the last month. Each of those five emails is an answer already written for the “question answered” line of a brief.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 28 October 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.