Purchase blocker research from public discussions

Short answer

A purchase blocker is the reason someone who wants to buy does not. In public discussions, blockers fall into six families: price and value, trust, delivery and logistics, fit, risk and commitment, and process friction. To find them, track phrases such as "I wanted to buy, but", "too expensive", "I don't trust it" or "the contract is too long" together with category terms, then log each blocker in a register: a quote, how many different authors, whether the blocker is real or perceived, who can fix it, and what was done.

How a blocker differs from a complaint

A complaint comes from someone who already bought — they have a problem with the product or service. A blocker comes from someone who has not bought yet — they want to, but something holds them back. The difference matters because a blocker is an invisible loss of sales: the buyer does not call, does not complain, simply does not buy. Public discussion is one of the few ways to see that silent loss, because people talk about their hesitation to friends and on forums more openly than they would to you.

Six blocker families

• Price and value: "too expensive", "is it worth the money?", "it's cheaper elsewhere". The problem is often not the price but that the value is never explained.
• Trust: "never heard of them", "the website looks dodgy", "no real customer reviews", "will they take the money and vanish?".
• Logistics: "they don't deliver to our district", "can't wait two weeks", "installation costs extra".
• Fit: "will it suit my home/car/business?", "the size isn't clear".
• Risk and commitment: "a one-year contract", "no returns", "the warranty is unclear".
• Process friction: "the order form doesn't work", "I call and nobody answers", "no cash payment".

Phrases that reveal blockers

The strongest signal is the "I want to, but" construction. Add phrases of this kind to your tracking list: "I wanted to buy, but", "I'm thinking about it because", "I'm hesitating", "I'm afraid that", "what if...?", "has anyone else had this?". In Azerbaijan, build the same list in Azerbaijani and Russian. Combine these phrases with category terms, or hesitation about every area of life will come in.

A blocker register

1. 1BlockerA short name: "installation cost is unclear".
2. 2EvidenceTwo or three quotes with links; how many different authors wrote this in the last 90 days.
3. 3Real or perceivedReal — the blocker genuinely exists (delivery really does take two weeks). Perceived — the information is missing or wrong (delivery takes two days, but nowhere says so).
4. 4OwnerWho can fix it: marketing, product, operations, sales, legal.
5. 5Action and dateWhat was done and when; did the blocker shrink a month later?

Who fixes what

• Marketing — explaining value, real customer stories, stating the price range openly.
• Product — a compatibility table, a size guide, a selection tool.
• Operations — delivery area and times, an installation service.
• Sales — a trial period, payment options, explaining return terms.
• Legal — contract and warranty terms written in plain language.

Illustrative example

This is an illustrative example. Over three months, an online furniture shop finds the same hesitation from 14 different authors in public discussions: "do they deliver outside Baku, and is assembly extra?". The shop does deliver to the regions and assembly is free, but this is only mentioned after the order is confirmed. It is a perceived blocker. A delivery map and an "assembly included" note are added to the product pages. Two months later the same question rarely appears in public discussions.

Competitors' blockers

Include posts about competitors in the register too. "I wanted to buy from X, but they don't take returns" is an opportunity for you — if you do accept returns and say so openly. But naming a competitor's blocker in your own advertising creates ethical and legal risk; the better route is to show your own advantage clearly.

Measuring after a fix

After each fix, watch two things: did public posts about the same blocker become fewer, and did a related sales indicator change — basket abandonment, say, or how often the same question comes up on calls. Public discussion volumes are small, so judge the change after a month or two; a week's numbers can be random.

Linking it to your own conversations

Public sources show the hesitation of buyers who have not reached you yet; sales calls show the objections of those who have. Compare the two. Analysis of price objections in calls is in price objection analysis; to organise category questions, see the customer question bank.

Limitations

The most worried people post most in public discussions, so a blocker's weight can look exaggerated. Telling real blockers from perceived ones needs internal information — the team does that, not monitoring. Do not draw conclusions about the whole market from a handful of posts; the register shows direction, not statistics.

Common mistakes

• Putting every blocker down to price.
• Answering a perceived blocker with a discount — information would have been enough.
• Leaving the register without owners.
• Not measuring after a fix.
• Searching only by brand name — blockers are often written by people who do not know you yet.

Blockers in Vexvon Monitoring

Vexvon Monitoring reads every post found on the sites you add and shows its type (question, criticism, comparison and so on), its tone and up to five topic tags — "price", "delivery", "warranty", for example. If competitors are named in a post, they are listed separately. These labels speed up the first sort of the blocker register; telling real blockers from perceived ones is the team's job. More on the Vexvon Monitoring page.

Next step

Write 10 "I want to, but" phrases for your category, fill in the first 10 rows of the blocker register from the last three months of public discussion, and mark each one "real" or "perceived". Fix the most frequent perceived blocker this month. Other articles are in the buyer intent and customer needs section; to look at it together, get in touch.