Production notes on AI systems, WordPress infrastructure, and SuperControl websites. No fluff, just signal.
Sync property data, ask SuperControl for live dates, and hand off to checkout with a calendar that belongs to the theme — not an embed.
Dated templates and bolted-on calendars are not a reason to rip out the PMS. Keep SuperControl. Rebuild the public site around it.
Use AI to inventory plugins, map ACF groups and draft a cut list. People still do the rebuild. Generators do not reduce plugin debt.
Most WordPress AI plugins are demos. Production AI on WordPress runs off the public request, behind a human, with a cost cap and an owner.
Treat WordPress MCP like WP-CLI: a small role, a small catalogue, staging first, and logs. Prompts are not access control.
Model Context Protocol is a tool interface for WordPress, not a chatbot plugin. Use it for inspection and local ops, not overnight publishing.
Share one ACF value across selected pages with a source of truth. That is not the same as syncing WordPress between environments.
Renaming or moving an ACF field leaves stored values behind. Treat schema changes as migrations with preview, transaction and rollback.
A lean, high-impact AI development stack for small teams shipping fast without losing quality.
What changes between demo and production when building an internal AI coding assistant.
A practical multi-provider architecture for quality fallback, cost control, and vendor resilience.
How to lock down tool execution paths so AI agents remain useful without introducing avoidable risk.
Tell us what is actually broken. We will suggest the smallest sensible next step.
Nought Digital is happy working with ambitious agencies, SaaS teams, ecommerce businesses, and local operators — especially when the work improves real operations rather than adding noise.
