Finding the objections your buyers already voice
Every sales page answers objections. Most of them guess. The objections are already public, stated by buyers who had no reason to be polite.
The short answer: watch the reviews and comparisons of products in your category, collect the resistance verbatim, then keep only the statements that would actually block a purchase. Ten to fifteen sources is usually enough for the list to stop growing, and what is left is a better objection map than most companies have after a year of selling.
Objection handling is normally treated as a sales-team discipline, learned expensively after launch. That ordering is backwards. The objections already exist in public, in the moment when someone is being told to use a tool and pushes back — which is exactly the moment a review video captures and a comment section preserves.
Where the objections actually live
Not all video content is equally productive here. Tutorials show you workflow; reviews and comparisons show you resistance. The distinction matters because you are hunting for a specific speech act — someone explaining why they will not, or did not, adopt something.
| Source | What it yields | Reliability |
|---|---|---|
| Head-to-head comparisons | The trade-off buyers actually weigh | High — the creator has to justify a choice |
| “Why I switched away” videos | Deal-breakers with a story attached | High, but one person’s context |
| Comment threads under reviews | Unfiltered price and trust objections | Medium — loud minority effects |
| Sponsored tool showcases | The objections the sponsor pre-empts | Medium, and revealing in a different way |
| Conference talks and panels | Procurement, security and compliance blockers | High for enterprise categories |
The fourth row rewards a second look. A sponsored segment is written by someone who knows the category’s standard objections and is being paid to defuse them, so the script is effectively an objection list with the answers already attached. Talks and panels carry the procurement-side blockers that consumer-facing content never touches — the sourcing case made in using conference talks and podcasts as research sources.
Sorting blockers from wishes
A raw objection list is mostly noise. The single most useful filter is whether the statement, if true, prevents a purchase — everything else is a roadmap input at best.
- ✗The UI feels dated
- ✗I wish it had more integrations
- ✗Would be better with a mobile app
- ✗The docs could be clearer
- ✓It cannot export, so I would be locked in
- ✓No SSO means security will not approve it
- ✓Migrating our existing data is a week of work
- ✓Per-seat pricing does not fit how our team works
The right-hand column shares a structure: each names a cost or a risk the buyer cannot remove on their own. That is the working definition of an objection, and it is why the answer is rarely a feature. Lock-in fears are answered by an export guarantee, migration cost by a done-for-you import, pricing-model mismatch by a second pricing model — none of which appear on a feature roadmap.
Ranking what you find
Two properties decide priority: how often an objection recurs across unrelated sources, and how expensive it is to answer. Frequency alone will mislead you, because the cheapest objections to voice are also the most repeated.
Count independent sources rather than mentions. If one widely-shared video made the point and eleven others restate it, that is one source with distribution, not twelve confirmations — the counting error described in separating hype from signal in creator content. Objections that show up independently in a comparison video, a conference Q&A and an unrelated comment thread are the ones to design around.
If the recurring blocker in your category is something you also cannot solve, you have learned the most valuable thing available before writing any code. That is a disqualifying signal in the sense described in how to disqualify a SaaS idea early — and finding it in week one is cheap, while finding it in month nine is not.
The stated objection is rarely the real one
Objections arrive in a socially acceptable form. “It is too expensive” is the most common thing a buyer says and one of the least common things they mean, because price is the objection that requires no explanation and implies no criticism of the speaker.
Underneath it there is usually a risk the person cannot articulate comfortably: uncertainty about whether the thing will work in their specific setup, doubt that a small vendor will still exist next year, or an unstated fear of being the person who championed a tool that failed. Each of those has a different answer, and none of them is a discount.
| Stated as | Often means | What answers it |
|---|---|---|
| Too expensive | I am not confident it will work here | A trial on their own data, not a lower price |
| We could build this ourselves | I do not see enough depth to justify buying | Showing the hard part they have not considered |
| Not a priority right now | The problem is real but nobody owns it | Naming the cost of the status quo in their terms |
| We already use something for this | Switching cost, not satisfaction | Migration help, plus one thing the incumbent cannot do |
Video content is unusually good at exposing this gap, because a creator working through a decision on camera will often state the polite version first and the real one a few sentences later, once they have warmed to the subject. The second version is the one to record.
Turning the list into copy
Objections earn their keep in three places, and the instinct to put them all in one place is wrong.
The landing page answers only the two or three that recurred independently and that block the first purchase. Any more and the page starts arguing with the reader about problems they had not considered. The mechanics of writing that page from research material sit in turning research into landing page copy.
The FAQ and docs take the second tier — real objections that only surface once someone is seriously evaluating. These need direct answers rather than reassurance, because the reader has already decided vague answers mean no.
The roadmap takes whatever is left, weighted by how many independent sources raised it. This is where the objection pass overlaps with prioritisation, and the same evidence should feed both — the argument in prioritising features with research evidence.
Use their words, not your summary of their words
The wording matters more here than anywhere else in research. An objection paraphrased into product language stops matching what the buyer thinks, and copy written from the paraphrase reads like it was written by someone who has not met the customer.
Keep the verbatim phrasing and the timestamp attached to each objection. When you write the answer, use the buyer’s noun, not yours. If they say “it is another thing to maintain”, the page should address maintenance burden in those words, not “operational overhead”. A summary that has lost the original phrasing has lost the part you were mining for. The same verbatim objections are the skeleton of the live pitch, which is why they feed directly into a demo script built from video research.
Running the pass
This is a small, bounded research job — one category, ten to fifteen sources, a day of work. As of August 2026 the plans are $19 a month for 25 videos and 2 projects, $59 for 80 videos and 8 projects, and $199 for 250 videos, 20 projects and 3 seats, all detailed on the pricing page. An objection pass fits comfortably inside the smallest tier, which is the point: it is meant to happen before you have revenue to justify anything larger.
Agencies running this for clients tend to do it as the first deliverable of an engagement, since it is the fastest way to sound informed about a market you joined last week — the pattern in client market research for agencies.
Pull the recurring resistance out of review and comparison content, with the exact wording and source timestamp attached to every line. 7-day free trial.
Closing thought
Nobody tells a salesperson the real reason they said no. They will, however, say it plainly in a comment thread under a video about a competitor — and that comment was published before you started building.
Frequently asked
How do I find the objections buyers will raise before I have any buyers?
Watch what people already say when a competing product is recommended to them. Review videos, tool comparisons and their comment sections contain the same four or five objections your sales page will have to answer, stated in the buyer's own words and without a salesperson present.
Are objections in creator content representative of real buyers?
They are representative of the informed, self-selecting slice of buyers — people engaged enough to watch a tool review. That skews toward the technical end of your market, so treat the list as a superset of objections rather than a ranking of them.
What is the difference between an objection and a feature request?
An objection blocks a purchase; a feature request assumes one. 'I cannot get this past security review' stops the deal. 'It would be nice if it had dark mode' does not. Sorting your list on that single test removes about half of it.
Which objections should a landing page answer directly?
The two or three that appear across unrelated sources and that a reasonable buyer cannot resolve alone — usually price framing, migration cost, and trust in a small vendor. Answering minor objections on the page adds doubt rather than removing it.
How many videos does it take to find a stable objection list?
Objections saturate faster than most research questions. Ten to fifteen review or comparison videos in a category typically surface the recurring set, and additional sources after that mostly repeat them in new words.
Can I use competitors' objections if I am not building a competitor?
Yes, and it is often the better source. Objections attach to the category rather than to a specific product, so the resistance customers voice about an incumbent is largely the resistance they will voice about you — minus whatever you deliberately design out.
What does this cost to run?
As of August 2026 the tiers are $19 a month for 25 videos and 2 projects, $59 for 80 videos and 8 projects, and $199 for 250 videos, 20 projects and 3 seats. An objection pass on one category typically fits inside the smallest plan.