What are attention merchants in the context of AI tools?

Attention merchants are AI tool companies whose primary business model depends not on the tool being genuinely useful, but on engineers feeling like they need to try it, evaluate it, and stay current with it. They create and sustain anxiety about falling behind, missing productivity gains, or being replaced — then sell the cure. The anxiety is the product. The tool is the delivery mechanism.

Why does AI tool marketing specifically target competent engineers?

Competent engineers are the most vulnerable to this playbook because they have the most to lose. They care about craft, they have existing expertise they're proud of, and they're the ones who'll feel it most acutely when their skills start eroding. A marketing campaign designed to create anxiety works best on people who are already conscientious — who take their professional development seriously and whose self-worth is connected to their technical capability.

What's the real cost of constant AI tool evaluation?

The cost isn't just the time spent evaluating new tools — it's the attention residue left behind. Every tool you evaluate occupies working memory. The average software engineer now tracks 6-8 active AI tools in various states of evaluation, onboarding, and use. The cognitive overhead of maintaining this evaluation state is substantial and invisible. It manifests as a persistent low-level anxiety that something better is out there, that you're not doing your best work, that you're falling behind — even when your actual output is fine.

How do I know if I'm being manipulated by AI tool fear campaigns?

Three signals: First, you feel urgency to try a new tool before you've finished evaluating the last one. Second, the primary emotion driving your tool adoption is anxiety — fear of falling behind, fear of being replaced, fear of missing something — rather than genuine curiosity about a better approach. Third, you can't remember the last time you mastered a tool deeply instead of surface-level evaluate-and-switch. If all three apply, you're in the attention merchant's target zone.

What's the ethical stance on AI tools — are they all bad?

This isn't about whether AI tools are useful or not. Many of them are genuinely useful. The attention merchant critique is about the marketing apparatus that surrounds them — the fear campaigns, the manufactured urgency, the manufactured anxiety. You can use excellent AI tools while simultaneously recognizing that the marketing ecosystem around them is designed to keep you anxious and perpetually evaluating. The tools aren't the problem. The anxiety-for-growth loop is.

How do I build a healthy relationship with AI tools without falling for the hype cycle?

The framework: evaluate tools on a fixed cycle, not in response to marketing. Pick your evaluation windows — perhaps one tool per quarter, deeply — and stick to them. Use tools that solve problems you've already identified, not tools that promise problems you don't know you have yet. The engineers who navigate this best are not the ones using the most tools. They're the ones who feel no urgency about the next release because they've already found stable ground with what works for them.

The Attention Economy Applied to Engineers

The Attention Merchants: How AI Tool Marketing Creates Engineer Anxiety

Every AI tool launches with a fear campaign. You'll fall behind. You'll be slower. Your peers are more productive. Here's the playbook — and why it works on exactly the engineers who should be immune.

There's a business model you've seen before. It doesn't sell software. It sells anxiety — then sells the cure. The anxiety is the product. The tool is the delivery mechanism.

You've seen it in social media: the platform that made you feel like you were missing out on what your friends were doing, then provided the connection to cure that feeling. You've seen it in news: the outlets that made you feel like the world was going to hell, then provided the information to ease that anxiety. The product was never the platform or the information. The product was the anxiety. And the cure was whatever they were selling.

Now it's in AI tools for software engineers. And the specific targeting — the specific vulnerability it's designed to exploit — should concern you.

6–8

The estimated number of AI tools the average software engineer is currently evaluating, actively using, or considering adopting — at any given time. This evaluation state has become a persistent background process, consuming working memory and creating low-grade anxiety about falling behind.

The Playbook: How AI Companies Engineer Your Anxiety

The attention merchant's playbook has clear stages. Once you see them, you can't unsee them. Every AI tool launch follows a version of this script:

Stage 1: The Gap Creation

Before the tool exists, or before you know about it, the marketing apparatus creates a sense of inadequacy. "Engineers who aren't using AI-assisted coding are falling behind." "The best developers have already adopted X." "Y company reports 40% productivity gains with AI." The gap is manufactured before the solution arrives. You're already behind before you know there's a race.

Stage 2: The Specific Fear

The gap isn't just "you might be missing out." It's specific enough to sting. "Your code review turnaround is 3x slower than engineers using Copilot." "Engineers who don't learn prompting will be replaced by those who do." "While you were writing tests by hand, engineers using Claude completed the same sprint in half the time." The specificity is the point — it makes the threat feel concrete and personal.

Stage 3: The Social Proof Flood

Launch day brings testimonials, case studies, and social proof. "We shipped 3x faster after adopting X." "I can't imagine going back to coding without Y." The testimonials are real — some of them. But they're selected for maximum aspirational gap: the most dramatic improvements, the most enthusiastic early adopters, the most visible power users. The engineers who tried the tool and found it mediocre or disruptive aren't in the launch blog post.

Stage 4: The Perpetual Update Cycle

