Booking systems, CRMs and back-office automation for UK and Ireland
businesses. We watch how your team actually works, write a fixed-price spec you sign
off, then build it in stages. You own everything at the end.
Our CRM runs the sales floor at Phillip McCallen Motorcycles, Lisburn.
The problems we get called about
F-01
Enquiries land in one person's inbox and sit there when they're off, busy, or on holiday.
F-02
Bookings live on paper, a whiteboard, or a spreadsheet two people edit at the same time.
F-03
The same customer details get typed into three different places, and none of them agree.
F-04
Getting a simple answer, like how many enquiries turned into sales last month, means an evening in Excel.
Your team isn't the problem. The system they're working inside is, and systems can be rebuilt.
/ Work — Systems in service
Booking pages, CRMs, event systems and automation. Each one built for
a specific job a real business was losing time on, and still in use.
SectorsMotorcycle trade · Events · SMEs
DisciplinesBooking · CRM · Automation
TerritoryUK & Ireland
01 / Case study
ClientMotorcycle dealership
Services
BookingLive availabilityAdmin view
BuildNext.js · Supabase
Open-day test-ride booking
Motorcycle trade · Booking
A dealership's annual demo day: 16 bikes, one ride per hour, and a queue of
customers who used to book by phone and paper. We built a public booking page with
live availability, a hard limit of two rides per customer, and an admin list staff
check on the day. It dropped straight into the dealer's existing website, and the
hosting costs them nothing.
16Bikes scheduled
0Double bookings possible
£0A month hosting
Fig.01 — Booking grid · live slots
02 / Case study
ClientMotorcycle festival · Ireland
Services
BookingPaymentsRace-day
BuildCustom build · database
Race entries, payments & race-day
Events · Booking & payments
A large motorcycle festival in Ireland was taking rider and spectator entries
across several booking platforms, then rebuilding it all by hand: allocating
numbers, chasing forms, seeding entries and reconciling payments in spreadsheets.
We replaced the lot with one system. A customer-facing form collects each entry,
applies the festival's rules, and takes the right payment at the point of booking.
Everything lands in one database, which builds the race entry pages officials use
on the day to sign riders in and run each race. What used to swallow hundreds of
hours of manual admin now runs on its own.
HundredsAdmin hours removed
1System, several platforms replaced
On-dayRace sign-in built in
Fig.02 — Entry → payment → race-day
03 / Case study
ClientPhillip McCallen Motorcycles
Services
CRMPipelineMulti-user
BuildProduct · MotoCRM
MotoCRM
Motorcycle trade · CRM
Our own product: a CRM built for UK and Ireland bike dealers rather than adapted
from generic automotive software. Priced at £129 a month per location with unlimited
users. Phillip McCallen Motorcycles in Lisburn switched to it after enquiries kept
stalling in individual inboxes.
"With our old CRM, if a salesman was off or busy his enquiries just sat there.
MotoCRM puts everything in one place the whole team can see, so calls get returned
and nothing slips."
£129Flat, per location / month
TeamOne shared view of every enquiry
LiveRunning the Lisburn sales floor
Fig.03 — One shared pipeline
04 / Case study
ClientInternal tooling · MOND
Services
AutomationScraperData enrichment
BuildNode · scraper
A 414-dealer lead list, built by software
Automation · Data
We needed contact details for every motorcycle dealer in the UK and Ireland.
Instead of weeks of copy-and-paste, we wrote a scraper that walked manufacturer
dealer locators and compiled 414 dealers, enriched with contact details. This is the
shape of job we automate for clients: repetitive, rule-based, and quietly eating
someone's week.
No open-ended day rates and no retainer you can't leave. You get a
written spec and a fixed price before any code, working software early, and full
ownership of everything at the end.
What we build — Deliverables
01 / Deliverable
Booking & event systems
Public booking pages for open days, festivals and events. Live availability so two
customers can't claim the same slot, limits per customer, and one admin view of every
booking. Embeds into the website you already have.
02 / Deliverable
CRM & pipeline systems
Purpose-built CRMs shaped to your trade, not adapted from generic software. Every
enquiry visible to the whole team, so nothing sits in one salesperson's inbox while
the customer waits.
03 / Deliverable
Automation & AI workflows
The jobs nobody has time for: building lead lists, chasing follow-ups, moving data
between systems, drafting routine emails for your approval. Done by software, checked
by you.
How a project runs — Method
Step 1
Discovery
A short call, then we look at how the work actually flows through your business.
We're hunting for the places where things get retyped, lost, or forgotten.
Step 2
Written spec, fixed price
You get a spec in plain English: what the system does, what it doesn't, and what it
costs. Nothing gets built that isn't in it, and the price doesn't move after you sign off.
Step 3
Build in stages
You see working software early and react to something real, instead of signing off
on promises and waiting months for a reveal.
Step 4
Deploy, hand over, stay close
We put it live, hand over the keys, and stay available. The code, the data and the
accounts are yours outright.
Questions we get — FAQ
"We're not a tech company."
Good. Our clients sell bikes, run events and manage workshops. If you can describe the problem in a sentence, that's all the technical input we need from you.
"What does it cost?"
A fixed quote after discovery, before any code is written. A single-purpose booking page sits at the low end; a full CRM sits at the top. The price you sign off is the price you pay.
"We already have a website."
Keep it. Our systems embed into the site you have or run on their own link. The test-ride booking page dropped into a dealer's existing site without touching it.
"Where does the AI come in?"
Where it does a real job: reading incoming enquiries, drafting replies for your approval, enriching lead data. We don't bolt a chatbot onto your website and call it progress.
"Who owns the system?"
You do. Code, data, hosting accounts, the lot. If we disappeared tomorrow, your system keeps running and any developer could pick it up.
"How long does it take?"
Depends on the system, and the spec will say. Small systems like the test-ride booking page go from brief to live in days, not months.
Tell us about the thing your team keeps losing, retyping, or chasing.
We'll reply with whether software can take it off your hands, and roughly what that
would involve. No pitch deck, no obligation.