Fred Campos has been building websites in the Dallas-Fort Worth area since 2010. His agency, DFW Website Designers, hosts what it builds, which by 2026 meant around 550 client websites and, less obviously, six servers he was personally responsible for keeping alive.
He is now on one. This is how that happened, and what it changed.
The challenge: six servers, and one that stayed down for three days
The sprawl was not a design decision. Five of the servers were at A2 Hosting and one at GreenGeeks, and each had a hard ceiling that had nothing to do with disk space.
“We had to limit to 100 clients per server because speed would be a huge problem.”
A hundred clients per box meant a new box roughly every year, and each one arrived with its own updates, its own patching and its own capacity to fail independently. Growth did not get easier as the agency got bigger. It got heavier, and it arrived as a bill and a weekend. By the time Fred started looking around he was preparing to buy a sixth server and, in his words, “managing five servers as I was about to buy a sixth was beginning to be time consuming”.
Underneath the arithmetic was a support problem. Getting a reply “in a day or two was the norm”, on a good day. Four or five client sites were being hacked each year with, as he puts it, no server help. Backups were “inconsistent and missing”, with no fast or organised way to restore one.
None of that is what ended the relationship. A single incident did.
“We had a server crash affecting 100 clients. It took A2 Hosting three days to fix. No urgency. It was at that point I knew it was time to look for another company.”
A hundred businesses offline for three days, and an agency in the middle of it that could not fix the problem and had nothing to tell anyone except that somebody else was working on it. The outage was not DFW's fault. That made no difference at all to who had to answer for it.
The solution: why DFW moved to FastCow
Moving 550 live client sites is not a decision an agency takes lightly, and Fred's hesitation was not really about hosting. It was about the two costs he could already see.
“I was very worried about two things. How am I going to find additional time to do this? And second, I was sure there would be a lot of client downtime.”
Both are rational. An agency owner who has just spent three days apologising for someone else's outage has every reason to assume that moving 550 sites will produce more of the same, and the time cost is real no matter who does the work.
So our engineers did the work. Every site was audited, batched by risk and moved by hand, with the awkward ones given their own window. What Fred noticed was not the migration technique. It was the spreadsheet.
“Migration went great, and the most surprising part was the FastCow staff created a spreadsheet and did almost all of the work during the conversion.”
That is less mundane than it sounds. At this volume the audit is the migration: which sites are transactional, which carry custom cron jobs, which have DNS records that need their TTL dropped days in advance, which can move in a batch of twenty and which need a maintenance window of their own. Get that right and the moving is mechanical. Skip it and you find out the hard way, 550 times.
The results
1. Six servers became one dashboard
The clearest change is also the simplest to state. The annual ritual of buying another server, provisioning it and dividing clients across it is gone.
“When you are managing and scaling, I was always having to buy a new server each year,” Fred says. “Now we have one, one dashboard, and I can add without worrying about server loads or buying a new server.”
2. Support measured against a clock, not a calendar
This is the change Fred leads with, and the one he says he cannot put a number against because the two situations are not comparable. A day or two for a reply has been replaced by a ticket system and, for anything urgent, a shared Slack channel.
“Support, oh my goodness. On a good day, getting a response in a day or two was the norm. With FastCow we have a fast ticket system, and for emergencies we have a Slack channel with instant help.”
3. Speed stopped being the ceiling
The 100-client cap existed because performance degraded as each server filled. That constraint set the shape of the whole business: how many clients could be onboarded, how often a server had to be bought, how much of Fred's week went on capacity planning rather than design work. Removing it removed the planning as well as the limit.
4. Backups that restore
Inconsistent and missing backups with no organised way to restore them is a risk an agency carries on behalf of every client it hosts, usually without those clients knowing. That risk now sits with the platform rather than with Fred.
5. A supplier became a partner
The improvement he rates highest is the one that resists measurement entirely.
“FastCow is a partner with real people, and advice and help on all aspects of our website business. Previously I was lucky if I ever talked with a human.”
Which shows up, in the end, somewhere other than a metrics dashboard: “I don't worry. I have a partner. I sleep better at night not having to wake up and see websites down. I ask myself, why didn't I do this sooner?”
Asked whether he would recommend it to another agency hosting client sites, his answer is aimed squarely at agency owners who think this problem is just part of the job.
“Trying to manage the infrastructure of upkeep, updates and load levels is not the focus of your job. Even if you think you have managed servers, you have no idea the power of outsourcing and scaling. Not only are their prices competitive, the amount of money in time management down the road and peace of mind is priceless.”
What Fred told us to fix
We ask every customer what we should do better, and we publish the answer. Fred's is a fair hit, and it is about the thing he otherwise rates highly.
“The FastCow dashboard for clients is 10X better than the traditional cPanel that most clients are familiar with. I really like it and it is much less geeky. That said, because cPanel has been the standard for so long, more videos on 'cPanel stuff was here and now it's here on FastCow' would be helpful.”
He is right, and it is a gap we had framed the wrong way round. An agency arriving from cPanel is not learning a control panel from scratch. It is translating one it already knows, and a tour of a new interface is no help with that. Those are different problems and they need different documentation. We are building it.
About DFW Website Designers
DFW Website Designers builds custom WordPress websites and provides SEO, hosting and ongoing support for small businesses across the Dallas-Fort Worth area. The agency has been going since 2010, and its own figures put it at more than 1,250 clients, with 15 agencies white-labelling its work. You can find them at dfwwebsitedesigners.com, or call them on (817) 247-6003.
If you run an agency and any of this sounds familiar, our guides to migrating a client portfolio without downtime and reseller versus agency hosting cover the two decisions Fred made, and agency hosting is the plan his sites run on.