“Could you hold that projector until tomorrow? I just need the venue to confirm.”
If you run an equipment hire business, that sounds like a reasonable request. You open the booking sheet, enter the customer’s name against Friday’s date and colour the row yellow. A few hours later, a colleague gets another call about the same projector. They check Friday’s bookings, see that the deposit column is empty and confirm it for someone else.
By the time you spot the problem, two customers have made plans around one piece of equipment.
It’s tempting at that point to say, “We need a booking app.” You might be right. But before paying someone to build one, it’s worth asking what went wrong. Did the team have different ideas about what a hold meant? Was the rule clear, but easy to overlook? Or were both people looking at different copies of the sheet? Each problem calls for a different fix.
Give the spreadsheet a fair chance
Many businesses start with a spreadsheet for good reason. You can set one up in an afternoon, change a column after a conversation and see most of the week’s work at a glance. When you’re still learning how the business operates, that flexibility is valuable.
For the hire company, a yellow row carries quite a lot of meaning. It might mean a customer has made an enquiry, an item is reserved, or someone needs to follow up. The person who coloured it knows which one they meant. Everyone else has to interpret it.
A sensible first step would be to agree on the booking states. An enquiry leaves the projector available. A hold reserves it until a recorded time. A confirmed booking commits it to the customer. Put the status, expiry time and person responsible in the sheet, then make sure everyone handling bookings uses the same copy.
Try that change through a few busy Fridays. If colleagues can now answer the phone confidently and customers get reliable answers, the spreadsheet is doing its job. That might settle the question for another year.
Notice the work happening around the sheet
The stronger case for an app often shows up in the work people do between entries.
Perhaps the sales team rings the warehouse before confirming almost every booking. Someone checks all the yellow rows each morning to see which holds have expired. A late return means searching through the rest of the week to find out who needs a call. By Friday afternoon, the most accurate picture of availability sits with the employee who remembers the last six conversations.
Pay attention to those interruptions for a fortnight. Record what someone had to check, roughly how long it took and what would have happened if they had missed it. Five minutes spent checking availability may be perfectly acceptable. Promising equipment that is still at another venue can cost a delivery trip, a refund and a customer’s confidence.
This is also where you can identify what an app would actually need to do. For the hire company, the requirement might fit into one sentence. Before anyone confirms a booking, they need to know that the item will be back, checked and ready for the next customer.
That sentence gives you something concrete to test. Suppose a projector is due back at four and needs an hour for inspection. A booking that starts at half past four should flag a conflict. If two colleagues try to reserve the last available projector at the same moment, only one should receive confirmation. A calendar that looks impressive in a demonstration can still fail both tests.
Access can matter just as much as availability. A driver needs the delivery address and collection time. The accounts team needs payment details. Your manager may need to know who approved a booking without a deposit. Once those responsibilities are clear, you can decide which information each person needs to see, what they can change and which decisions need a record.
Test the smallest change worth paying for
At this stage, take a few actual bookings to an existing software provider or a developer. Include an ordinary hire, a cancelled hold and a late return. Ask the person who usually handles Friday’s calls to work through them. They are likely to notice details you would never think to put in a brief.
An existing booking tool may already handle the awkward cases at a reasonable cost. A small custom app may make sense if your rules are unusual or the team spends hours copying information between bookings, dispatch and billing. When comparing the options, include the time needed to move records, train staff and support the system when something changes.
Keep the first trial narrow enough to learn from. The hire company could start with projectors and agree that all bookings for those items go through the trial system. The rest of the equipment can stay in the spreadsheet. After a few weeks, check whether staff make fewer calls to confirm availability, whether conflicting bookings have fallen and how the team handled a genuine exception.
A spreadsheet earns its replacement when you can point to a recurring business problem, explain the rule a system should enforce and see enough benefit to justify maintaining it. For the hire company, the test comes the next time someone asks, “Can you hold that projector?” Whoever answers the phone should be able to make a promise the whole team can keep.