Sales funnel content: what to publish at each stage, and the one job each piece does

Sales funnel content is a set of pages and assets, each written for one stage of a buyer's decision and each with one job. The job at the top is to be found by somebody who does not yet know a solution exists. In the middle it is to make a category of solution make sense. At the bottom it is to make choosing you the obvious, low risk decision. Most content programmes fail not because the writing is weak but because every piece is written for the top of the funnel, so there is plenty of traffic and nothing that converts it.

The fix is a map: five stages, the question the buyer is asking at each one, the format that answers it, and the number that shows it worked. Build the map first and the publishing calendar writes itself.

The five stages and what each one needs

Stage	The buyer's question	Formats that work	The metric
Problem aware	Why is this happening to us	Explainers, diagnostic guides, benchmark pieces, calculators, how to articles	Non brand organic entrances and scroll depth
Solution aware	What kinds of answer exist	Category explainers, approach comparisons, buying guides, frameworks, worked examples	Progression to a vendor stage page in the same session
Vendor aware	Who does this, and how do they differ	Alternatives and comparison pages, integration pages, use case pages, pricing explanations	Demo, quote or trial starts from the page
Decision	Will this work for us, and can I defend the choice	Case studies, implementation detail, security and compliance pages, FAQs written for a procurement reviewer, ROI workings	Opportunities that cite the asset, and sales cycle length
Post purchase	How do I get value and prove it	Onboarding guides, templates, reporting walkthroughs, customer stories for internal use	Activation rate, retention, expansion

Two rules keep the map honest. One job per piece, always. And one stage per piece: a page that tries to explain a problem and sell a product does the first badly and the second too early.

How to tell which stage a query belongs to

Do not guess from the words. Search the query and read what already ranks, because the ranking set is the clearest available statement of what the searcher wants.

• Explainers and guides ranking means the searcher is problem or solution aware. A product page will not rank there and would not convert if it did.
• Listicles and comparison pages ranking means vendor aware. This is where a comparison page of your own belongs.
• Product and pricing pages ranking means decision stage. Write the page that answers the objection, not another article.
• A mix of all three means the query is split, and the right move is a page that answers the question directly at the top and routes to the other two below.

The handoff rules that stop a funnel leaking

A funnel leaks at the joins, not in the middle of a page. Four rules fix most of it.

• Every piece links forward to the next stage, once, in the body, with link text that describes what the reader gets. One clear forward link beats four competing calls to action.
• Nothing asks for more than the stage justifies. A problem aware reader will take a template. They will not take a sales call, and asking kills the page.
• The asset a reader lands on next has to exist. Audit the map for stages with nothing in them before you commission anything new. The gap is nearly always vendor aware.
• Sales gets the list. Every decision stage asset should be something a salesperson can send, named in words they would use. An asset sales does not know about was written for nobody.

Auditing what you already have

Before writing anything, put your existing content in a sheet with these columns: URL, stage, the one job, the query it targets, entrances last quarter, conversions last quarter, and the next asset it links to. Two patterns always appear.

• A pile at the top. Many problem aware articles, often ranking, with nowhere to send the reader. Fix this by writing two or three vendor aware pages, not more articles.
• Orphans at the bottom. Case studies and product detail nothing links to and nobody finds. Fix this by linking forward from the stages above and naming them in the sales handover.

That audit usually finds the next quarter's work without any keyword research at all.

A worked map for one buyer

• Problem aware: an explainer on why the problem shows up, with a diagnostic checklist the reader can run. Links forward to the category explainer.
• Solution aware: a guide to the kinds of solution, what each is built for, and how to choose between the approaches. Links forward to the comparison page.
• Vendor aware: a comparison page that names the real options and describes each accurately, plus a use case page for the reader's industry. Links forward to the proof.
• Decision: one customer story with the numbers the customer agreed to publish, an implementation page with the timeline and what is required from the buyer, and a security page a reviewer can forward.
• Post purchase: an onboarding guide and a reporting template, which produce the renewal conversation and the next case study.

Five pieces, one buyer, one path. That beats twenty articles with no route through them, and it is a quarter's work rather than a year's.

How much to publish, and in what order

Build the path for one buyer completely before starting a second. The order that works: the vendor aware page first, because it converts and it is usually missing. Then the decision stage proof, because sales needs it immediately. Then the solution aware guide to feed them both. Then the problem aware articles, which take longest to earn their traffic and have somewhere to send it by the time they do.

That order is the opposite of how most programmes run, and it is why most programmes take so long to show a result.

This page covers mapping content to funnel stages. For the strategy decisions behind a programme, see our guide to building a content marketing strategy, and for the calendar that runs it, see our content calendar template.

Asked and answered: sales funnel content

What is top of funnel content?

Content for somebody who has the problem but has not started looking for a supplier. Explainers, diagnostics, how to guides and benchmarks. Its job is to be found and to be useful, and judging it on enquiries misreads what it is for.

What is bottom of funnel content?

Content for somebody choosing between named options or justifying a choice internally. Comparison pages, case studies, implementation detail, security pages and pricing explanations. This is where most programmes are thinnest.

How many pieces do I need per stage?

One per stage, per buyer, before you add a second anywhere. A complete path for one buyer outperforms a partial path for three.

Should gated assets sit in the funnel?

Gate sparingly and only where the asset is worth an email address on its own, such as a template or a model. Gating a problem aware explainer removes the traffic that would have reached the next stage.

How do I know which stage a piece of content is working at?

Look at what readers do next. Problem aware content is working when readers move to a solution page. Vendor aware content is working when readers start a demo or a quote. If nobody moves forward, the forward link or the next asset is the problem.

How often should the map be reviewed?

Quarterly. Update the stage labels on anything that changed, check for stages with nothing in them, and refresh the decision stage proof, since that is the content that ages fastest.

The stage that happens in a chat

Your funnel assumes the comparison stage happens on pages you can map. For many buyers it now happens in a conversation: they describe their problem to an assistant, ask for options, and ask why one is better than another.

Those are the middle of the funnel questions you wrote content for. Ask them as the buyer would and see which pages the reply leans on. If it quotes a rival's comparison, you know which stage needs work. AI Knows Us runs that set and shows the cited pages for each question.