Bottom-of-funnel content: use your CRM's loss reasons as a topic list
The loss reason field in your CRM is the most accurate topic list for the bottom of the funnel. See how to read each reason, the content that answers it and how to measure it.
Bottom-of-funnel content is what helps people who are already evaluating a purchase make the decision: comparisons, case studies, calculators and technical answers. The most accurate topic list for it is already sitting in your CRM, in the “loss reason” field. Every lost deal with a recorded reason is a real objection your content hasn't answered yet.
That answer needs to arrive before the conversation with a salesperson. In a Gartner survey of 646 buyers, 67% said they prefer buying without contact with a sales rep, and 45% used AI in a recent purchase. Whoever can't find the answer on their own moves on to the competitor who made it easy to see.
Pull and group your loss reasons
The first step is turning the CRM field into a short, reliable list. Without that, your topic list becomes guesswork. The routine:
- Export the lost deals from recent months, with the reason, the stage where the sale stopped and the salesperson's notes.
- Standardize the names. “Expensive”, “high price” and “no budget” are often the same reason written three ways.
- Count and rank. The reasons that show up most become your first topics.
- Read the notes. The reason says what was ticked; the note says what the customer actually said.
Also look at the stage where each sale stopped. The same “price too high” means different things at the first meeting and at the final proposal: early on, the conversation never reached value; at the end, the value didn't convince whoever signs.
If the field is still free text, start there. Sales and marketing alignment then gets a closed list of reasons, and marketing gains the best topic source there is.
What sits behind each reason
The recorded reason is the symptom; the content has to answer the cause. At one of our clients, a technology company, the list had five reasons: picking the conversation up later, a product that didn't meet a technical requirement, slow response from sales, a price above expectations and a proposal requested only to compare quotes. Each one hides a different cause:
- “Let's pick this up later” is often a polite no. The problem didn't become a priority, or the contact couldn't convince the rest of the buying committee.
- “Price too high” is almost always value that didn't come across. Whoever only sees price saw no difference between the options.
- “The product doesn't fit” is sometimes a real requirement and sometimes a technical question nobody answered.
- “Sales was slow” is a process issue, and content won't fix it.
- “It was just the third quote” shows the company entered the race too late, when the choice had already been made.
The right bottom-of-funnel content for each objection
Each cause calls for a format, and some reasons aren't a content problem at all.
| Reason | Content that answers it | Where it goes |
|---|---|---|
| Pick it up later | the cost of delaying the decision and a summary the contact can share internally | follow-up email |
| Price too high | a case study with numbers, a total cost calculator and an honest comparison | proposal and service page |
| Product doesn't fit | technical FAQ, list of requirements and integrations | website and first meeting |
| Slow response | a fix in the sales process, not a post | sales routine |
| Third quote | brand presence before the request for quotes | top and middle of funnel campaigns |
At the technology client, the team's reading followed the same line: price got more emails, about quality, support and time in the market; quote comparison went to the brand campaign; and slow response became a fix for sales.
For price, the underlying question is why you and not someone else. If your message would work for any competitor, the swap test shows where it needs to change.
Put the content in the sales team's hands
Bottom-of-funnel content that salespeople can't find at the right moment doesn't exist. Three habits make sure it gets used:
- a library organized by objection, not by format, with the link and a ready-made line for email and WhatsApp;
- sequences that trigger the content by loss reason or stage, as we show in CRM-triggered sequences;
- up-to-date proof, with numbers and case studies the team can cite, built from an inventory of proof.
Present each new piece to sales in a short meeting, with the reason it answers and the right moment to send it. Salespeople who understand what a piece is for actually use it.
How to measure it
The final test is the list of loss reasons in the following months. Track three signals:
- usage: how many times sales sent each piece;
- response: whether the opportunities that received the content moved to the next stage more than the others;
- the reason: whether that reason's weight dropped in the list of losses.
Review it with sales once a month. Reasons change with the market, and the topic list changes with them. Turning objections into content, from the research to production, is part of our content marketing and SEO work.
Talk to usWant help planning this at your company?Tell us what you need. We'll reply by email or WhatsApp and, if it makes sense, put together a quote.Contact us
Frequently asked questions
What is the difference between bottom-of-funnel content and sales collateral?
Sales collateral is used by a salesperson in a conversation; bottom-of-funnel content also works without them, on the website, in email and on social media. The best pieces serve both purposes.
How should loss reasons be recorded in the CRM?
As a closed list, with a few clear options and a notes field next to it. A short list gets filled in; a long list turns into “other”.
How many pieces should I create for each reason?
Start with one per reason, for the ones that show up most. After a sales cycle, see which ones sales used and which changed the list of losses, and invest in those.
Does bottom-of-funnel content belong on social media?
It does, in short versions: an excerpt from a case study, an answered technical question, a summarized comparison. The full piece lives on the website and in the sales team's hands.
