Foldspace GTM — Messaging Matrix (June 2026)
Purpose. The connective map for the awareness + pipeline push (paid media + influencers). It replaces the old "tracks," which were secretly bundling four independent things into one label. Here those dimensions are separated so messaging is reusable and targeting is precise.
The one rule before anything else — AI-Native is the spine. It's the company priority: CPO and CTO are both behind it and Product is all-in. For almost everyone you talk to, the lead is the AI-Native story — who owns the interface between the user and the product, the three-layer stack, the data flywheel, and shipping AI-Native experiences in hours instead of quarters. AI-First Growth is not a parallel motion you choose between — it's a sharper lens for one persona, the Growth PM (whose number is activation and who speaks click tax and time-to-value natively), with an outcomes flavor you can layer for the CX leader. Everyone else hears the AI-Native story first. Don't lead with activation curves for an exec or an engineer — lead with the transformation and the architecture, and save the growth language for the person whose comp depends on it.
An asset = one Persona × one Angle. Pick who you're talking to and the value narrative; the proof, hooks, and avoid-list come with them. The motion shapes the CTA/funnel, not the words.
Built from icp-a-algplg.md, icp-b-ainative.md, icp-c-product-manager.md, icp-d-cx-leader.md, and the canonical narrative in core/. Scope this cycle: mid-market + enterprise; persona depth = Exec + Champion.
The four dimensions
- Persona (WHO) — by title. Stable and reusable. A person can receive several angles.
- Trigger (WHICH companies) — the situational fact that makes an angle land: has a free trial, declared an AI-Native initiative, product got complex, onboarding/support pain, eng team building agents.
- Angle / message (WHAT we say) — the reusable value narrative.
- Motion (HOW the deal grows) — land & expand vs. top-down.
Personas (7, by title) — with the lead
For each persona, Lead with is what you open on. AI-Native is the default door; only the Growth PM opens on AI-First Growth, and the CX leader opens on AI-Native priority with an outcomes flavor.
| Persona | Type | Function | Lead with | Also carries | Brief |
|---|---|---|---|---|---|
| VP Product / CPO | Exec | Product / Growth | AI-Native — transformation, the three layers, who owns the interface, the flywheel | Modernize & True Intent · AI-First Growth (free-trial orgs) | persona-vp-product-cpo |
| CTO / VP Engineering | Exec | Engineering | AI-Native interface layer — build the brain, buy the operator | Build-in-codebase | persona-cto-vp-eng |
| PM | Champion | Product | AI-Native — Modernize & True Intent (agentify the feature, ship intents not screens) | — | persona-pm |
| AI Engineer (Staff/Lead) | Champion | Engineering | AI-Native interface layer — Trust Lab evals (early access), inference gateway, model routing | — | persona-ai-engineer |
| Developer (IC) | User → Champion | Engineering | AI-Native — Build-in-codebase (CLI/SDK, one command, drop-in) | — | persona-developer |
| CX leader (VP CX / Head of CS / CCO) | Exec/Champion | Customer Experience | AI-Native priority, outcomes flavor — AI Onboarding (activation / TTV) | — | persona-cx-leader |
| Growth PM | Champion | Growth | AI-First Growth — the one growth-lens persona (activation, click tax, TTV) | AI Onboarding | persona-growth-pm |
Budget owner (from real deals): the economic buyer is typically Product (VP Product/CPO) or the CTO — sometimes Marketing. (Optibus = CTO; EverCommerce = Marketing / CTO / Product, unconfirmed.) Treat Growth PM, PM, CX leader, AI Engineer, and Developer as champions/users/influencers — line up a Product or CTO economic buyer behind them.
Angles (5) — the reusable messaging modules
Four of these five angles are AI-Native expressions for different personas — interface layer (CTO / AI Engineer), Modernize & True Intent (PM / VP Product), AI Onboarding (CX leader, and the activation cut for Growth), Build-it-in-your-codebase (Developer / CTO). AI-First Growth is the one growth-lens angle — reserve it for the Growth PM (and an outcomes flavor for the CX leader).
| Angle | Trigger (company) | Primary personas | Module | Lead proof | Motion |
|---|---|---|---|---|---|
| AI-Native interface layer | Company declared an AI initiative; building agents | CTO/VP Eng · AI Engineer | SDK · Trust Lab · A2A/MCP · real-time context | Optibus (4 products) · 20–35% lower token cost | Top-down |
| Modernize & True Intent | Complex product; no "why" data | PM · VP Product | Conversational Analytics + Product Agent | Intent / unresolved prompts · Optibus modernization | Either |
| AI Onboarding | Onboarding / activation / support-load pain | CX leader · Growth PM | Product Agent + Conversational Analytics | Activation / TTV (quantified proof thin) | Land & expand |
| Build it in your codebase | Eng team building agentic features | Developer · CTO | Developer plugin / SDK | Time-to-first-agent — TBD | Land & expand |
| AI-First Growth (⊃ PLG) | Has free trial / self-serve | Growth PM · VP Product/CPO (situational) | Product Agent + Conversational Analytics | MixMax 57→90 · AskCody +344% · Qonto 8→16% | Land & expand |
Per-angle guardrails (non-negotiable)
- AI-Native interface layer — avoid "agentic transformation," "production-ready," "reliable," "revolutionary." Concede Anthropic Managed Agents, sell the layer above it: build the brain, buy the operator. See
icp-b §4,§6. - Modernize & True Intent — avoid all funnel/activation language (signals Growth PM), "black box," "yet another dashboard." Say intent sharpens/feeds the roadmap, never writes it. Conversational Analytics reads the Product Agent's conversations, so the agent comes first (analytics is the dividend, not a standalone tool). See
icp-c §6–7. - AI Onboarding — ⚠️ do not use "deflection," "support bot," "chatbot," or "agent does it vs answers it." Decagon/Sierra already execute tasks — leading there walks into a bake-off Foldspace can't win. Lead activation / time-to-value, sold against the product/adoption budget, not the support/cost budget. See
icp-d §5,§7. - Build it in your codebase — peer-engineer tone only; no marketing-speak; never claim a metric we don't have.
- AI-First Growth — avoid "AI-powered," "AI Copilot," "personalization at scale," "tours/tooltips," "PLG is dead." Frame as AI-First Growth ⊃ PLG — PLG solved access, it broke on outcomes. See
icp-a §4.
How to pick the door, fast
- Default to AI-Native. It's the company priority, and execs plus product are aligned on it.
- Lead AI-Native with: the transformation, the three layers, who owns the interface, the flywheel, ship in hours not quarters.
- Only switch into AI-First Growth language for the Growth PM, and optionally the CX leader (outcomes flavor). Those are the people whose number is activation.
- They already have agents or loops → "you built the brain, we're the operator."
- They have nothing yet → "the interface is the prize, and the window is closing."
- Their build is stalling → the 80% of internal AI projects never reach production stat, then "build the brain, buy the operator."
- Their AI cost is the problem → inference gateway and model routing.
Motions (the overlay)
- Land & expand — AI-First Growth, AI Onboarding, and Build-it-in-your-codebase. Self-serve or single-team entry that grows into a broader buy. (Developer adoption rolls up to the CTO; a growth/CX win expands across the product.)
- Top-down / strategic — AI-Native interface layer. The company's declared AI initiative drives a platform-level evaluation by engineering leadership.
- Either — Modernize & True Intent rides whichever motion the account is already in.
How to use
- Pick a Persona; open on its Lead with angle (AI-Native for all but the Growth PM). Add a second angle only if the trigger fits.
- Pull Lead proof + a Hook from the persona brief; obey the angle's guardrails.
- Let the Motion set the CTA (self-serve trial/plugin for land-and-expand; "talk to us / exec briefing" for top-down).
- Modules (Conversational Analytics, Trust Lab) are early-access — message forward-looking, never "available now."
On proof points
Internally, name the reference customers: MixMax, Optibus, EverCommerce, AskCody, Vidmob, Base, Togal. In any external-facing copy, anonymize unless the logo is explicitly cleared — default to "mid-market B2B SaaS platform" + the metric.
Open gaps
- Naming reconciliation: the growth angle is now AI-First Growth (formerly Agent-Led Growth / ALG) per owner sign-off (2026-06-01).
core/(alg-principles.md, overview.md, executive-summary.md, devex-strategy.md) and several shipped assets still say "ALG" — pending a separate core-level reconciliation with the owner. - Build-it-in-codebase has no published proof metric (time-to-first-agent). Don't invent one for paid.
- Conversational Analytics = Foldspace's analysis of the conversations users have with the embedded Foldspace Product Agent (intent, gaps, unresolved prompts) — not a standalone tool that ingests your existing clickstream/tickets. So it requires the Product Agent to be deployed. Consequence for PM and CX: the Product Agent is the entry (modernize / onboard); the intent analytics is the compounding dividend once it's live. Never pitch Conversational Analytics as a standalone discovery tool for a product without the agent.
- AI Onboarding competitive risk: Fin/Decagon/Sierra. Differentiate on surface + goal (in-product, core-workflow, activation), not "we take action."
Companions: icp-a-algplg.md, icp-b-ainative.md, icp-c-product-manager.md, icp-d-cx-leader.md. Canonical product truth: core/. Last updated: 2026-06-01.