How to Hire an ISP Subscriber Management and Billing Development Company
Shortlist firms that have provisioned a live access network, not just written billing screens, and make each one show you how a suspension reaches the OLT or the RADIUS server and how they prove it landed.
On this page
Shortlist firms that have provisioned a live access network, not just written billing screens, and make each one show you how a suspension reaches the OLT or the RADIUS server and how they prove it landed. A subscriber management core runs $80,000 to $180,000 in 13 to 20 weeks. If a firm cannot tell you when to buy Sonar or Splynx instead, keep looking.
Hiring for ISP software has the same shape as buying a bucket truck. Everything on the lot looks equivalent in the brochure, and the one you regret is the one whose boom does not quite reach your worst pole. You find that out on a Tuesday with a customer standing in the yard. Software vendors sell the billing screens because billing screens demo well, and the thing that decides whether the build was worth it is invisible in a demo: whether a status change in the ledger actually reaches the access platform, and whether anyone checks that it did.
This category is unusually hard to buy for a reason most guides avoid. The incumbents are good. Sonar, Splynx, Powercode, Azotel, UISP and Rev.io were built by people who understand this business, and for a single technology operator under a few thousand subscribers one of them will serve for years at a fraction of a build. So the honest first job of a development firm here is to talk half the people who call out of the project. Most will not, and a build sold to an ISP that needed a subscription is a two year detour paid for in fiber that never got laid.
What an ISP software development company actually does
The visible build is a subscriber record and an invoice. The work that decides the outcome sits underneath it. A firm worth hiring starts by mapping every path by which service is turned up, changed, restricted and torn down, per access technology, because a GPON subscriber, a fixed wireless subscriber and a bonded copper subscriber are provisioned by three different mechanisms that must sit behind one interface. They define a small set of network states, active at plan speed, restricted to a payment portal, suspended, disconnected, and implement each per technology with a verification step that confirms the platform applied it rather than assuming.
Then the parts nobody demos. Serialised customer equipment from receipt through van stock to the subscriber address, with a valued recovery task generated automatically on cancellation. Serviceability held as data joined to standardised addresses with the network element and remaining capacity serving each location, so sales stops promising installs engineering will refuse. Install scheduling against skills, van stock and geography. And a continuous reconciliation between network, inventory and ledger, because an account that is connected and not billed never generates a complaint and therefore never gets found.
What it really costs in 2026
| Project tier | Cost | Timeline |
|---|---|---|
| Provisioning, CPE inventory and serviceability layer around the billing product you already run | $45,000 to $95,000 | 8 to 12 weeks |
| Subscriber management core: subscriber and service record, plans and promotions, billing and dunning, verified access control, CPE, serviceability, install scheduling | $80,000 to $180,000 | 13 to 20 weeks |
| Full platform: customer portal, technician app, second access technology, network documentation and mapping, wholesale or open access billing, grant reporting | $220,000 to $500,000 | 8 to 14 months |
| Support, plan changes and integration maintenance | 15 to 20% of build cost per year | Retainer |
Two line items are missing from nearly every ISP quote. The first is the parallel billing cycle. Migration gets priced as data movement, and moving subscriber, invoice and inventory records is the easy part. The real cost is running one complete billing cycle in both the old and new systems and comparing invoice by invoice before you switch, then working the handful that differ. That is a month of somebody's time and it is the only thing standing between you and a mass credit run in your second month live.
The second is provisioning verification. Every quote says it integrates with RADIUS. Almost none price the closed loop that reads back from the access platform to confirm the change applied, plus the nightly reconciliation that compares who the network thinks is on against who the ledger thinks is paying. Skip it and suspension stays symbolic, delinquent subscribers keep streaming until an engineer runs a batch by hand, and the connected but unbilled accounts stay invisible. That reconciliation is usually the first hard revenue number a build produces, and it is routinely left out to make a bid look competitive.
Signals of a strong partner
- They will tell you to buy a product instead. A firm that says a single technology operator under roughly 5,000 subscribers should run Splynx and spend the difference on plant is a firm that has done this work and is not desperate for it.
- They ask about your access technology mix before your feature list. The provisioning path is the project. The invoice template is not.
- They describe suspension as a network state with a verification step. If the answer stops at updating a status field, they have built billing systems, not ISP systems.
- They ask about your entity structure early. Cooperatives, municipal networks and holding companies that acquired several small ISPs need member and patronage accounting that products fight, and it is a design decision, not a report.
- They have handled standardised address and location data. Serviceability and availability reporting share a source or they will contradict each other in public.
- They ask what happens to the ONT when a subscriber cancels. Unrecovered customer equipment is the quiet write off in this business, and a firm that raises it unprompted has seen the number.
Red flags
- A fixed price before they have seen your access platform. The same subscriber count on GPON and on fixed wireless is two different builds, and a number quoted without that knowledge becomes a change order queue.
- The demo is all billing screens. Invoicing is the part your current product already does adequately. Watch for whether they can show a plan speed change reaching a live piece of network equipment.
- No answer for mixed technology. If they intend to write the fiber path and handle wireless manually, you are buying the leak you already have with a nicer interface.
- They want to host the provisioning integrations in their own tenancy. Your network credentials and your subscriber records should never sit inside a vendor account, and this arrangement recreates the lock in you left a product to escape.
- Grant obligations treated as reporting to be added later. If your build is funded and carries eligibility and reporting conditions, those shape the data model and belong in scope before engineering starts.
Questions to ask on the first call
- We run GPON and fixed wireless. Show me how you would suspend one subscriber on each, and how the system proves the network applied it.
- How would you find accounts that are live on the network with no billing record, and how often does that check run?
- How do you model serviceability by address, and have you worked with the standardised location data our availability reporting is based on?
- Walk me through van stock. What happens to a radio or an ONT when a subscriber cancels, and who chases it?
- We are a cooperative with two legal entities and patronage accounting. What changes in your ledger design?
- Describe the migration. How do subscriber records, invoice history and inventory move without interrupting a billing run?
- What does the installer see on their phone at the door, and does completing the job activate service and update inventory on the spot?
- At handover, what sits in our repository and our cloud accounts, and what stays in yours?
A simple way to decide
Buy a paid discovery before you buy a build, and make its deliverable a written specification you own: the network state model per access technology, the serviceability data design, the migration plan including the parallel cycle, and a costed phase plan. Require one more thing in it, a plain build or buy verdict with reasoning. If the honest answer is that Sonar covers you for another three years, you have bought that answer cheaply, and the same specification makes every quote on your shortlist comparable.
If you want it written by a team that stays on the hook for the build, Digital Heroes works PRD first with a 50 plus team and more than 2,000 projects delivered, and contracts through India LLP, US LLC and UK LTD entities so the intellectual property assigns under your own law. Verifiable through D-U-N-S, Clutch and Trustpilot.
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.
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
Frequently asked questions
How much does it cost to hire an ISP software development company?
A provisioning, inventory and serviceability layer built around the billing product you already run costs $45,000 to $95,000 over 8 to 12 weeks. A full subscriber management core with billing, verified access control, customer equipment tracking and install scheduling runs $80,000 to $180,000 in 13 to 20 weeks. Adding a portal, technician app, a second access technology and regulatory reporting takes it to $220,000 to $500,000.
Should we build at all, or just buy Sonar or Splynx?
Most ISPs should buy. A single technology operator under roughly 5,000 subscribers with one legal entity and conventional plans is well served by Sonar, Splynx or Powercode. Building earns its place on structural mismatch rather than missing features: genuinely mixed access technologies, cooperative or multi entity accounting, wholesale and open access billing, or plan structures your product cannot express without workarounds finance then unpicks.
What is the test of whether a developer understands ISPs?
Ask how a billing suspension reaches the network for each access technology you run, and how the system verifies the change applied. A firm that has done this immediately separates the ledger status from the network state and describes a read back plus a nightly reconciliation. A firm that answers by describing a status field and a dunning email has built billing software, which you already have.
How do we migrate without breaking a billing run?
Never as a single cutover weekend. Move subscriber, service, invoice history and inventory data first, then run one complete billing cycle in parallel against your existing system and compare invoice by invoice before switching. Budget that parallel cycle as real cost rather than overhead, because it is the only thing that catches plan and proration differences before they reach several thousand customers at once.
Who should own the code and the network integrations?
You should own the repository, the cloud accounts, the provisioning integrations and the right to hire another firm, written into the contract before kickoff. This system holds subscriber records, serviceability data and credentials to your access network. Any arrangement where a vendor controls that access recreates exactly the lock in that pushed you off a packaged product in the first place, only with a smaller vendor.
Can a custom ERP meet compliance requirements like SOC 2 or GDPR?
Yes, and often more cleanly than a shared SaaS platform because you control exactly where data lives and who touches it. The build includes role-based access control, full audit logs, encryption at rest and in transit, and data residency in whatever region your regulator requires. If you need SOC 2 attestation, tell the agency before development starts, since audit logging is far cheaper to design in than to bolt on.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
What happens to my ERP if the agency shuts down or we part ways?
If ownership was set up correctly, nothing breaks: you hold the source code, the system runs in cloud accounts you own, and handover documentation lets a new team take over. Insist on repository access from day one, admin ownership of all hosting and third-party accounts, and documentation as a contract deliverable rather than a favor. This is the single most important clause to check before signing an ERP contract.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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 a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
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.
What tech stack should a custom ERP be built on?
A boring, hireable one: Digital Heroes most often ships ERPs on PostgreSQL with a Node.js or Python backend and a React frontend, hosted on AWS or Azure. The stack matters far less than the database design, because your ERP schema will outlive every framework choice. Be skeptical of any agency proposing a niche or proprietary framework, since your ability to hire maintainers later is part of the total cost.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
What does it cost to maintain a custom ERP each year?
Budget 15 to 20 percent of the original build cost per year, so a $150,000 ERP needs roughly $22,000 to $30,000 annually for hosting, security patches, integration upkeep, and small improvements. Across Digital Heroes maintenance contracts, third-party APIs changing is the biggest recurring work item. That total still usually sits well under the license bill for a comparable NetSuite or Dynamics seat count.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
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.
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
Published · Last updated .
