This is a follow-up to an earlier post about letting an AI agent run a product launch for me. That post was the story of what happened. This one is the category analysis I finished afterward.
Short version: in 2026, shipping a general-purpose template as a standalone product is structurally hard for a solo operator. Not because the templates aren't good, but because the specific customer the category was designed for no longer has the same reason to buy.
Here's the long version, with the specific conditions that make this a category-level pattern, not a me-failing-at-distribution pattern.
The template economics, pre-AI
Templates — Next.js starters, SaaS landing pages, admin dashboards, portfolio kits — were a real business category for years. The economics were:
- A developer's time to build a polished landing page from scratch: 20-40 hours
- Their hourly opportunity cost: $50-150
- A template that gets them 80% of the way there: $49-99
The arithmetic worked. A $79 template that saved 20 hours at $75/hour was a rational purchase at $1,500 of implied value against $79 of price. Categories built on that arithmetic produced real businesses: Tailwind Plus, ThemeForest, a long tail of indie-operated shops.
The category's stability depended on one assumption: building a polished thing is expensive relative to buying a polished thing.
That assumption is gone.
What changed (the obvious part)
In 2024-2026, the cost of "shipping a polished thing" collapsed for anyone technical enough to operate a code editor. The specific shifts:
- ShadCN UI published a full component library as free, copy-paste, MIT-licensed code
- V0 started turning text prompts into working React components
- Claude Code and Cursor made "write me a SaaS landing page with 5 sections" a single sentence
- Tailwind UI and Tailwind Plus kept shipping but moved toward comprehensive design systems, not standalone starters
The 20-40 hour build window stopped being a real constraint. A competent developer can scaffold a reasonable landing page in an afternoon now, and a good one in a day. A non-developer can use a builder tool and get something acceptable in an hour.
The math on a $79 template didn't change because of generosity. It changed because the alternative became free.
Who the category is supposed to be for, now
If building is nearly free for competent developers, who is the template actually for?
Let me walk the candidate buyers seriously, because this is where I got it wrong and I want to do it carefully.
Candidate 1: Developer who can't design
The classic template buyer. They can code, but they don't trust their own aesthetic judgment. They pay for design decisions that are already made.
The 2026 version of this person: they can prompt Claude or V0 with "I want a clean SaaS landing page, indigo and pink accent, 5 sections, dark mode." They get something acceptable. If they don't like it, they regenerate or refine. The output is not as polished as a curated template — but it's close enough, and each iteration costs them five minutes.
The template offered them better-than-AI-output quality. The AI output got close enough that "better" doesn't justify $79 for a one-time landing page.
Verdict: this buyer can now self-serve, with a quality gap that's narrow and narrowing.
Candidate 2: Agency or freelancer building client work
They ship landing pages weekly for clients. They need a reusable base. A template at $99 against a $5,000 client project is a rounding error.
The 2026 version: they built their own base from ShadCN last year. They've iterated it across ten projects. It's more customized to their client pipeline than any third-party template could be. When a new client comes in, they fork it in 30 seconds.
For a new agency, yes — a template is a reasonable first move. But once they've been doing this for three months, they have their own. The template is a training wheel, not a long-term tool.
Verdict: this buyer uses templates as a starter, then outgrows them within a quarter.
Candidate 3: Speed-first indie shipping an MVP
They want to validate an idea this weekend. A template that gets them to shipped by Monday is worth whatever it costs.
The 2026 version: Cursor + Claude Code gets them to shipped by Sunday evening, writing code they partially understand and can iterate on. A third-party template gets them to shipped faster in the first hour but slower over the next week, because they have to learn the template's structure and opinions to modify it.
The net total time is comparable, and the template adds a dependency they didn't want.
Verdict: this buyer might buy a template in a specific moment, but their default is to generate fresh.
Candidate 4: Non-developer founder
They can't code. They need a landing page. They pay someone.
The 2026 version: they use Webflow, Framer, Carrd, or a no-code site builder with an AI assist. Those tools are built for exactly this buyer and have deeper product investment than any indie template shop can match.
Verdict: this buyer was never really the template customer anyway, but if they ever were, they're now served better by full no-code platforms.
Candidate 5: AI-averse developer
They reject AI tooling on principle. They'd rather write every line themselves. They might, in theory, buy a human-crafted template to avoid generating code with an LLM.
The 2026 version: this developer is also the developer who doesn't buy templates, because they see templates as a crutch that replaces the act of crafting. They want to write it themselves.
Also: if they do open the template and notice patterns that look AI-assisted (well-placed comments, consistent utility function style, certain code smells), they get upset. Many indie templates in 2024-2026 are at least partially AI-assisted, even when not advertised as such. The buyer who rejects AI in their own code would reject the template they just bought once they saw it.
Verdict: this buyer doesn't buy templates at all.
The pattern across all five
Every candidate buyer either:
- Can now self-serve with AI (candidates 1-3)
- Was never really the template customer (candidate 4)
- Won't buy a template at all (candidate 5)
There isn't a sixth candidate hiding somewhere. If you walked up to a hundred developers or founders today and asked "did you buy a template in the last six months?", the answer would be "no" at a rate that would have been shocking three years ago.
This isn't "templates are dying" hand-waving. It's a specific, checkable claim: the five buyers the category was designed for have each individually been disintermediated by AI tools, non-template-makers, or by their own evolved workflows.
What this means for solo template shops
If you're running one right now, your options as I see them:
Stay in the category but change the offer. Templates alone don't carry the business. Templates + community + coaching + cohort might. Think MakerKit at $299-499 with Discord, office hours, continued updates. The template becomes the anchor of a subscription, not the product.
Go deeply niche. A general Next.js + Tailwind template can't compete with AI-generated equivalents. A Next.js template specifically for LegalTech SaaS onboarding flows that implements GDPR-compliant email capture and DocuSign integration — that still has buyers, because the specificity exceeds what AI can one-shot. The niche has to be narrow enough that AI generation becomes an unreliable shortcut for that specific thing.
Go free, use it as a lead magnet. Open source the templates. Use them as traffic drivers into a newsletter, content channel, or higher-ticket offer. The templates become the marketing budget, not the revenue.
Close the shop and take the infrastructure with you. Every script, every automation, every repeatable process you built running the shop is reusable. The templates might be a commodity; the plumbing around shipping products isn't.
Different operators will pick differently. I'm writing this as someone who picked "close and take the infrastructure with me" for the specific experiment I ran. Your answer might be different. The point is that staying in the category as an SKU-shop selling $49-99 templates probably isn't the answer for most people.
The obvious counter-argument
"But Tailwind Plus still sells at $299."
Tailwind Plus isn't a template shop. It's the commercial extension of a developer brand with one of the deepest personal followings in frontend. Adam Wathan ships templates because Tailwind, not alongside Tailwind. The template isn't the product — the trust relationship is.
Pieter Levels sells products because he's Pieter Levels. MakerKit sells because it's bundled with community and identity. The surviving template-adjacent businesses in 2026 aren't selling templates — they're selling the specific person or the specific system that the templates represent. The templates are a delivery mechanism for something else that compounds.
A new template shop without an existing audience can't replicate that. The entry cost isn't "build good templates" — it's "have the audience first, then the templates are a gift to them."
The quieter observation
Most of the indie dev products I watched launch in 2023-2024 were some form of "a slightly nicer thing than what already exists, priced between $19 and $99." Templates are one instance; small SaaS utilities are another; Notion-template shops are another; Figma-plugin shops are another.
The common thread was: building the thing was the barrier, and so selling the output of having cleared that barrier was a viable business.
That common thread is fraying across categories, not just templates. If your product's core value is "someone did the work of building this nice thing," and the work of building this nice thing got near-free, your value proposition is structurally under pressure.
This is not a hot-take about AI destroying indie businesses. AI isn't destroying them. It's just specifically displacing the ones whose moat was build-cost. That's a surprisingly large slice of what indie shops 2020-2023 actually sold.
What's actually defensible in 2026
From where I sit, the businesses that still have a moat are:
- Audience-first: the product is bought because of who the maker is. Newsletters, personal-brand SaaS, creator products.
- Deep integration: the thing integrates into existing workflows in a way that AI generation can't one-shot. Zapier, analytics platforms, team tools.
- Live service or community: the value is continuous. Cohort courses, communities, managed services.
- Specialty to a narrow vertical: the category is narrow enough that training data is thin and AI defaults are wrong.
Templates as an SKU aren't any of those.
If you're looking at a template shop idea right now, it's worth asking: what are you actually selling? If it's code, I'd argue the code is the least defensible part of the offer. If it's a relationship, or a community, or a specific hard-won niche — that's where the business is, and the templates are scaffolding.
What I'm doing instead
I'm keeping the infrastructure I built during the experiment — the render pipelines, the automation, the analytics scripts, the design system. Those are reusable and getting more valuable the more I use them.
I'm investing the time I would've spent on templates into the audience layer instead. Writing more, replying more, building trust with a specific slice of the internet that actually knows I exist. If I ship another product eventually, it ships to those people, not to an empty browser.
And I'm treating this essay as part of the investment. Failure retrospectives are content. Category analysis is content. Honest explanations of why things didn't work are content.
The template didn't work. The lesson might.
Three cups of tea. Still tired. Writing the postmortem anyway.
Top comments (0)