Malcolm Peralty is a long-time WordPress veteran who began using WordPress at version 0.72. After work across blogging, project management, agencies, and time in the Drupal/Acquia world, he joined Pressable as a Technical Account Manager (TAM). The role appealed to him because it aligned with his CMS experience and offered a career path and compensation that made sense.
What a TAM does
A Pressable TAM focuses on long-term strategy, performance optimization, and planning rather than sales or tier-one support. Key responsibilities include:
– Helping customers plan for growth, choose hosting tiers, and evaluate plugins and architecture.
– Acting as an escalation point for complex issues and performing deeper investigations than standard support workflows allow.
– Proactively recommending changes that can reduce resource needs—sometimes even advising a customer to downgrade plans after optimizations, which benefits both the customer and Pressable’s resource allocation.
Platform and performance trade-offs
Pressable runs a proprietary stack called WP Cloud rather than relying purely on public cloud layers like AWS or Google Cloud. Owning the stack lets Pressable make hardware and software choices tuned for WordPress.
Performance needs vary by site type. Simple brochure sites are highly cacheable and are cheap to run. Highly dynamic applications—WooCommerce stores, membership sites, learning platforms—create uncached sessions and require more resources and architectural thought. Common performance pain points include plugin bloat and heavy page builders (Elementor, Divi, Beaver Builder), plus integrations or plugins that break caching and force many uncached PHP workers.
Pressable’s worker model assigns one worker per vCPU—a dedicated lane—rather than packing many workers onto a single CPU. That design favors predictable performance and resiliency under load.
Monitoring, collaboration, and customer education
TAMs review server metrics, identify troublesome sites, and work with customers and WP Cloud engineers to optimize configurations. They walk a line between not being overly prescriptive about hardware and bringing WordPress-specific infrastructure expertise to planning conversations.
A major part of the job is educating site owners. Many choose hosts using single-user speed tests, but hosts must optimize for concurrent traffic. Platforms that feel fast for one user can fail when many visitors arrive at once. Pressable aims to be transparent about caching, resource usage, and plugin choices so performance meets business goals.
Emerging hosting technologies
Among interesting trends Malcolm highlights:
– Browser-based WordPress playgrounds and WebAssembly, which let users try WordPress in-browser and could change onboarding and testing workflows.
– Faster, more reliable database replication and real-time streaming for high availability. Current replication approaches can add latency and risk lost transactions during failovers—especially harmful during high-traffic commerce events.
– Virtual clusters and multi-datacenter setups that behave like a single local server, improving resilience and reducing migration complexity.
– Better logging and actionable insights: current logs are noisy and hard to parse at scale; AI-assisted analysis could surface the most relevant incidents and speed remediation.
AI and the MCP control plane
Pressable is building MCP, an AI-enabled control plane that lets users operate WordPress via natural language. The goal is to let skilled users and agencies run complex tasks—spin up sandboxes, push code, sync production content, or batch-update plugins—using conversational prompts or integrations with editors and tools like VS Code or GitHub.
MCP is API-driven, which makes exposing endpoints straightforward; the tougher challenge is teaching AI what each endpoint does and how to use them safely. MCP will be rolled out in phases, with the aim of enabling AI to perform UI actions with appropriate human oversight.
Guardrails, auditability, and backups
Because AI can take invasive actions, Malcolm emphasizes guardrails and human-in-the-loop confirmations. Pressable keeps hourly database backups and daily filesystem snapshots; core files are symlinked to reduce the risk of destructive edits to core WordPress files.
Audit logs and human-readable change histories are critical. Natural-language prompts can trigger many small edits across themes, content, and settings; clear, searchable logs and rollback capability are essential to understand who changed what, when, and why.
Operational challenges from AI-driven load
AI crawlers and bots can create intense, unusual loads—repeatedly adding and removing cart items, for example—causing many uncached sessions and heavy resource usage. Bots that spoof IPs and user agents can evade simple blocks, increasing bandwidth, CPU, and storage costs (logs and backups).
This raises pricing and fairness questions: who pays for AI-driven indexing and audit storage? Malcolm suggests hosts may need explicit controls—toggles to block AI crawlers and clear pricing or limits for handling AI-induced traffic and storage costs.
Human-first relationships in an AI era
Malcolm expects features to be human-first and then exposed to AI. Agencies and advanced users will adopt AI-assisted workflows earliest, automating repetitive tasks and speeding delivery. Pressable sees AI as a force multiplier, enabling scalability for agencies while letting human support focus on customers needing hands-on help.
At the same time, over-automation can erode trust and the human relationships customers value. Pressable intends to use AI to augment human capabilities rather than replace them.
Practical MCP examples
Possible MCP tasks include creating staging sandboxes, syncing production assets, running security or performance scripts, updating plugins across multiple sites, and generating lists of installations needing attention—triggered by natural-language prompts. AI might also generate themes, CSS, blocks, or plugins on demand, but early outputs will require human review for security and optimization.
Where to learn more
– Pressable: pressable.com
– Malcolm Peralty: peralty.com, LinkedIn, and WordPress Slack communities
Summary
Malcolm Peralty outlines a managed-hosting world where TAMs bridge customer needs and infrastructure, focusing on strategy, performance tuning, and resilience. Pressable pairs WordPress-specific optimizations and a worker-based architecture with plans for an AI-driven control plane (MCP) that will let agencies automate complex workflows via natural language. Key challenges include strong auditability, robust backups, handling AI-induced load, and preserving human trust within more automated processes.