A connectivity operations platform for the fleet and carrier relationships you actually run
We build or extend software for cellular IoT subscription inventory, activation, status, usage, alerts, billing support, carrier APIs, customer operations, and reconciliation. Discovery starts with carrier and eSIM capabilities, contracts, device lifecycle, systems of record, and support ownership. The platform does not replace radio coverage, carrier agreements, certified hardware, or regulatory responsibility.
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
01
Operations teams switch among carrier portals and spreadsheets to understand subscription state, usage, cost, customer ownership, and device incidents?
02
A proposed custom platform assumes carrier APIs, eSIM switching, usage timing, or billing data can do more than the contracts and hardware allow?
Plain answer
An IoT connectivity management platform helps operators manage cellular subscriptions, carrier integrations, usage, alerts, customer assignment, and billing support across a device fleet. RaftLabs builds or extends this software around verified carrier and hardware capabilities. A focused platform starts at $40,000 and commonly takes 12 to 18 weeks after integration access is ready.
The portal said active. The device was still offline.
The carrier had accepted the subscription change, the hardware had not attached, usage data was delayed, and support had no shared record linking the device, customer, SIM, and latest request.
A connectivity platform should expose those boundaries rather than collapse them into one green badge.
Connectivity management joins records controlled by different parties
A useful platform can unify subscription inventory, lifecycle changes, status, usage, thresholds, costs, customer ownership, tickets, and billing support. It still depends on carrier APIs, commercial contracts, coverage, roaming partners, certified modules, SIM or eSIM capabilities, device firmware, network conditions, and human support.
This page remains distinct from IoT development because it serves connectivity operations rather than the full device product. It may integrate a carrier CMP instead of replacing one. A custom build is justified only when the operating model or economics are distinct enough to outweigh another platform to secure and maintain.
A connectivity offer grounded in verified capabilities
Lifecycle flow first
1
One fleet segment, carrier set, role model, and reconciliation path
Indicative delivery weeks
12-18
After carrier sandboxes, records, hardware context, and owners are ready
Starting investment
$40K
Fixed after integrations, billing, migration, volume, and support are known
These figures are planning ranges, not a claim that ownership always beats per-subscription pricing. The comparison must include carrier fees, engineering, cloud, security, monitoring, support, ongoing API changes, certification, migration, and opportunity cost. We model the actual contracts and fleet rather than inventing a breakeven device count.
Build when connectivity operations are a product capability, not just an invoice.
Use a commercial CMP when it meets the workflow and total-cost test.
A fit
01
The organisation manages a meaningful cellular fleet, owns carrier relationships, and needs one operating view across systems or customers.
02
Carrier and hardware capabilities can be verified, with sandbox access, representative records, and named operational owners.
03
Custom lifecycle, billing support, service experience, integrations, or economics create a defensible reason to own software.
Not a fit
01
A commercial carrier or aggregator portal already meets the workflows at an acceptable total cost.
02
The proposal assumes software alone can improve coverage, certify hardware, change contracts, or enable unsupported eSIM operations.
03
No team owns connectivity support, billing review, carrier escalation, security, platform maintenance, or device identity quality.
Platform scope
What one connectivity-operations release may include
01
Subscription and device inventory
Link subscription identifiers, SIM or eSIM profiles, devices, modules,
customers, plans, carriers, regions, lifecycle state, ownership, and history.
Define a system of record for each field and expose sync status and conflicts.
02
Carrier workflow integration
Connect supported APIs and events for ordering, activation, suspension,
termination, plan changes, profile operations, status, and diagnostics. Apply
role approval, idempotency, rate limits, retries, audit records, and manual
fallback.
03
Usage alerts and billing support
Ingest delayed or revised usage records, allocate them to devices and
customers, evaluate thresholds, version rating rules, surface exceptions, and
reconcile with carrier statements and the accountable finance system.
04
Operations support and reporting
Provide fleet views, last-known connectivity, workflow queues, customer
support context, carrier escalation records, dashboards, alerts, exports,
integrations, observability, and runbooks with source freshness visible.
Choose the connectivity-management model
Option
Use it when
Carrier portal
Operate one carrier directly
The fleet and workflow are simple and cross-system reporting is modest.
Commercial CMP
Use managed multi-carrier capabilities
Coverage, APIs, support, pricing, and controls meet the operating need.
Integration layer
Unify existing carrier and CMP services
The core connectivity works but staff and customers need one workflow.
Custom platform
Own differentiated connectivity operations
Lifecycle, billing, customer, integration, or economic requirements justify long-term ownership.
Reconciliation matters more than a polished fleet map
Carrier systems and device telemetry answer different questions. A subscription may be enabled while a device is powered off, outside coverage, incorrectly configured, or attached through a roaming partner. Usage may arrive after the session. Customer assignment may live in CRM while invoice ownership lives in ERP. The platform needs timestamps, provenance, and exception states for each view.
Lifecycle changes also need safeguards. A duplicate suspension or wrong-customer termination can interrupt a fleet. We use idempotency keys where supported, approval for sensitive bulk requests, preview and reason capture, bounded batches, result reconciliation, retry rules, and an audit trail. Emergency manual paths remain documented when provider APIs fail.
Delivery
From carrier capability map to controlled fleet rollout
Four phases verify external limits before automation and migration.
Phase 1
01
Map fleet contracts and authority
Inventory carriers, subscriptions, device identities, contracts, APIs,
hardware, lifecycle states, roles, customers, usage, billing, regions,
risks, and systems of record.
Phase 2
02
Prove carrier and data paths
Validate sandbox and production capabilities for activation, suspension,
status, usage, alerts, eSIM or profile operations, webhooks, limits, and
reconciliation.
Run a bounded fleet, compare platform and carrier records, test failures and
support procedures, stage migration, document ownership, and expand by
evidence.
Dependencies
What the platform cannot abstract away
Carrier capability
Document supported actions, environments, limits, data timing, events, service commitments, escalation, commercial rights, and change notice.
Hardware and network
Record modules, bands, profiles, firmware, bootstrap, roaming, certification, coverage, power state, device commands, and diagnostic limits.
Billing responsibility
Name source records, contract versions, taxes, currency, bundles, adjustments, approvals, reconciliation, disputes, accounting integration, and final invoice owner.
Operations and security
Define roles, bulk-action approval, audit, support hours, incidents, secrets, personal data, regions, backups, vendor access, maintenance, and exit.
Scope and price
A focused connectivity platform starts at $40,000.
Start with one fleet segment, carrier set, lifecycle flow, operating team, and reconciliation path.
The proposal separates software engineering from carrier, connectivity, cloud, certification, hardware, third-party, maintenance, and support costs.
Starting investment
Starts at $40,000
A first release commonly takes 12 to 18 weeks. More carriers, customer billing, migration, eSIM operations, regions, volume, or continuous support add scope.
Capability before automation
Carrier, contract, hardware, and data limits are verified before the
workflow is promised.
Reconciled rollout
A bounded fleet is compared with carrier records before broad migration.
Buy when carrier coverage, workflows, pricing, reporting, support, and integration fit are adequate. Build an integration layer when the main pain is a unified experience over existing carriers. Consider a custom platform when connectivity operations are strategically distinct, volumes and contract economics justify ownership, and your team can support carrier changes. We model build and operating costs against the current option rather than assuming custom is cheaper.
Only when the hardware, SIM or eSIM arrangement, carrier agreements, profiles, regions, and APIs permit it. A software screen cannot create radio support or commercial rights that do not exist. During discovery we verify profile download, activation, fallback, bootstrap connectivity, roaming, certification, and failure behaviour. Unsupported operations remain manual or outside scope.
That depends on each carrier or aggregator. Some data arrives through events, while usage records may be delayed or revised. We document source timing, watermark records, display last-updated state, reconcile corrections, and avoid presenting delayed usage as instantaneous billing truth. Threshold alerts include the source lag and should not be treated as guaranteed prevention of overage.
It can support rating, allocation, invoice preparation, and reconciliation using approved contract rules and source data. Finance and legal owners must validate tariffs, taxes, currencies, minimums, bundles, roaming, adjustments, disputes, and accounting treatment. Carrier records may arrive late or change. The software should preserve inputs and calculation versions, support review, and integrate with the accountable billing or ERP system.
A focused platform starts at $40,000 and commonly takes 12 to 18 weeks. Each additional carrier, contract model, customer billing path, migration, eSIM workflow, region, volume tier, regulated control, or 24-hour support expectation adds scope. The proposal separates engineering from carrier charges, connectivity, cloud, third-party tools, certification, device work, ongoing maintenance, and support.
Work with us
Which connectivity operation is still split across portals?
Bring carrier contracts and APIs, subscription counts, device identities, lifecycle states, usage samples, billing rules, support workflows, integrations, regions, and rollout constraints.
Scope and cost agreed before work starts. No surprises. No obligation.
Working prototype within 3 weeks of kickoff.
Pay by milestone. You see progress before each invoice.
60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.