What we built, and exactly how.
A booking platform, an ordering and back-office system, and the site you are reading. Below is what each actually does: the mechanisms, not the adjectives. Two are live and you can use them today. The ordering system launches soon with its client; until then it is shown in screenshots, with a demo you can try.
At a glance
Built, replaced, result.
ShotBot
Padel People, Corsham, live
Built
A booking platform for a padel ball machine: real-time availability, payment at the point of booking, and double-booking made impossible.
Replaced
A £500 website with £45–£60 a month of add-ons, a booking tool that charged for every booking, and confirmations sent by hand.
Result
35 paid bookings in two months on the platform (8 in August, 27 in September, against 3 in July on the old setup). Booking admin down from 2 hours a day to 10 minutes. The growth came alongside a visibility push at the venue, not from the platform alone. As of 30 September 2026.
Easy Bite Nutrition
Meal prep, launching soon
Built
Ordering and subscriptions, a prep sheet for the kitchen with allergens flagged, and an owner’s dashboard.
Replaced
Orders over WhatsApp, dietary requirements on a whiteboard, and prep sheets rewritten by hand every week.
Result
No results yet: it launches soon on the client’s own domain. The screenshots below use invented orders, and results will follow the launch.
01Own product
ShotBot
A ball machine is hardware. The business around it is software.
Real-time availabilityWhatsApp enquiries answered from live availabilityDouble-booking made impossibleStripe payments, PCI-compliantAutomatic confirmationsAdmin dashboardTerms recorded against every bookingTracked from first click to payment
The problem
A padel ball machine hired by the hour at a club in Corsham. The machine was the easy part. Taking a booking for a specific hour, taking the money up front, making sure two people cannot book the same hour, and telling the customer the six things they need to do that the booking alone does not arrange. That is the actual product.
Try it
Two customers want Friday, 10:00. Press both Pay buttons, as fast as you like.
Customer A
Customer B
Friday 10:00 · free
A demonstration in your browser: nothing is booked or charged. £10 is ShotBot’s real price for an hour. On the live system the same rule is held by the database, so it holds however close together the two payments arrive.
How it was built8 parts
Booking engine, built from scratch
Availability worked out live, hour by hour, with the bookable window calculated properly rather than assumed, including the awkward parts most systems get wrong, like which hours are genuinely still open once today has started.
Double-booking made impossible, not unlikely
A partial unique index on the active slot key means the database itself rejects the second booking. It is not a check that runs before the write and hopes. It is a constraint the write cannot get past. A cancelled booking releases its slot, which sounds obvious and was a real bug, found and fixed on 31 August 2026.
A test that runs the real migrations
The slot-availability test applies every migration in order against a scratch database and then asserts the behaviour. It encodes the cancellation bug so it cannot come back. If a booking system gets this wrong, you find out when two customers turn up at once.
Payment at the point of booking
Payment captured through Stripe, so card data never touches the application and there is nothing there to leak. Customers hand their card details to the same processor they already trust on far bigger sites. Taking the money at the point of booking means anyone who does not turn up has already paid.
The confirmation is the product, not a receipt
The session is unsupervised, so the email is the delivery: where to collect the machine, when the hour actually starts, and how to work it, with the setup video sent alongside rather than left on a page nobody goes back to. Owner notification and customer confirmation run on separate delivery paths, so a failure in one cannot silently swallow the other, and a rare duplicate is preferred to a silent miss. Every send is recorded against the booking and a bounce raises an alert, because a customer who hears nothing has no way of knowing where to turn up.
Terms enforced server-side, and recorded per booking
Consent validated server-side in the checkout route, not merely ticked in the browser, with the accepted terms version persisted against the booking. Cancellation policy written against the actual regulations, with the exemption cited rather than implied.
The venue’s diary fills itself
Padel People subscribe to a calendar feed once and upcoming bookings appear beside their own diary, refreshing on their own. It carries no personal data at all: the venue needs to know an hour is booked, not who booked it, and a subscription replicates whatever it contains into their own calendar account permanently. The feed is read-only, the URL is the credential because a calendar client cannot send a header, and rotating one secret revokes every subscription at once.
Every step counted, on our own product first
The whole journey is measured: how many people arrived, how many opened the booking page, how many started, how many paid, and exactly where the rest gave up. We did not build this for a client and then try it on ourselves.
How this applies to your business
What this is in another trade
Strip out the padel and this is any business selling a slot: a garage booking MOT bays, a studio booking rooms, a hire firm booking kit that can only be in one place at a time. The hard parts are identical: availability, taking the money up front, and two people never getting the same slot.
Where it stands
Live and taking bookings, at a real club, from real customers who paid before they arrived.
02Client build · launching soon
Easy Bite Nutrition
They did not lose customers on the food. They lost them on everything around it.
Recurring subscriptionsPaperwork generated automaticallyAllergen data, access controlledCustomer self-service, no loginLive delivery-area checkingThe week runs itselfAdmin dashboard
A separate demo built on the same system: a made-up kitchen and test payments. Nothing is charged and no real orders are placed.
The problem
Orders over WhatsApp. Dietary requirements on a whiteboard. Prep sheets rewritten by hand every week. Customer details in a phone. It works while you are small and it breaks the week you get busy, which is the week you can least afford it to.
How it was built8 parts
Ordering, subscriptions and one-off weeks
Weekly menu with full macros and allergens on every dish. Two plan sizes. A meal picker that enforces the right count so an order cannot arrive short.
A prep sheet the kitchen actually uses
Generated automatically: cook counts per dish, the delivery run sorted by postcode, allergy flags in red, print-friendly. No transcription, no rewriting, no misread handwriting.
Allergen data treated as health data
The fourteen FSA allergens held per dish, per customer, access controlled, and accurate at the point the food is made. Get this wrong and it is not a paperwork problem, it is a hospital problem and a legal one.
Customer self-service, with no login
A signed link lets a subscriber skip a week, change plan, change meals or cancel. No password to forget, no DM for the owner to answer at ten at night.
A postcode returns a price, not a maybe
Delivery is quoted from the postcode before checkout rather than at it: four bands running from £5.00 in Chippenham to £8.00 in Bath, priced by how far along a single Sunday round the address sits, with a £40 minimum order on the two furthest bands so the longest legs carry their own cost. An out-of-area postcode is offered collection rather than failing silently, so the order is kept instead of lost at the last step.
QR codes on the product
A container becomes a touchpoint after the sale, which is exactly when most food businesses go quiet.
The owner’s dashboard
Orders, portions to cook, revenue, active subscribers, deliveries. Customer list with lifetime spend and weekly recurring revenue. Prices, cutoff and delivery area editable without a developer.
The week runs itself
Scheduled jobs lock the week at cutoff, bill the subscribers and email the kitchen its prep list, then open the next menu the following morning.
What this is in another trade
Strip out the food and this is any business with a back office: job cards for a garage, treatment notes for a clinic, run sheets for an installer. The pattern repeats everywhere: the detail that matters most is written somewhere nobody can search, and the sheet your team works from gets rebuilt by hand every week.
Where it stands
Built, and launching soon on the client’s own domain. It is not open to the public yet, so there is nothing live to link to. The screenshots are from a copy of the system running on invented orders, not real customers or takings.
03This site
Archline Digital Solutions
The site you are reading is the argument.
Arrives as finished HTML, nothing to wait forEvery enquiry tracked to its sourceSigned, expiring admin sessionsReadable with JavaScript switched offKeyboard and reduced-motion friendly
The problem
An agency that sells measurement while running none of its own is asking to be taken on trust. Everything claimed on these pages is either demonstrated by the page itself or it is not claimed. That constraint decided most of the technical choices below.
How it was built6 parts
Spam filtering that stays out of the visitor’s way
Bots fill a field a person never sees, and are shown the success page rather than an error. Tell a bot it failed and it simply retries. Behind that sit a hidden time check, a content score that holds suspicious enquiries without emailing them, and an invisible human check that only appears when a visitor looks automated. Real people are not asked to tick boxes or read distorted letters.
Attribution applied to its own links
Campaign tags are carried through to the enquiry itself and stored with it, so the source is recorded against the lead rather than guessed at afterwards. If the pitch is that you should know which post produced the booking, the site has to be able to say which post produced you.
A launch condition enforced in code, not in a checklist
A commercial precondition, a client’s written permission to be named, was wired as a flag that physically prevented publication and anonymised the case study until it was cleared. A note in a document gets forgotten. A refusal does not.
Content readable with JavaScript disabled
Scroll reveals are applied only once the browser confirms it can deliver them, with timed sweeps as a fallback. An earlier version hid content by default and rendered a blank page whenever the observer failed to fire. On a page whose only job is to be read, invisible content is the worst available bug.
One file holds every price and claim
A price rise is a single edit, and every assertion on the site can be checked against one list rather than hunted through markup. Three claims in the original copy did not survive being checked against the code they described, and were corrected before launch rather than after a client asked.
Fast because there is nothing in the way
Pages arrive as finished HTML. Nothing to hydrate, nothing to wait for, and nothing that stops working in eighteen months because a dependency moved on.
What this is in another trade
This is the Enquiry build with the enquiry capture and measurement turned on, which is exactly what most businesses need before they need anything bigger. If you want to know what that tier feels like, you are looking at it.
Where it stands
Live on its own domain since 1 September 2026, which you can verify without taking our word for it: you are reading it.
What clients say
Three Google reviews, quoted exactly.
“Customer rave about the website and how easy it is to book. The CRM System is super easy to use, full booking automations and reminders make the admin non existent which helps me concentrate on the running of the facility.”
“They rebuilt the website, simplified how customers contact us and put a proper system behind everything so enquiries, customer details and follow-ups aren't getting lost.”
“He understands where businesses lose time, money and customers when their processes and systems don’t work together. … A genuinely smart proposition built by someone who understands both the technology and, crucially, the commercial realities of running and growing a business.”
→Start
Tell us what breaks when you get busy.
The first step is a call, and it costs nothing: twenty minutes on what your business does and what breaks when you get busy. Most projects then start with the £450 Diagnostic: half a day walking your process end to end, with a written recommendation and a fixed quote, credited in full against a build if you go ahead within thirty days. If you already know which package you need and its scope is clear, we quote it directly.
You might not need one.
Three questions. How many enquiries turned into paying customers last month? How many no-shows and cancellations did you have, and what did they cost you? Where do people drop out between first hearing about you and paying?
If you can’t answer all three, that is what the Diagnostic is for. If you can, and you already know which package you need, we quote it directly.