Where this tends to matter in Colchester is a site that was set up well once, then handed nothing more than the bare minimum for years.
That's the gap Karl fills. Working only in ExpressionEngine and Craft CMS since Expression 37 started in 2007, and it's Karl on every job, not a team.
The site gets a proper review before anything's recommended. That turns into a fix, a version upgrade, or a retainer, depending on what it needs.
Where this tends to matter:
- Retailers and hospitality businesses whose site needs to hold up during the town's busier trading periods, not just cope on an ordinary week.
- Firms with HubSpot or CRM connections wired into the site by a developer no longer around to explain the setup.
- Businesses whose previous agency stopped taking on ExpressionEngine work, leaving a site that's technically live but nobody's actively watching.
- Installs several major versions old, where the honest work in an upgrade is checking every add-on individually first.
How a typical engagement starts:
Karl won't quote anything until he's gone through the templates and add-ons directly, since these handovers rarely arrive with documentation worth relying on. Most people get in touch after something specific: an integration that's stopped syncing properly, a security notice nobody's acted on, or a decision the site can't keep running unsupervised. From there it's a defined project or an ongoing retainer, agreed before anything starts.
Common questions Colchester clients ask:
Does it matter that you're not based in Colchester?
It doesn't come up as an issue. Reviews, deployments, testing, all of it happens remotely, and Colchester's rail link to London means a face-to-face visit is easy to arrange the rare time it's actually worth having.
Can you take over a site the previous agency's walked away from?
Regularly, yes. Before anything gets touched, the priority is understanding what's genuinely bespoke work versus a repurposed add-on, which only comes from reading the codebase properly.
Is an old ExpressionEngine version something we should worry about?
Less than most assume. The core software rarely causes issues by itself. The real exposure is in whatever add-ons have been left unmaintained alongside it.
Do you handle the CRM or integration side too, or just the CMS?
Both. Those connections are usually wired directly into the templates, so treating the CMS and the integration as separate problems tends to be exactly where things get missed.
What does an ongoing retainer actually include?
Faster turnaround on anything urgent, someone keeping an eye on the site rather than waiting for it to fail, and continuity: you're not re-explaining the setup to a different person each time something needs doing.
What's the likely cost?
A one-off job gets a fixed quote once the scope's clear. Retainers are billed monthly at a rate agreed in advance, no surprises either way.
Ready to get started?
If your website is business-critical and needs a specialist who will take proper long-term ownership of it, get in touch. Karl will respond personally and give you an honest view of how we can help.
