AI's Impact on WordPress Agencies — Matt Schwartz (Part 2)

This is a rewritten summary of the second part of Nathan Wrigley’s Jukebox podcast conversation with Matt Schwartz about how AI is reshaping WordPress agencies.

Who is Matt Schwartz

Matt runs a WordPress agency in Atlanta (since 2011) and builds QA tooling for WordPress forms and checkouts. He focuses on practical, cautious ways agencies can incorporate AI to gain real benefits while avoiding common pitfalls.

Episode focus

This episode builds on a previous discussion. It moves beyond general enthusiasm for AI to concrete strategies agencies can use: linking AI to internal documentation, employing Model Context Protocols (MCPs) to safely bridge systems, building internal tools and QA automation, watching plugin-market effects, experimenting beyond WordPress with low-risk stacks, and managing security, vendor, and reliability risks.

Key takeaways

1) Let AI access your agency brain

• Point AI chat agents at your project management systems, wikis, or documentation so answers are based on your real processes (ClickUp, Asana, internal SOPs).
• This reduces hallucinations and lets AI pull up-to-date, contextual answers that include citations or links back to source documents.
• It’s an easy, low-effort way to bring value from AI without heavy engineering.

2) Model Context Protocol (MCP) and internal guardrails

• MCP is an agent-friendly, open approach to connecting AI with external systems. Think of it as a gatekeeper that knows how to safely map actions to APIs.
• Agencies can build or subscribe to an MCP that aggregates connections (billing, CRM, sites, helpdesk) so employees don’t need individual API keys.
• MCPs also enable role-based guardrails (for example, preventing destructive actions like deleting a site) and centralize control.
• Some SaaS providers already offer hosted MCP-like services; evaluate trust and security before outsourcing credentials.

3) Vibe-coded (one-off) agency tools: pros and cons

• Agencies are experimenting with small, AI-generated internal apps: reporting dashboards, profitability views, time-tracking summaries — generally lower-risk and useful.
• Be cautious about replacing established SaaS (site management dashboards, public-facing tools) with quickly generated internal tools: maintenance cost, errors, and missing error-handling can make that a false economy.
• There’s a rise of disposable, single-purpose tools built for a one-time need. That can be efficient for low-risk tasks, but persistent systems need proper QA, maintenance, and code reviews.

4) QA, checklists, and automation

• AI is useful for producing and running repeatable checklists (e.g., launch and onboarding flows). Claude Skills and similar features let you teach an agent a process and run it reliably.
• Use AI to automate routine, low-risk checks (binary validations like “is noindex set?”), freeing humans to focus on higher-risk judgment items.
• Always decide up front which steps are automated and which require human review; embed that in your SOPs and AI vision document.

5) WordPress plugin market implications

• AI lowers the barrier to producing small utility plugins or one-off solutions, which can depress sales for small plugin authors and reduce incentives for hobbyist contributors.
• Larger plugin makers may consolidate, focusing on defensible, complex products rather than niche one-off plugins.
• There’s a community concern: if small plugin authors and contributors drift away, we lose entry points that sustain the open-source ecosystem and the collaborative culture.

6) Experimenting beyond WordPress

• AI makes trying other stacks or static-site approaches faster and less risky. Agencies are testing alternatives for brochure sites or simple projects (e.g., static frameworks, cloud platforms).
• For some clients, a lighter stack plus AI-driven maintenance/chat may be preferable. But complex sites still benefit from WordPress’s ecosystem and extensibility.

7) Risks and cautions

• Data security: entering keys or client data into AI tools can expose sensitive information. Some vendors treat inputs in ways that make them accessible or reproducible; always check terms and retention policies.
• Overdependence on vendors: tools and pricing can change. Services available cheaply today may become expensive or restricted tomorrow; design processes so you can scale back or switch providers.
• Error handling: AI-generated tools often lack thorough validation and logging. Without careful error handling, edge cases can break things in unexpected ways.
• Human complacency: the low friction of AI can lull teams into assuming outputs are correct. Maintain a human-in-the-loop for critical decisions.

8) Likely outcomes for agencies

• Hiring and roles: routine execution may be automated, reducing demand for junior designers/developers doing repetitive work. Agencies will likely emphasize productised services, strategy, and higher-value roles.
• Productisation: AI can help agencies package repeatable processes into offerings tailored to niches (e.g., plumber-specific site builds), improving margins and predictability.
• Monitoring and QA demand: as AI automates more, investment will increase in monitoring, testing, and tools that validate and observe automated flows.

Practical advice

• Start small: connect AI to internal docs and PM tools first.
• Document an AI vision: decide which tasks should be automated and which require human oversight.
• Secure credentials: use an MCP or similar controlled bridge rather than exposing keys broadly.
• Don’t replace robust SaaS or public tools with quick, untested one-offs unless you plan maintenance and code review.
• Prepare for vendor cost changes: avoid making AI essential in a way that would cripple operations if pricing or features change.

Final thoughts

AI offers real productivity gains for WordPress agencies but needs thoughtful adoption. The best path is pragmatic: pilot internal uses, build guardrails, focus automation on low-risk, high-frequency tasks, and maintain human review where it matters. Agencies that document strategy, secure systems, and invest in monitoring will be best positioned to benefit as tools and costs evolve.

Where to find Matt

Matt participates in agency communities (Admin Bar Facebook group), LinkedIn, and runs CheckView and Inspry. He encourages agencies to experiment cautiously and to document their AI approach before scaling up.