Skip to content
§
§ · hiring guide

How to Hire a Number Portability Management Software Development Company

Ask every candidate to draw the port state machine, including rejection and resubmission, before you discuss price. A firm that draws a status field with three values will build you a spreadsheet with a login screen.

Internal Tools Development product interface illustration for Number Portability Management Software.
The short answer

Ask every candidate to draw the port state machine, including rejection and resubmission, before you discuss price. A firm that draws a status field with three values will build you a spreadsheet with a login screen. Expect $75,000 to $160,000 for a working port and inventory system, and buy a paid discovery phase so the counterparty rules are documented before anyone quotes a build.

Hiring a developer for porting software is like hiring a freight forwarder for cargo you never see. The paperwork moves between two companies who are commercially opposed, on regulated timers, through forms and shared mailboxes, and the first time you find out something went wrong is when a twelve line dental practice opens at eight in the morning and the phones are dead. The rejection arrived three days earlier as an email nobody read. Every part of that failure is administrative, and none of it shows up in a product demo.

The category is hard to buy because the value sits in knowledge that is currently undocumented. Two people on your provisioning team know that one carrier rejects anything where the authorised contact does not match the customer service record exactly, that another wants a copy of the bill attached, and that a third has a form layout of its own. That knowledge is the system. A developer who has never fought a losing carrier will quote against a generic workflow, discover the counterparty variations in month two, and hand you something your team routes around. Meanwhile the number inventory, which is stock you pay for monthly, is usually in a spreadsheet that nobody has audited.

What a number porting software development company actually does

The queue screen is the small part. Most of the engagement is turning tribal knowledge into rules.

  • Modelling the port request as an explicit state machine where rejection is a transition, not an end state, with every counterparty message held against it.
  • Building per counterparty adapters that encode each carrier's form layout, required attachments and validation quirks, which means sitting with your provisioning team for a week.
  • Designing DID inventory with real states: spare, reserved with an expiry, assigned, disconnected and inside an aging window before reissue.
  • Reconciling upstream provider billing against your own assignments so numbers you pay for and nobody uses become visible.
  • Treating port out as a retention event, alerting the account owner on arrival and applying authorisation checks consistently every time.
  • Deriving provisioning tasks from the confirmed date and blocking activation until preconditions pass, including the dispatchable location record on the number being moved.
  • Keeping an append only history, because when a port goes wrong the record of who did what and when decides whether the outcome is a credit or a dispute.

What it really costs in 2026

Bands from our own carrier and hosted voice work, not a published survey.

Project tierCostTimeline
DID inventory with reservation and aging, plus port in lifecycle and rejection handling$75,000 to $160,00010 to 16 weeks
Adding port out, provisioning hooks, counterparty adapters for your main partners and an operations queue$150,000 to $260,0004 to 7 months
Full platform: multi country porting rules, toll free handling, automated request generation, customer facing port status$220,000 to $450,0006 to 11 months
Hosting, counterparty rule maintenance and support15 to 20 percent of build per yearRetainer

Two items are missing from most quotes here. The first is counterparty discovery. Each carrier or aggregator you deal with directly is its own small integration with unwritten rules, and the honest way to price a build is to count them first. Ten counterparties is not twice the work of five, because the fifth one teaches you what to look for and the tenth still surprises you. Ask for a per counterparty figure rather than one blended number.

The second is switch integration, which buyers consistently assume is one line item. A platform of one lineage, a class 4 softswitch and a cloud provider API are three separate problems with three separate failure modes. Porting software that does not reach into provisioning is a tracking tool, so this is not optional scope. Name your switch on the first call and ask whether the firm has touched it before, by name.

Signals of a strong porting software partner

  • They ask which counterparties you deal with directly versus through an aggregator. That question shapes the entire adapter layer and only someone who has done this asks it first.
  • They treat rejection as a first class state. Rejections need parsing into reason codes and routing to whoever can fix that class of problem, with an elapsed time clock behind them.
  • They ask to see a month of your rejection emails. That corpus is the requirements document, and a firm that wants it is scoping from evidence.
  • They model inventory states rather than a flag. Reservation expiry and aging windows exist for real reasons, and a firm that treats numbers as a list with an assigned column has not met double allocation yet.
  • They connect activation to the location record. A number that ports successfully but carries a stale dispatchable location is a compliance problem attached to a working phone, which is worse than an outage because nobody notices.
  • They can name the softswitch and provider APIs they have integrated. Specificity beats a logo slide every time in this category.

Red flags

  • A workflow demo with one generic submission form. If there is no concept of per counterparty variation, your team will keep the spreadsheet.
  • Port out treated as the same flow reversed. It is a retention event and a consistency obligation, and inconsistent rejection is exactly what generates regulatory complaints.
  • No interest in your upstream billing data. The reconciliation that finds dormant DID spend is usually the first hard number a build produces, and skipping it is leaving money on the table.
  • Edits allowed on historical port records. When a customer disputes a failed port, a silently editable history is worth almost nothing.
  • Weeks quoted for portal or carrier integration without any partner paperwork discussion. The constraint there is access and rate limits, not code.

