The 2026 buyer's guide to housing management software

If you're reading this you're probably weighing up whether to change your housing management software — or buy your first proper system. This guide is the distilled version of the conversations we have with prospective customers every week. It's written for housing co-ops, TMOs, EMBs and small-to-mid housing associations, not for 30,000-home landlords with dedicated procurement teams.

Start with the pain, not the feature list

Every housing system has a tour. Every tour hits rent, repairs, voids, allocations, reports. What matters is which of those things currently hurts — and which of those things the product you're looking at handles in a way that actually fixes it.

Before you look at any demo, write down:

• Three things your team complains about every week.
• Three reports your board or regulator asks for that are painful to produce.
• One thing that has gone wrong in the last twelve months that software should have caught.

Score every shortlist supplier against those seven items. The rest of the feature matrix is noise — most systems do most things adequately.

Questions to ask every supplier

On the product

• Show us a tenancy with a housing benefit schedule, a UC direct payment, and a partial-period rent change. Talk us through how the rent account reconciles.
• Show us a live repair being raised by a tenant, assigned to a contractor, and invoiced. How many clicks?
• Show us the workflow for a complaint under the Housing Ombudsman Complaint Handling Code.
• What reports do you ship out of the box for the RSH / Welsh / Scottish regulator returns?

On implementation

• Who is our named implementation lead, and what else are they doing during our project?
• What will our data actually look like on day one? Show us a sample.
• What does a typical cutover weekend look like, and who covers the Monday morning rent run?

On the supplier

• Who owns the company? Who owned it three years ago?
• How do we raise a P1 at 4:45pm on a Friday? Can we speak to someone whose first language is “housing”?
• Give us the names and numbers of two reference customers of similar size.

Things to ignore in a sales deck

• “AI” unless they can show you a specific, working use case — not a roadmap slide.
• Feature counts. You'll use 15% of what's there.
• Total customer count. The number that matters is how many customers like you.
• Awards. The sector is small. Almost every supplier has a shelf of them.

Scoring a shortlist

We recommend a scorecard with four columns per supplier: fit (does it do the seven things you wrote down), total cost over five years (licence + implementation + support + the integrations you'll need), risk (supplier stability, migration complexity, reference quality), and gut feel. The last one matters more than procurement theory suggests — you're buying a relationship that'll outlast most senior hires.

What to budget

For a housing organisation of 100–2,000 units, expect annual licensing in the low-to-mid five figures, implementation in a similar range, and six-figure total cost of ownership over five years. Anything meaningfully below that is a flag (what's missing?); anything meaningfully above that needs justification in the scope.

The question almost no-one asks

“What happens if we want to leave?” Ask every supplier how they hand over your data, in what format, and over what timescale. The answer tells you a lot about the relationship before you've signed.

One last thing

Don't buy the thing that demos best. Buy the thing your team will still like in three years, from the supplier whose name you'll remember when you're annoyed at 4:45pm on a Friday.