Another estate should not always mean another hire

A new estate can look like growth until the team starts counting the extra chasing, reports and approvals. If every new property adds the same administrative load, winning more work can quickly turn into a staffing problem.

“We need another person” may be exactly right. Before accepting or dismissing that request, it is worth understanding what the additional person would spend the day doing.

What is filling the working day?

A facilities team may be short of people to inspect sites, supervise contractors or deal with residents. Those are responsibilities that need time and attention at the property. Software does not turn a desk into an extra pair of hands on site.

A different team may be losing hours collecting updates, preparing the same approval twice and turning messages into reports. It can feel just as overloaded, but the response need not be identical.

Often both are true. The manager needs more site coverage and is also spending too much of the existing team's capacity on administration. Treating the entire workload as one undifferentiated staffing shortage makes it harder to see where a change could help.

The useful discussion is therefore more specific than “can AI replace a hire?” Which responsibilities genuinely need another person, and which repeated tasks are preventing the current team from doing the work it was hired to do?

What did the expensive system actually change?

A familiar software name can make a purchase feel safer. A long feature list can help justify the budget. Neither tells a manager what the team will stop doing after launch.

If staff still prepare the same information outside the system and copy it back in later, the business may have bought a more elaborate place to store the result. If every change needs another paid project or a long wait for support, the cost continues after the initial purchase.

This does not mean expensive software is poor value. A larger organisation may have requirements that genuinely justify a larger investment. Equally, a cheap service can become costly when the team spends its own time making it work.

The comparison is the total cost of getting useful work done: the supplier's charges, the effort left with staff and the support needed when circumstances change. A lower headline price is not enough if the workload remains untouched.

Do not turn every saved hour into a payroll saving

Here is a simple fictional example, not a Wisbid result. A team spends ten hours a week preparing recurring reports. A new arrangement reduces preparation to six hours but needs one extra hour of checking and upkeep. The net gain is three hours of capacity each week.

That is useful time. It may go towards inspections, follow-up on difficult cases or work for another property. But the salary bill has not automatically fallen. A cash saving appears only when spending actually changes, such as less paid overtime or outside support.

Three hours also does not establish that the team can take on a whole new estate. The next property may need regular attendance, have difficult access arrangements or generate work the current portfolio does not. Capacity needs to be useful at the time and place the new responsibilities arise.

A credible business case keeps these claims separate: time available, costs reduced and additional work the team can realistically take on. Adding them together as if they were three separate cash benefits would overstate the gain.

The cost of staying and the cost of changing

If your organisation has already spent heavily on a system, the decision can become emotional. Replacing it may feel like admitting the earlier investment failed. Keeping it may feel easier than explaining another purchase.

Past spending cannot be recovered simply by carrying on. But a replacement brings its own costs: moving information, training people, disruption and a period when both arrangements may be running. The sensible comparison is what each option will cost and deliver from this point onwards.

Sometimes the existing system can be improved. Sometimes it needs to remain because a client requires it or it does another job well. A proposal that counts savings from retiring a tool the business must keep is not a usable proposal.

For practical help with that choice, our facilities software buyer's guide covers evaluating the service alongside its setup effort and ongoing costs.

What would make the next estate easier to take on?

Wisbid is intended to reduce the repeated coordination around property work: finding information, preparing updates, following up on routine tasks and getting decisions ready. The business benefit is more useful capacity in the team. It needs to be judged after the effort of adopting and using the service is included.

Help during that change matters. Staff should know who to turn to when something does not fit their day-to-day work, and the proposal should make future support and charges clear. A quick acknowledgement of a problem is welcome; useful help getting past it matters more.

Before buying, agree which burden should become smaller. After a reasonable period of ordinary work, ask whether it did. If people are spending less time reconstructing what happened and more time managing the properties, there is a credible improvement to discuss.

And if the team still needs another person for physical coverage, judgement or service quality, hire for that need. The goal is a portfolio the business can serve well and profitably, with a clear understanding of what each person and each system contributes.