How Much Does Public Housing Authority Software Cost in 2026?

The bands a housing authority build falls into

There are two honest bands, and one clear recommendation for small agencies that is neither.

The layer band is $110,000 to $250,000 over 16 to 24 weeks. That buys inspection scheduling with geographic grouping and multilingual reminders, an offline capable mobile inspection form, a landlord portal, applicant and waiting list self service, and quality control reporting including a submission monitor. It runs alongside your existing system of record and touches none of the calculation logic.

The extended band is $280,000 to $750,000 phased across 12 to 20 months. That adds recertification workflow with income calculation, rent reasonableness with a comparables database, housing assistance payment processing, and family report preparation and monitoring.

The third option is the right one for a small authority with a few hundred vouchers: do not build. Buy a compliant system of record, run it properly, and spend the difference on staff. We say this to boards regularly and it costs us work.

Below the layer band there is a narrower project worth naming: inspection scheduling and mobile capture on their own. In our delivery experience that is $50,000 to $85,000 over ten to fourteen weeks. It is consistently the highest return custom work in this category, because voucher inspections are a routing and logistics problem that agencies fund as a clerical one.

What drives a housing authority build up

Programme count is the largest driver. Public housing, the voucher programme, project based assistance, moving to work flexibility if your agency holds it, and any state or local programme each bring their own rules, their own eligibility structure and their own reporting. Two programmes is not twice one programme, but it is well short of the same price.

Rent determination scope is second, as set out above. It is a step change rather than an increment, because reproducibility is the requirement. Any system where a rules update silently changes what a prior year calculation would produce will fail a file review, so the design has to carry dated parameter tables and versioned calculation logic from the first line of code.

Accounting integration is third. Subsidy and payment posting has to satisfy your auditors, and that means agreeing the posting rules with your finance staff before anything is built rather than reconciling afterwards.

Data conversion is fourth and it is always larger than the estimate. It is also the point at which the true state of your historic files becomes visible, which is a finding rather than a task.

Then the obligations that apply because you are a public body. Accessibility standards, language access across the languages your population actually speaks, records retention aligned to your schedule, and a security review appropriate to data that includes social security numbers and full household composition. These are genuine work, not checkboxes, and retrofitting any of them costs more than building them in.

What keeps the number down

Start with inspections and the landlord portal. These are the two areas where packaged housing products are consistently thinnest and where staff time is most visibly consumed, and neither requires you to touch the compliance calculation. Agencies that sequence this way get a demonstrable result inside one budget cycle, which matters when the next phase needs board support.

Keep the system of record. The federally defined compliance surface changes without your input, and vendors maintaining it across hundreds of agencies are doing work no single authority should own. An agency that builds its own submission engine has taken on a permanent obligation with no upside.

Design language access in from the start rather than adding a translation widget later. It is cheaper as a design constraint than as a remediation, and the same is true of accessibility.

Convert active files only. Terminated and historic tenancies can be preserved as archived extracts under your retention schedule. Nothing in the new system computes from them.

Finally, name a decision owner from operations who can translate your administrative plan into rules without convening a management meeting. In this domain the unresolved questions are policy questions, and unresolved policy questions turn directly into schedule.

A worked example that adds up

A mid sized authority administering about 2,400 vouchers plus 600 public housing units, keeping its existing system of record, building the layer. Reminders in three languages, one inspection team of four inspectors.

• Discovery, translation of the administrative plan into rules, and observation of a full inspection day: $14,000
• Inspection scheduling with geographic grouping, tenant and landlord reminders in three languages: $28,000
• Offline capable mobile inspection form with photos, defect codes and severity: $26,000
• Re-inspection and follow up workflow with payment consequence flags: $15,000
• Landlord portal with payment history, statements, upcoming inspections, document upload, and ownership or banking changes routed for review: $32,000
• Applicant portal and waiting list self service including online purge response: $24,000
• Quality control reporting plus a submission monitor with ageing on unresolved records: $19,000
• Read integration with the system of record and an accounting export agreed with finance: $16,000
• Accessibility testing, language access review and security review support: $12,000
• Testing, deployment and parallel running across one full inspection cycle: $12,000

That totals $198,000, inside the layer band and toward its upper half because of the three languages and the applicant portal. An authority with about 700 vouchers scoping inspections and the landlord portal only, in one language, lands nearer $118,000.

