Vol. 01 Strategy Memo Internal AM · distribute carefully Lite → Pro upgrade engine

Stop collecting data.
Start converting it.

By AM Growth Strategy POC v0.3 7 May 2026

01 TL;DR

AIOSEO already collects enough data to drive a meaningful Lite → Pro lift, but ships none of it as trigger campaigns. This memo maps the fix: 4 layers (telemetry, segments, campaigns, outcomes), 24 data points, 24 named segments queryable in Metabase, and 24 trigger campaigns sequenced in Lindris, across a 6–8 month roadmap gated on a one-sprint decoder.

Top-of-funnel campaign work cannot start until P0a ships. PLAN.md is the 651-line strategy memo; this page is the visual model.

Telemetry data points

Named segments

Trigger campaigns

Honest delivery, P0–P4

6–8 mo

I. The stack

Four layers, one causal chain.

Each row below is a layer of the program. The arrows are unforgiving: no decoder, no segments; no segments, no campaigns; no campaigns, no measurable lift. The current state is row 1. Everything else is what we’re building.

Layer 01

Telemetry

What the plugin emits and the warehouse stores.

Layer 02

Segments

Each is a Metabase saved question that materializes a list nightly.

Layer 03

Campaigns

Trigger-based sequences in Lindris. Every campaign owns one segment.

Layer 04

Outcomes

Measured in the warehouse, not in Lindris.

N1Lite → Pro upgrade rate — headline goalprimary

N2Pro renewal rate — defensive12-mo

N3Addon attach rate — expansionper addon

N4Failed-payment recovery — bottom-funnelrecovered $

N5Wizard completion rate — activationstep-7 reach

N6GSC connect rate — activation14-day

N7AI credits utilization — entitlement use% used

II. Telemetry inventory

What we collect — and why.

Every row fills eight columns: data point, plan, WP.org safety, why we want it, queryable status, segments fed, campaign powered, success metric. Rows that couldn’t fill all eight got cut.

Class

Plan

№	Field	Plan	WP.org	Why	Queryable	Feeds

III. Segment ledger

24 named segments. Five ship first.

Every segment is a Metabase saved question. Five are bracketed [Top 5] — buildable the sprint after P0a lands. Anything marked † is gated on P2 telemetry, Stripe ETL, or helpdesk ETL.

Show

[id] Top-5 first-wave † Gated on P2 telemetry, Stripe ETL, or helpdesk ETL → feeds campaign listed at right

IV. Campaign matrix

When each touch lands.

Every campaign is a horizontal lane; every touch is a marker on the day it fires. Round = email, square = in-product. Color = tier. Hover any marker to read the actual copy. This is what AM doesn’t do today.

Bottom-funnel intent High-intent Activation / retention Renewal defense Broad / volume Targeted / niche Hygiene / win-back ● email ◆ in-product

Campaign · Segment

Day from trigger

V. Roadmap

P0a first. Everything follows.

The honest delivery window for the full P0–P4 path is 6–8 months. Anyone quoting faster is compressing scope, ignoring the WP.org adoption curve, or both. Owners are TBD — the doc does not ship until each phase has a named DRI.

Phase · Owner