How to Hire a Hosted Voice Provisioning Software Development Company
Hire on two answers: how they handle a partial failure at seat thirty one of fifty, and whether they attach dispatchable location to the seat or the account. A provisioning automation layer over your switching platform runs $70,000 to $160,000 in 12 to 18 weeks.
On this page
Hire on two answers: how they handle a partial failure at seat thirty one of fifty, and whether they attach dispatchable location to the seat or the account. A provisioning automation layer over your switching platform runs $70,000 to $160,000 in 12 to 18 weeks. If you turn up two or three customers a month on one platform, do not build.
Buying provisioning automation is like paving a footpath that already exists as a rut across the lawn. The route is not in dispute. What you are paying for is that the route stops living in the head of the one person who knows where it goes, the person whose holiday nobody in your company can comfortably schedule. Every hosted voice provider has that person, and every provider discovers what they were worth the first week they are unavailable during a fifty seat cutover.
The category is hard to buy because the work looks like configuration and behaves like orchestration. A demo shows a switching platform administrative screen and a form. The actual product is a sequence: which objects get created in what order, which conventions apply, what happens when the port date moves, what happens when seat thirty one fails halfway through a build, and what stops a seat activating without a dispatchable location. Vendors who have driven a platform API before understand that. Vendors who have only looked at one will quote the form.
What a hosted voice provisioning company actually does
Assume the screens are a fifth of the engagement. Four other pieces carry the value.
The first is encoding your process, not replacing your platform. NetSapiens, BroadWorks, Metaswitch, KAZOO and Sangoma are switching platforms and they should stay exactly where they are. What belongs in the new layer is your dial plan conventions, your class of service tiers, your device standards, your naming, your order of operations between porting and building, and your rule that a seat does not activate without a location. A signed order produces a build plan, and the build plan drives the platform API with those conventions applied automatically.
The second is validated intake. Every provider has a form and nobody fills it in correctly. Extensions collide, the auto attendant tree arrives as prose, and the device count does not match the shipping addresses. Validating at submission rather than at build is what stops your provisioning engineer becoming a data cleaner interrupted by phone calls.
The third is device lifecycle keyed on the hardware: MAC, model, firmware, current assignment and history, with configuration generated from templates rather than hand edited files, and an enforced wipe and reassign step. The fourth is the location record as a first class object attached to the seat, with a confirmation date, a block on activation without one, a prompt on every move and add, and a periodic revalidation that asks the customer administrator to confirm or correct.
What it really costs in 2026
These are Digital Heroes delivery bands, assuming one switching platform unless stated otherwise.
| Scope | Cost | Timeline |
|---|---|---|
| Validated intake, build plan generation, seat and device templates, number assignment, location capture | $70,000 to $160,000 | 12 to 18 weeks |
| Adds narrow customer self service, port coordination workflow and reseller scoping | $130,000 to $260,000 | 5 to 9 months |
| Full platform with a second switching platform, firmware management, billing reconciliation and partner hierarchies | $200,000 to $450,000 | 8 to 13 months |
| Each additional switching platform after the first | Add 40 to 70 percent | Add 8 to 14 weeks |
Two line items are usually absent. The first is documenting the conventions. Your dial plan rules, device standards and order of operations are not written down anywhere a developer can read, so somebody has to sit alongside your senior provisioning engineer for a couple of weeks and extract them. Providers with a written onboarding checklist move noticeably faster, and providers relying on institutional memory should expect that fortnight to appear whether or not it was quoted.
The second is device model coverage. Supporting handsets is not one line item. Each vendor family has its own configuration semantics and firmware behaviour, so the second and third model cost real time. Name your two most common models in the brief and price additional families explicitly rather than assuming a generic template covers them.
Signals of a strong partner
- They ask which switching platform and which API version. Then they talk about rate limits and partial failure behaviour without being prompted.
- They define what happens when a build fails midway. Roll back, resume, or flag and continue, chosen deliberately. Without a defined answer you get half built customers.
- They attach location to the seat, not the account. Anyone modelling it at account level has not read the dispatchable location requirement and your exposure survives the project.
- They raise redeployed handsets unprompted. Only people who have seen a returned phone arrive at a new customer still pointing at an old configuration bring up wiping without being asked.
- They find billing reconciliation interesting. Comparing provisioned objects to billed items is often the fastest return in the engagement.
- They argue for a narrow self service surface. A broad portal invites customers to break their own dial plan and then call you.
- They want your intake form and a real order. Estimating from a sample order beats estimating from a feature list.
Red flags
- An offer to replace the switching platform. That is not the problem and it is not the budget you have.
- Location treated as an address field. Building, floor and suite tied to a seat with a confirmation date is the requirement. An account address is the thing you already have and it is already stale.
- Silence on partial failures. Fifty seat builds fail partway through routinely. A vendor without an answer will leave customers half provisioned and your team cleaning up by hand.
- Multi platform support quoted as a small increment. A second switching platform is a multiplier, not an addition, and a low number here signals inexperience.
- Templates delivered as hand edited config files. That is the current problem with a new coat of paint.
Questions to ask on the first call
- Which switching platform APIs have you driven by name, and what were the rate limits like at fifty seats?
- A build fails at seat thirty one of fifty. What does your system do, and what does my engineer see?
- How do you model dispatchable location, and what triggers a revalidation?
- What blocks a new seat from activating without a confirmed location, and who can override it?
- How does a redeployed handset get wiped and reassigned, and what does the device history record?
- How would you validate a customer intake spreadsheet, and which errors would you reject outright?
- How would you reconcile provisioned seats, devices and numbers against what we actually invoice?
- Which handset families have you generated configuration for, and what did the second family cost in time?
- Who owns the repository, the cloud accounts and the device configuration templates, in writing before kickoff?
A simple way to decide
Do not choose between three proposals written against three guesses at your process. Buy a paid discovery phase as a small fixed engagement and require a written specification you own outright: the build plan sequence with your conventions captured, the platform API assessment including partial failure behaviour, the device lifecycle including redeployment, the location model with its revalidation cycle, and the reconciliation approach between provisioning and billing. Send the firm your onboarding checklist, a real customer intake form and the platform you run, and expect them to map where the day of manual work actually goes before quoting.
Then take that document to everyone on your shortlist. Digital Heroes works PRD first for that reason, and contracts through India LLP, US LLC and UK LTD entities so intellectual property assigns under the law your own advisers already read.
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.
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
Frequently asked questions
How much does it cost to hire a hosted voice provisioning developer?
A provisioning automation layer over your existing switching platform runs $70,000 to $160,000 across 12 to 18 weeks, covering validated intake, build plan generation, seat and device templates, number assignment and location capture. Extending into narrow customer self service, a second switching platform, firmware management and billing reconciliation runs $200,000 to $450,000 over 8 to 13 months. Each switching platform after the first adds 40 to 70 percent.
Should we replace NetSapiens or BroadWorks?
No. They are switching platforms and they are good at switching. What they do not own is your process: dial plan conventions, class of service tiers, device standards, the order of operations between porting and building, and your rule about not activating a seat without a location. Hire for an orchestration layer that drives the platform API with those rules applied, and leave the platform exactly where it is.
Why does dispatchable location decide who we hire?
Because it is the requirement most often modelled wrong, and modelling it wrong leaves your compliance exposure intact after you have paid for the project. Location is a per seat fact covering building, floor and suite, and it changes whenever staff move desks or a customer takes another floor. If a candidate attaches it to the account rather than the seat, and has no revalidation cycle, they have not read the requirement.
What happens if a provisioning build fails halfway through?
That depends entirely on a decision the developer should make deliberately with you: roll back the whole build, resume from the failed object, or flag and continue. Fifty seat builds fail partway through as a matter of routine, whether from a rate limit, a duplicate extension or a platform timeout. A team without a defined answer will leave you with half provisioned customers that your engineers finish by hand, which is the problem you were trying to remove.
Who owns the code and the provisioning templates?
You own the repository, the cloud accounts, the device configuration templates and the right to hire another developer, written into the contract before kickoff. Digital Heroes gives the provider ownership from the first commit. This system encodes your dial plan conventions, device standards and compliance workflow, which is your operational knowledge rather than a vendor's product, and it should never sit somewhere you cannot reach or extend.
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.
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.
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.
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.
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 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.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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 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.
Will a custom internal tool scale as our company grows?
Yes, provided it sits on a standard stack with a real database: PostgreSQL comfortably handles millions of records, and adding users costs hosting pennies rather than per-seat fees. The real scaling risks are organizational, not technical: new departments want features, processes change, and the tool needs a budget line to evolve. Set aside a small quarterly improvement budget instead of treating launch as the finish line, and the tool stays useful for a decade rather than getting rebuilt every two years.
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 long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
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
Published · Last updated .
