Build vs Buy ISP Subscriber Management and Billing Software
Buy. For a single technology internet service provider under roughly five thousand subscribers, Sonar or Splynx will serve you for years and the money belongs in plant.
On this page
Buy. For a single technology internet service provider under roughly five thousand subscribers, Sonar or Splynx will serve you for years and the money belongs in plant. Build only for structural reasons: mixed access technologies, cooperative or multi entity accounting, wholesale and open access billing, or plan structures your product simply cannot express.
This is a category where the products are genuinely good
We turn down work here regularly, so take the recommendation at face value. Sonar, Splynx, Powercode, Azotel, Visp, UISP, Rev.io and Inomial Smile were built by people who understand internet service providers. They cover the subscriber record, plan management, invoicing and dunning, provisioning integration, ticketing, inventory and scheduling to a standard that would take a custom team many months to reach, and they are priced at a fraction of a build.
If you run one access technology, have a conventional plan structure, operate as one legal entity and sit under a few thousand subscribers, pick one, implement it properly and go back to splicing fibre. A custom platform at that size is a distraction that competes with plant for capital, and plant is the thing that grows the business.
Buying is also correct while you are still growing quickly. A network heading from two thousand to eight thousand subscribers in eighteen months changes shape as it goes, and committing engineering budget to a bespoke subscriber model during that period means building for a business you will not recognise in a year. Let the product absorb the change, note every workaround your staff invents, and revisit the question once the shape settles.
There is a third case. If your immediate pain is that suspension in billing does not actually disconnect anyone, that is often a single integration rather than a platform. Fixing the path from billing status to network state inside your existing product is a far smaller project than replacing the product, and it recovers real money.
The structural mismatches that justify a build
When a product stops fitting an internet service provider, it is almost never about features. It is about structure, and there are five recognisable versions of it.
Mixed access technology is the first. Products carry the heritage of the networks they were born on, so a platform shaped around fixed wireless makes assumptions about how service is delivered that do not map cleanly onto passive optical networks, and the reverse holds too. An operator running both usually ends up with one technology properly modelled and the other handled by convention and memory.
Entity structure is the second, and it is the most common among cooperatives, municipal networks and holding companies that acquired several small providers. Products assume one company with one general ledger. Member and patronage accounting, separate ledgers per entity and consolidated reporting across them tend to sit outside the model entirely.
Wholesale and open access is the third. Where you carry another provider subscribers over your network, or your subscribers ride someone else network, the billing subject is a provider rather than a household. That effectively doubles the billing model and very few products attempt it.
Plan and promotional structure is the fourth. Contract terms, promotional pricing that steps up, equipment instalments, bundled services and grant funded tariffs are expressible in some products and not others, and where they are not, finance ends up unpicking the workaround every month.
Scale is the fifth. Per subscriber licensing that was invisible at two thousand subscribers becomes a visible line at forty thousand, and at that point the annual fee starts to look like an amortised build.
What each route costs over five years
Per subscriber pricing is the number to model carefully, and there is a detail buyers rarely notice until the first bad month. Many platforms count active subscribers including those suspended for non payment, so a delinquency backlog costs you licence fees at exactly the point you are collecting nothing. Ask how suspended and seasonal accounts are counted before you sign, and model the fee at three times your current subscriber base rather than at today.
On the build side, a subscriber management core runs $80,000 to $180,000 across 13 to 20 weeks, covering the subscriber and service record, plan and promotion rules, billing and payment with dunning, access control integration with verification, serialised customer equipment inventory, address based serviceability and install scheduling. Extending into a self service portal, a technician application, a second access technology, network documentation, wholesale billing and regulatory reporting runs $220,000 to $500,000 across 8 to 14 months. Support and hosting land near a fifth of build each year.
The cheapest version of the build is often the smartest. Keep your existing product for invoicing in phase one and build only the provisioning, inventory and serviceability layer around it. Several operators never replace billing at all, because once those three are solved the product is fine.
The costs that appear after the first billing cycle
The most expensive hidden line in this category is address data. Federal broadband availability reporting is built on a location fabric with its own identifiers, and your customer records hold address strings typed by sales staff. Matching one to the other is a genuine project, it goes stale as the fabric is updated, and challenge windows are short. Operators discover during their first filing that what the sales team believes is served and what the records say is served are two different lists, which is both a reporting exposure and a marketing problem.
The second is provisioning fragility. The path from billing status to network state runs through a RADIUS attribute change, an optical line terminal policy, a wireless queue or a captive portal redirect, depending on the technology. Access vendor firmware updates change behaviour on that path without notice, and a change that silently stops applying looks exactly like nothing happening. Build verification into the design so the system confirms the network accepted the change rather than assuming it.
The third is unrecovered customer equipment. A subscriber cancels, no recovery task is generated, and the optical network terminal or radio is written off quietly. Nobody ever complains about it, which is why it persists, and the annual figure surprises people when it is finally counted.
The fourth is grant obligations. If your build is funded through a federal or state broadband programme, reporting and eligibility requirements arrive with their own definitions and deadlines. Scope those with whoever manages your grant compliance before engineering starts, not after.
The reconciliation test that produces your business case
Run three lists against each other on one afternoon: every subscriber your access network is currently authorising, every unit in your customer equipment inventory marked as deployed, and every account your billing ledger considers active and payable.
Three differences matter. Subscribers live on the network with no billing record, which is the leak nobody reports because the customer is happy. Accounts billing with nothing provisioned, which generates a support call eventually. And deployed equipment attached to accounts that churned months ago, which is capital sitting in someone loft.
Put a dollar value on each of the three. Then count how many times last month a member of staff did something outside the system to make the system work: a manual policy change on the access platform, a spreadsheet to work out a promotional price, a note to remind someone to chase a router. When that count is a daily habit rather than a monthly annoyance, the product has stopped fitting, and you now have both the reason and the number.
One caveat on interpreting the result. A large gap on its own argues for better process before it argues for a build, because a reconciliation report inside your current product will close most of it and costs nothing. What justifies engineering is a gap that reopens every month after you have closed it, since that means the structure of the system keeps recreating the problem rather than staff being careless.
How to sequence it and what to require
Never cut over an internet service provider in a single weekend. Move subscriber, service and inventory data first, run one full billing cycle in parallel against the existing platform, and compare invoice by invoice before switching anything off. Budget that parallel cycle as real cost rather than overhead, because it is where the errors surface cheaply.
In evaluation, ask how a billing suspension becomes a network state change for each technology you run, and how the system verifies it applied. If the answer stops at a status field, the team has built billing software and not provider software. Ask how they would model serviceability against standardised location data. Ask what they would do about subscribers connected and not billed, and listen for continuous reconciliation rather than an annual audit.
Digital Heroes will not start coding before a requirements document is signed off, so the network state model and the reconciliation rules get settled in writing rather than in production. The firm has delivered over two thousand projects, employs more than fifty people, holds Fiverr Vetted Pro status, and maintains entities in the United States, the United Kingdom and India, which matters when a cooperative board or a municipal counsel wants to sign locally. Its YouTube channel has 2.5 million subscribers and shows the team explaining technical work in plain language.
Get repository, provisioning integration and cloud account ownership written down before kickoff. You left a product to escape lock in, and recreating it with an agency would be a poor trade.
If you want a second opinion before signing anything, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- Per Sensor Tower's State of Mobile 2026, worldwide consumers spent about $85 billion on apps in 2025 (up 21% YoY), and for the first time non-game apps surpassed games in consumer spending; generative-AI in-app purchase revenue more than tripled to top $5 billion. Source: Sensor Tower (via TechCrunch) (2026) →
- 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) →
Frequently asked questions
How much does custom ISP subscriber management software cost?
A subscriber management core with plan and promotion rules, billing, access control integration, equipment inventory, serviceability and install scheduling runs $80,000 to $180,000 across 13 to 20 weeks. Adding a customer portal, technician application, a second access technology, mapping and regulatory reporting runs $220,000 to $500,000 over 8 to 14 months. Migration from an existing platform is a separate and frequently underestimated line.
How long does it take and can we migrate without breaking billing?
Expect 13 to 20 weeks before a first release carries live subscribers. Migration should never be a single cutover weekend. Move subscriber, service and inventory data first, run one full billing cycle in parallel against the existing platform, and compare invoice by invoice before switching. Treat that parallel cycle as budgeted work rather than overhead, because it is where errors surface cheaply.
Should we replace Sonar or Splynx or build around them?
Build around them wherever you can. Keeping your existing product for invoicing while building the provisioning, inventory and serviceability layer on top is cheaper, lower risk and often sufficient. Several operators never replace billing at all, because once suspension reaches the network and equipment is serialised, the product does the remaining job perfectly well. Full replacement is a structural decision, not a feature one.
Which integrations break most often for an internet service provider?
The provisioning path from billing status to network state. It runs through a RADIUS attribute change, an optical line terminal policy, a wireless queue or a captive portal depending on technology, and access vendor firmware updates change behaviour without notice. Build verification in so the system confirms the network accepted the change, because a silently failing suspension looks identical to a suspension that was never attempted.
How do we handle broadband availability reporting and serviceability?
Hold serviceability as data joined to standardised addresses, with the network element that would serve each location and the current capacity on it. Federal availability reporting uses a location fabric with its own identifiers, and matching your typed address strings to it is a real project that goes stale as the fabric updates. Generate filings and sales answers from the same source so they cannot disagree.
Who actually builds ISP platforms of this kind?
A few product vendors, and a small number of custom firms that have actually touched network provisioning. Digital Heroes suits cooperatives, municipal networks and mixed technology operators who need entity structure and network state modelled correctly, and it can sign under American, British or Indian law so counsel stays comfortable. A board can verify the Fiverr Vetted Pro listing and a delivery record beyond two thousand projects.
What makes Digital Heroes different from a generic development shop?
The network state model and reconciliation rules are written and approved before code exists, so suspension, restoration and speed change behaviour per access technology is settled on paper rather than discovered in production. Three products of its own, ShopScore, HeroCheckout and Section Vault, are run by the same team, which is why upgrade and maintenance paths get designed in rather than bolted on later.
How do we verify a development partner before we pay anything?
Begin with the D-U-N-S record: does the registered company match the name on the contract. Move to Clutch and Trustpilot and read what named organisations actually wrote. Call another network operator they have delivered for and ask what happened in year two. Then get the repository, the provisioning integrations and the cloud accounts assigned to you before the first invoice is paid.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
How many developers does it take to build an ERP?
A typical Digital Heroes ERP pod is five to seven people: two or three backend engineers, one frontend engineer, a QA engineer, a project manager, and a part-time architect and designer. Bigger teams rarely go faster on ERP because the bottleneck is decisions about your business rules, not typing speed. What you need on your side is one empowered internal owner who can answer process questions within a day.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
What mistakes kill ERP projects most often?
The three we see most in rescue work at Digital Heroes: recreating the old system's broken process in new software, launching everything at once instead of module by module, and having no single internal owner with authority to decide. A fourth is skipping the parallel run on data migration to save two weeks, which trades a short delay for months of distrust in the numbers. None of these are technical failures, which is why vendor selection should weigh process discipline over demo polish.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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 we keep our current ERP and just build custom modules around it?
Often yes, and it is frequently the smartest first move. Digital Heroes regularly builds custom scheduling, quoting, or warehouse tools that sit on top of SAP, NetSuite, or Odoo through their APIs, which fixes the painful 20 percent without a risky replacement. The hybrid route costs a fraction of a full rebuild and tells you within months whether a bigger migration is even necessary.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 Dhruv.
Director of DevOps & Infrastructure · Delhi · 5 posts on the site
Published · Last updated .
