03 · Track record
Some recent work, broadly speaking.
A flavour of what's been delivered recently. Specifics (businesses, numbers, the lot) are kept off the page on purpose; they belong in a real conversation about your situation, not a marketing pitch about mine.
Recent · Holiday park
A full systems relaunch, in a single day
New booking system, revenue management brought in-house, new website, new payment provider, new marketing strategy, all live on the same morning. The kind of project most operators put off for years because of how risky it looks. Done without losing a booking.
In-house
Recent · Same site
Direct booking mix, rebuilt from scratch
By taking pricing in-house and rewiring distribution, the share of revenue coming from direct bookings shifted significantly in a single quarter. The kind of change that usually takes operators a year or more, and the basis for renegotiating a long-standing commission contract.
Direct first
Recent · Pricing
A dynamic pricing engine, built in-house
A pricing model built from scratch to replace an agency's rate sheet: unit-grade and whole-park occupancy, a point-based weighting system to balance value across accommodation types, seasonal week scoring, and stay-length weighting. It reacts to booking patterns faster than the old model ever could.
Built in-house
Ongoing · Apps & tools
Small apps that replace big admin
Purpose-built working tools rather than software subscriptions: guest-facing apps, order-at-table with kitchen screens, revenue and commission calculators, cash-up and banking apps, plus HR and staff productivity tools that take the friction out of rotas, tasks and handovers. Each one built around how the team actually works, and documented so it keeps running.
No subscriptions
Recent · Websites
Two websites, designed, built and maintained in-house
A restaurant site with menus, promotions and reservations wired straight into the booking system, and a destination guide built to pull search traffic and convert it into direct bookings. Both designed, written, built and hosted without an agency, and both maintained as the businesses change rather than left to rot.
Direct traffic
Ongoing · Stock
Wet and dry stock, counted and explained
Regular bar and kitchen counts across a restaurant and a holiday park, with GP by category and variance reporting that actually gets read. The counts caught the pricing errors, the pour issues and the supplier mistakes that a till report never will, and gave the team par levels and a routine they could keep running themselves.
Counted properly
Ongoing · Multi-site
IT & infrastructure, kept in-house
Cloud accounts, devices, remote access, plus the physical layout of WiFi and network across the site. The kind of work that gets quietly outsourced for a steep monthly fee, or done properly in-house for a fraction of that.
No outsource
Earlier · Restaurants
Restaurant booking systems, more than once
Multiple restaurants moved between booking systems (data, table layouts, integrations, payments) without losing a service. Different domain, same migration discipline.
No downtime
Always · Everywhere
Documented, so it survives me leaving
Every system, process and tool above comes with a written handover: what it is, how it works, what to do when it breaks. The test of good work isn't whether it runs while I'm there. It's whether it still runs six months after I've gone.
Build to leave