Turn SaaS Objections Into Blog Posts That Close Deals

The Core Problem: Content That Does Not Convert

The Blog as a Feature Announcement Channel Willard's first and sharpest point is about what most SaaS blogs actually contain: feature updates. She is emphatic that feature updates are not useless — they belong in a changelog and serve a purpose there — but they should not be the primary or dominant content on a company blog. The people a company most needs to reach with blog content are prospects who have not yet signed up. Those prospects do not care about a feature they have never used. They are asking a different set of questions entirely: Is this worth my money? How is this different from what I already use? Will this actually work for my situation?

Feature-update-heavy blogs speak only to existing users, and even then, only partially. They do nothing to move a prospect through a sales cycle.

The Keyword Trap The second major problem Willard identifies is an over-reliance on keyword research as the starting point for content strategy. She frames keyword research as inherently backward-looking: it surfaces what people were searching for in the past, based on accumulated search volume data. For established product categories, this can be a useful signal. But for SaaS products — especially those that have created a new category or introduced a novel solution — historical keyword data is nearly useless because there was no search history to record. Nobody was searching for something that did not exist.

Willard is explicit that she is not dismissing SEO entirely; she is arguing against leading with keywords. She frames keyword consideration as "a problem for later" — once you have built an audience, established trust, and begun to attract organic interest. In the early and growth phases of a SaaS product, chasing keywords is a distraction from the more immediate problem of explaining why someone should sign up at all.

The Organisational Silo Problem Willard identifies a structural issue that compounds both of the above problems: marketing, sales, product, and support typically do not talk to each other. She describes the dysfunction vividly: Marketing is chasing keywords.

Sales is answering the same pre-sales questions over and over, individually, with no mechanism for those answers to propagate.

Support is actually solving real customer problems but has no pipeline for feeding those learnings back to marketing or product.

Product is sometimes building features nobody asked for.

Because these departments are siloed, the company ends up with no shared source of truth.

Sales over-promises because it does not know what product has ruled out. Marketing publishes content that does not reflect what prospects are actually asking. Support invents answers on the fly because there is no agreed canon of responses. The result is confusion, friction, and stalled deals.

The Framework: Pre-Sales to Conversion

Willard presents a clean, linear framework: Pre-sales objection —> Sales conversation —> Content creation —> Trust building —> Conversion The logic is anchored in a principle she credits as a business truism: people do business with those they know, like, and trust. She acknowledges it is a cliche precisely because it is accurate. When a prospect is being asked to put a credit card on a SaaS product — particularly one from an unknown company — that trust has to be established somewhere before the transaction happens. Blog content that honestly addresses the specific questions a prospect is already asking is one of the most direct ways to build that trust at scale.

Where Objections Live: The Five Sources

Willard gives a detailed account of exactly where objections and real customer questions can be found. She is specific and practical about each.

1. Sales Calls and Demo Calls The most direct source. During live calls, prospects voice their hesitations, comparisons, and concerns. Willard recommends physically writing these down during the call — she is an advocate for handwriting over purely AI-assisted note-taking, on the grounds that neurological research supports stronger recall for things written by hand. She is not dismissing AI note-takers; she recommends using them in parallel. But she emphasises that

the act of physically writing something down in the moment locks it into memory in a way that reviewing a transcript later does not.

She recommends logging the date and time alongside the note, and if the sales call is conducted by someone other than the content creator, establishing a process for those notes to be captured and shared.

2. Direct Messages Across Social Platforms DMs on X (Twitter), LinkedIn, Facebook, and wherever else the company is running paid or organic activity contain real pre-sales questions. Willard notes she has observed SaaS companies running heavy paid campaigns on Facebook and that the comment sections on those ads are rich with objections, questions, and competitor comparisons — all in the natural language of the target audience.

3. Support Tickets Support tickets are particularly valuable because they contain customer language — the words real users reach for when something is not working or not clear. Willard credits a specific example: a contact she met at a dinner before WordCamp Paris in 2017 (she could not recall his exact name but described him as Dutch, well-known, and named something like "Richard Vander something") who had built a system where incoming support tickets were anonymised and directly converted into draft blog posts. The question as asked by the customer became the basis of the content. The insight is that a question asked once will be asked again, often in nearly identical language, because the underlying confusion is structural, not individual.

4. Onboarding Calls and Post-Purchase Friction Onboarding is where the gap between buyer intent and actual use often becomes visible.

The person who signed the contract is not always the person who uses the software daily.

Willard illustrates this with a personal example: her day job at TJ Maxx, where the company transitioned from Oracle to Workday. The decision was made at the executive level but the friction was experienced all the way down through regional vice presidents, district managers, and store managers who were unfamiliar with the new system.

This distinction — between the customer who said yes and the users who have to make it work — is an important nuance. Onboarding calls surface friction from actual practitioners, and that friction is content-ready material.

