The question I get asked most often by business owners is some version of: what will this cost? It’s a fair question, and the honest answer is that it depends on things that are specific to your site. But there’s enough of a pattern to give you a useful framework.
Support for an existing ExpressionEngine or Craft CMS site typically works in one of two ways: ad-hoc work billed by the hour or project, or a retainer arrangement where a set amount of support is available each month for a fixed fee.
Ad-hoc is fine for sites that don’t change much and don’t need frequent attention. You pay for work when it’s needed. The downside is that when something urgent comes up, you’re starting from scratch in terms of context, which adds time and cost.
A retainer works better for sites that are genuinely business-critical. The developer knows the site, is available when needed, and handles routine maintenance as part of the arrangement. The cost is predictable, and you’re not scrambling to find someone when something breaks.
The complexity of the site. A straightforward brochure site with a few channel entries and a contact form requires much less ongoing work than a site with multiple channels, complex relationships, third-party integrations, and custom addons.
How much the site changes. A site that’s updated regularly requires more attention than one that’s essentially static. Content changes, new features, and design updates all require developer time.
The current state of the site. If you’re taking over a site that hasn’t been maintained properly, there’s usually remedial work to do before ongoing support makes sense. Getting the site into a maintainable state has a cost that’s separate from the ongoing support cost.
This is the part that most business owners don’t factor in. A site without ongoing support gradually drifts further behind on security patches, PHP compatibility, and addon updates. When something eventually breaks, the cost of fixing it is significantly higher than it would have been if the work had been done incrementally.
A server PHP upgrade that breaks a site that’s three versions behind EE and running outdated addons is an expensive emergency. The same situation on a properly maintained site is a planned upgrade that takes a fraction of the time and cost.
A proper support arrangement for a business-critical ExpressionEngine or Craft CMS site should include regular monitoring, security updates when they’re available, proactive communication about anything that needs attention, and responsive support when issues arise. It shouldn’t be purely reactive.
If you’re currently without support for your EE or Craft site and you’re not sure what’s involved, the starting point is usually a one-off audit. That gives you and any prospective developer a clear picture of where things stand and what’s needed.
Related Services
Related Case Studies
A meaningful part of the work we do at Expression 37 involves inheriting Craft CMS sites that were built by developers or agencies who are no longer involved. The circumstances vary, but the practical challenge is always similar: a site you didn’t build, with code you didn’t write, and decisions that were never documented.
If your Craft CMS site connects to any external service, whether that’s Stripe for payments, HubSpot or Salesforce for CRM, or Mailchimp for email, you have a dependency that you probably don’t think about until it fails. Integrations break. Here’s why they fail and what to do about it.
Craft CMS has a strong but relatively specialised developer community. The difference between someone who has built seriously with Craft and someone who has touched it once or twice is meaningful. If your site runs on Craft and you need ongoing development or support, knowing what to look for matters.
Most clients come to us when their site has started to feel like a risk rather than an asset. Whether the agency relationship has ended, an upgrade has been delayed, or the site has simply grown beyond what it can handle, a conversation costs nothing.
Get in touch with KarlTrusted by established businesses and growing brands across the UK
Expression 37 works with a small number of clients at any one time. These are some of them.
Karl is the founder of Expression 37 Ltd and has been working exclusively with ExpressionEngine and Craft CMS since 2007. In eighteen years he has supported more than 80 clients across the UK, from long-term retainer arrangements to emergency rescues when something has gone wrong at the worst possible moment. Every piece of work is handled personally by Karl, with no account managers or junior developers between you and the person doing it.
Find out how we workOur ExpressionEngine website had been running on an outdated version for some time and we knew it needed attention, but finding someone with the right expertise to handle it properly was a concern. Expression 37 assessed the site thoroughly, explained exactly what was involved, and carried out the upgrade with no disruption to our business. The site has been noticeably more reliable since, and having ongoing support in place means we know any issues will be dealt with quickly. Straightforward to work with and clearly know what they are doing.
James Dawber - Managing Director
Dawber Williamson