Telecom Service Fulfillment Software: Custom Build or Buy
Do not build under about 200 activations a year on one product line. A disciplined checklist and one good project manager will beat anything you buy or build at that size, and we would rather say so than take the work.
On this page
Do not build under about 200 activations a year on one product line. A disciplined checklist and one good project manager will beat anything you buy or build at that size, and we would rather say so than take the work. Building starts to pay when your activation logic wraps a mixed estate of controllers and legacy scripts that no product catalogue describes.
What Amdocs, Netcracker, Cerillion and Sonar actually do well
Sales closes a hundred megabit enterprise Ethernet circuit on a Tuesday. Billing starts, at best, when the customer accepts the circuit. Every day between those two events is a day you carry cost on a service earning nothing, and the interval is not set by physics. It is set by how long the order sits in an inbox.
Amdocs, Netcracker, Ciena Blue Planet, Comarch and Cerillion all sell real products that work at tier one scale. They model a product catalogue properly, decompose an order into a service order and resource orders, orchestrate across domains, and give you a genuine inventory. Salesforce Communications Cloud is strong at the commercial front end, meaning quote to order, and if that is where your pain sits it is a reasonable answer. For smaller internet service providers, Sonar covers billing, provisioning and customer management as one package at a price no custom build reaches.
The difficulty for a regional operator is not quality. It is the shape of the engagement. These platforms are built around a canonical product and service model, and the value depends on your catalogue conforming to it. At a national carrier with a modernisation budget and a systems integrator on site for two years that works, and it ends in a good place. If a two year transformation is a normal thing for your organisation to undertake, buy the suite.
Below all of it sits the honest floor. At low order volume with one product line, the constraint is process discipline rather than software, and buying either kind is spending money on the wrong problem.
Where they stop: conformance becomes the project
Ask an operations director where a specific order is and watch what happens. They open their mail client, search the customer name, and find a thread with an attached PDF forwarded four times, with a reply from an engineer saying facilities look acceptable at the A end and nothing after that for nine days because that engineer moved to a different project. Nobody is lying. There is simply no object in any system representing this order.
The suites solve that by giving you an object, on condition you remodel the network to fit theirs. At a regional operator with an estate assembled through three acquisitions, a mix of vendor equipment spanning fifteen years, and provisioning that partly runs through scripts written by someone who left, conformance is the project. You are not buying orchestration, you are buying a mandate to normalise everything first. The programmes that stall, stall there.
The second stopping point is serviceability. Can we serve this address is the first question and the hardest, and the honest answer depends on whether there is fibre in the street, spare strand count in the right cable, capacity at the splice point, a port on the right card at the nearest node, whether that card is the right generation, and whether capacity reserved for a deal in March is still held for a deal that died in April. That data exists across a mapping system, an element manager, an asset spreadsheet and one engineer's memory. No catalogue conformance exercise assembles it for you.
The third is the leak nobody puts on a slide. The circuit is accepted on the eleventh, the engineer closes the ticket, billing creates the recurring charge when the completion notice arrives on the twenty second and sets the start date to the day they entered it. Eleven days of revenue gone, permanently, on every circuit, and no report in the company could show it.
The arithmetic: cost per activation versus a build
Suites are priced on subscribers or services under management with a large implementation line, and integrator time usually exceeds licence in the first two years. Smaller platforms price per subscriber per month. Restate whichever applies as a three year total, then divide by the activations you expect across those three years.
Now the build. A first release covering the order lifecycle, product driven task decomposition, serviceability lookup against your existing inventory, jeopardy management and automated billing start runs $110,000 to $220,000 in our delivery experience. Amortise the midpoint over five years, add year two support at the rate below, and you carry roughly $47,000 to $58,000 a year.
At 200 activations a year that is $235 to $290 per activation. At 1,500 a year it falls to $31 to $39. Against a suite whose three year cost lands at $150 per activation, the crossover sits near 320 to 390 activations a year. Against $60 per activation it moves out past 800.
The number that settles it is on neither quote. Take your average monthly recurring charge, multiply by the average gap in days between acceptance and billing start divided by thirty, and multiply by your annual activations. That is recovered revenue rather than efficiency, it lands in the first release, and in most regional operators it is the whole business case. Add the disconnect side and you also stop paying a wholesale supplier for a circuit your customer cancelled seven months ago.
What a custom build actually costs
A first release covering the order lifecycle, product driven task decomposition with the right task set generated per product and per facilities situation, serviceability lookup, jeopardy management and automated billing start runs $110,000 to $220,000 across 16 to 24 weeks. Hold activation manual in that release while the orchestration and the billing start go live, because that sequence delivers most of the money in the first quarter.
A full platform adding activation adapters per element type, turn up test capture including service activation test results, third party access ordering, a partner or wholesale ordering interface and interval analytics runs $300,000 to $750,000 phased over 9 to 18 months.
Data migration lands at 10 to 25 percent of build cost, and in fulfilment it is inventory reconciliation rather than a load. The correct pattern is to query the inventory, verify against the live network where possible, flag disagreements and refuse to activate on data that failed a check. Where the inventory is bad enough that serviceability cannot be answered at all, reconciliation is a prerequisite project and any developer who does not tell you that is going to build orchestration on top of lies.
Year two runs 15 to 20 percent of build cost annually. Each element type is its own adapter with its own failure modes and its own test environment problem, and every firmware upgrade in the field is a regression risk. Each wholesale partner brings its own access ordering process and format, which is real work per partner rather than a configuration setting.
The four situations where building wins
- Standards and contractual fit. Carrier Ethernet services are specified against Metro Ethernet Forum service definitions, access to another carrier's network is ordered through the Access Service Request formats maintained by the Ordering and Billing Forum, and acceptance normally rests on a turn up test to RFC 2544 or ITU-T Y.1564 whose results the customer signs. When your firm order commitment dates and test evidence have to be defensible against an enterprise contract, the workflow belongs where you control it.
- Scale economics. Past roughly 320 to 400 activations a year on typical suite economics the arithmetic turns. Under 200 it never does.
- A workflow that is your advantage. If your delivery interval is what you sell against a national carrier, the process that produces it is a commercial asset. Encoding your own task durations from your own history, and escalating before the customer notices, is not a feature any catalogue ships with.
- Integration sprawl across three or more systems. Count them: the mapping system holding outside plant, the element managers and controllers, the asset register, billing, the wholesale partner portals and the field scheduling system. Once three or more must agree on one order, the orchestration is the product.
How to decide in a week
Pull thirty recent activations. For each one, find the date the customer accepted the circuit and the date the recurring charge starts in billing. Subtract. Take the median, multiply by your average monthly recurring charge divided by thirty, and multiply by your annual activation count.
That single comparison takes an afternoon and we have watched it justify an entire project in one meeting. If the median gap is under two days, your handoff works and you should spend the money elsewhere. If it is over a week, you have found recurring revenue you are giving away with no offsetting benefit.
Run the second test on serviceability. Take five addresses your sales team quoted last month and time how long it took to answer whether you could serve them. If the answer arrived by a message to one engineer, that person is your constraint, and no amount of catalogue configuration removes them. Ask what happens when they are on leave.
Third, take one order that was cancelled midway and trace what was released. Reserved capacity, partial configuration on network elements, a third party access order that may already carry costs. Compensating actions are the hard part of orchestration, and if nobody can tell you what was unwound, you are stranding capacity every month.
If those tests point to building, take a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the order model, task decomposition rules, the adapter approach per element type and acceptance criteria. The specification is yours to take to any other firm on your shortlist. We are the wrong partner if your inventory is so unreliable that serviceability cannot be answered, because that is a reconciliation project first and we will say so before quoting orchestration. We are an India LLP with US LLC and UK LTD entities so intellectual property assigns under your own law, with more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and a public record on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
- Nucleus Research's analysis of published analytics deployment case studies found business intelligence and analytics returned an average of $13.01 in benefits for every dollar spent, up from $10.66 three years earlier. Source: Nucleus Research (2014) →
Frequently asked questions
How do we stop losing revenue between circuit acceptance and billing start?
Make acceptance an event in the order record that emits a billing start carrying the acceptance date, rather than relying on a completion email reaching a billing team who then enter today's date. Before spending anything, pull thirty recent activations and compare the two dates in your billing system. In most regional operators that comparison produces the business case for the whole project and it takes an afternoon.
Can orchestration work if our network inventory is unreliable?
Only if the system treats the inventory as a claim rather than a fact. Query it, verify against the live network where possible, flag disagreements, and refuse to activate on data that failed a check. Where the inventory is bad enough that serviceability cannot be answered at all, reconciliation is a prerequisite project, and any developer who does not tell you that will build orchestration on top of lies.
What does automated activation involve for older equipment?
An adapter per element type, and adapters are allowed to be ugly where the equipment is ugly. A modern controller gets a clean interface. A legacy element may need a scripted session against a command line returning unparsed text, wrapped in explicit verification after the change, idempotent retries and a defined rollback. The failure to avoid is a system that assumes a command succeeded and leaves half configured services in the network.
What is jeopardy management and why does it matter?
An order is in jeopardy when a task has missed its date and the committed delivery is now at risk. In a spreadsheet operation this is detected when the customer calls, which is the worst possible moment because you have lost the chance to recover or reset expectations. Deriving expected task durations from your own history rather than from a guess lets the system escalate internally before the customer notices anything.
Is Salesforce Communications Cloud enough for fulfillment?
It is strong at the commercial front end, meaning quote to order, and if that is where your pain sits it is a reasonable answer. It does not remove the need for network activation, facilities checking and element provisioning underneath it. Treating it as a full fulfillment stack is how projects end with a beautiful order capture screen and the same email thread behind it. Be clear which half you are solving.
How long before a fulfillment build pays for itself?
Faster than most software, because the earliest returns do not depend on automation. Correct billing start dates and reservation expiry both land in the first release and both are recovered revenue rather than efficiency. Automated activation delivers larger gains but arrives later and costs more, which is why we recommend holding activation manual in release one and shipping orchestration and billing start in sixteen to twenty four weeks.
Who owns the code and the order data if an agency builds this?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm, in the contract before kickoff. At Digital Heroes you own all three from the first commit. The order history matters more than people expect, because task durations extracted from it become the evidence for where your delivery interval actually goes, and that is the data your operations improvements depend on.
What should happen when an order is cancelled halfway through?
Compensating actions, and this is the hard part of orchestration. Reserved capacity has to be released, partial configuration unwound on the network elements it touched, and any third party access order cancelled, which may already carry costs. If a prospective developer has not thought about compensation, they have built a checklist rather than an orchestrator, and you will discover the difference the first time a large deal falls through.
What is the difference between service fulfillment and service assurance?
Fulfillment gets a sold service from order to accepted and billing, so it is measured in interval and first time right. Assurance keeps a live service working, so it is measured in outage minutes and time to restore. They share the inventory and often the same field crews, but the workflows and the data they need are different, and buying one expecting it to cover the other is a common and expensive mistake.
Can we build orchestration and keep our existing billing platform?
Yes, and it is the usual arrangement. Orchestration owns the order lifecycle, task decomposition and serviceability, then emits a billing start with the correct date to whatever platform you run. Where that platform exposes an interface it is a write. Where it does not, it becomes a queued item with the date already populated and a human clicking confirm, which still fixes the date and most of the leakage.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
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.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
Who can build a custom software system?
Digital Heroes builds custom 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 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 .
