Productization
Productization by segment

How Keedian is sold, delivered, and measured by segment.

Single source of truth for how Keedian packages and positions its offering across the seven segments of the multi-site operations market. The managed-service layer is delivered as Agentic Operations — AI agents handle routine triage, remediation, and analysis 24/7; human operators handle exceptions, judgment calls, and the customer relationship. One service, one SLA, one accountability. Each segment is built from products organized by asset class, structured in accumulative tiers, with product-specific add-ons, platform-wide add-ons, and a Custom advisory layer. This is a living document — iterate via Pull Requests on GitHub.

01 Segments

Seven segments, one shared template.

Each segment follows the same pattern: products organized by asset class, three accumulative tiers per product (Essential / Managed / Optimized), a Data Enabler with three models (Direct / Connect / Hybrid), product-specific add-ons, platform-wide add-ons, and a Custom advisory layer. The four founding segments share this productization template, with each segment's primary product set drawn from the asset classes that apply to it. The three expansion segments add product candidates specific to their operations.

Segment 01
Grocery
In review
Multi-site grocery chains with critical refrigeration loads protecting perishable inventory. Average ~460 sites per customer. Pain points: product loss, food safety, refrigeration energy spend, customer comfort, vendor coordination.
HVAC ✓ Refrigeration ✓ Lighting Energy ✓
3 of 4 products developed — open the segment hub
Segment 02
Convenience stores
In review
Convenience networks with thousands of small-format sites. Average ~3,500 sites per customer. Pain points: lean store labor, fuel/site systems, customer comfort, and energy waste replicated across many similar locations.
HVAC ✓ Refrigeration Lighting ✓ Energy ✓
3 of 4 products developed — open the segment hub
Segment 03
Small retail
In progress
Traditional retail chains — apparel, beauty, and specialty — with multiple locations across standalone and in-mall formats, typically 500–8,000 sq ft per store. No refrigeration load. Primary pain point: climate comfort for customers. Two configurations: standalone (full product catalog) and in-mall (monitoring-only, limited control).
HVAC ✓ Lighting ✓ Energy ✓
3 of 3 products developed — open the segment hub
Segment 04
Big-box retail
Pending
Large-format retail with BMS / EMS already installed, sophisticated facilities teams, high demand for governance, SLA, vendor performance, and executive reporting. Average ~620 sites per customer.
HVAC Lighting Energy
Next iteration
Segment 05
Foodservice / QSR
In progress
Casual-dining and quick-service brands, typically 50 to 2,000+ sites per chain. Dining-room comfort under kitchen-exhaust load, walk-in temperature during prep-rush, dining ambience as a brand standard, multi-utility spend (electric + gas + water). Reference customer: Outback Steakhouse.
HVAC ✓ Refrigeration Lighting ✓ Energy ✓ Kitchen Equipment
3 of 5 products developed — open the segment hub
Segment 06
Bank branches
In progress
Branch networks of banks and credit unions, from a hundred to several thousand near-identical sites. Customer-facing space where comfort and lighting are part of the experience, plus IT-heavy infrastructure (ATMs, branch IT, video, security) that requires continuous power and cooling. The hybrid case: retail equipment (RTUs, priced per branch) on office-like connectivity — corporate real estate standardizes a BMS across the network, so the Data Enabler leads with Model B.
HVAC ✓ Lighting ✓ Energy ✓ Operational Continuity
3 of 3 products developed — open the segment hub
Segment 07
Offices
Published
Corporate workplaces from single-tenant headquarters to multi-tenant Class A buildings, typically 5 to 500 buildings per portfolio. Tenant comfort by floor and common zone, HVAC energy spend, indoor air quality, and ESG reporting. Almost every building already runs a BMS (Honeywell, Schneider, JCI, Siemens), so the Data Enabler leads with Model B — connect to the system you already have.
HVAC ✓ Energy ✓ Lighting ✓
3 of 3 products developed — open the segment hub
02 Approach

Three principles that structure the entire productization.

01

Product = asset class

Each product is named by the asset class it protects. This reflects how customers actually buy and how Keedian operates internally. A customer with refrigeration buys Refrigeration Protection — not a generic "facilities operations" package.

02

Accumulative tiers

Three tiers per product — Essential, Managed, Optimized. Each tier adds capabilities on top of the previous one. Customers never lose functionality by upgrading, and can start at any tier. Managed and Optimized are delivered via Agentic Operations.

03

We capture the signal anywhere

Data Enabler with three models: our sensors, your existing BMS, or a hybrid. The managed service, dashboards, SLA, and outcomes are identical across all three models. Only the data source changes.

03 How to contribute

This document lives on GitHub.

Any change is proposed via Pull Request, discussed, approved, and merged. Decision traceability is captured in commits and in the DECISIONS.md log. Product owns the structure, Engineering owns the BMS classification, Sales contributes copy and talk tracks.

Join the repo

The repository lives on GitHub. To propose changes — pricing, new products, BMS classification, copy refinement — open an Issue or a Pull Request following the conventions documented in CONTRIBUTING.md. For strategic discussions, Issues are the preferred channel.