Churchill Mortgage

The first job was to replace Churchill's old in-house system with a content management system, or CMS, meaning software that lets non-technical staff create and update pages themselves. Their in-house team gave us the designs as flat graphics, and we built those into working, standards-based HTML that matched what they'd drawn.

A design becoming a website is only half the value, though. The real point was giving Churchill's editors control, so we built a set of bespoke modules and components on top of the CMS. These let the team update the site through purpose-built tools shaped around their content, rather than wrestling with a generic editor. The result was a site Churchill could maintain day to day themselves, which is exactly what they'd been missing with the old system.

A second phase went deeper, and this is where the project grew past a website. Churchill has branches across the country, and staff who sometimes work at more than one of them, which is difficult to keep track of. So we built a Loan Officer Management System: a complex, fully bespoke admin system for managing staff postings across the branch network, including people posted to multiple locations at once. It ties branch pages and staff profiles together and keeps them accurate as people move around.

We also tackled a slow manual process. Checking whether a client qualified for a loan meant a member of staff reading through that client's uploaded documents and working the numbers by hand. We built an AI-powered eligibility checker to do that first pass instead. It reads the documents a client uploads and assesses eligibility from what it finds, while the actual lending decisions stay with Churchill's staff. Automating that step removed over 100 hours of manual work a month, time their people now spend on work that genuinely needs them.