Most Craft CMS enquiries out of Plymouth involve an install that's either running fine but neglected, or one that's stopped working with the previous developer unreachable.
Karl handles it from start to finish, always has. Craft CMS and ExpressionEngine are the only two platforms Expression 37's worked in since 2007. You're dealing with him, not a team.
He reviews what's actually in the install before quoting anything. That's usually a fix, a version upgrade, or an ongoing retainer.
Why does July matter more than the rest of the year for a Plymouth site?
Because a lot of the local economy, the naval dockyard at Devonport, the fishing fleet, the tourism trade built around the Sound, runs on a completely different rhythm to an average UK business. A Craft install can sit fine and unremarkable for eleven months, then get properly tested the one week the summer crowds actually arrive. Enough of these sites were built years back that whoever set them up has since retired, moved away, or simply gone quiet.
Karl works with Plymouth businesses wherever that's left the install: a pre-upgrade audit, a full takeover when the original developer can't be reached, or a standing retainer for anyone who'd rather have someone watching than find out about a problem by accident. Nothing gets priced without reading the actual code first.
Common questions Plymouth clients ask:
Summer traffic properly stresses our site, does that change your advice?
Quite a bit. A site coasting through winter and getting hit hard every July needs its hosting and slow pages checked in the spring, not patched up reactively on a Saturday in August once it's already fallen over.
Not being on the ground in Plymouth, is that a real limitation?
Barely comes up. Every stage happens remotely and holds up fine. If a conversation face to face is ever actually useful, getting down here isn't difficult.
Whoever built this has vanished, is that a dealbreaker?
Not even close. It's a common enough starting point that it barely counts as unusual. The plugins, the customisation, whatever's genuinely bespoke, all of it gets worked out from the code itself rather than guessed at.
Should the age of our Craft version worry us?
Less than most people assume. The platform itself tends to keep running. It's the plugins riding along on top, and Composer dependencies nobody's touched, that eventually cause the actual grief.
What's actually different between a fixed job and ongoing support?
A fixed job is scoped, priced, and done. Ongoing support means priority when something breaks and someone already familiar with your setup, useful if the alternative is scrambling to find a developer cold every time an issue turns up.
How does someone actually get started with you?
A short call about where things stand and what's prompted the enquiry. Enough for an honest read on what's involved, before either side commits to anything.
The install this usually turns out to be:
A tourism or visitor-facing business with a hard seasonal swing, where a slow site in July costs actual bookings, not just traffic. A marine or maritime supplier whose site needs proper technical specification content, not brochure copy dressed up as such, sometimes with Salesforce handling the commercial side and needing the same standard of care. A site left behind entirely when a small agency or freelancer stopped trading, no record of what's installed or why. Several major Craft versions behind, needing a proper plugin-by-plugin pass before anything's touched.
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.
