We use cookies to understand how visitors use our site and improve your experience. By clicking "Accept", you consent to our use of analytics cookies. See our Privacy Policy for more details.

Case Studies

Decisions that matter - systems that deliver.

Cases where real business constraints shaped the work, not templates or tools.

Book a discovery call →

Case Study: Chetham Farm

From beautiful venue to fully operational business - with a bespoke booking system at its heart

Why this mattered:

Chetham Farm had a stunning venue and a range of consultancy and wellbeing services to offer, but no formal systems holding the business together. Enquiries were handled ad hoc, bookings were informal, and there was nothing stopping people from simply turning up unannounced. The business needed structure, automation and a professional presence - all built around how it actually works.

The problem

The venue was being marketed without the infrastructure to support it. There was no reliable way to show availability, take bookings, handle payments or communicate with enquiries consistently. She needed:

  • -a single source of truth for venue availability
  • -a way to take bookings and payments online
  • -formal agreements and terms in place
  • -a process to qualify serious enquiries
  • -systems for add-ons, consultancy and wellbeing services
  • -email marketing and a way to grow her audience
  • -a website that reflected the full scope of what she offers

Everything existed in her head. None of it was joined up.

What I built

A website and a bespoke calendar app built specifically around the way Chetham Farm operates - plus the back-office structures to run it professionally.

  • -A custom calendar app that acts as the live availability hub for the whole venue
  • -Separate booking options for the barn, the house, or the full venue - so two events can run simultaneously
  • -Online booking with automatic payment link generation
  • -Automated booking confirmations and reminder emails
  • -Automatic place deductions as bookings come in
  • -Shareable event links for easy marketing of individual events
  • -Third-party event listings with links to external booking systems
  • -Venue hire agreements and terms of use built into the enquiry flow
  • -Add-on options for catering and wellbeing services
  • -Back-office structure for consultancy and wellbeing offerings
  • -Newsletter setup, welcome sequence and lead magnet delivery

Built as an operational system, not just a website.

The result

Chetham Farm now has:

  • -one calendar that runs the whole venue
  • -bookings and payments handled without manual back-and-forth
  • -formal agreements that protect the business
  • -a qualification process that filters serious enquiries from time-wasters
  • -a growing email list with an automated welcome journey
  • -a website that reflects both the venue and her consultancy and wellbeing services
  • -the structures and systems that weren't there before

The business didn't just get a website. It got the foundations it was missing.

The business didn't just get a website. It got the foundations it was missing.

Case Study: Content Engine 52

Solving the "what next?" problem after a website goes live

Why this mattered:

A new website on its own wasn't the issue - the real problem was what happened next. Without a clear content and follow-up strategy, momentum stalled and visibility dropped despite the investment in the site.

The problem

After a website launch, clients kept asking the same question: "This looks great... but what do I actually post now?"

  • -consistency
  • -knowing what to say
  • -tying content back to business goals
  • -keeping marketing moving once the site was live

Great websites were being built. Momentum stalled soon after.

What I built

Content Engine 52, a practical content system designed around real businesses, not marketing theory.

  • -A full year (52 weeks) of ready-to-use content prompts
  • -Blog, social and newsletter ideas aligned to business goals
  • -SEO-aware structure without the overwhelm
  • -Built as a tool, not a course
  • -Designed to plug straight into a live website and marketing flow

No blank pages. No guesswork. No overthinking.

The result

Clients leave with:

  • -clarity on what to say
  • -a consistent content rhythm
  • -marketing that answers "what next?"
  • -a website that stays active, visible and working

The website doesn't just launch. It keeps doing its job.

The website doesn't just launch. It keeps doing its job.

Case Study: Automated Referrals & Back Office

Turning enquiries into paid referrals automatically

Why this mattered:

The business wasn't struggling to attract interest - it was losing time, clarity, and revenue in the handover between enquiry, referral, admin, and invoicing because nothing was properly connected.

The problem

A growing therapy practice relied on manual processes to manage referrals to associate therapists. This meant:

  • -enquiry requests handled by hand
  • -therapists contacted individually
  • -referral fees invoiced manually
  • -admin duplicated across systems
  • -revenue dependent on someone remembering to follow things up

The setup worked, but only just.

What I built

A redesigned website with joined-up systems that handle the entire referral journey automatically.

  • -Website redesign with a clear referral pathway
  • -Embedded smart request form
  • -Automatic notifications sent to the relevant therapist
  • -Referral fee invoice generated and sent instantly
  • -Emails triggered to the client, therapist and practice owner
  • -All invoices logged automatically in QuickBooks

Everything handled through one connected setup.

The result

The practice now has:

  • -a smoother referral process
  • -no manual chasing
  • -no missed fees
  • -less admin behind the scenes

Enquiries turn into paid referrals without anyone managing the process manually.

Enquiries turn into paid referrals without anyone managing the process manually.

Case Study: Custom Fundraising Apps for a Charity

Bespoke tools built around how the charity actually raises funds

Why this mattered:

Off-the-shelf donation tools forced the charity to work around the software instead of the other way round, creating friction for donors and unnecessary admin for the team.

The problem

A charity had an outdated website that wasn't mobile-friendly, wasn't optimised for search, and didn't support how they actually raised money. They needed:

  • -flexible donation options
  • -proper Gift Aid handling
  • -GDPR consent built in
  • -automated communication with donors
  • -a way to accept donations instead of gifts for events and dinners

Off-the-shelf tools didn't fit their needs.

What I built

A redesigned, mobile-responsive website with bespoke fundraising tools built specifically for the charity.

  • -Custom fundraising app embedded into the website
  • -One-off, monthly and annual donation options
  • -Gift Aid and GDPR consent built into the flow
  • -Automated emails sent to both donor and charity
  • -A second app allowing guests to donate instead of bringing gifts
  • -Personal messages included and emailed to the host and charity

Everything designed to support real-world fundraising, not just payments.

The result

The charity now has:

  • -flexible, compliant donation tools
  • -a better experience for donors
  • -less manual admin
  • -fundraising systems that match how supporters actually give

The website actively supports fundraising, rather than just explaining it.

The website actively supports fundraising, rather than just explaining it.

The pattern across every project

Across these projects, the pattern is the same.

I'm usually brought in when:

  • -manual steps are slowing everything down
  • -tools don't talk to each other properly
  • -websites exist, but don't actively support the business
  • -teams are working around systems instead of with them

These aren't surface-level fixes or "nice-to-have" upgrades.

They're strategic interventions that remove friction, tighten decision-making, and turn digital setups into something the business can actually rely on.