Technical
WordPress in the AI Era: Still the Right Answer for a Specific Client
Every time I mention WordPress in 2026, someone asks why I do not use a modern stack. The answer is that WordPress is the modern stack for a specific kind of client. Understanding that client saves me hours of bad advice.
The WordPress Client Profile
Non-technical team that will edit content. Budget under 20k USD for a marketing site. Needs to be handed off and maintainable without me. Content-heavy, app-light. Expects a familiar admin.
This profile is huge. Ignoring it costs consultants clients they could serve well.
Why WordPress Still Wins for This Profile
Editorial UX is twenty years of polish. Nothing open source comes close. The client can edit without a developer. The block editor is finally good. The plugin ecosystem solves problems my custom stack would take months to solve.
Where I Use AI in WordPress Work
Theme development: Claude Code generates block patterns, template parts, and style.json entries faster than I would by hand.
Custom blocks: the boilerplate is 80 percent generated, 20 percent custom. An afternoon of work becomes an hour.
Plugin configuration: I describe what I want, Claude produces the JSON config. Done.
Content migration: a Python script reads the old site, transforms to WP REST API, posts in batches. Zero manual entry.
Where WordPress Is Wrong
Apps with real user accounts and business logic. Anything requiring real-time features. Anything where performance is a competitive axis. B2B SaaS with deep integrations. In these cases Next.js plus serverless wins.
The Honest Stack Choice Matrix
| Client Need | Best Stack | |---|---| | Marketing site, content-heavy | WordPress | | Newsletter-first publication | Custom serverless | | Small app with auth | Next.js + serverless | | Enterprise portal | Django + Next.js | | Ecommerce starter | WooCommerce or Shopify |
Reading
The WordPress block editor handbook got great in 2025. Read it before dismissing WordPress.
Right tool, right client. WordPress is still right for a large share of them.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read