Alan Kingston runs Noble Mortgages, a mortgage and insurance brokerage. When he first came to us, he had no website. His business ran on word of mouth, referrals, and a WhatsApp number.
Potential customers searched his name online and found nothing. Referrals from existing clients had nowhere to send people for more information. Alan needed a web presence that matched the quality of his service.
The first build
We built the first Noble Mortgages website in React with CSS Modules. The site gave Alan a homepage, a services section, a mortgage calculator, an about page, and a contact form with WhatsApp integration.
The design used Alan's existing brand colours: a teal and dark colour scheme that he wanted to keep. The layout was mobile-first. The contact form connected directly to his WhatsApp so enquiries arrived on his phone without delay.
The site went live and started generating enquiries in the first week. Customers who had been referred to Alan could now search his name, find a professional website, and reach out through the contact form or WhatsApp button.
Coming back for a rebuild
Six months later, Alan came back. The site was working. Enquiries were steady. But the web moves fast, and the technology we had used in the first build had room to improve.
The original React and CSS Modules setup worked but lacked server-side rendering, automated SEO tooling, and the performance advantages of a framework like Next.js. Alan wanted the site to rank higher on Google for mortgage-related searches in his area.
The rebuild
We rebuilt the entire front end in Next.js 14 with Tailwind CSS.
The same teal and dark colour scheme. The same brand Alan wanted from the start. The execution changed.
Server-side rendering replaced client-side rendering. Pages load faster because the server sends fully rendered HTML instead of waiting for JavaScript to build the page in the browser.
Tailwind CSS replaced CSS Modules. Styling is now consistent across every component, responsive breakpoints are handled in the markup, and the stylesheet is smaller because unused styles are automatically removed.
We added a custom admin dashboard so Alan can manage his own content. FAQ questions, lender logos, mortgage products, and page copy are all editable from one interface. No developer needed for day-to-day updates.
Structured data was added to every page. LocalBusiness schema on the homepage. Service schema on service pages. FAQ schema on the contact page. The site is now readable by Google and AI search engines.
The admin dashboard
The dashboard has four sections. Page Content for editing hero text, section headings, and the about page. FAQ for adding, editing, deleting, and reordering questions. Lenders for managing the partner logo carousel. Products for editing mortgage and insurance product descriptions.
Alan logs in, makes a change, and it appears on the live site. No CMS subscription. No WordPress plugins. No third-party dashboard with features he does not use.
Results
The first website proved the concept. A mortgage broker with no online presence started receiving enquiries from day one. The rebuild raised the standard. Faster load times, better SEO, content management, and a site structured for both Google and AI search.
When a client comes back for a rebuild, the first site did its job. The second one builds on what worked and fixes what did not.