Booking and web systems
Custom web systems for organisations that have outgrown paper forms, WhatsApp threads and spreadsheets: bookings, registrations, member portals and dashboards.
A web system is software your staff and customers use in a browser: a booking calendar, a registration form that feeds a list, a member portal, a dashboard of records. Each one is built for one organisation, so we price it only after a discovery session that maps the process. A responsible estimate is not possible before that.
What a web system can do
Bookings and reservations
Customers choose a date, room, table or time slot online. Staff see one calendar instead of a notebook and three phones.
Registration and applications
Events, courses, tournaments or admissions. Entries arrive in one list, complete and readable, instead of in messages.
Member and client portals
People log in to see their own documents, payments, results or project status.
Dashboards and records
Stock, jobs, cases or students in one searchable place, with different access for different staff.
Quotes and enquiries
Enquiries are captured, assigned and followed up, so none is lost in a chat.
Connections
Linking the website to the tools you already use, where those tools allow it.
How a system project runs
Map
We sit with the people who do the work and write down each step of the process as it runs today.
Decide
Together we mark which steps the system should take over, and which should stay manual.
Scope
Written scope: screens, user roles, data kept, security, price and delivery window.
Build in stages
The most valuable part is built and used first, then the next.
Train and hand over
Staff are shown how to use it, and you receive the accounts and documentation.
Three honest questions
- Is the process stable? Software fixes a process that works on paper. It does not fix one that nobody agrees on.
- Does something already exist? If an off-the-shelf tool does the job for a small monthly fee, we will say so.
- Who will own it day to day? A system needs one person inside the organisation who is responsible for it.
Systems hold other people's information
A system that stores names, phone numbers, payments or student records has to be built differently from a brochure website. Each scope sets out who can see what, how people log in, where the data is kept and how it is backed up.
Our own sites separate public pages from the admin area, with login protection on the admin side. We apply the same separation to client systems.
Common questions
Why can you not give a price up front?
Two booking systems can differ by a factor of ten in work, depending on payments, user roles, reports and what they connect to. A number given before the process is mapped would be a guess, and guesses lead to arguments later. The discovery session produces a written scope with a fixed price for a defined first stage.
Can a system be added to our existing website?
Usually. The system can sit on its own address, such as bookings.yourname.com, and be linked from the existing site.
What happens if we need changes later?
Changes are quoted before they are built. Systems normally sit on a care plan so that updates, backups and small changes are covered.
Tell us the problem. We will tell you what it takes to fix it.
Send a message, call, or use the form. You get a written scope and a price before any work starts, and there is no charge for the first conversation.