Equipment, devices, and connectivity that keep paying after the sale.
If your revenue is anchored to what’s deployed in the field — serialized units with their own entitlements, service obligations, and subscriptions — this is your page.
THE DEFINITIONA Hardware-enabled Recurring Service business earns recurring revenue anchored to deployed hardware — equipment, devices, or connectivity infrastructure — where each serialized unit in the field carries its own entitlements, service obligations, and subscription or usage billing. The initial sale starts the relationship; the install base sustains it. Sometimes called servitization.
Is your XaaS business one? One question routes it: is there a deployed, serialized unit whose install base anchors entitlement and recurring billing? Device-as-a-Service, IaaS, hosting, managed infrastructure, connectivity — yes, you’re here. Security-, Data-, Desktop-as-a-Service and other software-only models — see SaaS. AI-native companies — see AI SaaS.
The install base nobody can see.
The equipment shipped. Then the truth scattered: warranty in one system, entitlements in another, the service history in a third, and the definitive record of what’s actually deployed — in your customers’ memory. Service starts with the customer supplying their own equipment details. Parts ordering means hoping the model number is right. Renewals arrive as surprises, per unit, at the worst time.
The sale and the service revenue live in different systems — and the gap between them is where the recurring revenue leaks.
What Genesis executes
IoT device fleets
Serialized devices tied to subscriptions — metered, provisioned, entitled per unit. Device-as-a-Service is this segment’s purest form: the hardware ships, the revenue recurs, and every commercial question routes through the unit. If your fleet’s billing lives in spreadsheets keyed by serial number, you already know why the Install Base has to be the system of record.
Communications
Site-based delivery, provisioning workflows, usage-rated services. The commercial complexity isn’t the network — it’s that every site is its own configuration, every configuration its own entitlements, and every change a coordination project across ordering, provisioning, and billing. Genesis holds the site’s commercial state and executes the change against it.
Hosting, IaaS & managed infrastructure
The hardware side of “anything as a service”: racks, capacity, and managed environments sold as recurring commitments. Same anatomy — deployed units, per-unit entitlement, usage and subscription billing — same execution model.
What is a Hardware-enabled Recurring Service business?
One whose recurring revenue is anchored to deployed hardware — each serialized unit carrying its own entitlements, service obligations, and subscription or usage billing. The category is sometimes called servitization.
Is DaaS a Hardware-enabled Recurring Service?
Depends which DaaS. Device-as-a-Service — yes, it’s practically the definition. Data-as-a-Service and Desktop-as-a-Service are software-only models — those belong with SaaS.
Why does entitlement need to be computed rather than stored?
Stored entitlement is a copy — and copies drift from the contracts, warranties, and subscriptions that granted them. Computing coverage live from its sources means the answer is correct at the moment it’s asked, every time.
Most Hardware-enabled Recurring Service engagements land on one of three doors:
Portals & Buying Roomwhere your customers and service network stop calling and start executing
Billing & Subscriptionsper-unit truth from meter to invoiceCPQquoting against what’s already deployed