Before You Write Another Blog Post, Ask Sales This Question
By Emily Kirschenbaum7 min read
When your content calendar starts to feel repetitive, the sales team can tell you what buyers actually want to know.
I knew one client’s blog was getting stale when I could look at a perfectly good title on our content calendar and tell you, before I’d written a word, roughly how the post would go. Because I’d written it 20 times already in slightly different variations.
We’d been publishing several blogs a month for a while. I knew the business well, we had a rhythm, and there was no shortage of content ideas. Each title even looked different enough when putting the content calendar together. Once I sat down to write, though, I’d find myself making a familiar argument, explaining the same benefits, and arriving at the same conclusion we’d arrived at all the other times.
I know very well that, for the most part, blogs are an SEO play anyway and it’s unlikely anyone is going to sit down and read through every blog. So the fact that there is a consistency that can get boring to me as the writer doesn’t mean it’s boring or unhelpful to the reader. Quite the opposite, in fact.
What I wanted to be absolutely sure of was that the topics we were covering were actually the ones making a difference to the audience, repetitive or not.
So I asked if I could talk to a few people on the sales team. What I wanted to know boiled down to one question: What do you find yourself explaining to potential clients over and over again?
Part of what I heard was reassuring. Some of the subjects we were covering were exactly the things potential clients wanted to understand. I might have been getting tired of writing about them, but someone encountering the company for the first time still needed those answers. That alone was a good reminder. When you’ve written six versions of an explanation, it’s easy to forget that your reader may never have read even one.
Then there were the things we’d never thought to write about. They were specific enough that I doubt any of them would have made it onto our topic list in another round of brainstorming. And yet the sales team was having some version of the same conversation with prospect after prospect.
A Buyer on a Sales Call Has a Different Question
When you sit down to plan content, it’s only natural to start with a subject. You might want to explain how your technology works, why companies adopt it, or how it compares with something they already use. Those are all reasonable things to cover, and give a fairly orderly view of what it means to buy your product.
An actual buyer gets to bring their own complications. They have a team of a certain size, a system they’re stuck with for another year, or a stick-in-the-mud colleague whose approval they’ll need and will be hard to get. They might understand your product, love what it does, want to buy it, and still have one unresolved question that holds them back. From your side, that question might be a minor implementation detail, but from the customer’s side, it’s the first thing their boss is going to ask about.
The thing that really gave the sales conversations weight to me was knowing who was asking the questions. These were people who’d made it all the way to a call. They’d seen enough of the product to give someone their time, and now they were telling the salesperson exactly what was still unclear to them. Some of the concerns we’d never addressed in our content belonged precisely to the people the company wanted to reach.
What to Ask the Sales Team?
Let’s start with what NOT to ask them. Do not ask the sales team what they think marketing should write about. That’s just asking them to do a version of the brainstorming you’ve already done. Instead, ask them to tell you about a conversation they remember. A good place to start is “what came up on your last call that you’ve had to explain a dozen times?” Give them time to tell you the long version of the story because the detail you didn’t even know you need may be halfway through it.
Say a rep tells you that prospects ask about onboarding. It would be easy to jot down “blog post on onboarding” and move on. Before you do that, ask what the last buyer actually wanted to know. Were they worried about how long the process takes? Was it more about who has to do the work? Were they concerned about being able to keep serving customers during a transition? Without those details, you could end up writing a comprehensive explanation of your onboarding process and still leave two of those people looking for an answer.
Here’s another example. Let’s say a buyer asks how long it takes to get the product up and running. The rep gives them a timeline, and then the buyer says, “okay, but during those six weeks, how much time do you need from our engineers? We’ve got a release coming up and they will be busy with that too.”
That second question changes what I’d write in a blog post. A timeline might already be on the website, but what’s missing is a sense of what those six weeks will ask of the customer. They need to be able to set expectations with the relevant people on their team and make sure the process runs smoothly. This gives me something to talk about with the implementation team and a reason to ask for more than the standard description of the process.
I’d also want to hear how the rep answered the question. Someone who’s handled the same concern a dozen times may have found a clear way to explain it. Maybe they walk the buyer through a recent rollout, or ask particular follow-up questions that help them give a more accurate answer. That part of the conversation is easy to miss if you ask sales to send over a list of frequently asked questions. You may get the question in writing, but you lose the explanation that made it click.
Decide Where the Answer Belongs
After speaking to the sales team, resist the urge to take everything you heard, turn it into a list of titles, and declare next month’s content calendar done. Once you know what buyers are asking, take a look at the experience they have today and think about where a reasonably motivated person would go looking for that answer and what they would find when they got there.
Let’s go back to the buyer who’s concerned about engineering time. If your product page touts a “seamless implementation” and then invites them to book a demo, you can see why they’re asking sales this question. A short explanation on that page of who does what during implementation could be enough to help them decide whether the timing is realistic. If the answer depends on their setup, you can explain what it depends on. That gives them something concrete to take back to their engineering team.
Sometimes you’ll find that an excellent answer already exists to some of the most pressing questions. It’s in a guide that the sales team sends out after a first call, but there’s no obvious way for a prospective customer to find the information on the site. In that case, making the guide easier to find might do more for the buyer than commissioning another article. Other times, a question deserves a post of its own because a useful answer needs examples, trade-offs, or more room than you can give it on a product page.
Of course, not every question that comes up to the sales team is relevant for a blog post. I’d give priority to concerns that come up independently across several prospects, matter specifically to the kinds of customers you want, and have an answer you can give fully enough to be useful without knowing someone’s whole situation.
Keep the Conversation With Sales Going
Once the piece is written and published, don’t judge it solely by how many people read it. If you wrote it to help buyers understand what implementation will demand of their team, go back to the reps who told you about this issue and ask them if they sent it to anyone or if it’s helped at all. A rep who says, “I send it, but I still have to explain this one part myself,” has just given you a pretty good brief for your next edit.
What I learned about my client’s blog was that we could keep coming up with ideas even as the writing started to feel repetitive. We could have carried on happily filling the calendar and even being satisfied with our rankings and search results. Meanwhile, people who were seriously considering the product were volunteering better questions than the ones I was trying to think up at my desk.
So if you’re staring at next month’s calendar with the feeling that you’ve written all of this before, ask someone in sales about their last few calls. And when they mention something that sounds a little too specific for the blog, let them finish the story. That might be the very thing a future customer is trying to find out.
(And, it goes without saying, if you don’t want to do any of the above yourself, I’m here to help - let’s talk!)