GTM / HubSpot engineering backlog — Robert asks (Platform + Sales)
Status: Planned (prioritization draft)
Last updated: 2026-04-09
Sources: ai-team Slack threads (outbound ask, HeyReach → Supabase), Linear Platform + Sales queries.
Executive summary
Robert is pushing on three clusters: (1) mixed email + call outbound at volume from Cursor, grounded in HubSpot; (2) LinkedIn / HeyReach conversation data landed somewhere durable for training and analytics; (3) reliable HubSpot-in-Cursor (MCP) and CRM completeness (activities, LI messages, backfills). Platform already has PLT-1273 for the orchestrator extension; a follow-up Platform ticket for HeyReach JSON ingest is still needed. Sales SAL-1001 and Outbound campaign tickets should stay aligned on properties and naming.
1. Slack threads (canonical context)
1.1 Outbound orchestrator — email + calls
- Ask: Extend
tools/hubspot-api-serviceafter the first cut (PR #718) perknowledge/sales/gtm/outbound-email-call-mix-spec.md: parallel cohorts (e.g. signal-triggered vs call-heavy), email A/B, dialer handoff + dispositions, reporting by cohort × step × variant × channel, idempotency, CRM as system of record. - Linear: PLT-1273 — Extend outbound orchestrator for email and call cohorts (Triage at time of writing).
1.2 HeyReach / LinkedIn JSON → Supabase
- Ask: Land HeyReach MCP export JSON for training better responses; Supabase creds Robert tried looked old (May).
- Direction from thread: Add Robert to Supabase; store on internal AI Core in a new table; confirm format (JSON) and volume; Sam offered to load if easy to share.
- Gap: Capture as a Platform issue (schema + ingest + access doc), not only Slack.
2. Related ai-team themes (backlog context)
- HubSpot deal nudges — Stuck-deal follow-up to EA/Slack (PR #153); filtering refined to deal stages starting with To Do: or In Progress:; notifications toward sales-notifications; Railway weekday cron discussed; HubSpot custom fields for touch tracking.
- HubSpot MCP in Cursor — OAuth /
mcp-remote/ timeouts; team guidance on HubSpot MCP auth app and PAT vs MCP reads/writes. - GTM runner pattern — Prefer Linear as queue for cloud agents; avoid huge parallel fan-out; ~30 min run expectation; prove flows locally first (per Uttam in thread).
3. Platform Linear — prioritized for Robert / GTM engineering
| Tier | Issue | Notes |
|---|---|---|
| P0 | PLT-1273 | Outbound orchestrator email + calls |
| P0 | New: HeyReach / LI JSON ingest | Table + load path on internal-ai-core; link from this plan when filed |
| P1 | PLT-1200 / PLT-1264 | Global search + full HubSpot deal index |
| P1 | PLT-256 | Chat with CRM (HubSpot) demo |
| P1 | PLT-287 | Backfill emails + Zoom → HubSpot |
| P1 | PLT-438 | LinkedIn messages → HubSpot |
| P2 | PLT-778 | File-gated emails in Supabase → HubSpot (Ryan) |
| P2 | PLT-735 | Slack sales updates → HubSpot |
| P2 | PLT-501 | Deals dashboard HubSpot + Supabase |
| P2 | PLT-898 | HubSpot SOW/budget → Snowflake |
| P2 | PLT-97 | Legacy followup-sales bot — reconcile vs HubSpot nudge stack |
4. Sales Linear — AI / outbound alignment
| Issue | Notes |
|---|---|
| SAL-1001 | MQL lead qualification with AI team (explicit bridge) |
| SAL-980–SAL-985, SAL-981 | Gov Outbound campaign — AI/Codex/human steps |
| SAL-723 | dbt lead list — escalated / needs SME |
5. Suggested execution phases
Phase 0 — Unblock (this week)
- Groom PLT-1273: owner; split into integration map + vendor choices + reference campaign; MVP orchestrator; HubSpot tasks + email provider + dialer spikes.
- File Platform ticket for HeyReach JSON: contract, volume, RLS/table design, ingest path.
- Short internal note on HubSpot MCP + Cursor (supported config, OAuth app, PAT scope) to reduce repeat threads.
Phase 1 — CRM completeness (enables reporting + automation)
- Sequence PLT-287, PLT-438, PLT-778, PLT-735 as bandwidth allows.
- Advance PLT-1200 / PLT-1264 for search and operational visibility.
Phase 2 — Product + deduplication
- Land PLT-256 for sales-facing CRM chat demo.
- Merge or retire PLT-97 vs live HubSpot nudge work.
Cross-team
- Align SAL-1001 with PLT-1273 on HubSpot properties and naming.
- Run Outbound campaign tickets through Linear-first runner discipline.
6. References
knowledge/sales/gtm/outbound-email-call-mix-spec.mdknowledge/sales/gtm/outbound-subagent-architecture.mdtools/hubspot-api-serviceREADME
This document is a prioritization draft for internal planning; ticket states in Linear may change.