If you don't need WordPress, what is Etch Studio actually selling?

On August 25, 2026, Kevin Geary said that for non-ecommerce sites, most of the sites he builds only needed what he called WordPress light — dynamic data, loops, and logic without WordPress baggage:

“8 to 9 out of 10 sites that I built only needed … what he called WordPress light — dynamic data, loops, and logic without WordPress baggage.”

If that diagnosis is correct, Etch Studio enters a crowded field of AI-assisted builders that already ship prompt plus visual edit plus real code. The question is not whether Studio is good. The question is whether it beats tools that hand you a repository.

The "you don't need WordPress" claim

On the same stream:

“This is a dead product. This is a dead platform.”

“You don't want to start on a massive dinosaur infrastructure like WordPress.”

Thirteen months earlier, in July 2025:

“All of this can be fixed without abandoning WordPress—we don't even have to sit around waiting for Automattic to get its ducks in a row.”

Both statements are public and dated. The pivot from fix-in-place to leave-entirely is the premise behind Studio — and it reframes the competitive set entirely.

If WordPress is optional, Studio is not competing with page builders inside WordPress. It is competing with the wider stack of AI site tools, prompt-to-repo products, and IDE-first agent workflows that already target brochure sites, landing pages, and lightweight apps without a PHP backend.

Other solutions, as workflows

Each row below is a basic day-to-day loop. Read it as an ownership test: after step four, who holds the project?

A visual layer is not unique to Studio. Local IDEs already pair prompting with files you can open anywhere. Hosted AI builders already pair a preview with a repository you can clone — though repo sync or export varies by product and plan. EtchWP already pairs the same Svelte canvas with a WordPress database you host. Studio's loop is the same canvas on a vendor tenant, with compiled files out.

When last reviewed on 2026-09-22, the public checkout at studio.etchbuilder.io/purchase showed $49/month. That page did not publish a separate price for lifetime-deal holders or other early backers.

Their strongest counterargument — stated fairly

“Just working in Cursor, just working in Claude Code … not having a visual interactive interface, it's not really that interesting.”

This is a real product argument, not a lock-in argument. Geary's point is that pure agentic coding traps you in a reprompt cycle, while Etch keeps a visual layer over its own loops, logic, and data keys so you can click and edit what the model built. In Svelte or React vibe-coding, changing one element can require regenerating the whole component. Etch's structured canvas — loops, facets, data bindings — gives AI a constrained vocabulary and gives humans a click target. That is worth paying for if the visual layer is genuinely better than reprompting. It is not, by itself, a reason to accept that your project lives only in the vendor's database with no Git history and no re-import path.

Why that is a feature argument, not a lock-in argument

Visual plus AI already exists across the mainstream builder field. Many of those tools also return a repository. A visual layer justifies a subscription when leaving does not cost you the engine. Studio's ZIP download gives you output files; it does not give you the project — content types, loops, logic, styles, and the editing environment stay in the hosted app. Stop subscribing and you keep the compiled files, not the ability to edit them.

Their own /why/ page defined builder lock-in as work "trapped in a proprietary builder environment." Measured against that standard, a hosted canvas with no Git and no re-import is the thing they sold against.

The comparison table

Who Studio genuinely suits

Studio makes sense for WordPress agencies who want the familiar Etch canvas, one-click Cloudflare deploy, and client-owned output files — without managing WordPress for brochure sites. It makes less sense as an answer to "you don't need WordPress" when the wider market already answers that question with repository output and lower recurring tiers.

If you still want WordPress, EtchWP keeps your data in core WordPress and your lifetime deal still applies to the plugin. See EtchWP vs Etch Studio for that branch, and Is Etch Studio included in the lifetime deal? for the entitlement question.

To pick a path — brochure, dynamic, prototype-then-own, or WordPress — and follow a get-started baseline, see Workflows.