{"id":14776,"date":"2026-07-30T07:38:38","date_gmt":"2026-07-30T07:38:38","guid":{"rendered":"https:\/\/wpm.si\/?p=14776"},"modified":"2026-07-30T07:38:38","modified_gmt":"2026-07-30T07:38:38","slug":"wpm-modular-ds-case-study-maintenance","status":"publish","type":"post","link":"https:\/\/wpm.si\/en\/wordpress-development\/wpm-modular-ds-case-study-maintenance\/","title":{"rendered":"Scaling WordPress Maintenance: Our Modular DS Case Study"},"content":{"rendered":"

Modular DS has published a case study about WPM<\/a>.<\/strong> It tells the story of how we grew past 100 maintenance clients without growing the team, and what changed after we moved our entire portfolio to a new site management system. We’re proud to be among the first agencies featured in their case studies, and the first one from Slovenia.<\/p>\n

You can read the full story on the Modular DS website<\/a>. Here’s our own take on it, including the part that matters most to our clients.<\/p>\n

Why We Changed Tools in the First Place<\/h1>\n

For years we managed client websites through ManageWP. It worked, until it didn’t scale with us. As the portfolio grew, getting a clear picture of every site’s status took longer than it should have. Performance was inconsistent, the interface felt dated, and we spent time hunting for information instead of acting on it.<\/p>\n

At 100+ websites, that kind of friction adds up fast. “I didn’t have time to wait or search through notifications. I need to trust the tool, and I didn’t trust it anymore,”<\/em> says Jurij Oblak, our CEO.<\/p>\n

We knew we needed something better. What held us back was the obvious problem: migrating a portfolio that size is the project you never quite have time for. Then we met the Modular DS team at WordCamp Europe 2025 in Basel<\/a>, and the timing finally made sense.<\/p>\n

The migration itself turned out to be the easy part.<\/strong> We shared access to our ManageWP account and Modular DS handled the rest in the background. No manual moving of sites, no setup weekends.<\/p>\n

What Actually Changed<\/h1>\n

The biggest difference was transparency. Having a clear, real-time overview of every website we manage makes the whole process easier to control. Less time chasing information, more time on work that helps clients.<\/p>\n

Day to day, our team leans on automatic updates, backups, health and security notifications, and one-click login to any site. Where this shows most clearly is security. We get alerted to risks as they appear, which means we can act before they turn into actual problems. When something like the recent critical WordPress 7.0.2 vulnerability<\/a> lands, the difference between seeing it immediately and finding out later is the whole ballgame.<\/p>\n

For our clients, this mostly looks like nothing happening.<\/strong> Fewer disruptions, fewer emergencies, fewer of those emails that start with “our site is down.”<\/em> That quiet reliability is a big part of why our churn stays below 1%.<\/p>\n

The Numbers From 2025<\/h1>\n

The case study pulled together figures we don’t often put in one place:<\/p>\n

    \n
  • 118 websites<\/strong> managed through Modular DS<\/li>\n
  • 8 hours saved per week<\/strong> on maintenance tasks, a full working day<\/li>\n
  • 25 new maintenance clients<\/strong> added in 2025, with the same core team of 13<\/li>\n
  • 28 websites delivered<\/strong> and 17 new partnerships in the same year<\/li>\n
  • 100% completion rate<\/strong> across 7,653 support tickets<\/li>\n
  • 25% revenue growth<\/strong> year over year<\/li>\n<\/ul>\n

    The point isn’t any single number. It’s that we could take on more clients and more scope without expanding the team proportionally, while keeping the same response times and the same quality of care.<\/p>\n