Craft CMS enquiries from Carlisle tend to come in once an install's either drifted along untouched, or something's actually stopped working properly.
Karl's who sorts it, always has been. Expression 37's only ever been Craft CMS and ExpressionEngine, since it started in 2007.
He works out what's genuinely in the install before recommending anything. What follows is usually a fix, an upgrade, or an ongoing retainer.
Where we typically come in:
- Retailers and distributors covering Cumbria and the borders, needing Craft to hold up reliably across a genuinely wide catchment.
- Agricultural trade businesses whose pricing and content shifts with the farming calendar.
- Logistics firms tied into the M6 corridor, where a site going down has consequences well past the local area.
- Businesses taking payments through Stripe across a large trading region, needing someone who understands the checkout as well as the CMS.
- Owners whose site has simply outgrown its current level of care and want that properly addressed rather than patched around.
How a typical engagement starts:
Regional pressure tends to be the trigger: a busy farming trading period exposing cracks, a delivery zone rule that's stopped working correctly, or a routine scan turning up outdated plugins. Karl looks at the actual Composer setup and codebase before saying anything about cost, and clients covering this kind of geographic spread tend to want ongoing cover rather than a one-off fix.
Common questions Carlisle clients ask:
Can you actually support a site this spread out if you're not based here?
Geography doesn't really factor into how the work gets done, it's all remote regardless of catchment size. What matters more is understanding the regional logic built into the site, which comes from a proper review, not proximity.
Our site covers a huge area with different rules by region, is that unusual?
Not for Carlisle. It's typical of businesses trading across this border region, and it's exactly the sort of custom logic that gets missed by anyone unfamiliar with how the site was actually put together.
Our trade volume follows the farming calendar closely, does that matter for support?
It changes the timing of what gets checked. Pricing accuracy and load capacity get reviewed ahead of known busy trading windows rather than treated as a constant, year-round concern.
How much of a concern is an old Craft version for a site like ours?
The scale of the site actually raises the stakes, an outdated install with regional logic built on top is harder to safely patch the longer it's left, so it's worth addressing sooner rather than later.
Is Stripe something you'll look at, or only the Craft side?
Both, since the two are rarely separable in practice, the checkout logic usually lives inside the same templates as everything else on the site.
What would this cost us?
Depends what's needed, a scoped piece of work gets a fixed number, ongoing cover runs as a monthly figure. Either way it's set before anything begins, not billed after the fact.
Where do we go from here?
Send over what the site currently covers and what's brought you to ask, and you'll get a clear, honest answer on what's actually involved.
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.
