Product Marketing Lead · Post-acquisition · 2023–2024

Kpler AIS: three vessel-tracking networks, one product.

SECTOR

Maritime data and API

STAGE

Post-acquisition integration

MARKET

Global

ROLE

Product Marketing Lead

PERIOD

2023–2024

COMPANY

kpler.com

The situation

The coverage was the best available, and there was no product a customer could buy.

Kpler's acquisition of MarineTraffic brought two terrestrial AIS networks together, alongside satellite and shipborne feeds from partners. On paper that was the most complete positional picture of the global fleet available anywhere.

In the market it was several datasets with several names, several stories and no single thing a customer could buy.

01 · What this engagement produced

22 of 34 outputs

22 of the 34 outputs, across all six stages.

Kpler AIS, the single feed, came out of stage 03, segment, position and price.

01Research3 of 6

3 not produced

Win / loss, Assumption log, Pre-mortem

02Competition2 of 4

2 not produced

Table-stakes read, AI visibility

03Segment, position and price6 of 6
04Message3 of 4

1 not produced

Message drift

05Launch and enable7 of 8

1 not produced

Launch tiers

06Measure and maintain1 of 6

5 not produced

Product funnel metrics, Launch post-mortem, Trust metrics, Half-Life Map, Six-stage readout

Solid is what this engagement produced. Dashed is what it did not reach.

02 · The diagnosis

The advantage already existed. Nobody could explain it.

Terrestrial AIS is dense near coasts and blind mid-ocean. Satellite fills the gap but at lower frequency. Sold separately, each has an obvious weakness and a customer has to assemble continuous coverage themselves, from more than one contract. Combined and normalised, the weakness disappears. The work was to make that advantage a product with a name, a boundary and a price.

03 · When I arrived, when I left

When I arrived

When I left

Several datasets

One product

Coverage gaps between sources

Continuous positional coverage

A different story per source

One narrative for five kinds of buyer

The customer integrated the sources themselves

One endpoint, one contract

04 · What I built

4 workstreams

One product, out of three networks.

01Product definitionOne product where there had been several sources.

03 Segment, position & price

  • A single feed of terrestrial, satellite and shipborne positions
  • A single API endpoint returning the latest available position for the global fleet
  • A written scope: boundaries, capabilities and limitations
  • Every position cleaned, validated and normalised before it reaches the customer

Three sources, one feed

Terrestrial network A

Coastal, high frequency

Terrestrial network B

Coastal, high frequency

Satellite and shipborne

Open ocean, lower frequency

Kpler AIS

One endpointGlobal fleet, every responseCleaned, validated, normalised

Coastal density and open-ocean continuity in one feed.

02Positioning on coverage and trustThe claim: a trusted, verified, owned source.

03 Segment, position & price · 04 Message

  • Positioned on continuous coverage and ownership of the network
  • Main value proposition: coverage and granularity from a network Kpler owns
  • Named the limitations, because a data buyer who finds them later stops trusting every other claim
03Messaging for five buyersOne reason to buy for each of five buyers.

04 Message

  • Government and maritime security: detecting suspicious vessel activity, enforcing maritime law, monitoring pollution
  • Trade finance analysts: origin, destination and route of cargo to assess risk and monitor supply chains
  • Traders: market intelligence, arbitrage, trade route optimisation, counterparty reliability
  • Supply chain and risk managers: visibility of goods in motion, accurate arrival and departure times
  • Fleet operations managers: vessel tracking, collision avoidance, route optimisation, performance reporting
04Enablement for a technical productWhat sales needed to sell a data feed.

05 Launch & enable

  • A Product Oracle: one internal document on what the product is, who it is for and who it is not for
  • A sales playbook, factsheet and FAQ
  • Competitive battlecards built from a sourced grid
  • A messaging matrix that ties every claim to a buyer and to its proof

05 · The judgment call

I put the limitations in writing before launch.

The temptation with a merged data product is to describe it as complete. It never is. Positional data has latency, gaps and edge cases, and the buyers for this product, government analysts, traders, risk managers, are the people who will find them.

The Product Oracle stated the limitations and prerequisites in writing, internally, before anything went to market. A data buyer who discovers a limitation after signing stops trusting every other claim you made.

06 · What this proves

Four things, if you're deciding whether to hire me.

I integrate after acquisitions.

Three networks, one sellable product.

I make technical products easy to buy.

An API feed with a narrative five different buyers recognise.

I write the internal source of truth.

Product Oracle, playbook, battlecards, messaging matrix.

I state the limits.

The limitations were in writing before the product went to market.

Frameworks installed

Product OracleThe Messaging Matrix