5. Social Conversations and Listening Willard is a strong advocate for active social listening, particularly on X. She draws a sharp distinction between passive use (posting your own content, replying to your own replies) and genuine listening, which requires using tools like Twitter Lists to follow and monitor specific

conversations. She calls Twitter Lists "the biggest tool that nobody uses" and notes she has produced multiple videos on the subject.

For monitoring beyond X, she recommends: AlertMouse (alertmouse.com) — a tool from Rand Fishkin (formerly of Moz, now of SparkToro) that has a free tier and alerts you to mentions of specified terms.

Google Alerts — set to "as it happens" and "all results" for your brand name, product name, domain, and key competitors.

She explicitly suggests setting up alerts for competitor names plus words like "problems" — so if you compete with Dropbox, you would monitor "Dropbox problems" and surface real complaints from that user base that your product might address.

The GiveWP Case Study: Breaking Silos in Practice

Willard draws on her experience at Thought House, where GiveWP (a WordPress donation plugin) was a client. She was hired to grow their Twitter account in June 2015, when the account had 167 followers. By December 2015, GiveWP hired her directly.

The relevant detail is structural: GiveWP's team — Devin Walker (Product), Jason Connell (Sales), Matt Cromwell (Support), and Willard (Marketing) — worked in a shared San Diego office. Despite Willard commuting an hour and a half each way, she was in the office every Tuesday. More importantly, the four departments shared a lunch table.

She frames the lunch table as the mechanism that eliminated silos. Product, marketing, support, and sales were having informal, continuous conversations about customer friction, support issues, the product roadmap, and pre-sales questions — without anyone needing to be formally invited to another team's meeting. Information moved organically because the people were physically proximate.

She connects this to a point Jimmy Rosen (the preceding speaker) had also raised about the value of physical co-location. Willard's argument is that the content and messaging alignment this produced at GiveWP — publishing four blog posts per week at peak cadence — was a direct product of teams being genuinely connected, not siloed.

For teams that cannot be physically co-located, she suggests Slack as a partial substitute for sharing real-time customer insights, but notes it requires intentional discipline to maintain.

The Content Creation Process

The Rule of Three Willard offers a practical threshold for deciding when a question deserves its own blog post: if the same question arrives three or more times (from different people), it warrants dedicated content. She draws an analogy to a paper filing system from her secretarial

experience — miscellaneous invoices stay loose until a vendor has three invoices, at which point they earn their own folder. The same logic applies to customer questions.

AI as Aggregator, Not Author Willard positions AI tools (she mentions Claude, Perplexity, Gemini, and ChatGPT) as categorisation and aggregation tools, not as the source of content. The process she recommends is: Collect raw objections and questions from the five sources above.

Use AI to categorise repeated questions and identify patterns.

Bring the team together to agree on the real answer — not the sales-friendly over-promise, but the honest, accurate answer that all departments can stand behind.

Publish that answer as a blog post.

She is emphatic that the answer must be agreed upon across sales, product, marketing, and support. This prevents the classic failure mode where sales promises something product has not built, or support is forced to contradict what marketing has published.

The Website as Living Source of Truth Once blog posts are published that reflect honest, team-agreed answers to real objections, the website stops being a static legacy asset and becomes what Willard calls "your living sales, marketing, product, support assistant that works 24/7." Prospects can self-serve answers to the questions they would otherwise raise on a sales call. Support can link to posts rather than writing out individual responses. Sales can share posts with prospects mid-cycle to address specific hesitations.

The Question Is the Title Willard is direct on this point: do not translate the customer's question into keyword-friendly language. Use the question as the blog post title. If a prospect asks "How are you different from DocuSign?", the post is titled "How Are We Different From DocuSign?" If they ask "Is this software worth the cost?", that is the title. The post then covers pricing, ROI, comparison, and use cases — whatever the question naturally demands.

She gives three representative example titles: - "Is your software worth the cost?" (covers pricing, ROI, what you get for your money) - "How are you different from [Competitor]?" (covers direct comparisons, feature parity, pricing differences) - "Will this work for me?" (covers use cases, customer types, limitations) One Post, One Objection, One Conversation Per Week The cadence she recommends for most SaaS companies is one objection-busting post per week. This is manageable, sustainable, and builds a library over time. She cautions against 1.

trying to publish everything at once or treating this as a content sprint; the value compounds slowly and requires consistency.

Repurposing Across Channels Each blog post becomes source material for multiple formats:

• A direct link share on X or LinkedIn
• An Instagram image or slide
• A short video
• A LinkedIn article (which she specifically flags as carrying extra weight because it puts the answer directly in front of decision-makers on the platform where they spend time) The blog post is the canonical, long-form version; everything else is a derivative.

Why This Approach Works