Once you're in the ecosystem, the anxiety doesn't end. Every feature update from every competing tool becomes news. "X tool just added capability Y — and it's a game changer." "Version 2.0 of tool Z changes everything." The update cycle is designed to keep you in evaluation mode permanently. You can't settle into mastery because the ground keeps shifting. The tool companies have no incentive to let you feel like you've arrived — that would end the anxiety, and with it, the attention.

Stage 5: The Competitor's Threat

Just as you've started to feel comfortable with your current AI tool, the competitor releases a benchmark showing they're 15% faster. Or a Twitter thread from a power user shows a workflow you haven't tried. The competitor's threat is always one tab away. The anxiety isn't just about one tool — it's about whether you're using the right tool, whether there's something better that would make you more effective, more competitive, more caught up.

Why Competent Engineers Are the Target

Here's the part that should bother you most: the attention merchant's playbook works best on exactly the engineers who should be immune.

Low-skill engineers aren't particularly vulnerable to this. They don't care that much about falling behind because they don't have strong professional self-worth tied to their technical capability. They're not tracking the frontier of the field. They don't read the benchmark comparisons.

Competent engineers are the most vulnerable precisely because they have the most to lose. They care about craft. They have existing expertise they're proud of. And the threat of that expertise becoming obsolete — of skills they've spent years developing being devalued — lands hardest on the people who care most about those skills.

"The engineers most likely to adopt a new AI tool fastest are the ones who are most conscientious about their professional development — which means they're also the ones who will be most anxious about whether they're using the right tool, staying current, keeping up with the field. The anxiety is the feature, not the bug, of the attention merchant's model."

This is a deliberate targeting choice. Marketing teams at AI companies aren't stupid. They know that the engineer who reads every benchmark, tests every new tool, and tracks every productivity study is the same engineer who will evangelize the tool to their team, write about it on social media, and drive adoption. They're also the engineer who will feel most anxious about being left behind.

So they build the anxiety on purpose. They create the gap, then provide the solution. They make you feel behind, then offer the path forward. And they do it in a way that's invisible to the target — because the engineer who would notice a manipulation campaign is, by the same professional instincts, the engineer who is most susceptible to it.

The Cost Nobody Counts

The actual cost of the attention merchant's playbook isn't just the time spent evaluating new tools. It's the attention residue — the working memory consumed by the evaluation state — that nobody measures.

The Evaluation Overhead

Maintaining 6-8 tools in various states of evaluation uses real cognitive resources. Every tool you're partially committed to — even if you're not actively using it right now — occupies slots in working memory. This is invisible. Nobody puts "evaluating AI coding tools" on their task list. But it's there, and it costs something.

The Mastery Penalty

Surface-level evaluation prevents deep mastery. Deep mastery — knowing a tool well enough that it becomes an extension of your thinking — is what produces the 10x productivity gains that the marketing claims are automatic. But you can't go deep when there's always another tool to evaluate, another release to check, another benchmark to review.

The Comparison Trap

Even when you settle on a tool and start using it, the comparison trap keeps the anxiety active. "Is Copilot better for this task?" "Should I try Claude for code review?" "I heard Cursor has a feature I don't have." The grass is perpetually greener on another tool's lawn — not because it is, but because the attention merchant's business model depends on you believing it might be.

The Expertise Anxiety

Perhaps the subtlest cost: the constant tool-switching prevents the development of genuine expertise. Real expertise — the kind that makes you valuable, the kind that produces architectural judgment, the kind that lets you debug the genuinely hard problems — takes years to build. If you're spending 30% of your professional attention on evaluating tools, you're not spending it on the deep work that makes you an expert.

The trap within the trap: The attention merchant's model means that the more tools you evaluate, the more anxious you become about tools, the more likely you are to keep evaluating. The anxiety doesn't resolve — it escalates. The engineer who starts evaluating AI tools from a place of mild curiosity ends up in a persistent state of tool anxiety, always behind, always catching up, never settled.

The Five AI Tool Marketing Tropes (And Why They Work)

You've seen these headlines. You've felt the little spike of anxiety when they appeared in your feed. Here's why each one works:

1. "X% of Engineers Are Already Using Y" — The Social Proof Pressure

The statistic is usually from a survey of early adopters, power users, or Twitter-engaged developers — not a representative sample. But the framing implies you're in the minority if you're not using it. Social proof is powerful precisely because it exploits our deep social nature: the fear of being the one who doesn't know, who's behind, who's missing out.

2. "We Saved Z Hours Per Week" — The Productivity Stat

Productivity statistics from AI tool companies are measured in the most favorable possible conditions: simple tasks, favorable contexts, power users who have already optimized their workflows. The variance is enormous and never reported. The engineer who tried the tool on a complex debugging session and found it unhelpful doesn't publish their experience.

3. "The Tools Your Competitors Don't Want You to Know About" — The Conspiracy Angle

