We recently delivered a WordPress site with genuinely custom functionality: features tailored to one company's specific workflow, not something you could install as a plugin. The honest part: nobody on the build knew PHP, and we didn't write the code by hand. We described what we wanted, in plain language, and worked with an AI to build it.
This used to be unthinkable. WordPress customization meant PHP, hooks, the template hierarchy, and a stack of conventions you learned over years. Here's what changed, and where it bites.
What We Built
The client needed behavior that didn't exist off the shelf: custom content types, tailored admin workflows, and front-end features specific to how they actually run their business. The kind of thing that normally means either bending an ill-fitting plugin to your will or hiring a dedicated WordPress developer.
Instead, we built it conversationally: describe the feature, get working code, test it on the site, refine. Iterate until it does exactly what the company needs. The result was custom software, in a language we don't write, shipped to production.
How It Actually Went
Faster than it had any right to be, for the straightforward parts. Standard custom post types, fields, and admin tweaks came together quickly, because these are well-trodden patterns the model has seen thousands of times.
The further we got from common patterns, the more the process became a real collaboration. We'd describe intent, read what came back, test it, and feed back what broke. Not "type a prompt and walk away." It was more like working with a fast, knowledgeable developer who needs clear direction and a careful review of their work.
The Catch
Here's the part the hype skips: you cannot fully outsource understanding.
We didn't need to write PHP, but we absolutely needed to understand systems: how WordPress structures content, what a hook conceptually does, why one approach is safer than another, what "this works but it's insecure" looks like. The AI writes the code. It does not own the consequences. You do.
When something broke in a way the model couldn't see, we had to reason about why, and that required real technical literacy, just not language-specific fluency. Vibe-coding without any foundation doesn't get you a custom site. It gets you a fragile pile you can't debug, maintain, or trust.
What It Means for Studios
The skill that matters has shifted. It's moved from syntax (memorizing the exact incantation in a specific language) to judgment: knowing what to build, how to structure it, how to tell good output from dangerous output, and when to slow down and verify.
For a small studio, that's enormous. It means we can take on work in stacks we don't specialize in, as long as we bring strong fundamentals and a careful eye. It does not mean anyone can ship anything. The floor got lower; the ceiling still rewards people who actually understand what they're shipping.
