I have been doing this for over 20 years. WordPress builds, server management, cloud infrastructure, deployments. Mostly for small and medium businesses.
One question comes up all the time: “Do I need a WordPress person, or a DevOps person?”
For most SMEs, the answer is usually one person who gets both sides. Here’s the lowdown on what it covers and what you can expect to pay.
Why two expertise in one person?
The WordPress side and the infrastructure side are not separate worlds for an SME. Your hosting is your infrastructure. The way your site gets updated is a DevOps problem. When your site goes down, the fix usually lives somewhere across both.
I have seen this play out many times. A client’s landing page was crashing under traffic from a paid ad campaign. Lost spend, lost leads. The problem looked like a hosting issue, then a plugin issue, then a theme issue. It was all three, compounding each other. I rebuilt the page with proper caching, image optimization, and server-side configuration, and the crashes stopped. A WordPress developer without infrastructure knowledge, or an infrastructure person without WordPress experience, would have maybe solved only part of it.
That’s the value of the combination. You get someone who can look at the whole picture.
What the work actually looks like
When SME leaders say they need a “DevOps person,” they rarely mean Kubernetes. What they usually mean is a set of connected needs that fall somewhere between an IT helpdesk and a full engineering team.
On the WordPress side, that typically includes keeping the site fast and up, handling updates and plugin conflicts, security basics like SSL and backups, and occasionally building or rebuilding something.
On the infrastructure side, it’s things like making sure deployments don’t happen by someone FTP-ing files manually, setting up automated backups to off-site storage, basic monitoring so you know about problems before your users do, and having a proper staging environment.
Most SMEs don’t need all of this at once. A good professional will tell you what actually needs doing now and what can wait.
What things cost
This is the part people find hardest to get a straight answer on, so here it is.
Monthly retainer (ongoing management): Basic plugin updates and security checks start around €50 to €100 per month. A real retainer that includes monitoring, automated backups, and actual availability when something goes wrong runs €150 to €350 per month. Watch out for retainers that are just “we’ll update plugins once a month.” That’s a task, not a service.
WordPress build or rebuild: A straightforward site with a good theme runs €1,500 to €3,500. A WooCommerce store with custom integration and performance work sits between €5,000 and €10,000. What SMEs often don’t account for is the ongoing cost after launch. Maintenance, security, and backups typically add €1,000 to €5,000 per year. It’s worth discussing this before you sign anything.
Infrastructure setup or migration: Moving from shared hosting to a proper VPS or cloud setup, with Docker, SSL automation, and backups configured, is usually a fixed-price project between €800 and €2,500 depending on what’s already in place.
DevOps automation: A CI/CD pipeline with GitHub Actions, basic secrets management, and a staging environment for a small team typically runs €1,500 to €4,000. One-time fee is almost always the better structure for this kind of defined project.
Emergency work: Expect to pay a premium for same-day help. The better approach is a retainer with monitoring included. Most of my clients never experience a real emergency because problems get caught early. I usually tell clients their site is down before they even notice it themselves.
What to look for, and what to avoid
A good professional asks about your business before they ask about your tech stack. They want to know what the site does for revenue, what happens when it goes down, and what success actually looks like for you. The technical decisions follow from that.
Ask to see a live site they manage. Check its PageSpeed score on mobile. Ask how it’s hosted and why. Someone who has actually done the work can answer those questions without hesitating.
Documentation matters more than people think. You should be able to move to a different provider without losing anything important. A service provider who doesn’t document their setup is building dependency into the relationship. That’s worth asking about upfront.
Be honest about what you don’t need. A WordPress and DevOps generalist is the right fit for most SMEs, but not for every problem. Complex mobile apps, data engineering, enterprise database architecture, those need a different level of expertise and know-how. Anyone who claims to handle everything with equal skill is probably not the right person for anything specific.
A few things I would treat as red flags:
- A quote with no discovery call. You can’t scope a project properly without understanding the current setup and the business context.
- Hourly-only billing for defined deliverables. For a project with a clear endpoint, a fixed price is better for both sides. Hourly billing on a defined project transfers all the risk to you.
- No mention of backups, monitoring, or documentation in the first conversation. If these aren’t coming up early, they’re probably not part of the workflow.
A few things that have changed in 2026
AI tools have made some things faster and cheaper. Simple sites and standard pipeline setups cost less than they used to because experienced professionals can build them quicker. What hasn’t changed is the judgment part. Knowing which solution fits your situation, and recognizing when a cheap option will create an expensive problem later, still requires experience. You’re paying for that, not for time at a keyboard.
Security is also less optional than it used to be. Clients increasingly expect pipelines with dependency scanning and secrets management as standard, not as an add-on. If a provider’s setup doesn’t include these basics, it’s worth asking why.
WordPress 7.0, released in May 2026, introduced a native AI Client API. It lets WordPress sites connect to AI providers, whether locally hosted or cloud-based, through a built-in interface. This is still early, but it opens up real possibilities for SMEs who want smart features without paying ongoing SaaS costs. A professional who understands both WordPress and AI infrastructure can actually build something useful here.
Before you hire anyone
Whether you talk to me or someone else, these are the questions worth answering first:
- What is the current hosting setup, and who has access to it?
- What breaks most often, and what has it cost you when it does?
- What would “working well” look like in six months?
- Does anyone on your team have technical involvement, or is this fully outsourced?
- What is the monthly budget range you are working with?
If a provider skips these and sends you a quote the same day, that tells you something.
I reply within 24 hours with a concrete plan.