Skip to content

gtm.md

Latest commit

 

History

History
119 lines (85 loc) · 10.5 KB

gtm.md

File metadata and controls

119 lines (85 loc) · 10.5 KB

Threadplane GTM Strategy

Durable strategy. Hand-edited. Operational details live in docs/gtm/. Workstream plans live in docs/superpowers/specs/gtm/. Last reviewed: 2026-05-13.

1. What we are

Threadplane is the production agent UI framework for Angular teams. It turns LangGraph, AG-UI, A2UI, and custom agent streams into real Angular experiences — chat, threads, tool progress, human approvals, generative UI, fallbacks, observability, tests — without rewriting in React or adopting a proprietary cloud.

2. Category

  • Primary: Threadplane
  • Secondary (only after "Agent UI"): Angular Agent UI Framework
  • Do not use: "Threadplane" (ambiguous with backend runtimes and coding agents), "Enterprise Angular agent framework" (reads sales-first).

The category claim is the Angular final mile: official streaming SDKs (LangChain, AG-UI, A2UI) get events into Angular; Threadplane turns those events into production-ready Angular experiences. We do not compete as a general agent UI framework. We do not compete with backend runtimes.

3. ICP

Two tracks, both addressed from the homepage via the CTA fork.

Track Buyer Channel Primary CTA Secondary surface
Developer Angular engineer on an agent project docs, GitHub, npm, search Install @threadplane/chat cockpit recipes
Enterprise Architect / eng lead at an Angular shop direct, partner, content Talk to our engineers /contact → LeadForm

Detailed personas, buying signals, and disqualifiers: docs/gtm/icp.md.

4. Funnel & activation

Two funnels share acquisition surfaces and diverge at the homepage CTA.

Developer funnel: $pageview → comparison/content view → Install @threadplane/chat (copy) → cockpit recipe start → cockpit recipe complete → cockpit six-signal activation.

Enterprise funnel: $pageview → Talk to our engineers click → /contact view → LeadForm submit → lead_form_success → lead_qualified (server-side enrichment) → discovery booked → pilot started → pilot shipped.

North-star activation milestone (developer): in under 30 minutes, complete all six cockpit signals: install command copied, transport connected, first chat message sent, thread persisted, interrupt handled, generative Angular component rendered. Event-level definitions in docs/gtm/taxonomy.md. Measured via PostHog cohort Activated developers.

North-star qualified lead (enterprise): see operational definition in docs/gtm/icp.md §Enterprise track. Fired on lead_form_success; criteria are non-personal email_domain, non-empty company, and track=enterprise. Measured via PostHog cohort Qualified leads.

5. Metrics

Two scoreboards, separate. Dashboard index (PostHog ids generated by tools/posthog/sync.ts):

Slug What it measures Source spec
developer-funnel pageview → install → cockpit activation Spec 1
enterprise-funnel pageview → talk-to-engineers → lead_qualified → pilot Spec 1, 7
activation-six-signals the six cockpit signals and the 30-min funnel Spec 1, 4
content-intent docs/comparison/pillar page engagement and CTAs Spec 1, 3, 5
package-telemetry ngaf:postinstall, runtime adapters, opt-in browser Spec 1

Spec numbers refer to the workstream DAG in meta-spec §6. Not all referenced specs exist on disk yet — they get authored as each workstream is brainstormed.

Event/property/CTA-id taxonomy: docs/gtm/taxonomy.md. Weekly snapshot: docs/gtm/reports/.

6. Phases

Four phases. Each phase = one or more workstream specs. Exit gates are blocking.

Phase Goal Specs Exit gate
0 Measurement foundation analytics-foundation-1a, 1b, 1c, 1d 5 dashboards live, 3 event namespaces emitting, @threadplane/telemetry@0.0.1 published, weekly report runnable.
1 Developer clarity in 30 sec positioning-and-risks, comparison-pages, cockpit-activation-recipes New hero shipped (incl. CTA fork), 4 comparison pages live, six-signal activation funnel non-zero, ≥1 qualified lead recorded.
2 Ecosystem path (SEO + recipes) content-pillar-pages 6 pillar pages indexed, organic traffic baseline captured.
3 Community launch community-launch Launch executed, week-1 snapshot committed, post-mortem committed.
4 Enterprise design partners enterprise-pipeline 3 pilots tracked end-to-end in enterprise-funnel, ≥1 sanitized public artifact produced.

Deferred (post-Phase-4, own specs): PostHog feature flags as code, experiments as code, session replay, group analytics, Cowork plugin packaging.

7. Workstream agents

Operational progress lives in agent runs and PostHog. The repo holds durable strategy and the Cowork skill definition. This table is the static inventory — who owns what, not what's done.

Phase Workstream Subagent Spec Dashboard
0 gtm-meta cowork/gtm/SKILL.md meta —
0 analytics-foundation-1a cowork/gtm/SKILL.md spec developer-funnel (sample)
0 analytics-foundation-1b cowork/gtm/SKILL.md spec package-telemetry
0 analytics-foundation-1c cowork/gtm/SKILL.md (pending) activation-six-signals
0 analytics-foundation-1d cowork/gtm/SKILL.md (pending) enterprise-funnel
1 positioning-and-risks cowork/gtm/SKILL.md (pending) —
1 comparison-pages cowork/gtm/SKILL.md (pending) content-intent
1 cockpit-activation-recipes cowork/gtm/SKILL.md (pending) activation-six-signals
2 content-pillar-pages cowork/gtm/SKILL.md (pending) content-intent
3 community-launch cowork/gtm/SKILL.md (pending) —
4 enterprise-pipeline cowork/gtm/SKILL.md (pending) enterprise-funnel

8. Non-goals (current phase)

  • We do not compete as a general agent UI framework. We claim the Angular final mile.
  • We do not ship telemetry from @threadplane/* browser packages by default. Opt-in only. Node-side package telemetry is minimal and honors DO_NOT_TRACK, npm_config_do_not_track, and NGAF_TELEMETRY_DISABLED; see libs/telemetry/README.md for the full contract.
  • We do not run paid acquisition until Phase 2 organic baselines exist.
  • We do not pursue stars as a vanity metric.
  • We do not run A/B positioning experiments in Phase 1. Ship one hero, measure, iterate.
  • We do not instrument the smoke/demo app — it's a canonical reference, not a funnel surface.
  • We do not auto-commit weekly snapshots. A human reviews Notes before merge.
  • We do not publish the Cowork skill as a marketplace plugin in Phase 0–4. Project-local; reconsider after Phase 4.

9. Cadence

  • Weekly: /gtm Cowork skill runs the weekly snapshot procedure — npm run posthog:report, drafts a 3-bullet Notes section, opens a PR with docs/gtm/reports/<date>-weekly.md. Human reviews Notes before merge.
  • Monthly: re-read this document. Edit positioning, ICP, non-goals, or phase exit gates if reality has moved.
  • Per workstream: brainstorm → spec → plan → execute → dashboard signals verified → spec frontmatter status: done → §7 inventory updated.

10. References