Affordable Housing Compliance Software: Build or Buy, and What Decides It
The threshold is not unit count, it is how many programmes sit on the same unit.
On this page
The threshold is not unit count, it is how many programmes sit on the same unit. Under roughly 2,000 units on a single programme in one or two states, buy: Yardi Affordable Housing, RealPage OneSite Affordable and MRI Affordable Housing all handle a conventional Low Income Housing Tax Credit or Section 8 portfolio properly, and their voucher handling alone justifies the licence. Once units carry three or more programmes, or you use the average income set aside, or you report to five or more state agencies, a compliance layer built above the property platform runs $70,000 to $150,000 over 14 to 20 weeks for a first release, and most owners in that position should build it.
When is off the shelf genuinely the right call here?
Buy if you hold under roughly 2,000 affordable units, mostly on one programme, in one or two states. Yardi Affordable Housing, RealPage OneSite Affordable and MRI Affordable Housing each carry genuine programme knowledge, and Yardi in particular has long heritage in transmitting certifications and vouchers to the federal Tenant Rental Assistance Certification System. Reproducing that transmission layer is a poor use of capital and we would tell you so rather than quote for it.
Buy also, whatever your size, if the honest diagnosis is that your compliance problem is knowledge rather than consistency. If two sites certify the same household differently because one manager was never trained on the rule, software will document the inconsistency rather than remove it. A written determination policy, a peer review step and a day of training will fix that faster and for a fraction of the money.
And buy the property management platform in every scenario. Leases, units, rent rolls, accounting and household composition already work in those products. Nothing in this guide argues for replacing them, and an owner who reads a build case as permission to rip out Yardi has read it wrong.
The clean signal that buying is still right: your specialists are not maintaining parallel spreadsheets. The moment a compliance analyst rebuilds an income calculation in Excel because the platform cannot express your programme stack, and then types the answer back in, you have started paying for custom software without receiving an asset for it.
When does a custom build actually pay off?
The build case rests on a structural limit rather than a missing feature. Packaged platforms model programme as an attribute of the property. Your exposure lives at the unit and the household, where several rule sets apply at once and do not agree with each other.
- Three or more programmes on the same unit. Tax credits plus project based Section 8 plus a HOME loan plus a local restriction is four income limit series, four household definitions, four recertification cadences and four consequences for failure. A household can be qualified under one and out of compliance under another.
- You use the average income set aside. Income averaging turns a unit level fact into a building level constraint, so one over income household determines how the next several units must be designated. That is continuous arithmetic, not a monthly report.
- A finding traced back to inconsistent income determination across sites. This is the signal that your problem is process rather than knowledge, which is exactly what software fixes.
- Five or more state agencies. Each housing finance agency takes annual owner certifications and tenant data in its own format, several revise the specification yearly, and each revision arrives with a deadline attached.
- You provide compliance services to other owners. Then the platform is your product rather than your overhead, and the arithmetic changes completely.
The underlying point is defensibility. An agency reviewer disagreeing with an annualisation method eighteen months after the fact turns into a recapture conversation, and the difference between a clean outcome and a bad one is whether the file can show how the number was reached, from which documents, under which rule, on which date.
How do they compare on the things that matter in this industry?
On voucher and certification transmission to the federal system, buying wins outright. Specifications change field requirements and validation on their own schedule, and keeping pace is continuous work with no strategic value to you.
On multi programme certification, a build wins because the packaged model cannot express the question. Programme participation needs to attach to the unit and the household with effective dates, so a certification runs every applicable rule set and returns a result per programme, stating conflicts explicitly rather than collapsing them into one pass or fail.
On reproducibility, a build wins and this is the point most owners underrate. Income and asset determination has been changing in stages under the Housing Opportunity Through Modernization Act. A system that recomputes a 2024 file under 2026 logic produces a number that does not match what was certified, which is precisely the discrepancy a reviewer will pursue. Versioned effective dated rules, with each figure storing its inputs, source document, rule version and approver, is the fix.
On file completeness, a build can score continuously against a required document list keyed to household composition and income type, and can flag a verification that will age out before the effective date while there is still time to redo it. Packaged platforms store documents well and generally do not know what is missing.
On configuration ceiling, packaged products are strong at the mainstream configuration of each programme and thin at the edges. That is a rational product decision on their part, not a defect, and it is why the honest answer for most portfolios is a layer rather than a replacement.
What does total cost of ownership look like at your scale?
A focused first release runs $70,000 to $150,000 over 14 to 20 weeks in Digital Heroes delivery experience: the certification engine with income and asset determination, programme participation with effective dates, set aside and applicable fraction tracking, and live document completeness scoring. A full platform adding federal voucher processing, state agency submission formats, utility allowances, next available unit enforcement at leasing and an audit ready repository runs $180,000 to $420,000 across 8 to 14 months.
The line items that move the total are specific. Each additional programme is $25,000 to $55,000. Each state agency mapping is $6,000 to $12,000. The average income set aside engine is $20,000 to $45,000. Rule versioning is $18,000 to $40,000. Integration with Yardi, RealPage or MRI is $25,000 to $50,000, and they are three different problems rather than one with three labels.
Running costs are the part quotes omit. Support and maintenance is 18 to 25 percent of build annually. Federal submission releases add $12,000 to $30,000 a year, state format changes $10,000 to $25,000, rule maintenance $15,000 to $40,000. Retention storage grows and is never pruned, because records must be kept well beyond the compliance period.
Against that, take your per unit per month compliance module figure, multiply by affordable units and twelve, then add the analysts rebuilding calculations in spreadsheets and the file assembly effort in the fortnight before each review. For most portfolios that comparison alone does not decide it. What decides it is exposure sized by your asset management team, because a bad certification risks the credit on one unit while a broken set aside is a building level problem.
What does the hybrid look like, and when is it the honest answer?
For nearly every owner reading this, the hybrid is the recommendation rather than the fallback. Keep the property management platform for leases, units, accounting and household composition. Keep its voucher transmission. Build only the compliance layer above it, and integrate.
That structure preserves the integrations you already paid for, puts custom effort exactly where the exposure sits, and keeps the platform decision reversible. It also lets you start narrow. Begin with your largest programme combination and the properties still inside their initial compliance period, which is where risk concentrates, and leave the long tail of smaller stacks for a later phase.
Sequence agency formats by unit count. Two agencies covering seventy percent of units first, the rest once the mapping pattern is proven and cheap to repeat. Let the platform keep voucher processing through the first release: certification correctness is the expensive problem, and transmission is a process that already runs.
On history, be deliberate. Legacy certification records carry the resulting figures but almost never the workings. How much you reconstruct is a policy decision for compliance leadership, not a technical requirement, and most owners bring current certifications forward and index the rest as documents. That single decision often saves more than any feature you could cut.
Which should you choose, by operator size and stage?
Under 2,000 units, single programme, one or two states: buy. Yardi Affordable Housing or RealPage OneSite Affordable will serve you properly, and the money is better spent on compliance staff who can absorb the next rule change.
Two to six thousand units, two programmes, a handful of agencies: stay bought, and fix the process first. Write the determination policy down, introduce peer review on complex households, and count how many certifications currently require a spreadsheet. If that count is small, you do not have a software problem yet.
Six thousand units and up, three or more layered programmes, or any portfolio using income averaging: build the compliance layer. The first release at $70,000 to $150,000 is the defensible starting point, and it should sit above the property platform rather than replace it.
Large owners reporting to five or more state agencies, or compliance service providers: build the full platform over 8 to 14 months, and add a contingency, because at least one agency will reissue its file specification mid project.
Whatever the size, settle ownership in writing before kickoff. You should hold the repository, the cloud accounts, the database and the document store. Affordable housing records must be retained well beyond the compliance period, and a system whose data is reachable only while a licence is current is the one arrangement you cannot accept.
When you are ready to turn this into a specification, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- In a February 2026 survey of 517 small-business employers, 82% had adopted at least one AI tool (typical firm uses five), 66% reported revenue increases linked to AI (22% reported gains exceeding 10%), and 74% said digital platforms make it easier to compete with larger firms; owners saved a median of 5 hours per week and businesses saved a median 11.5 employee-hours weekly. Source: Small Business & Entrepreneurship Council (SBE Council) (2026) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
Frequently asked questions
What does it cost to switch off Yardi or RealPage later?
More than the licence difference, which is one reason we advise building above the platform rather than replacing it. The cost sits in lease and unit history, accounting integration and the retrained habits of site staff, and it recurs every time you change.
A compliance layer that owns certifications and the document store keeps that decision open. If you do change platforms later, the integration is re pointed rather than rebuilt, and the compliance history that a reviewer will ask about never moves.
What happens if our platform vendor changes per unit pricing at renewal?
Your exposure is proportional to how much of your compliance record lives inside their product. If certifications, workings and audit evidence sit in vendor fields, a per unit increase across a growing portfolio is a notification rather than a negotiation.
Owning the compliance layer while renting leases and accounting caps that. It also gives you a real alternative to price the vendor's compliance module against, which tends to improve the conversation.
How long does a compliance platform take to build?
Fourteen to 20 weeks for a first release with the certification engine, programme participation, set aside tracking and completeness scoring. Eight to 14 months for the full platform with federal submission, state agency formats, utility allowances and audit export.
The largest schedule risk is historical certification migration, because legacy records carry figures without workings. Decide how much history to reconstruct before kickoff and treat it as a policy call made by compliance leadership.
Is MRI Affordable Housing a better answer than a custom layer?
If your portfolio is conventional and already on MRI, keeping it is the cheaper answer and the integration you have is worth something. Judge it on one test: ask whether it can evaluate a unit under tax credits, project based Section 8 and a HOME restriction at once and report a result per programme.
Where the answer is custom fields plus a spreadsheet, you are paying a licence to keep the manual work. Where the vendor can genuinely configure it, buy the configuration.
Can we build only the certification engine and keep everything else?
Yes, and it is the structure we recommend most often. The first release at $70,000 to $150,000 covers determination, programme participation, set aside tracking and completeness scoring, while the platform keeps leases, accounting and voucher transmission.
Budget $25,000 to $50,000 for the integration, and expect it to differ materially depending on whether you are on Yardi Affordable Housing, RealPage OneSite Affordable or MRI Affordable Housing.
Why does the average income set aside change the build or buy answer?
Because it converts a unit level fact into a building level constraint. The mix of designated imputed income levels has to average to the committed figure, so one over income household can determine how the next several units must be designated.
That needs recalculation on every move in, move out, recertification, transfer and designation change, surfaced when leasing approves an applicant. Expect $20,000 to $45,000 for that engine, and treat a spreadsheet version as a temporary arrangement rather than a control.
Will a state agency reviewer accept records from software we commissioned?
Yes. Reviewers examine the file and the evidence, not the vendor name on the system. What matters is that each figure carries its inputs, the source document for each input, the rule version applied and the approver, and that the file exports in the order the reviewer wants with an index.
A portfolio whose files assemble themselves continuously arrives at a review in a different position from one that assembles them the week before.
When should we not build compliance software at all?
When the inconsistency between your sites comes from training rather than tooling. Software will record two managers certifying the same household differently, and recording it is not the same as preventing it.
Also hold off under roughly 2,000 units on a single programme in one or two states. The packaged platforms handle that portfolio properly, and a six figure build will not pay back against a licence that is already doing the job.
Who owns the code when an agency builds our internal tool?
You should, outright, with full IP transfer in the contract and the code delivered to a repository you control, such as your own GitHub organization. Digital Heroes transfers complete ownership on final payment as standard practice, and any agency that keeps the code or licenses it back to you is building a dependency you will pay for later. Confirm you also own the hosting, domain, and database accounts, since many of the vendor disputes Digital Heroes gets called into involve infrastructure registered under the agency's name.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How much does a custom internal tool cost to build?
Most custom internal tools cost $8,000 to $40,000 to build, based on Digital Heroes delivery data across 2,000+ client projects. A single-purpose tool like an approval dashboard or inventory tracker sits at the low end, while a multi-department platform with role-based access and several integrations pushes past $40,000. The three biggest cost drivers are the number of user roles, the number of systems the tool must connect to, and custom reporting requirements.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
How many developers does it take to build an internal tool?
Two to four people covers nearly every internal tool: one or two developers, a part-time designer, and a project manager who doubles as your single point of contact. Internal tools rarely need consumer-product polish, so a full-time dedicated designer is usually wasted budget. On Digital Heroes projects, a two-person core team handles the typical 4 to 8 week build, with a specialist pulled in briefly for a tricky integration or a security review.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other internal tools companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Olivia.
Performance Marketing Lead · New-york · 4 posts on the site
Published · Last updated .