If that authority later adds recertification workflow with income calculation, rent reasonableness with a comparables database, housing assistance payment processing and family report preparation, expect a further $150,000 to $450,000, taking the programme to roughly $350,000 to $650,000 in total.

How the spend phases

Discovery is three weeks and typically 7 to 10 percent of the layer build, and part of it has to happen in a van with an inspector. Watching a real inspection day produces requirements nobody articulates in a meeting, particularly around what an inspector will and will not stop to type.

Weeks three to twelve carry the heaviest spend at roughly 45 percent: scheduling, mobile capture and the follow up workflow. This is the operational core and it is where the labour saving comes from.

Weeks twelve to twenty are the portals and quality control reporting, around 33 percent. Portals are public facing, so accessibility and language testing run alongside rather than after.

The final three to four weeks are conversion, parallel running and cutover, around 15 percent. Run through at least one full inspection cycle in parallel, and if the extended phase is coming, plan for a parallel recertification cycle then too.

The ongoing costs nobody quotes

Infrastructure for a layer of this shape runs $400 to $1,200 a month in our delivery experience, driven mostly by inspection photographs and document retention rather than compute.

Text and voice reminders carry a per message cost. It is small, but at several thousand inspections a year across multiple reminder points it is a real line, and it grows if you add languages.

Inspector hardware is a recurring cost. Devices used in the field on a daily basis do not last as long as office equipment, so carry spares and plan a replacement cycle rather than treating it as a one time purchase.

Support and enhancement typically runs 12 to 18 percent of the build cost annually, so roughly $24,000 to $36,000 on a $198,000 layer. Get it into the operating budget, because it needs to survive a change of executive director.

Then the obligations that recur rather than complete. Accessibility testing on every public facing change. Security review at whatever cadence your agency and your funders require. Records retention housekeeping. None of these are software costs exactly, but they all land in the same budget conversation.

Comparing a build against your current renewal

Do this arithmetic before you take anything to your board. Take your annual maintenance on the system of record. Add whatever you spend on vendor change requests in a typical year, because in this category that figure tells you how much of your operation the product does not fit.

Then add the staff time absorbed by the manual layer. The paper calendar or shared spreadsheet the inspectors are scheduled from. The phone calls from landlords asking when payment is coming and when the inspection is. The waiting list purge that takes weeks and returns poor response because applicants cannot update anything online. The side spreadsheets that answer leadership's routine questions because the system will not.

Then weigh the exposure that has no labour number. An incorrect income treatment produces a tenant rent that is too low and a subsidy payment that is too high, and it repeats every month until a verification discrepancy surfaces it. The authority then corrects the record and enters a repayment agreement with a family whose entire situation is that they do not have spare money. Nobody in that story was careless. The rules governing income and assets are set by federal notice and have been through significant change with implementation dates that have moved more than once, so confirm current requirements with your field office rather than with any document you found online, including this one.

The honest counterweight: a build carries delivery risk, and public sector procurement adds its own timeline. An agency that cannot free an operations decision owner should phase smaller rather than start bigger.

When buying beats building

If you administer a few hundred vouchers, do not build anything. Buy a compliant system of record, run it well, and put the money into staff. At that scale the fixed cost of custom software cannot be recovered from the labour it saves, and we would say so in front of a board of commissioners.

Buy the system of record regardless of your size. Yardi Voyager with its housing modules and MRI Software's HAPPY bring genuine depth in accounting and portfolio management. Emphasys Elite and Tenmast were built for housing authorities specifically and reflect that in workflow familiarity, which is why so many mid sized agencies run them. None of these is bad software, and rebuilding the federally defined compliance surface is a permanent obligation with no upside for a single agency.

Build the layer when the symptoms are clear. Your inspectors are scheduled from a paper calendar. Your landlord communication is phone and mail. Your waiting list purge takes weeks and produces poor response. Leadership's routine questions are answered from spreadsheets rather than the system. Or a local policy your board adopted cannot be represented in the product and staff are working around it by hand.

Build more than a layer only in narrow circumstances: a large authority where the economics genuinely change, an agency with moving to work flexibility whose local policies diverge substantially from the standard model, or a consortium building once for several authorities. In those cases the scope is justified by scale or by real policy divergence, not by dissatisfaction with a vendor.

If you would rather someone argued with your brief than agreed with it, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. The document is yours whichever way you go.