The OS argument: why pods need software to scale past hardware margins

A pod sells once. A $25K-50K unit ships, the customer pays, the manufacturer recognises the revenue, and depreciation begins on a roughly seven-year schedule. Gross margin on that unit, at scale, lands somewhere between 30% and 40%. The number isn't bad — it's the ceiling that's the problem. Hardware-only revenue is one-shot. There is no compounding.

The category parallel everybody points to is Tesla versus the legacy car business: the bet that software-defined hardware would re-shape the margin profile of an industry that had spent decades optimising for steel-and-glass cost-down. It played out in networking (Cisco versus passive-hardware vendors), in security cameras (Verkada versus DVR companies), and in physical-access systems (Brivo, Verkada Access, Latch in its time). The pattern is consistent: the company that owns the software layer captures the recurring revenue, the customer relationship, and the data flywheel. The hardware-only company becomes the supplier.

What "the OS layer" actually means for pods

It isn't one product — it's a stack of operating responsibilities the customer would otherwise have to assemble themselves:

• A booking engine, with rate management and conflict handling.
• Payments — card, invoice, member-billing, off-network walk-up.
• Real-time availability and access control, with badge / QR / app / kiosk options.
• A pricing engine that flexes by utilization signal, not a static rate card.
• An operator dashboard for the GM, head of operations, or facility manager.
• An end-user app or web flow for the booker — the tenant, the guest, the hybrid worker.
• Analytics and utilization reporting, weekly and monthly, to the operator and to corporate.
• Integrations into property management systems, calendar systems (Outlook, Google), and identity providers (SSO, SCIM).

Each of those is non-trivial. Together they are 18-24 months of engineering, somewhere between $3M and $8M in cost, and the hire-and-retain challenge of staffing a software team inside what is structurally a manufacturing business.

Why this matters specifically for manufacturers

Margin expansion

Software ARR per pod compounds in a way hardware revenue never can. A $50K pod earning $1,200/year of OS attach ARR is, at typical SaaS multiples, worth more in software-revenue-multiple than the hardware unit itself.

Customer lock-in

Once an operator's bookings, payments, access, and reporting are running through your software, the cost of switching the underlying hardware drops to near zero — but the cost of switching the software is high. Software changes the direction of the lock-in.

Channel power

Hardware-only manufacturers sell through resellers, integrators, and distributors who own the customer relationship. The software layer puts the manufacturer back in direct contact with the operator. That changes pricing power and renewal economics.

Defensibility

The long-term moat in this category will not be acoustic performance or panel quality. Those converge. The moat will be data — utilization patterns, demand windows, customer segments — and integrations into the systems operators already run. Both of those live in software.

The build-versus-partner choice

There are two paths. Building in-house: hire a software org, ship the OS in 18-24 months at $3-8M, and accept that the first 12 months are pre-revenue. Partnering: ship the OS layer in weeks, keep the hardware brand on the front-end, and run a revenue-share arrangement on the recurring economics.

Both are real choices. Building in-house gives you full control and full margin, but the time-to-market cost is significant, and the team you have to build is different from the team that ships your hardware. Partnering lets you reach the market this quarter, with a smaller cash outlay, and lets the manufacturing org stay focused on what it's already good at.

This is the conversation we're having with pod manufacturers right now — on the structure, the revenue share, the front-end branding, the data ownership. Read the manufacturers brief for the partner-side details, or get in touch directly if you'd like to walk through the unit economics on your specific volume.