Number Portability Management Software: Custom Build vs Off the Shelf
Buy, which here means keep using your upstream provider portal. Under roughly twenty ports a month with one provider, a spreadsheet and a portal login are the correct answer and a build is pure overhead.
On this page
Buy, which here means keep using your upstream provider portal. Under roughly twenty ports a month with one provider, a spreadsheet and a portal login are the correct answer and a build is pure overhead. Porting justifies custom software once a single failed port takes a business customer's main line down and your contract carries service credits against it.
What the existing tools in this space actually cover
The honest starting point is that there is no product to buy for the thing you are trying to do, and understanding why saves you a procurement cycle. iconectiv administers the Number Portability Administration Center, the authoritative routing database that makes portability work at all. That is infrastructure. It tells the network where a number lives and it has no view of your relationship with a losing carrier. NetNumber occupies a similar space around number data, routing and registry services. Somos administers the toll-free registry where responsible organisation assignments live. TransNexus is strong on call authentication and analytics and belongs in a voice stack, but it is not a port order management system.
What you do have is your upstream provider portal. Bandwidth, Telnyx and Inteliquent all give you a place to submit a port, see its state and receive a firm order commitment date, and for a small operator that portal is genuinely sufficient. It is maintained by someone else, it stays current with the carriers behind it, and it costs you nothing extra.
Buy, or rather stay on the portal, if you port fewer than about twenty numbers a month, use one upstream provider, and your provisioning team is two people who talk to each other across a desk. At that volume a custom system is overhead. Keep a clean spreadsheet, keep the portal, and spend the money on sales.
Where they stop: the rejection nobody read
A twelve line dental practice signs with you on the fifth. The port is submitted on the sixth. On the eleventh at 8:04am the practice manager calls because the phones are dead, patients cannot get through, and they have been open four minutes. Your team digs. The losing carrier rejected the request on the eighth because the service address on the customer service record carries a suite number your form omitted. The rejection arrived as an email to a shared mailbox. Nobody read it.
Nothing in that sequence is unusual, and no portal prevents it. Porting is a workflow spanning two companies who are commercially opposed, running on regulated timers, communicating through forms and email. The Federal Communications Commission one business day interval for simple ports sets a customer expectation that the mechanics regularly miss, and the mechanics fail in boring ways: an account number keyed wrong, a personal identification number the customer never knew, an authorised signature from someone who left, an address matching the billing record but not the service record.
The second half of the gap sits in a spreadsheet. Spare direct inward dial numbers, reserved ranges, numbers held for a customer who has not signed, numbers disconnected last quarter sitting in an aging window before they can be reissued. Somebody maintains that file. Somebody else assigns a number already promised to another account, and two customers now have a claim on the same number. Nobody sells software for that either, because it is your inventory and your rules.
The arithmetic: cost per port against a build
Restate everything as cost per port. Upstream providers charge a per port fee, sometimes waived above a commitment, and your real cost is that fee plus the fully loaded provisioning time each port consumes, plus the occasional failure.
At fifteen ports a month, a coordinator spending twenty minutes each is five hours of work, and the portal fee is small. There is no case for a build at any horizon and we would talk you out of it.
At 400 ports a month across three upstream providers, the same arithmetic reads differently. Each provider has a different form, a different response format and a different set of unwritten rules, so your team is not doing one job three hundred times, it is doing three jobs. Add the numbers you pay for monthly that no customer uses, which in most operators is a meaningful line once anyone counts it.
The crossover we see is between 100 and 150 ports a month, and it moves earlier if you use more than one upstream provider or sell to business customers with service credits attached. It moves later if you are consumer only with a single provider and a tolerant customer base. The real tipping point is not volume anyway. If one dead phone system costs you a customer worth five figures a year, the system pays for itself the first time it catches a rejection at hour one instead of day three.
What a custom build actually costs
In Digital Heroes delivery experience a working port orchestration and number inventory system runs $65,000 to $150,000 and ships in 10 to 16 weeks. That covers inventory with reservation and aging, port-in and port-out lifecycle with rejection handling, firm order commitment tracking, counterparty adapters for your main partners, switch provisioning hooks, an audit trail and an operations queue. A broader platform adding multi country porting rules, toll-free responsible organisation handling, automated request generation per counterparty, customer facing status pages and analytics runs $180,000 to $400,000 phased across 6 to 11 months.
Data migration is 10 to 25 percent and it is almost entirely inventory. Your spreadsheet has to become a stateful inventory, which means someone reconciles it against upstream provider billing and against the switch, number by number, and resolves the disagreements. That reconciliation is where operators discover the dormant spend, so it usually pays for part of itself. Open ports at cutover need entering and verifying twice, because a mis-keyed firm order commitment date is an outage rather than a data error.
Year two is 15 to 20 percent of build cost annually. It buys new counterparty adapters as you add carriers, response format changes when a partner revises its process, switch upgrades, and regulatory changes in any jurisdiction you operate in.
What drives price up: the number of counterparties, multi country operation where timers and rules differ with no shared model, toll-free work because responsible organisation mechanics are their own discipline, and switch integration, since a BroadSoft lineage platform, a class 4 softswitch and a cloud provider interface are three different problems.
The four situations where building wins
Regulatory fit. Several obligations land on the same records at once. Aging and reissue behaviour interacts with reassigned number exposure the moment your customers use those numbers for outbound campaigns. Dispatchable location obligations under Kari's Law and the RAY BAUM'S Act mean the emergency location record has to be correct on a number the day it moves, and a working phone with a wrong location record is worse than a dead one because nobody notices. Attestation under the STIR and SHAKEN framework depends on knowing which numbers you legitimately serve. Inconsistent port-out rejection is exactly the behaviour that generates complaints. One inventory with enforced states answers all four.
Scale economics. Past 100 to 150 ports a month, or two or more upstream providers, the manual work stops scaling and starts multiplying.
A workflow that is your competitive advantage. If you sell to businesses on the promise that the cutover will not hurt, port reliability is the product. Deriving the provisioning task set from the firm order commitment and blocking activation until preconditions pass is the difference between a scheduled event and a fire drill.
Integration sprawl. Upstream provider interfaces, your softswitch, a ticketing system, billing and an emergency location database is five, and the port is the object that has to touch all of them on the same morning.
How to decide in a week
Two exercises, both cheap. First, take one month of rejection emails from the shared mailbox and classify every one by reason: wrong account number, address mismatch, missing authorisation, name mismatch, other. Then count how many hours passed between the rejection arriving and someone acting on it. If most rejections were handled within an hour and the categories are varied, your process is working and you do not need software.
Second, export your number inventory spreadsheet and reconcile a sample of two hundred numbers against your upstream provider invoice and your switch. Count three things: numbers you pay for that nobody uses, numbers assigned in the sheet but absent from the switch, and reservations older than ninety days. That reconciliation typically finds enough dormant monthly spend to be worth reporting to finance regardless of what you decide next.
If the rejection latency is measured in days and the inventory sample is materially wrong, you have a build. If both come back clean, keep the portal.
Two things to verify about any firm you shortlist, including us. Which entity signs, because an intellectual property assignment drafted under Indian, United States or United Kingdom law are three different instruments, and Digital Heroes holds an India LLP, a US LLC and a UK LTD so yours is the one that applies. Then meet the engineers who will write the counterparty adapters before you sign, rather than a bench presented in month two. The remaining claims stand or fall on public record: more than fifty specialists, over 2,000 delivered projects, Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Then pay for a discovery phase before committing to a build. Ours ends in a signed product requirements document covering the port state machine, the counterparty adapters by name, the inventory model with aging and reservation rules, provisioning hooks and acceptance criteria. You own that specification whether you build with us or with anyone else. Send us a month of your rejection emails and your current number spreadsheet, and we will tell you where the failures are coming from before we quote.
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.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- 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) →
Frequently asked questions
Who owns the counterparty mappings and the code if we commission a build?
You should own the repository, the infrastructure accounts and the counterparty mappings, and it belongs in the contract before kickoff. The mappings matter more than people expect, because they encode knowledge that currently lives in two heads on your provisioning team. At Digital Heroes the porting logic and the repository belong to the client from the first commit.
How long does port orchestration take to build and go live?
Ten to sixteen weeks for a first release covering inventory, port-in and port-out lifecycle, rejection handling and provisioning hooks. Go live is staged rather than switched: run new ports through the new system while open ports finish on the old process, because a port in flight at cutover is a customer outage waiting to happen if the dates get mishandled.
Can we build only the number inventory and leave porting alone?
Yes, and it is the cheapest sensible first phase. Inventory is the foundation everything else attaches to, and it stands on its own value: states rather than a flag, reservation expiry, enforced aging windows, and reconciliation against upstream provider billing. Operators regularly find dormant monthly spend in that first reconciliation, which funds a useful share of the next phase.
What is the difference between the routing database and a porting workflow system?
The routing database, administered by iconectiv in the United States, is the authoritative record of which carrier serves a number so calls reach the right network. A porting workflow system manages the commercial and operational process of getting a number moved: producing the request, chasing a response, handling a rejection and coordinating cutover. One is infrastructure, the other is your operation.
What happens if a port fails on the morning of cutover?
You are inside a live outage and the priority is a working path, usually a temporary forward while the underlying issue is fixed. What decides how bad it gets is whether you can see immediately what happened and when. An append only history of every state change and counterparty message is the difference between a service credit conversation and a dispute nobody can resolve.
Should port-out requests be handled differently from port-in?
Yes, and most operators build port-in first because it is revenue. Port-out is a retention event that usually arrives as a competitor request and gets processed without anyone commercially responsible being told. Treat it as a first class flow with consistent, auditable authorisation checks and an immediate alert to the account owner, while there is still time to have a conversation.
How long should a disconnected number sit before we reissue it?
Long enough that the previous owner's inbound traffic has stopped, and consistently enough that you can prove the policy. Enforce the window in the inventory rather than trusting a coordinator to remember, because reissuing too quickly means inheriting somebody else's calls and, in the United States, exposure once a customer uses that number for outbound campaigns. Pick a policy, encode it, log exceptions.
Can we do this with a workflow tool instead of custom software?
You can get part way. A workflow tool will hold states and send reminders, and for a small operator that is a real improvement over a mailbox. Where it stops is counterparty adapters, inventory states with aging, and provisioning hooks into the switch. Porting software that does not reach into provisioning is a tracking spreadsheet with a login screen.
What happens when we add a fourth upstream provider?
In a spreadsheet operation it means a fourth portal, a fourth set of unwritten rules and a fourth place your team checks. In a built system it means one new adapter behind the same internal port object, so the operations queue does not change shape. That is the strongest argument for building at multi provider scale, and it is worth pricing an adapter explicitly during discovery.
How do we handle the emergency location record when a number moves?
Treat it as a precondition rather than a follow up task. Derive the provisioning task set from the firm order commitment date, include the location record among the blocking checks, and refuse activation until it passes. The failure mode you are designing against is a phone that works perfectly with a wrong address behind it, which nobody discovers until the worst possible call.
What does an internal tool cost for a small business with 20 to 50 employees?
Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.
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.
Can we start on Airtable or Retool now and move to custom software later?
Yes, and it is often the smartest sequence: run the workflow on Airtable or Retool for 6 to 12 months to learn what you actually need, then go custom once the process stabilizes. The no-code version becomes free requirements documentation, and its data exports cleanly into a custom database. The one risk is waiting too long, because teams stack automations and workarounds until migration becomes a project of its own, so set a concrete trigger in advance, such as hitting Airtable's 50,000-record Team plan cap.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
What does it cost to keep an internal tool running after launch, and do we need to hire a developer?
Budget 15 to 20 percent of the build cost per year, so a $25,000 tool runs roughly $300 to $400 a month covering hosting, security patches, dependency updates, and small tweaks, figures drawn from Digital Heroes maintenance contracts. You do not need an in-house developer; a monthly retainer with the agency that built it covers the typical internal tool comfortably. Hosting itself is cheap for internal audiences, often $20 to $100 a month, because you serve dozens of users rather than the open internet.
What are the most common mistakes companies make when building internal tools?
The three failures Digital Heroes sees most: building for every department at once instead of nailing one workflow, designing without the end users so staff quietly go back to their spreadsheets, and leaving no named owner after launch so small bugs pile up until the tool dies. A subtler fourth is faithfully recreating the old spreadsheet, including its workarounds, instead of fixing the process first. Start with one team's most painful workflow and put the actual users in the room from week one.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How do we migrate years of spreadsheet or Airtable data into a new internal tool?
Migration is a standard part of the build, not a separate project: the agency writes import scripts that clean, deduplicate, and map your existing rows into the new database. On typical spreadsheet and Airtable histories, Digital Heroes budgets 3 to 10 extra days, most of it spent resolving inconsistencies like the same customer spelled four different ways. The safe sequence is a trial migration first, a review of flagged conflicts with your team, then final cutover over a weekend so nobody loses a working day.
When does a company outgrow Airtable?
The usual breaking points are record limits, permissions, and automation complexity. Airtable's Team plan caps each base at 50,000 records and Business at 125,000, so operations logging thousands of rows a month hit the ceiling within a year or two. The other trigger Digital Heroes sees constantly is permissions: restricting who can view specific fields or records is clumsy below Airtable's Enterprise tier, which becomes a genuine problem once salaries, pricing, or client contracts live in the base.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools 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 internal tools 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 Aarav.
Backend Engineer · Delhi · 1 post on the site
Published · Last updated .
