What tends to bring people in Chelmsford to Expression 37 is a Craft install an agency built and then stopped supporting, left running unattended since.
Karl's the only person Chelmsford clients ever deal with on this. Expression 37's specialised purely in Craft CMS and ExpressionEngine since it opened in 2007.
He reviews the install thoroughly before quoting a figure. Depending on what's found, that's a fix, an upgrade, or an ongoing retainer.
Chelmsford's engineering streak, and what it means for Craft
This is where commercial radio broadcasting effectively started, and that same engineering instinct still shows up in the town's electronics and manufacturing businesses, alongside a growing base of London commuters running their own firms. A fair share of the local sites run on Craft, many built during a period of rapid growth and left largely unmanaged since.
Karl supports Chelmsford businesses whose install has reached that point: a developer no longer taking on Craft work, several major versions behind, or bespoke functionality nobody on staff currently understands. Nothing gets quoted without reading the actual codebase first.
Common questions Chelmsford clients ask:
What's the honest first step in fixing a neglected install?
Reading it properly. Templates, plugins, whatever custom work exists, all reviewed before a single figure gets discussed, because pricing off a description tends to miss exactly the parts that matter.
Is working with someone outside Essex a real drawback?
Rarely in practice. Chelmsford's proximity to London means most local businesses already deal with suppliers and partners further afield, and remote support fits that pattern comfortably.
Nobody currently understands how our site was built, is that common?
More common than you'd think, especially on sites that have changed hands a few times. Untangling it starts with actually opening the codebase, not asking around for institutional memory that may not exist.
How much does the Craft version itself matter?
Less than what's been added around it. An old core install with well-kept plugins tends to be safer than a recent one nobody's ever audited.
What's the real difference an ongoing arrangement makes?
The site gets checked before something visibly breaks, not after. And urgent problems jump the queue rather than waiting behind everyone else's.
What's the general shape of pricing?
A single job is one number, fixed, agreed before it starts. Ongoing work is billed monthly. Nothing happens without that figure being clear first.
What tends to bring people to us:
A manufacturer or engineering firm publishing product or technical data where a mistake genuinely costs something downstream, not just embarrassment. A retailer running Stripe that needs the payment side kept to the same standard as everything else on the site. A business whose agency has simply stopped responding, the site live but unwatched in any practical sense. And an install carrying enough age that every plugin gets checked on its own merits before an upgrade goes anywhere near it.
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.
