Booking & portals
Let your customers book, pay and find things themselves.
Online booking, a secure client login, documents and invoices in one place. Fewer phone calls, fewer resent attachments, and fewer things written on a pad that only one person can read.
Direct to the developer
You brief the person who writes the code. No account manager in between.
Fixed written price
Scope and cost agreed in writing before any work begins. No hourly drift.
You own everything
Code, hosting and data in your name from day one. No lock-in, ever.
Nottingham & Leicester
On site across the East Midlands, or online anywhere in the UK.
What this covers
Client portals
A secure area where your clients sign in to see their documents, bookings, invoices and progress. Cuts the volume of "can you just send me that again" email considerably.
Booking and scheduling
Systems that handle availability, reservations, reminders and payment, built around your rules rather than a generic calendar's assumptions.
Internal business platforms
The system that runs the operation: records, workflow, reporting and permissions, with staff seeing only what their role allows.
API integration
Connecting what you already use so data stops being typed twice. I have integrated with government services including the DEFRA waste tracking API, payment providers including Stripe, and a range of third-party platforms.
How it is built
React and TypeScript on the front end. Node.js, Python, PostgreSQL and Supabase behind it, with row-level security so access is enforced at the database rather than hopefully in the interface. Stripe where payments are involved. Deployed on Vercel or Render with automated builds.
That stack is boring on purpose. It is widely used, well documented and easy for another developer to pick up, which matters more for your long-term interests than whatever is fashionable this year.
You own all of it
Code, hosting, database and domain, in your name from the start. No lock-in, no licence you keep paying me for, and no situation where leaving means rebuilding.
How we work
Three steps, no surprises in between
Every project runs the same way, whether it is a full platform or an afternoon of changes.
Free scoping call
Thirty minutes. You tell me what you are trying to fix, open or win, and I tell you honestly whether I am the right person for it.
Written proposal, fixed price
Scope, what you get, timeline and a fixed price in writing before any work starts. No hourly drift and no surprise invoices.
Build, then handover
You get a link and regular updates as it comes together, then a walkthrough so your team can run it without me.
Questions
Custom software questions
When is custom software worth it over an off-the-shelf product?
When your process is genuinely unusual, when you are paying staff to rekey data between systems, or when the off-the-shelf option needs so much configuration and workaround that you are effectively building it anyway. If a product does cover you, buying it is cheaper and I will say so.
Who owns the code?
You do. The repository, hosting and database accounts are in your name. You can take the whole thing to another developer whenever you like, which is the main protection against being held hostage by whoever built your system.
What about ongoing maintenance?
Software needs occasional attention: dependency updates, security patches, small changes as the business shifts. I can handle that ongoing, or hand over cleanly enough that someone else can. Your choice, and not locked into the original contract.
Can you integrate with systems we already use?
Usually. If the other system has an API, it can generally be connected. I have integrated with government APIs, payment providers and third-party platforms. Where no API exists I will tell you at the quote stage rather than discovering it halfway through.
Get started
Got a process that no product quite fits?
Describe how it works now, including the spreadsheets and the workarounds. That conversation usually makes the answer obvious.