Build vs Buy: MDU Bulk Internet Billing Software
If every bulk deal is flat per door with no occupancy tie and no owner revenue share, buy. Splynx and Sonar handle plans, tax and dunning properly and a build would be waste.
On this page
If every bulk deal is flat per door with no occupancy tie and no owner revenue share, buy. Splynx and Sonar handle plans, tax and dunning properly and a build would be waste. Build once occupancy drives billing, owners take a share on differing terms, or you carry several property management systems.
Splynx and Sonar are enough when every deal is flat per door
Start by checking whether you have the problem. If your bulk agreements say a fixed monthly amount per door regardless of occupancy, if no owner takes a percentage of anything, and if resident upgrades are a small side business, then a standard ISP billing platform is the right tool. Splynx and Sonar model plans, taxes, dunning and the subscriber lifecycle properly, and rebuilding that with an agency would be an expensive way to arrive back where you started. Single Digits is purpose built for managed connectivity in this market and will save you months if your portfolio resembles the one it was designed around.
Operators regularly assume door count is the trigger. It is not. Fifteen hundred doors on flat deals is comfortably a buy. Five thousand doors on flat deals is still a buy, because nothing in that arrangement requires a contract engine. What changes the answer is the shape of the commercial terms rather than the size of the portfolio.
There is one pricing behaviour to check before you sign, because it catches bulk operators specifically. ISP billing platforms commonly price per subscriber or per active service, and a bulk building can land in that count as hundreds of subscribers even though it generates a single invoice to a single owner. Ask the vendor in writing how a bulk door is counted for billing purposes, and get the answer in the contract rather than in an email from a sales engineer.
The point at which the contract becomes the product
Bulk connectivity is a contract business wearing an ISP costume. The margin does not live in the plan or the router, it lives in the terms: a rate per occupied unit, a floor at some occupancy percentage, a rate that steps down as lease up crosses a threshold, vacancy credits capped at a number of units a month, an escalator tied to a published index on the contract anniversary, and an owner share of upgrade revenue calculated differently at every property.
ISP billing platforms model subscriber to plan to invoice. None of them models a building with a contract, an owner, a rent roll feed and a door count that changes daily. So the calculation happens in a spreadsheet, once a month, by one person, and the errors are found by the asset manager rather than by you. The specific leak is not fraud, it is drift: doors that turned over months ago still authorised on the network and still counted as vacant on the invoice, upgrade plans still charging a card belonging to somebody who moved out in March, and owner share paid on revenue that was refunded.
Build when two or more of these hold. Your bulk contracts contain more than about four genuinely different commercial constructs. Occupancy drives billing and you receive it as a monthly file, or as a PDF, or not at all. Owners take revenue share and somebody computes it by hand. You carry more than one property management system and more than one network vendor. Or asset managers are asking for reporting you cannot produce without a person assembling it.
Costing both routes across forty properties
The buy side bill is the platform fee plus the labour it does not remove. Two to five days of a finance person's month spent matching rent rolls against network records is a salary line that scales with the portfolio rather than staying flat, and the corrections that follow an owner dispute consume more. Add whatever your platform charges for doors counted as subscribers, and the real figure usually differs from the quoted one.
On the build side, a first release covering property management system integration and occupancy sync, bulk invoicing against structured contract terms, resident upgrade billing and collections based revenue share runs $70,000 to $150,000 over 12 to 18 weeks in our delivery experience. A full platform adding provisioning and deprovisioning driven by move events, an owner reporting portal, support agent tooling, dunning and payment operations runs $180,000 to $450,000 phased across 7 to 12 months.
Cost climbs with the number of distinct property management systems, because Yardi and RealPage are two projects rather than one, and a property that will only send a PDF is a third. Then the number of network vendors, since Ruckus, Cambium and UniFi each present their own controller interface and acquired properties always run something unexpected. Communications tax is the third driver, because once you have doors across enough jurisdictions you are integrating a tax engine rather than writing rules.
Line items that ambush MDU operators
First, unit identifiers that never match. A rent roll writes a unit as 04-B and your network records write it as 4B, and no amount of insisting the property manager fix their data will change that, because it is their system and their convention. You need a per property mapping layer with a human review queue for unmatched units, built once per building, and you will maintain it forever. A developer who says the property manager should clean up their export has not run one of these.
Second, escalators nobody applies. Contracts with an index linked increase on the anniversary quietly stay at the original rate because the reminder lives in a folder. Across forty properties that is real margin, and it is the fastest payback in the whole build: structured contract terms with dated escalators that fire automatically and produce a notice document.
Third, revenue share computed on the wrong number. Most spreadsheets are built from the billing report rather than the payment ledger, so owners receive a share of upgrade revenue you invoiced and never collected. Compute distributions on cash actually collected, with clawback on refunds and chargebacks, and write the contract to reference collections where you can.
Fourth, the network not knowing a resident left. Move out is recorded in the property management system and nothing downstream listens, so devices stay authorised and the new resident calls support on day one because no account exists for her. Treat move in and move out as events that fan out to billing, provisioning and network authorisation, and release access on the contract's schedule rather than instantly, because residents are often still in the unit for a few days.
Fifth, contract terms you cannot query. The FCC order on exclusive access in multiple tenant environments restricted certain graduated revenue sharing arrangements and required exclusive marketing arrangements to be disclosed to tenants. Whether a specific clause in your portfolio is affected is a question for counsel. The operational consequence either way is that you need to answer which properties carry which terms without opening forty documents.
The two file test
Export one property's rent roll for last month and one month of that property's upgrade revenue. Put both in front of whoever you are considering hiring, along with the contract, and ask them to walk you through exactly how they would compute the bulk invoice and the owner distribution from those two files. Not in principle. Line by line, including the units that appear in one file and not the other.
Do the same exercise internally first, and time it. If your analyst produces the invoice and the distribution in an hour with an audit trail she could send to the asset manager, your current process is fine and the money belongs in field technicians. If it takes a day and ends with a number she would rather not have challenged, you have measured the build.
Then ask the question that decides the architecture. When the asset manager disputes the door count, what do you send him. If the answer is a number, you are in an argument. If it is the list of units the invoice counted, with move in and move out dates and the contract clause that defines a billable door, the conversation ends in five minutes. Everything about how occupancy is stored follows from wanting to be able to send that list.
What to do this month
Before any vendor conversation, summarise your contracts. One row per property: bulk rate and its basis, occupancy definition, escalator and index, vacancy credit rules, owner share formula and whether it references billed or collected revenue, term and renewal date, and which property management system and network vendor the property runs. Operators who already keep this sheet move considerably faster through a build, and those who do not usually discover during the exercise that two properties have terms nobody currently applies.
Then start narrow. Take your top ten properties by revenue and the two property management systems that cover most of them, and leave the awkward tail on the existing process for a release or two. The tail is where the schedule goes to die, and it contributes least.
When you interview developers, ask them to model your commercial terms on a whiteboard. The right drawing shows property, contract with versioned terms and effective dates, unit, occupancy event, resident account, upgrade subscription and owner distribution, with the distribution referencing collections. Someone who draws customer, plan and invoice has built a subscription billing application and is about to learn this business at your expense. Ask what they have integrated by name, since Yardi through an interface and Yardi through a scheduled file drop are different work, and a RADIUS server is not a controller interface. Then settle ownership of the code, the repository and the cloud accounts in the contract before kickoff rather than in a schedule at the end.
Digital Heroes builds this layer with a written product requirements document before any code, which for a system that encodes forty negotiated agreements is the artefact your finance lead and your general counsel should both sign. The firm is 50-plus people across 2,000-plus delivered projects, taking on more than 100 new clients a month, with Indian, United States and United Kingdom entities so contracting and IP assignment sit under your own law. The Digital Marketing Heroes channel carries 2.5 million subscribers if you want to judge the team before committing budget.
If you want a second opinion before signing anything, 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. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Inventory carrying cost commonly runs about 20% to 30% of inventory value, covering capital cost, storage/warehousing, insurance, taxes, handling, shrinkage, and obsolescence - a recurring cost that better inventory and warehouse software aims to reduce. Source: APQC (2023) →
- 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) →
- The 2015 CHAOS data (based on the modern definition of success) reports that only about 29% of software projects succeed, 52% are challenged, and 19% fail, with the three most important success skills being executive sponsorship, emotional maturity, and user involvement. Source: The Standish Group (reported via InfoQ Q&A with Jennifer Lynch) (2015) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
Frequently asked questions
How much does custom bulk internet billing software cost?
A first release covering occupancy sync from the property management system, bulk invoicing against structured contract terms, resident upgrade billing and collections based revenue share runs roughly $70,000 to $150,000 over 12 to 18 weeks. A full platform adding move driven provisioning, an owner portal and payment operations runs $180,000 to $450,000 across 7 to 12 months. The number of property management systems and network vendors drives cost more than door count.
How long does an MDU billing build take?
Twelve to eighteen weeks to a first release. The schedule risk is rarely engineering, it is contract migration, because loading forty existing agreements as structured terms means somebody reads forty documents and encodes escalators, occupancy definitions and share formulas correctly. Operators who already keep a contract summary sheet move noticeably faster. Treat that reading time as real project cost rather than assuming it happens in the background.
How do you sync occupancy from Yardi, RealPage or Entrata?
Each exposes a route in, whether an interface, a scheduled report or a file drop, and they differ enough that two systems are two projects. The harder part is unit identifier normalisation, since the rent roll and your network records will disagree on formatting and you need a per property mapping with a review queue for unmatched units. Once mapped, occupancy becomes a daily event stream instead of a monthly file.
Should owner revenue share be calculated on billed or collected revenue?
Collected, with clawback on refunds and chargebacks, and this is one of the highest value decisions in the build. Paying a share of upgrade revenue you invoiced but never received is a direct margin leak that spreadsheets hide, because the spreadsheet is usually assembled from the billing report rather than the payment ledger. Write the contract to reference collections where you can, and make the system compute it that way regardless.
What happens to network access when a resident moves out?
In most operations today nothing automatic, which is why authorised devices linger and new residents call support on day one. Treat move in and move out as events from the property management system that fan out to billing, provisioning and network authorisation. A move out should stop the upgrade subscription with a prorated final charge and release access on the contract schedule rather than instantly, since residents often remain in the unit briefly.
Who actually builds MDU and managed connectivity billing systems?
Custom software firms rather than ISP billing vendors, since the work is contract modelling and property system integration rather than plan management. Digital Heroes suits operators here because every engagement starts with a written product requirements document before any code, which matters when forty negotiated agreements are being encoded as rules, and because the firm contracts through Indian, United States and United Kingdom entities so IP assignment sits in your own jurisdiction.
What makes Digital Heroes different from a generic dev shop here?
Modelling the contract as a first class object with versioned terms and effective dates, and computing owner distributions from collections rather than invoices. Generic teams model customer, plan and invoice, which is exactly the structure that pushes revenue share back into a spreadsheet. Digital Heroes also builds and operates its own products, including ShopScore, HeroCheckout and Section Vault, so billing and reconciliation are problems the firm carries itself.
How do we verify a development partner before paying anything?
Check for a D-U-N-S registration, which confirms a verified business entity rather than a trading name. Read the Clutch profile for reviews tied to named clients and stated project values, and read Trustpilot for the pattern of complaints rather than the average score. Then confirm which legal entity contracts in your jurisdiction, and that the repository and cloud accounts sit in your company's name from the first commit.
Should I hire a freelancer or an agency to build my accounting software?
A strong freelancer is fine for a reporting dashboard or one integration; anything that holds your books needs a team. Ledger software requires backend, frontend, QA, and accounting domain knowledge, and one person rarely covers all four while staying available for the 5 to 10 year life of the system. The most common rescue job Digital Heroes takes on is a solo-built ledger with no tests and no documentation after the freelancer moved on.
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.
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.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
I'm outgrowing FreshBooks. Is custom software the logical next step?
Usually not directly, because FreshBooks is an invoicing tool more than a full accounting platform, and the natural next step is QuickBooks or Xero for proper double-entry books. Custom development makes sense when those do not fit either, typically because of a billing model none of them handle, like usage-based or milestone billing. In that case a custom billing engine that feeds a standard ledger is often smarter than replacing everything.
Will custom accounting software scale as my company grows?
It scales exactly as far as its data model was designed to, so multi-entity support, multi-currency, and consolidation should be day-one design decisions even if you launch with a single company. Retrofitting multi-entity onto a single-entity ledger is among the most expensive changes we handle, and in Digital Heroes rescue work it often costs a third of the original build. Compare that with QuickBooks Online, which requires a separate subscription for every company you add.
When does it make sense to move off QuickBooks to custom accounting software?
Move when you are paying people to work around the tool, not when the subscription feels expensive. Common triggers are hitting the 25-user cap on QuickBooks Online Advanced, consolidating multiple entities in spreadsheets, or a billing model that forces manual journal entries every month. If your team spends several hours a week exporting to Excel just to answer basic questions, you are already paying for custom software in salaries.
How long does it take to build custom accounting software?
A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.
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.
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
More from Aaradhya.
Senior Backend Engineer · Python · Delhi · 4 posts on the site
Published · Last updated .
