FUD

Fear, uncertainty and doubt: a persuasion tactic that sells by alarming rather than demonstrating, common in tech marketing and forum debates.

FUD is marketing by anxiety. Instead of showing that a product is good, it implies the alternative is dangerous: they will lock you in, they are about to shut down, security people are worried. The term spread from the mainframe wars, where incumbents seeded doubt about upstarts' survival, and the pattern is now standard-issue in cloud migration pitches, database holy wars, framework threads and vendor comparisons of every kind, executed both by companies and by their unpaid volunteer armies in comment sections.

Why it matters to an indie builder: you will be FUDded, the moment your tool appears in a comparison thread, a competitor's answer to your pricing page is a paragraph about risk, and you will be tempted to FUD back. Recognizing the tactic structurally, claims about the future, unsourced worries, emotional framing dressed as prudence, keeps your positioning honest and your blood pressure stable. FUD also works on you from the inside: analysis paralysis about the safe stack is self-inflicted FUD, and it delays more indie products than any competitor does.

A concrete example: a thread compares two form builders. Vendor A's advocate posts: B is a two-person team, what if they quit, and no enterprise compliance. Both statements are facts, neither is an argument: A's own product also started as two people, and the buyer runs a bakery, not a bank. The winning reply for B is calm and specific: the export feature, documented and one click, is the real answer to lock-in fear, and a published SLA plus a track record addresses the risk question with evidence. B lands the sale because it answered fear with verifiable properties rather than counter-fear.

Common mistakes: answering FUD with FUD, which reads as guilt to exactly the audience you are courting, mistaking every hard question for FUD (what happens if you get hit by a bus is a fair buying question; have a public answer, continuity plans and escrowed data options exist for this), using fear in your own copy (it converts once and rots trust, and refund and churn rates eventually invoice it), and building your roadmap defensively against competitor whispers instead of off user evidence.