Questions to ask on the first call

  1. Draw the port state machine for us, including rejection, resubmission and cancellation.
  2. How would you encode the fact that one carrier rejects anything where the authorised contact does not match the service record exactly?
  3. How do you decide which ports are at risk this morning, and what drives that queue?
  4. How do reservation expiry and number aging work in your inventory model?
  5. How would you reconcile our upstream provider billing against our own assignments?
  6. Which softswitch and which upstream provider APIs have you integrated, by name?
  7. What preconditions block activation on the confirmed date, and who is told when they fail?
  8. How is the audit history protected from silent edits?
  9. What is handed over at the end, including the counterparty mappings and the infrastructure accounts?

A simple way to decide

Skip the beauty contest and buy a paid discovery phase from your strongest candidate. Give them a month of rejection emails and your current DID spreadsheet, and require the engagement to end with a written specification you own: the port state machine, the counterparty rule set documented per carrier, the inventory state model with aging and reservation policy, the provisioning task derivation, and acceptance criteria detailed enough for a different firm to build against. That document turns your team's undocumented knowledge into an asset the business holds, which is valuable whether or not you proceed with the same firm.

Digital Heroes starts every engagement with that specification and hands over the repository and the counterparty mappings from the first commit. Contracting runs through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law, which matters when the system holds your carrier specific operational knowledge and your audit trail for regulated processes. More than 2,000 projects delivered, 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.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
  2. Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
  3. SHRM's 2025 benchmarking data puts the average cost-per-hire at $5,475 for nonexecutive roles and $35,879 for executive roles - executive hires are on average nearly 7x more expensive than nonexecutive hires. Source: SHRM (Society for Human Resource Management) (2025) →
  4. In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
FAQ

Frequently asked questions

How much does it cost to hire a number porting software development company?

DID inventory with reservation and aging plus port in lifecycle and rejection handling runs roughly $75,000 to $160,000 over 10 to 16 weeks. Adding port out, provisioning hooks and counterparty adapters takes it to $150,000 to $260,000. A full platform with multi country rules, toll free handling and customer facing status runs $220,000 to $450,000. The number of counterparties you deal with directly drives the price more than volume does.

What is the single best test of a porting developer on the first call?

Ask them to draw the port state machine including rejection and resubmission. Someone who has built this will ask which counterparties you deal with directly versus through an aggregator, and will know a rejection is a transition rather than an end state. Someone who has not will sketch a status field with three values, and that sketch predicts the quality of everything else they will build for you.

Should we build at all if we use one upstream provider?

Probably not at low volume. Under roughly twenty numbers a month through a single provider whose portal shows the state, with a provisioning team of two who talk daily, the portal and a clean spreadsheet are genuinely enough. The case for hiring starts around a hundred numbers a month, or earlier if your customers are businesses whose main line goes dead when a port fails and your contracts carry service credits.

What costs get left out of porting software quotes?

Two. Counterparty discovery, because each carrier or aggregator you deal with directly is its own small integration with unwritten rules, so ask for a per counterparty figure rather than a blended one. And switch integration, which buyers treat as a single item when a legacy platform, a class 4 softswitch and a cloud provider API are three separate problems. Name your switch on the first call.

Who owns the counterparty rules and the code afterwards?

You should own the repository, the counterparty mappings, the cloud accounts and the right to bring in another developer, written into the contract before kickoff. This system holds your carrier specific operational knowledge and the audit trail for a regulated process, and neither belongs somewhere you cannot reach. Digital Heroes assigns ownership from the first commit and contracts through separate India, US and UK entities so assignment happens under your own law.

What should I prepare before contacting a software development agency?

A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.

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.

Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?

Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.

What tech stack should an internal tool be built with?

Boring and popular: a React or Next.js frontend, a Node.js or Python backend, and PostgreSQL covers the vast majority of internal tools and keeps future hiring easy. The stack matters far less than whether a different developer can pick the code up in two years, so require documentation as a deliverable and avoid anything exotic. Treat it as a red flag if an agency pushes a proprietary platform only they maintain, because that quietly converts your tool into a subscription to that agency.

At what point does Retool cost more than building a custom tool?

The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.

How much should a small business budget for its first custom app or website?

For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.

Is a freelancer or an agency better for building an internal tool?

A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.

Is a custom internal tool secure enough for HR records and financial data?

A properly built custom tool is generally safer for sensitive data than the shared spreadsheet it replaces, because you get role-based access, audit logs, encrypted storage, and the ability to cut one person's access instantly. Ask the agency specifically for encryption in transit and at rest, permissions down to the field level, and an audit trail showing who viewed or changed each record. If HIPAA, GDPR, or SOC 2 expectations from enterprise clients apply to you, raise it before the quote, because compliance features add real scope.

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.

How do I vet a development agency for an internal tools project?

Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.

What should I prepare before contacting an agency about an internal tool?

Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.

How do I calculate whether custom software will pay for itself?

Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.

How much does a custom internal tool cost to build?

Most custom internal tools cost $8,000 to $40,000 to build, based on Digital Heroes delivery data across 2,000+ client projects. A single-purpose tool like an approval dashboard or inventory tracker sits at the low end, while a multi-department platform with role-based access and several integrations pushes past $40,000. The three biggest cost drivers are the number of user roles, the number of systems the tool must connect to, and custom reporting requirements.

Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?

Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.

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.

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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply