Peterborough's Craft CMS enquiries usually mean one of two things: an install that's ticking over unpatched, or one that's genuinely broken with the developer who built it gone.
Karl's the person who works on it, every time. Craft CMS and ExpressionEngine are the only platforms Expression 37's ever touched, since 2007. No wider team stands in the way.
Before anything's recommended, the install gets a proper review. That's usually a fix, a version upgrade, or an ongoing retainer.
Why does supplier data cause more problems here than elsewhere?
Food processing and agriculture drive a big share of Peterborough's economy, alongside a substantial logistics presence along the A1, and Craft was a fairly natural fit for businesses needing to publish structured product and supplier information properly. A lot of those installs got left running once they were built, with nobody circling back to keep them current.
Expression 37 helps Peterborough businesses bring that back under control, an upgrade project, taking over from a previous developer who's stopped responding, or a monthly retainer for anyone who'd rather not wait for the next thing to break. The site gets reviewed properly before anything's quoted.
Common questions Peterborough clients ask:
Product or supplier data needs to be spot-on, is that a normal ask here?
Completely normal given the sector. It starts with the underlying data feed itself, properly checked and mapped, before anything else on the site gets touched.
Does location matter if you're not based in Peterborough?
Not for the actual work. Review, changes, testing, all handled remotely and reliably. A face-to-face conversation is easy enough to arrange if one's ever genuinely useful.
The developer who built this has stopped trading, what now?
That's a common enough starting point. Working out what's genuinely custom against a modified plugin comes down to actually reading the code, not assuming anything from the outside.
Is our old Craft version something to lose sleep over?
Generally not, on its own. The core software tends to be solid. Real exposure sits in whatever plugins and Composer dependencies were added and never revisited since.
What's the practical upside of ongoing support?
Priority when something actually goes wrong, regular check-ins rather than total silence between issues, and someone who already knows the site instead of learning it fresh every time you call.
What are we likely to pay?
Comes down to what's actually needed. A defined project is one fixed figure. Ongoing support is billed monthly. Either way, you'll have that number before agreeing to anything.
Where this tends to matter:
A food or agricultural business whose site holds supplier or product data that has to stay current, since mistakes there have real downstream cost. A logistics firm connecting into scheduling or tracking systems built years back by someone no longer around to explain them. An install inherited from a developer or freelancer who's stopped trading. Someone taking payment through Stripe or tracking leads via HubSpot needs those connections actively watched, since a quiet failure there is easy to miss until it actually costs something. And a Craft install old enough that every plugin needs checking individually before an upgrade's safe.
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.
