One person, thirty-plus sites.

A national treatment network that lived on phone calls, with a growing set of WordPress sites carrying paid traffic and nobody who owned the whole stack. I took it on end to end and ran it alone for three and a half years.

The situation

A national treatment network is a business that lives on the phone. Its websites exist to make the phone ring, paid campaigns point at those websites, and every hour a site is down or slow is an hour of intake that does not happen.

When I took the role in 2022 the network had a growing set of separate WordPress sites, more than thirty by my count, carrying that paid traffic. There was no dedicated infrastructure under them and no single owner of the stack: hosting, certificates, backups, caching and the integrations behind the forms and phone numbers had each grown up on their own.

Taking ownership

I took ownership end to end. The first move was infrastructure: a dedicated Linux server under Plesk, with every property migrated onto it, so there was one place to look when something went wrong and one place to apply a fix.

On that server I standardised the three things that fail quietly across a fleet of sites. SSL, so no certificate on any property could lapse unnoticed. Backups, on one schedule with one restore procedure. Caching, so the sites carried campaign traffic without each one being tuned by hand.

With the platform stable, I led rebuilds of the flagship sites, the ones the campaigns pointed at hardest.

The stack

• WordPress on PHP and MySQL for every property, because that is what the network had and what its marketing team could work in.
• A dedicated Linux server under Plesk for the fleet, with DNS and certificates managed in one place.
• Salesforce as the system of record for leads.
• CallTrackingMetrics on the phone side, so calls were data rather than a ringing handset.

Every call to a page

The integration that mattered most to the business was attribution. I wired Salesforce and CallTrackingMetrics into the sites so that marketing could attribute every call to a page: which property, which page and which campaign produced the inbound call that became a lead in the CRM. That turned the site count from a maintenance burden into something the marketing team could reason about, campaign by campaign.

Three and a half years

One person ran the entire platform, sites and servers, for three and a half years. That span took in redesigns, campaign launches that changed what the sites had to handle, and the 2 a.m. outages that come with being the only owner of a stack that makes the phone ring.

Result

Continuous single-person ownership of a fleet of more than thirty production WordPress sites and the infrastructure under them, from 2022 to 2025. The figures on this page are my own account of the work; the dates are on the record. The same rule, that a figure the evidence cannot support is labelled rather than asserted, runs through the Trading Cockpit case.

Evidence and limitations

The client has not yet cleared publication, so this page names neither the network nor its properties, and it shows no screenshots. The dates are consistent across my record and barbagallodigital.com. The site count is my own, with no external corroboration, and is labelled that way wherever it appears on this site. No uptime, traffic, conversion or call figures were recorded for publication, so none are claimed.

If the client clears publication, this page will add the name, two or three property URLs, and a redacted inventory of the server and its sites.