Malcolm Peralty joined the Jukebox Podcast to walk through his two-decade journey with WordPress and his current work as a Technical Account Manager (TAM) at Pressable, a managed WordPress host. He started with WordPress 0.72 as a blogger, moved into project management and agency work, spent time in the Drupal/Acquia world, and returned to WordPress when Pressable presented the right opportunity.
Role and responsibilities
Malcolm’s TAM role focuses on long-term strategy and technical advisement rather than sales or break/fix support. He helps customers plan for growth, choose appropriate hosting tiers, pick plugins and themes with an eye toward performance, and design migration or optimisation strategies. TAM duties include pre-sales guidance about which plan suits a site, custom tuning during migrations, and acting as an escalation point for issues that exceed standard support timeboxes.
Pressable’s approach is often proactive: TAMs identify sites that are burning resources, recommend optimisations, and sometimes advise customers that they can downsize tiers after improvements—benefiting both customers and Pressable’s shared WP Cloud pool.
WP Cloud and infrastructure choices
Pressable runs an in-house WP Cloud stack rather than relying entirely on third-party clouds. That gives the team control over hardware, configurations, and tighter feedback loops between TAMs and infrastructure engineers. Malcolm notes that many WordPress trade-offs come from plugin and theme complexity: page builders, LMS plugins, and WooCommerce setups often produce uncachable, session-heavy traffic.
A notable design choice is Pressable’s worker model: one worker per vCPU (a dedicated “lane”) instead of the high oversubscription some hosts use. That can give more predictable behaviour for uncached workloads, although it comes with cost and capacity considerations.
Performance, caching, and customer education
For brochure-style, highly cacheable sites, standard tiers usually require minimal intervention. The real challenges are uncached, session-based sites—ecommerce, learning platforms, and dynamic applications—where pages are built per request and require more planning and resources.
Competing hosts can mask inefficient code or architecture with aggressive caching or very fast hardware, which misleads customers running isolated tests. Under real-world load, differences in resilience and resource management become clear. Much of the TAM’s job is to educate customers on trade-offs, plugin behaviours that break caches (for example, specific Facebook or WooCommerce integrations), and ways to move toward cacheable patterns or more efficient stacks.
Emerging infrastructure trends
Malcolm highlighted several technical directions gaining traction:
– WebAssembly experiments that enable novel hosting or in-browser WordPress experiences.
– Better caching and database replication techniques; current replication models can add latency and risk lost transactions during failover for high-volume transactional sites.
– Virtual clusters and multi-datacenter setups that make geographically distributed infrastructure appear local, reducing sync and migration complexity.
– Usable, efficient auditing and logging that track who changed what without exploding storage or overhead.
The MCP: AI-powered control panel
Pressable is building an MCP—Managed Control Panel—a natural-language, AI-enabled interface that exposes control-panel APIs so operators can ask for actions in plain English. Examples include spinning up sandboxes, syncing files and databases from production, rolling out plugin updates across many sites, or summarising which sites need attention.
The vision: let users prompt the MCP from an IDE, CLI, or voice transcription to create a sandbox, push code and content, and get back a testing URL; or ask for a list of sites with a specific plugin and have the MCP apply vetted updates. The rollout will be phased and intends to make any control-panel action possible via AI while keeping guardrails in place.
Guardrails, backups, and auditability
Safety is central. Malcolm stresses confirmations for destructive actions, robust backups (hourly database, daily filesystem where appropriate), and filesystem protections to avoid accidental core deletion. Audit logs and step-by-step records are essential to review and reverse automated sequences.
He recommends human-in-the-loop checks for hazardous operations, system prompts requiring explicit confirmation, and clear audit trails so AI-initiated actions can be inspected later. Malcolm expects workflows that are human-first with AI as an assistive layer—features designed for people, then enhanced with automation.
Operational, business, and security implications
AI-driven workflows will reduce time-to-delivery for agencies by automating sandbox creation, theme and configuration setup, and repetitive tasks. Pressable anticipates early adoption from agencies and scale operators managing tens to thousands of sites; single-site owners are less likely to need full MCP automation.
There are cost and scaling concerns: auditing AI actions, storing logs and backups, and handling extra bot-driven or AI-driven crawling all add resource costs. Hosting providers must decide how much of that to absorb and how much to bill back to customers.
Malcolm shared a real example of an AI-driven bot that repeatedly added and removed products from carts, generating millions of uncached sessions in one day. Blocking it was only temporarily effective; it reappeared from new IPs and user agents. Hosts will need better detection and policy tools to manage bot-driven traffic and clarify who pays for the extra load.
AI-generated code and maintenance
AI can produce themes, plugins, or CSS quickly, but early outputs may lack performance optimization or secure practices. Malcolm foresees a future where AI helps maintain AI-generated artifacts, but that path requires careful validation and ongoing scrutiny to avoid accumulating technical debt or security issues.
Human relationships and the future of support
Malcolm and Pressable advocate human-first principles: AI should augment human workflows and free support teams to focus on customers who need hands-on help, not replace the trust built through high-touch relationships. While some vendors may market “no AI,” AI-enabled tooling will be necessary to remain competitive on speed and scale when implemented responsibly.
Contact and summary
Pressable is positioning itself as a WordPress-specialised host tackling modern challenges: predictable performance for both cacheable and dynamic sites, in-house WP Cloud with a one-worker-per-vCPU model, and a careful move toward AI-enabled control through the MCP. Key themes are customer education, robust backups and auditability, managing bot-driven costs, cautious AI rollouts with human oversight, and the need for better replication and virtual cluster technologies to increase resilience.
Pressable: pressable.com
Malcolm Peralty: peralty.com; active on LinkedIn and in WordPress Slack communities.