This one is explicitly manipulative: it implies that there's a secret, that the established tools are somehow suppressing information about a better alternative. It's a classic direct-response marketing technique. The implied insider information creates urgency and the feeling that you're being let in on something others don't have access to.

4. "This Changes Everything" — The Revolutionary Claim

Almost no software tool "changes everything." But the claim is effective precisely because it's so large and undifferentiated. When something claims to change everything, you're implicitly behind if you're not using it — because everything is different now, and you're living in the before. The engineer who doesn't adopt the revolutionary tool is, by definition, living in the past.

5. "Don't Get Left Behind" — The FOMO Engine

The oldest attention merchant play in the book. FOMO — fear of missing out — is the specific anxiety the attention merchant manufactures. It's not curiosity about a better way. It's fear of being left behind, of being obsolete, of being the engineer who didn't see it coming. And fear is a much more powerful motivator than curiosity. Fear makes you act. Fear makes you evaluate. Fear makes you keep the tab open.

The Real Problem With All This

The attention merchant's model has a specific harm beyond the anxiety itself: it keeps you in a state of perpetual evaluation instead of settled mastery. The productivity gains that AI tool companies promise — the 2x, 3x, 10x improvements — are real, but they require deep mastery of the tool. You can't get deep mastery when you're always evaluating, always switching, always wondering if something better is coming.

The engineers who get the most value from AI tools are not the ones who try every tool. They're the ones who found a tool that works for them, went deep, and stopped looking. They got past the evaluation state into genuine fluency. They know the tool well enough that it augments their thinking without replacing it.

That's what the attention merchant doesn't want you to reach. Settled mastery ends the anxiety. And if you stop feeling anxious about tools, you might stop paying attention to their marketing. And then the anxiety-for-growth loop breaks — and their business model breaks with it.

How to Escape the Attention Merchant's Playbook

This isn't about rejecting AI tools. Many of them are genuinely useful. The critique is about the anxiety apparatus around them. Here's how to stay in the useful part without getting trapped in the anxiety cycle:

Pick your evaluation windows, don't respond to marketing. Choose one quarter to deeply evaluate a new tool category, then commit for a fixed period. Don't evaluate in response to launch announcements. You'll always be in evaluation if you let the marketing drive the timing.
Establish deep mastery before moving on. Set a personal threshold for "I've gone deep enough on this tool" before you'll consider switching. This prevents the perpetual shallow evaluation that the attention merchant depends on.
Evaluate tools when you have a problem, not to find problems. The right time to evaluate a new tool is when you have a problem you think it might solve — not when a marketing campaign makes you feel like you should be evaluating it. Tools exist to solve problems. Problems don't exist to justify tools.
Track your actual productivity, not your anxiety level. If a tool is genuinely making you more effective, you'll see it in your output — not in how up-to-date you feel. If you're reading every benchmark and feeling constantly behind but your actual delivery hasn't improved, the tool isn't the problem. The anxiety apparatus is.
Recognize the social proof trick. When you see "X% of engineers are now using Y," ask: who was surveyed? What was the context? A survey of Twitter-active early adopters isn't a representative sample. Social proof is compelling precisely because it's hard to evaluate the source — which is exactly why it's used.
Set a "settled" date. For any tool you currently use, set an internal date — maybe 6 months from now — when you'll declare mastery. After that date, you don't evaluate alternatives unless you hit a problem the tool demonstrably can't solve. The goal is fluency, not coverage.
Separate the tool from the marketing. When you read a glowing testimonial about a tool, practice separating the genuine utility of the tool from the marketing apparatus that amplified it. Many AI tools are genuinely useful. The attention merchant problem is the marketing layer on top — and you can recognize that layer without rejecting the tool underneath.

What This Means for Your Team

The attention merchant's playbook has team-level implications. When one engineer on a team adopts a new AI tool and shares their enthusiasm, it creates social pressure on the rest of the team to evaluate it. The evaluation isn't optional — the social dynamics make it feel necessary. "If Alex is using it and says it's 2x faster, shouldn't we all at least try it?"

This creates a team-wide evaluation state that costs real cognitive resources. The team that is constantly evaluating new tools together is not a team that is deepening its mastery of existing tools. The velocity looks like it's about productivity, but it's actually about attention.

The fix at the team level: make some tools "settled" by team norm, not individual decision. "We use X for code review, Y for pair programming, Z for documentation. We're not evaluating alternatives for the next 6 months." This removes the individual anxiety about being left behind and lets the team go deep.

The Question to Ask Yourself This Week

Before the next time you open a new tool tab — before you sign up for the free trial, before you read the benchmark comparison, before you click the "getting started" guide — stop and ask:

Am I evaluating this tool because I have a problem it might solve? Or because the marketing made me feel like I should be evaluating it?

If it's the latter — if the primary emotion is anxiety about being behind, not curiosity about a solution — close the tab. The anxiety is the product. The tool is the delivery mechanism. And you don't have to play.

🧩