Dom Whiting
The website, back office and Discord bot behind the rides: events, tracklists, the gallery, the shop and memberships, plus a live map fed by a GPS tracker on the bike, which fans follow in real time.
Taking on projects for early 2027
I’m Tom, a software developer in Lancashire. I build web apps, integrations, automations and practical AI for businesses that have outgrown spreadsheets and copy-paste.
Or start with what’s eating your time:
Where the time goes
You keep the tools you already use. I connect them, so orders, invoices and updates move on their own and nobody types them in twice.
Now: One file, five editors, no history. Somebody sorted column B last Tuesday and nobody has noticed yet.
After: A back office built around your records, with roles, a record of every change and one source of truth.
That’s me: start here →Now: Shop to payments to accounts to courier, by hand, with a typo waiting at every step.
After: Your systems talk to each other directly. Every order is keyed in once, checked, and tried again if a service is down.
That’s me: start here →Now: Exports, VLOOKUPs and a chart that’s out of date by Monday.
After: A dashboard that updates as things happen, with the numbers you actually decide on.
That’s me: start here →Now: “Has this been sent?” “Did they pay?” “Who’s got this one?”
After: Status changes trigger the right message to the right person, and customers can check for themselves.
That’s me: start here →Now: You pay for an off-the-shelf tool and work around it every day.
After: A focused web app shaped to how your team really works, connected to the tools you keep.
That’s me: start here →Keep your tools
Nothing to rip out and no new system for your team to learn. If yours isn’t here, I’ll find a way in.
Recent work
Two recent builds, each a public site plus the back office that runs it.
The website, back office and Discord bot behind the rides: events, tracklists, the gallery, the shop and memberships, plus a live map fed by a GPS tracker on the bike, which fans follow in real time.
Everything around a competition: the season calendar, tickets with Apple and Google Wallet passes, a door scanner that works offline, ID-checked athlete cards and merch sent to parcel lockers, all run from one back office.
Web apps for a vehicle retailer, before Schofield Development.
A booking tool for vehicle servicing, so customers book work online instead of by phone.
A valuation tool for customers selling or part-exchanging a vehicle.
Web apps for a vehicle retailer, before Schofield Development.
A booking tool for vehicle servicing, so customers book work online instead of by phone.
A valuation tool for customers selling or part-exchanging a vehicle.
What I build
Pick one to see the kind of screen you’d get. You start with one job and add the rest as you go.
Every change recorded. Each role sees only what it needs.
Every order keyed in once.
Things happen on time without anyone having to remember.
The reading gets done. The decision stays yours.
Welcome, follow-up and win-back sequences that run from your own records.
One dashboard instead of five spreadsheets.
AI, with guardrails
A lot of slow work is reading: emails, invoices, forms. AI is good at that now. You choose how far it goes before anything is built, and you can change your mind later.
It reads and proposes. A person does the work.
It drafts the change. Nothing happens until someone taps Approve.
Small, reversible jobs run on their own. Every run is logged, capped and switchable.
In use today: a sports club uses level 01 to match uploaded ID documents to the right member record. An admin approves every match.
Not sure which level fits? Tell me about the jobHow I’d start
You react to working software, not documents, and the most painful job gets fixed first.
I’ll walk through how the work really happens today with you, screen by screen. You get a written map of where the time goes and what to fix first.
Every screen is designed, including what happens when something goes wrong.
The first release is in use straight away, and each one after adds the next job.
Hosting, monitoring and alerts are set up from day one. Data collected from launch shapes what gets built next.
Built to last
These are the targets every project is built and tested against.
Screens respond in under a tenth of a second
Pages appear in under 2 seconds on a 4G phone
Easy for everyone to use, including by keyboard or screen reader
No failed requests while an update goes out
UK hosting, with UK GDPR export and delete
Undo an update in under 30 seconds
Start here
Four quick questions, about a minute. I’ll reply within two working days.