It Shortens the Sales Cycle When prospects can read honest answers to their top questions before or during a demo call, they arrive better informed and with fewer unresolved doubts. The call becomes about closing rather than educating from scratch. Willard frames MRR (monthly recurring revenue) as the metric that validates the approach — shorter sales cycles mean more MRR, faster.

It Reduces Pre-Sales Friction Prospects who are not yet ready to book a demo can still have their questions answered by published content. This keeps them warm without requiring sales resource. It is, in Willard's phrase, "preventative support" for the pre-sales stage.

It Aligns the Team With agreed-upon answers published publicly, there is a shared reference point. Sales cannot credibly over-promise if the blog post says otherwise. Product has a record of what the company has committed to in its public communications. Marketing has content that reflects what the product actually does. Support can reference published posts in responses.

It Builds Measurable Trust Willard invokes the know-like-trust framework not as a vague aspiration but as a specific mechanism: the blog post is the tangible evidence that your company understands the prospect's problem, has a real answer, and is willing to be transparent about it. For a prospect evaluating whether to hand over a credit card to an unfamiliar SaaS company, that public evidence of honesty is meaningful.

The Documentation Distinction

Willard briefly addresses the relationship between blog content and product documentation.

Documentation is typically behind a paywall or login gate — available only to existing users.

Blog posts are public-facing and indexed. Both are necessary, but they serve different audiences. Documentation serves users who have already committed; objection-handling blog posts serve prospects who have not. The distinction matters because conflating the two often results in companies thinking they have answered the question ("it's in the docs") when the prospect cannot yet see the docs.

Social Listening as Competitive Intelligence

Willard expands her social listening argument in the Q&A section. On the question of Reddit versus X for finding objections and conversations, she notes: Reddit is valuable for hearing what people are frustrated about in a given category. The SaaS subreddit, for example, surfaces real problems. However, Reddit's community norms make it very difficult to build individual relationships. You can listen and extract insight, but engaging as a brand or founder without violating community norms is genuinely hard.

Reddit, she says, "stands on business" — it has strict rules and will downvote or remove content that violates them, regardless of your intentions. It is a listening tool more than a relationship-building tool for SaaS companies.

X (Twitter) is where relationships are more buildable, particularly through lists.

Conversations happen in real time, objections surface publicly, and you can engage directly in ways that are socially acceptable on the platform. Willard has been on Twitter since its early days and has built her professional reputation substantially through consistent, high-value public engagement there.

Conversations happen in real time, objections surface publicly, and you can engage directly in ways that are socially acceptable on the platform.

Cancellation as Content Research

One of the most practically specific points in the Q&A is Willard's approach to cancellations.

She argues that support is a "stealthy sales team" and that the moment of cancellation is an underused research opportunity. When a customer cancels, rather than simply processing the cancellation, she recommends asking: "I understand you're cancelling. But can I ask why you bought the software in the first place? What were you hoping it would solve? And what is it not solving now that's led you to cancel?"

She reports that adopting this approach measurably reduced churn for products she has supported. The mechanism is twofold: first, the question sometimes surfaces a solvable

problem that the customer had not thought to raise through support; second, even when the cancellation proceeds, the answer provides direct intelligence about unmet expectations that can inform content, product direction, and sales messaging.

The content loop closes here: cancellation data becomes objection data, which becomes blog post data, which (if the post addresses the underlying issue) potentially prevents future cancellations.

The Actionable Starting Point

When asked for a single golden nugget — one thing a SaaS owner should do immediately after watching the talk — Willard's answer was immediate and specific: Write down your top ten objections and write down the honest answer to each one.

No tools required. No AI needed yet. Just the act of naming the ten questions prospects most frequently ask or resist, and committing the real answers to paper. That document becomes the content backlog, the team alignment tool, and the foundation of the blog strategy described throughout the talk.

Speaker's Background and Context

Willard has been working in marketing for over 20 years. Her professional history includes time at an advertising agency (Thought House), client-side work for GiveWP, freelance consulting across a wide range of industries including franchise brands (Sport Clips, Win Home Inspection, Paul Davis Restoration), and product-level support work for companies such as Pneumonic Oxide during transition periods.

She works a day job at TJ Maxx alongside her consulting practice — a detail she volunteers without embarrassment as a reflection of the reality of building an independent business.

She references working 16-hour days during her early years building the business alongside a full-time commuter job, positioning this not as unusual hardship but as the expected cost of building something independently.

Her approach to her own marketing mirrors the advice she gives clients: she does not pitch herself in public interactions. She answers questions fully and publicly, treating each response as a "deposit" in the relationship bank. Over time, the people who have observed the quality of those answers become inbound clients. She has been doing this consistently enough that even organisations she worked with years ago (the host mentioned Atarim as an example) cite that pattern as how the relationship began.

About the speaker Bridget Willard Marketing Consultant

Bridget Willard is a marketing consultant who works with SaaS and WordPress companies on turning customer objections into content that moves deals forward.