'Replaces 6+ Premium Plugins.' I Count Two.

“Replaces 6+ premium plugins”.

That line is on every plan for Etch for WordPress, or EtchWP, the WordPress plugin from Kevin Geary’s company. It doesn’t say “will replace”. It says replaces.

There’s no asterisk on it. WooCommerce, the shop plugin, gets one on the same plan lists, explained as “not currently available”, and so does version control on the two agency plans. The plugin line doesn’t get one.

The pricing page has an asterisk. It left this line out.

Same page, two tenses

Scroll down the pricing page to the FAQ: “Etch will eventually replace the following:”. The FAQ lists six categories: page builders, block themes, field plugins, media, SEO and performance. It names ACF for custom fields, Yoast for SEO and Perfmatters for performance.

“Eventually” came first. It’s on the page in September 2024, during the pre-sale. “Replaces” isn’t on the page on 1 April 2025, and it is on 19 August 2025. That’s at least five months before version 1.0 of EtchWP, dated 30 January 2026.

EtchWP never says “6+” means those six. The count matches and Geary reaches for the same list, so I’m reading them together.

Here’s Geary on a stream on 2 June 2026, talking about that plan line:

“there’s a uh a part on the pricing page where it says replaces six plus premium plugins, right? Well, that that’s true. You know, uh you’re not going to need ACF or Metabox. You’re not going to need your SEO plugin eventually.”

That’s true. Eventually. In my view, a claim that needs that word is a roadmap, and it should be sold as one.

Three partly. SEO not at all.

I’ll count page builders and block themes as replaced. That’s two of the six.

• Fields. Partly. EtchWP’s docs call its built-in fields “more of a playground right now than a real part of your workflow (unless your needs are very basic)”.
• Media. Partly. EtchWP has an Asset Manager, from 1 July 2026. A month earlier, talking about media, Geary said “we can’t loop through the collections yet”. No doc shows that looping has shipped.
• SEO. Not replaced. I found no native SEO feature documented.
• Performance. Partly. EtchWP covers image handling. I found no caching, script management or preload feature.

The only date I found

On 17 December 2025, Geary called the built-in fields a proof of concept. He said to look “toward the end of Q1” for them to be solid “for most basic cases”.

On 7 April 2026, a week after Q1 ended, he was asked for the best stack. His answer was “Uh etch automatic CSS ACF.” Automatic CSS is his company’s CSS framework. ACF is the field plugin, and it was still in his answer.

On 2 June 2026, he said “the goal is that you never need Jet Engine and ACF ever again”. JetEngine is another plugin people use for custom fields.

He called it the goal. The docs now allow for very basic needs, so that goal’s partly met. The plan line still says replaces, and the field list is thinner than you’d hope.

I found no date for SEO. The live pricing FAQ lists “manage SEO optimization” among the things done “directly from within Etch”. On 8 October 2026, version 1.7.0 of EtchWP announced “Yoast SEO and Rank Math compatibility”. Those are two SEO plugins, and compatibility means working alongside them.

Etch Studio is the company’s separate version of Etch without WordPress. The etchbuilder.io FAQ says “most new features will be built in Etch Studio first”, with “We can’t give an exact timeline for each port”. A port means moving a feature across to EtchWP.

I don’t know why the work was ordered this way. I do know what the pricing page said while it happened.

Do the sums

Say you run 25 sites. Prices are as of 1 November 2026.

Etch Small Agency, the EtchWP plan for 25 sites, is $199 a year. You need more than very basic fields, so you keep ACF PRO Agency at $249. You want script management, so you keep Perfmatters unlimited at $124.95.

That’s about $573, before any paid SEO tool. Free plugin versions bring it down. Still, $373.95 of that is plugins the plan line says it replaces.

The licences are the small part. Build on ACF today and you may have rework when you move to the built-in fields. Build on those fields and you’re on what EtchWP’s own docs call a playground. Quote a client on a lighter stack, counting on those plugins going away, and that undated roadmap is your risk now.

“Will eventually replace” has no deadline. The FAQ does hold one date, for something else: “Etch V1 will be production stable in September 2025”. It’s still up, more than a year later. “Replaces 6+ premium plugins” is partly true at best, in my view, and it should carry the asterisk.