Scenario · IoT

Connected-device pilots into site expansion

An IoT provider had active devices but no shared definition of pilot success. We established the operating use case, included information-technology and operations teams in the evaluation, and equipped the account team for an expansion discussion grounded in the findings.

Client
Leading IoT organization
Sub-industry
IoT
Engagement
Embedded
Pillars
Assembled · Growth
Window
6 months
+60%
Funded site deployments

5 → 8

+15 pp
Pilot-to-funded-deployment conversion

25% → 40%

+140%
Contracted deployment sites

10 → 24

6 months
Measurement window

Comparable reporting periods

The situation

An IoT provider had active devices but no shared definition of pilot success.

The work focused on funded site deployments, pilot-to-funded-deployment conversion, contracted deployment sites. Sites counted only within accepted commercial scope. Device connections during a technical test were excluded; contracted value was not recognized revenue.

Which activity helped funded site deployments, and what happened at the next decision?

The commercial question

What we did

Three moves, in order.

  • Sharpen

    Define the commercial outcome

    The priority was funded site deployments. The team used pilot-to-funded-deployment conversion and contracted deployment sites to assess the next stages, with a clear distinction between activity and accepted outcomes.

  • Author / Architect

    Build the path to the next decision

    We established the operating use case, included information-technology and operations teams in the evaluation, and equipped the account team for an expansion discussion grounded in the findings.

  • Generate / Gain

    Review progress against consistent measures

    The team compared funded site deployments, pilot-to-funded-deployment conversion, contracted deployment sites across the agreed reporting periods. Sites counted only within accepted commercial scope. Device connections during a technical test were excluded; contracted value was not recognized revenue.

What changed

Funded site deployments moved from 5 to 8. Pilot-to-funded-deployment conversion moved from 25% to 40%. Contracted deployment sites moved from 10 to 24.

Sites counted only within accepted commercial scope. Device connections during a technical test were excluded; contracted value was not recognized revenue.

We calculated relative changes from the baseline and comparison values and reported conversion or retention changes in percentage points. We rounded displayed changes to one decimal place where needed. The figures did not establish that marketing caused the outcome.

Measurement window: Two six-month IoT pilot cohorts, with a further six-month purchasing follow-up.

IoT industry photograph
Where this sat in the system
01–02

Strategic

03–04

Assembled

Core
05–06

Growth

Core

Services in this example
Positioning & Messaging Creative & Content Development Digital Experiences Go-to-market Strategy Data, Tech & Operations Account-Based Marketing

Related reading

Explore the iot growth system.

Next step

Same problem?

If your budget conversation runs on impressions, that is the first thing we would fix.