The Build vs. Buy Paradox in the AI Agent Era

There's a growing paradox in the AI-assisted development space: developers who bill $100+/hour will happily burn 10–20 hours hacking together a bespoke solution with Claude and n8n instead of paying $30–50/month for an existing product. The original poster on HN spent ~100 hours building an MVP they market for $30–50/month, only to have a $100/hr developer say they'd "just hack this together in a few weeks with Claude and n8n." At the low end, that's ~10 hours = $1,000 of their time spent to avoid paying $30/month — a decision that "on paper makes zero sense."

Multiple commenters confirm seeing similar behavior. One notes that the "Claude sub is already paid for, so the output feels free," while paying for a product feels like a real decision. Another points out that "the majority of effort in any product is ongoing maintenance and evolution," and that self-built apps often break when browser/OS/LLM versions change — requiring rework that the builder didn't budget for. "Eventually all the dust will settle," they add, but "no worth trying to convince people otherwise" right now.

A third commenter suggests "subscription fatigue is real" and that enshittification, price hikes, and random product shutdowns make $50/month feel riskier than the sticker price. They also note "if the people you're speaking with feel they can solve this problem on their own, then they are not your ideal customer profile."

The implications for B2C SaaS are stark: anything less than thousands of hours of engineering work may face headwinds from DIY builders. One commenter asks directly: "Does this mean that consumer SaaS is essentially dead?" — a question the community hasn't fully answered yet.