Website & Design
Portfolio
We build on WordPress, Wix, Webflow and other platforms where a client's team needs to make its own changes, and custom websites on Astro and other frameworks where speed and page count matter more. Enquiry tracking is wired in during the build rather than added later.
Websites
Built on the platform that fits — WordPress, Wix, Webflow and others for managed sites, Astro and custom frameworks for performance-first builds. Enquiry tracking is wired in during the build rather than added later.
Looking at a rebuild or a migration? The first call covers what the site would need to do differently, and whether a rebuild is even the right answer.
Talk it throughProblem, build, result
Use cases
Described by the problem rather than by the client. Every one of these started as something the client had not measured.
Enquiries were arriving and nobody was answering them
Enquiry & Sales SystemsThe problem
A published enquiry address was forwarding to a mailbox that had been full for an unknown period. Messages were bouncing silently, and nobody had submitted a test enquiry since the site launched.
What we built
All routes consolidated into a single queue with delivery confirmation, failure alerting, and an owner assigned the moment an enquiry lands.
What changed
Enquiries stopped disappearing. The next time a route broke, it produced an alert the same day rather than silence for a quarter.
The sales team was spending its week on a channel that never bought
Enquiry & Sales SystemsThe problem
One marketplace channel produced high volume and almost no orders. Because nothing filtered it, the team worked every enquiry by hand, and genuine buyers queued behind them.
What we built
An AI qualification layer on WhatsApp that asks what sales needs to know and passes only qualified enquiries into the CRM.
What changed
The channel stopped consuming sales time, and real enquiries stopped waiting behind unqualified ones.
Cost per lead looked healthy, cost per order did not
Campaigns & OutboundThe problem
The ad account was comfortably hitting its cost-per-lead target. Joining enquiries to closed orders showed the cheapest campaign had never produced a single sale.
What we built
Offline conversion import so the platform optimises on revenue, budget moved to terms with order history, and the failing campaign paused.
What changed
Cost per lead rose. Cost per order fell. The client changed which number the monthly review reports on.
Traffic was climbing and enquiries were flat
Web & SearchThe problem
Rankings were improving on terms that turned out to be almost entirely research-stage. The best-performing pages were attracting students and competitors.
What we built
Keywords reclassified by buying intent, the content programme redirected to specification and comparison queries, and the pages pulling the wrong audience rewritten.
What changed
Traffic dipped slightly and enquiries went up. The monthly report stopped being a vanity exercise.
A calling team working across four disconnected tools
Analytics & EngineeringThe problem
Cold calling ran from a spreadsheet, with a separate dialler, a calendar link pasted into chat, and no analysis of the calls beyond how many were made.
What we built
One application: daily priority lists, call tracking and analysis, quality reports per caller, a leaderboard, meeting booking during the call, and automatic WhatsApp and email reminders to the prospect.
What changed
Coaching moved from call counts to call quality, and meetings stopped being lost between the call and the calendar.
Deals were dying on a single contact
Analytics & EngineeringThe problem
Pulling deal and email data showed that opportunities with only one engaged stakeholder almost never closed, and a large share of open pipeline looked exactly like that.
What we built
Prompting inside the CRM when a deal passes a value threshold without a second stakeholder, plus a sequence built to widen the conversation.
What changed
The problem became visible while deals were still live, rather than at the post-mortem.
Looking at a rebuild or a migration?
The first call covers what the site would need to do differently, and whether a rebuild is even the right answer.