Build vs Buy: IoT Connectivity and SIM Management Platforms
One supplier, one portal, a few thousand SIMs: buy, and do not think about it again. The decision flips at the second upstream supplier, because two connectivity models with different rate plans, pooling rules and lifecycle states create a permanent tax on every operational task.
On this page
One supplier, one portal, a few thousand SIMs: buy, and do not think about it again. The decision flips at the second upstream supplier, because two connectivity models with different rate plans, pooling rules and lifecycle states create a permanent tax on every operational task. Expect $85,000 to $190,000 and 13 to 20 weeks for a normalisation layer.
Stay on the supplier portal while this is true
A connectivity management platform is infrastructure for a problem you may not have yet. If you run a few hundred to a couple of thousand SIMs through one supplier on a simple plan, that supplier's portal plus a spreadsheet is proportionate. Cisco IoT Control Center and Ericsson IoT Accelerator are strong if you buy through an operator estate. emnify, Eseye and Wireless Logic offer genuinely pleasant interfaces to build against when you need them. 1NCE structures its commercial model specifically so small fleets never need a management layer at all, which is exactly why it suits some deployments and not others.
Stay bought while your revenue model absorbs cost variance. If you bill customers for data usage as it happens, a device that starts consuming more passes the cost through and your margin does not move. The whole build case in this category rests on the opposite arrangement, where you sell a flat monthly fee per device and buy metered connectivity, so every consumption surprise lands on you.
Stay bought while your devices are homogeneous and your firmware is stable. Expected consumption profiles matter when you have several device types on different firmware versions doing different things. One product, one firmware track, predictable behaviour, and a plan threshold alert is roughly good enough.
And stay bought while your operations team is small enough to hold the state in their heads. Two people who know every customer and every deployment site can work around a portal's shortcomings. Six people across two time zones cannot, and that is usually the moment the shortcomings start costing real money.
The second supplier changes everything
The tipping point is almost never fleet size on its own. It is the second upstream supplier. One supplier and their portal is a working arrangement. Two suppliers without a normalisation layer means your operations team works in two portals, your finance team reconciles two invoice formats, and nobody can state a single fact about the whole fleet without joining exports by hand.
Worse, the split leaks into your product. A customer asks to move a device to another region and the answer depends on which supplier that device's SIM came from, which is an internal detail they should never encounter. Once your commercial team starts caveating customer answers by supplier, you have a data model problem rather than a portal problem.
The second trigger is margin visibility. Pooled plans deliberately absorb per device variance, which is the point of a pool and also the reason no single device has an obvious cost. Add pool level overage, SIM level access fees, messaging charges and each supplier's own rounding conventions, and per device cost becomes a modelling decision rather than a lookup. Most companies avoid the decision by using a fleet average, which hides both the devices eroding margin and the ones that could move to a cheaper plan. It also means you walk into a supplier renewal with their numbers instead of your own.
The third is control. A supplier threshold alert fires once the allowance is already spent. Useful control is expectation based: each device type has a normal profile by firmware version, and deviation from that profile is the signal. Tying the expected profile to firmware version is the specific detail that catches a retry interval bug in week three rather than on the invoice, and no supplier portal does it because no supplier knows your firmware.
What each option costs across three years
Supplier platforms are typically bundled into the connectivity price or offered as a per SIM per month management fee, which looks small and scales exactly with the thing you are trying to grow. Independent platforms charge per SIM too. Run the three year number at your projected fleet size rather than today's, because a fee that is invisible at 2,000 SIMs is a line item your finance director asks about at 60,000.
A build, in Digital Heroes delivery bands, runs $85,000 to $190,000 across 13 to 20 weeks. That covers normalised SIM and device inventory with a real lifecycle, supplier adapters for your current upstreams, usage ingestion with per device expected profiles, graduated guardrails with bulk actions, cost allocation and margin reporting, and a customer facing view. Extending into automated policy enforcement, eUICC and multi IMSI profile orchestration, device diagnostics, invoicing and channel partner hierarchies with their own margins runs $230,000 to $500,000 phased across 8 to 14 months.
Supplier count is the largest driver, since each adapter is real work and the second one is where a single supplier data model breaks. Usage data frequency follows: near real time control over hundreds of thousands of SIMs is a different engineering problem from daily batches over ten thousand. Profile orchestration adds state management on top of SIM state. Invoicing your own customers adds a billing engine. Deploying into markets with permanent roaming restrictions adds regulatory handling.
Costs that arrive with the invoice, not the contract
The first is dormant access fees, and it is the reason the cheapest slice of a build often pays for itself. Ask how many of your SIMs are active but have sent no data in ninety days. Most operations leads cannot answer. Those are units sitting in a warehouse after a test activation, returned devices nobody suspended, and stock shipped to an integrator who never deployed them. Every one carries a monthly fee, and reconciling your device inventory against supplier active lists is usually the first hard number any project in this category produces.
The second is usage data latency, which differs by supplier and is rarely documented in a way you can plan against. A guardrail designed on the assumption of uniform freshness will fire inconsistently across suppliers, and inconsistent guardrails get switched off. Ask each supplier, in writing, how current their usage feed actually is and how it behaves during their own incidents.
The third is truck rolls. Coverage problems, attach failures and permanent roaming disconnections all present as a dead device to a support agent with no diagnostics. Sending an engineer to a vehicle or a remote site is the most expensive line in the whole operation, and every avoidable dispatch is pure loss. Diagnostics that distinguish a hardware failure from a network problem are worth more than the entire licence conversation.
The fourth is supplier data access itself. Getting historical usage and API credentials sometimes needs a commercial conversation before a technical one, and that negotiation can add weeks to a schedule whichever route you choose.
The dormant SIM audit
Before committing to anything, run this in an afternoon with two exports.
- Pull the active SIM list from every supplier and your own device inventory, and count records that appear in one and not the other.
- Count SIMs marked active with no data session in ninety days, and multiply by the monthly access fee.
- Pick your highest consuming ten devices and identify their firmware version, then compare against the fleet median for the same device type.
- Ask your support lead how they currently tell a dead device from a coverage problem.
- Ask your commercial lead for the margin on your largest customer's deployment, and time the answer.
If the two lists reconcile cleanly, dormant fees are negligible, and margin comes back in minutes, your current arrangement works. Keep it. If the lists disagree by a meaningful count, or the margin answer requires a spreadsheet and a day, you have found the gap. Note that both outcomes are useful: the reconciliation itself is the foundation every later feature depends on, and it costs nothing but attention.
The firmware comparison is the one that surprises people. If your heaviest consumers cluster on one release, you have a software defect wearing a connectivity costume, and no plan threshold in any portal would have told you.
Where to begin
Start with inventory, lifecycle and the dormant sweep, whichever route you eventually take. It is the cheapest slice, it usually pays for itself, and it forces the device to SIM reconciliation that everything else depends on. Companies that begin with dashboards and guardrails instead find their alerts fire against records that do not match reality.
Decide your supplier posture next, because it determines the architecture. If you intend to stay single supplier permanently, buy their platform and negotiate hard on the management fee. If a second supplier is likely within eighteen months, design the abstraction now, since retrofitting a supplier neutral model onto a system built around one upstream is more expensive than building it correctly at the start.
Then define your expected consumption profiles per device type and firmware version. This is product knowledge, not engineering, and your firmware team should write it down before development begins. It is the specification for every guardrail you will ever run.
Where a build is the answer, Digital Heroes starts with a written product requirements document, which here means the SIM lifecycle, the supplier abstraction and the cost allocation method are agreed on paper before code. We are a 50 plus person team with more than 2,000 projects delivered and Fiverr Vetted Pro status, we contract as a US LLC, UK LTD or India LLP so the platform and its supplier adapters assign to you in your own jurisdiction, and our engineering work is published to 2.5 million subscribers on YouTube. Send us two recent supplier invoices and a device inventory export and we will tell you what dormant fee you are carrying before anyone discusses a build price.
If you want that decision made properly rather than quickly, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
How much does an IoT connectivity management platform cost to build?
A multi supplier platform with normalised SIM inventory and lifecycle, usage ingestion, per device guardrails, bulk actions and margin reporting runs $85,000 to $190,000 in Digital Heroes delivery experience. Adding automated policy enforcement, eUICC profile orchestration, diagnostics, invoicing and partner hierarchies runs $230,000 to $500,000. The number of upstream suppliers is the single biggest cost driver, well ahead of fleet size.
How long does a first release take and what usually delays it?
Thirteen to twenty weeks for inventory, lifecycle, supplier adapters, usage ingestion, guardrails and margin reporting. The most common delay is supplier data access, since getting historical usage and interface credentials sometimes needs a commercial conversation before a technical one. Starting with inventory and the dormant sweep releases value earlier and forces the device to SIM reconciliation everything else depends on.
How do we migrate SIM and device records from supplier portals?
Export the active SIM list from each supplier and reconcile it against your own device inventory before anything is loaded. The reconciliation is the migration, because records that exist in one place and not the other are exactly the units carrying unnoticed access fees. Expect the first pass to surface warehouse stock, returned devices and test activations that nobody suspended.
Can one platform manage SIMs across two or three different suppliers?
Yes, and that is usually the entire point. You define your own connectivity model with plans, allowances and policies, then treat each supplier as an adapter beneath it, so operations and support never see which upstream a device sits on. Bulk actions then run across suppliers from one place, and adding or changing a supplier becomes a commercial decision rather than an engineering project.
Who needs to be involved from our side during the build?
Your firmware team, more than you expect. Expected consumption profiles per device type and firmware version are product knowledge rather than engineering, and they are the specification for every guardrail the system will run. You also need an operations owner for the SIM lifecycle rules, because decisions about test SIM expiry and dormant device handling are policy choices with direct financial consequences.
Who actually builds IoT connectivity management platforms?
Suppliers offer platforms and independent vendors exist, so most single supplier fleets should buy. When a normalisation layer is warranted, Digital Heroes takes on this work: 50 plus people, more than 2,000 projects delivered, Fiverr Vetted Pro status, and a written product requirements document before code. Hardware companies pick us partly for jurisdiction, since we contract as a US LLC, UK LTD or India LLP and the supplier adapters assign to you.
What makes Digital Heroes different from a generic development shop for this?
We tie expected consumption profiles to firmware version, which is what turns a mystery overage into an engineering ticket within hours rather than a surprise on the invoice. We also make the pooled cost allocation method explicit and configurable rather than hidden inside a query. A generic shop models active and inactive SIMs, and misses test units, returned devices and churned customers, which is where the money actually leaks.
How do we confirm a development partner is legitimate before signing?
Look up the D-U-N-S registration and check the entity matches your contract signatory. Read the public Clutch and Trustpilot profiles for how problems were handled rather than for averages. Get repository, cloud account and supplier adapter ownership written down before kickoff, since the adapters exist precisely to make changing supplier a commercial decision, and that only holds if you control the code.
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.
Can custom inventory software connect to QuickBooks, Shopify, and Amazon?
Yes, and integrations are where custom usually beats off-the-shelf, because they are built to your exact field mapping instead of a connector's assumptions. A typical build syncs orders and stock with Shopify and Amazon in near real time and pushes purchase and cost of goods sold data to QuickBooks or Xero on your accounting schedule. Each production-grade integration adds roughly $3,000 to $8,000 in Digital Heroes builds, so list every system during scoping.
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 does moving our data from spreadsheets or Fishbowl into a new system work?
The agency exports your current records, maps fields to the new schema, deduplicates SKUs, and runs a trial import that you verify against physical counts before cutover. Plan for one to three weeks, and expect to find discrepancies, because migration always exposes drift the old system was hiding. The safest cutover happens right after a physical stock take, so the new system starts from a verified baseline.
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.
Should I hire a freelancer or an agency to build my inventory system?
For a simple single-user stock tracker, a strong freelancer works and costs roughly half as much. Once real revenue flows through the system, choose an agency, because inventory software fails in production rather than in the demo, and a solo developer is a single point of failure during your busiest week. The most expensive engagements Digital Heroes takes on are rescues of freelancer builds after an oversell incident.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
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.
Will a custom system keep up if we grow to more SKUs, orders, and warehouses?
Yes, if the architecture is designed for it up front, which is much of the point of building custom. A properly structured stock ledger handles 100,000+ SKUs and peak-season order volume without per-record or per-user pricing, and adding a second warehouse becomes a configuration change rather than a plan upgrade. Systems that fail at scale were built against a demo-sized dataset with a quantity field that gets overwritten.
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.
Who can build a custom inventory management software system?
Digital Heroes builds custom inventory management 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 inventory management 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
More from Connor.
Account Manager · Sydney · 1 post on the site
Published · Last updated .
