Lincoln's Craft CMS enquiries usually take one of two forms: an install ticking along neglected, or one that's genuinely broken with whoever built it long gone.
Karl's who handles it, on his own. Craft CMS and ExpressionEngine are the only platforms Expression 37's ever worked in, since 2007. There's no account manager in the way.
The install gets a proper look before anything's recommended. Depending on what's found, that's a fix, an upgrade, or an ongoing retainer.
Where we typically come in:
- Agricultural and agri-tech businesses running dealer catalogues or trade information on Craft.
- Engineering firms with a site built for a specific technical purpose years back and left running since.
- University departments and research groups needing content structures that hold up to real scrutiny.
- Businesses selling equipment or trade goods through Stripe, needing a developer across both the Craft build and the payment flow.
- Teams who inherited a site rather than built it and want it properly explained before they're responsible for it.
How a typical engagement starts:
Someone new to a role finding an unexplained Craft install is a common trigger, as is a specific problem: a dealer catalogue showing wrong pricing, a security scan flagging outdated plugins. Karl audits the actual codebase and Composer setup before quoting, and a good number of those audits become ongoing monthly support.
Common questions Lincoln clients ask:
Is it a problem that you're not based in Lincoln?
Not really, no. Support happens remotely throughout, code review, deployments, ongoing fixes, and Lincoln's reachable enough for the rare occasion a visit genuinely helps.
Nobody here knows how the site was originally built, is that a common situation?
Very common in Lincoln specifically, plenty of sites were built years ago by someone no longer involved. Mapping out what's actually there is a standard first step.
Our content needs to stand up to genuine academic or technical review, does that shape your approach?
Yes, structure and accuracy get extra care wherever content carries real institutional or technical weight, rather than being treated like a standard marketing page.
How far behind on Craft is genuinely risky for us?
Security first, regardless of version. Beyond that, older installs tend to run into plugins that have stopped being maintained, and that's the real issue once an upgrade's due.
Would you support the payment side of our dealer site too?
Yes, it's usually built directly into the Craft templates, so proper support covers the CMS and the payment flow together.
How is pricing worked out?
Fixed cost for scoped project work, monthly retainer for ongoing cover, agreed before anything starts.
What's a good first step?
A short call about the site, its Craft version, and what's actually prompting the enquiry.
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.
