Submetering and Utility Billing Software: Build vs Buy
Outsource it. Under about 3,000 units in one or two states, hand recovery to Conservice or your property management platform and spend the difference on meters that read reliably.
On this page
Outsource it. Under about 3,000 units in one or two states, hand recovery to Conservice or your property management platform and spend the difference on meters that read reliably. Building becomes defensible once you bill back across many jurisdictions, or when you are the billing service provider running recovery for other owners and the fee is your margin rather than your cost.
Custom versus off the shelf: what Conservice and the platform modules do well
This category has three options rather than two, and the third is the one most owners should take. You can build, you can license a module, or you can outsource the whole function. Outsourcing is usually correct, and any honest comparison starts there.
Conservice does the unglamorous work: chasing utility invoices, entering them, allocating, producing resident statements, and handling the first line of resident questions. RealPage Utility Management and Yardi's utility billing sit inside the platform you already run, so the charge posts to the resident ledger without an interface. All of them track which jurisdictions permit which allocation methods, which is knowledge you would otherwise acquire the hard way.
Buy or outsource if this describes you:
- Under roughly 3,000 units, concentrated in one or two states.
- Mostly one recovery method across the portfolio rather than a mix by property.
- No ambition to bill on behalf of other owners.
- Resident disputes arriving at a manageable rate, and answerable within a day.
- Meters that read reliably, which matters more than any software decision on this page.
That last point deserves emphasis, because it is where the money actually goes. A portfolio with unreliable reads and excellent software produces confident, wrong bills. A portfolio with reliable reads and a spreadsheet produces correct ones slowly. If your read failure rate is high, fix the hardware before reading further.
Where they stop: the master bill and the resident bills never tie out
The workflow generic billing tools model badly is reconciliation, and its absence is invisible until it is expensive.
The utility bills the property a total. You bill residents a set of amounts. Those two figures should reconcile to a known difference: common area consumption, vacant units, and any owner retained portion. When they do not, something specific is wrong. A unit is missing from the roll. A read failed and was estimated. The utility billed 34 days and you billed 30, so the period boundaries do not match. A tier was applied at the wrong level.
Most systems produce resident bills and never compute that variance at all. Nobody finds out until a resident challenges a statement, an auditor samples a month, or a state agency asks how a total was derived.
The second break is that allocation formulas are legal text rather than arithmetic. A ratio utility billing system allocation weighted by occupancy and square footage is permitted in some jurisdictions and restricted in others, and some restrict it for water entirely. California governs water submetering in multifamily property through Civil Code sections 1954.201 through 1954.219, with specific billing content and dispute requirements. Texas regulates submetered and allocated water and electric charges through Public Utility Commission rules that dictate what may be recovered and how. A product with a dropdown of allocation methods does not carry the rule that permitted the method, and the rule is what you have to produce later.
The third is proration and vacancy, which is where money leaks quietly in both directions. A resident who moves out eight days into a read interval owes eight days. Those eight days belong to the owner unless your lease and jurisdiction say otherwise. Systems that prorate by calendar month rather than by actual days against the read interval either overcharge residents, which is the expensive kind of error, or silently absorb vacant cost that should have been posted to the property.
The fourth is the dispute. A resident asks why the bill is high. The answer should be a single statement showing the master bill, the period, the allocation method with the rule that permitted it, this unit's read pair with dates, the proration days, any fee, and every recalculation ever applied. In most portfolios that answer takes a person forty minutes across three spreadsheets.
The arithmetic: per unit billing fees versus the cost to build
Outsourced recovery is priced per unit per billing cycle, and platform modules are priced per unit per month. Both are small numbers that become significant at scale, so convert everything to cost per unit per year.
Take the fee, multiply by units and cycles, and add anything charged for resident statements or portal access. Then add what the fee does not cover: the on site staff time spent answering disputes, the accounting hours spent reconciling the utility invoice against what was recovered, and the vacant cost you are absorbing because nobody computes it.
Cost the build the same way. Midpoint of the bands below, plus year two support, over five years, divided by units.
In our delivery experience the crossover lands near 8,000 units billed, or any operator working across four or more states with different allocation rules, or the point at which you bill on behalf of other owners. The last case is decisive and has nothing to do with size. If recovery is a service you sell, the per unit fee is your revenue rather than your cost, and paying a third of it to a provider is a margin decision rather than a technology one.
Confirm whether your fee follows units, occupied units or statements issued. The three diverge sharply in a portfolio with meaningful vacancy.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering meter read ingestion, allocation and submeter billing, prorations and a per unit audit trail runs $60,000 to $130,000 and ships in 12 to 18 weeks. A full platform adding master bill reconciliation, state and municipal rule configuration, a resident portal with dispute workflow, property accounting posting and vacant cost handling lands at $150,000 to $380,000 phased over 7 to 12 months.
Data migration is 10 to 25 percent of build cost, and the read history is why. You need enough historic reads to detect a failing meter and to answer a dispute about a prior period, and historic reads frequently arrive with inconsistent interval boundaries and estimates that were never trued up. Loading them is easy. Deciding which are trustworthy is the work.
Year two runs 15 to 20 percent of build cost annually. It buys meter vendor format maintenance, utility invoice layout changes, and rule updates when a state or municipality revises what may be recovered. Name who watches for those changes, because after you build it is no longer a vendor's job.
The four situations where building wins
- Regulatory fit. Operating across several states and municipalities where permitted allocation methods, required bill content and dispute handling differ, and every bill must carry the rule that authorised it.
- Scale economics. A large billed unit count where per unit fees have passed the amortised cost of owning the system.
- Recovery as your product. You are a billing service provider, and accuracy, dispute turnaround and the audit trail are what your clients are actually buying.
- Integration sprawl across three or more systems. Meter data collection, the property management platform for the resident ledger, accounting for the property side posting, and a resident payment provider.
One of those true means keep the outsourced arrangement and build the reconciliation layer beside it. It is the cheapest way to find money you are currently losing.
How to decide in a week, ending with a specification you own
Run the tie out test on a single property.
Pick one property and one month. Add every resident utility charge issued for that period. Compare it against the master utility invoice for the same period, adjusted for common area and vacant units. Write down the difference and then explain it, line by line, until nothing is left unaccounted. Most operators doing this for the first time cannot close the last few percent, and the reason they cannot is the specification for what to build.
Then run the dispute test. Take one resident statement at random and produce the full derivation: master bill, period, allocation method, permitting rule, read pair with dates, proration days, fees, recalculations. Time it. If it takes more than five minutes, that is your daily cost multiplied by every call your site teams take.
Finish by pulling read failure counts for the last quarter and checking how many estimates were later trued up against an actual read. Estimates that never get corrected are the quiet liability in this business.
If the case holds, buy a discovery phase before a build. At Digital Heroes it ends in a signed product requirements document covering the allocation rule model, the reconciliation logic and acceptance criteria, and you own it whether or not you continue with us. We hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, run more than fifty specialists across over 2,000 projects including our own products ShopScore, HeroCheckout and Section Vault, and you meet the named team before signing. We are checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
We are the wrong firm for an owner with 1,500 units in one state. Outsource the function, buy better meters, and revisit this in three years.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- McKinsey argues software developer productivity can be measured by combining system-level metrics (DORA and SPACE) with its own outcome-oriented approach, which it reports deploying across nearly 20 tech, finance, and pharmaceutical companies - a claim that sparked significant debate in the engineering community. Source: McKinsey & Company (2023) →
- Sensor Tower's State of Mobile 2026 reports that global users spent 5.3 trillion hours in iOS and Google Play apps in 2025 (+3.8% YoY), roughly 3.6 hours per day per mobile user. (Note: the page does not itself contrast app time vs. mobile-browser time, so the 'overwhelming majority of time in apps vs browsers' framing is not directly supported by this source.). Source: Sensor Tower (2026) →
Frequently asked questions
How long does a submetering billing system take to build?
Twelve to eighteen weeks for a first release covering read ingestion, allocation, prorations and the audit trail. A full platform with master bill reconciliation, rule configuration and a resident dispute portal takes seven to twelve months. Run the new system in parallel for two complete billing cycles before it issues a single resident statement, comparing outputs line by line. Billing errors in this category reach residents immediately and are remembered.
Who owns the billing records and the code if the developer relationship ends?
You should own the repository, the cloud accounts and every read, statement and recalculation in the system. Settle it before development starts. At Digital Heroes the client owns the code from the first commit. Read history matters especially here, because a dispute or a regulatory question about a prior period cannot be answered from a current balance, only from the underlying reads and the rules applied.
Can we build only the reconciliation piece and keep our current provider?
Yes, and it is the highest return first step by a wide margin. A reconciliation service takes the master utility invoice and the issued resident charges for the same period, computes the variance, and raises an exception with a probable cause. It touches no resident bill and requires no change to your provider relationship. Most operators find money in the first quarter of running it.
What happens if a meter fails and reads are estimated?
Estimation is acceptable in most jurisdictions provided it is disclosed and trued up against a later actual read. The failure that causes trouble is an estimate that is never corrected, which quietly becomes the resident's permanent charge. A build should mark every estimated read, hold the truing obligation open as a task, and recalculate automatically when a real read arrives, keeping both versions visible.
Should an owner with 1,200 units build anything?
No. At that size outsourced recovery costs less than the specification work, and the provider carries the jurisdictional knowledge that would otherwise take you a year to acquire. Put the money into meter reliability, which improves every downstream number. Revisit the build question when you cross several thousand billed units or start operating in states with materially different allocation rules.
What is the difference between submetering and a ratio utility billing system?
Submetering measures each unit's actual consumption with a physical meter and bills the measured amount. A ratio utility billing system allocates the master bill by a formula, usually occupancy and square footage, with no measurement at unit level. Submetering is defensible almost everywhere. Ratio allocation is restricted in some jurisdictions and prohibited for water in others, which is why the permitting rule belongs on the bill record.
Can we post utility charges straight to the resident ledger?
Yes, and you should, but keep the derivation outside the ledger. The ledger holds the charge and the payment. The billing system holds the master bill, the reads, the allocation method, the rule, the prorations and every recalculation. Posting a summarised charge into the property platform keeps your accounting unchanged while preserving the detail that answers a dispute two years later.
How do we handle vacant unit consumption?
Compute it explicitly and post it to the property rather than absorbing it into the pool residents pay. A vacant unit still consumes, particularly during a turn with heating, cooling and cleaning running. Systems that prorate by calendar month rather than by actual days against the read interval tend to lose this amount silently, which distorts both your recovery rate and your operating expense reporting.
What happens if a state changes what we are allowed to recover?
After you build, tracking that change becomes your responsibility. Keep permitted methods, required bill content and fee caps as configuration with effective dates, so bills issued under the previous rule remain provable and new ones follow the current one. Assign the monitoring to a named person in each state you operate in, and write that into the year two support scope rather than assuming it.
Is it worth building if we bill on behalf of other owners?
Usually yes, and this is the clearest case in the category. When recovery is a service you sell, the per unit fee is revenue rather than cost, and dispute turnaround and audit quality are the product. You also need tenancy separation so each owner sees only their portfolio, plus per client rule configuration. Those requirements alone tend to rule out the packaged modules.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
How many developers does it take to build accounting software?
The standard Digital Heroes team is 4 to 6 people: a backend developer, a frontend developer, a QA engineer, a part-time designer, and a project lead who owns the accounting logic. A single-workflow automation can ship with two people, while multi-entity platforms with payroll can need eight. Headcount matters less than having one named person accountable for the books balancing.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Can I extend QuickBooks with custom features instead of replacing it?
Yes, and it is often the right first step. QuickBooks Online has a public API, so an agency can build a custom layer for quoting, inventory, or field service that pushes clean transactions into QuickBooks, which stays your ledger of record. Roughly half of the accounting engagements Digital Heroes scopes start this way because it costs a fraction of a full build and leaves your accountant's workflow untouched.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What happens to my accounting software if the agency shuts down?
If you own the repository, the hosting accounts, and the documentation, another team can take over within weeks, usually before a missed closing cycle does real damage; if the agency owns any of those, you have a hostage situation. Before signing, confirm the code sits in your GitHub or GitLab organization, hosting bills to your card, and a written deployment runbook exists. A competent agency agrees to all three without friction, and hesitation is itself the answer.
What tech stack should custom accounting software use?
A boring, proven one. Digital Heroes defaults to PostgreSQL for the ledger because transactional integrity is non-negotiable, a typed backend such as Node with TypeScript, .NET, or Java, and standard React on the front end. The avoid list is clearer than the pick list: floating point math for money, a NoSQL database as the primary ledger store, and any framework young enough that hiring for it in three years will be a problem.
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.
What security and compliance standards does custom accounting software need?
At minimum: encryption at rest and in transit, role-based access control, and immutable audit logs recording every change to the ledger. If outside parties rely on your numbers you will want SOC 2 style controls, and storing card data pulls you into PCI DSS, which most builds avoid by tokenizing payments through Stripe or a similar processor. Your industry adds its own rules, so compliance requirements belong in the written spec, not in a post-launch retrofit.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software 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 accounting software 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
Published · Last updated .
