A booking button does not automatically make a project a custom software build. Follow one request past the button. If an existing booking system already handles availability, changes and reminders, the website may only need to help the right person reach it.
Follow one booking past the button
Imagine a training business that sells public classes. A customer chooses a class on its website and books an available seat through its scheduling provider. The provider holds the booking; staff know where to find it. Start by testing that handoff on a phone, including a full class and a cancelled booking.
Now imagine the same business sells private training to employers. A coordinator proposes three dates, a manager approves a budget and an instructor confirms a room. If staff must track which version each person approved, the important feature is a shared record with permissions and a history. A new page layout cannot provide that on its own.
Compare three ways to deliver the job
- Website and enquiry form
- Use this when the customer needs information and a person can handle the next step. Check that a real recipient gets the enquiry and the visitor can recover if sending fails.
- Website plus an existing service
- Use a booking, shop or account provider if it already supports the hard part. Check accessibility, recurring fees, data export and what happens when a visitor returns from the provider.
- Custom web application
- Consider this when off-the-shelf tools cannot support a necessary rule, approval or integration. Budget for the people who will maintain permissions, backups and support after launch.
What should you test before commissioning software?
Draw four columns: person, action, record changed, next owner. Fill them in for one normal request and one exception, such as a manager declining a date after the customer has confirmed it. Ask someone who does the work to walk through both cases. If a current tool handles both, ask for an integration estimate before requesting a custom build.
In Richverse’s own enquiry redesign, the useful change was to carry a choice between two pages. It did not require a customer account. That example demonstrates the handoff; the private-training scenario above is illustrative.
What belongs in the quote?
Name the records the business must own, who can change them, which tools stay, and which recurring costs are excluded. Agree on a handover test: a member of staff can complete a normal request, correct a mistake and export the record without the developer.
Use the editable website brief to give suppliers the same starting point, or describe the workflow to our web development team.
