{"slug":"strategy/business-strategy/2026-07-30-1600-partnerships-gtm-brief","title":"IntegrateWise — 16:00 IST Partnerships & GTM Execution Brief","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/2026-07-30-1600-partnerships-gtm-brief.mdx","bytes":12551,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Date:** 2026-07-30  \n**Phase:** P0 Prove (technical go-live gates remain No-Go; public T1 launch remains No-Go)  \n**Status:** Seed partnerships only — no formal partner program active. GTM momentum is design-partner proof, not public launch.\n\n---\n\n## 1. Partnership Pipeline\n\n| Partner Type                                                    | Status                      | Details                                                                                                                               |\n| --------------------------------------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |\n| MuleSoft / Salesforce ecosystem architects & SIs                | **Warm relationships only** | ~5 warm contacts; founder credibility is the wedge. No formal agreements. Phase 2 gate: ≥ 10 paying customers.                        |\n| CS consultancies & fractional CS leaders                        | **Warm relationships only** | ~3 relationships; 1 joint webinar/quarter target. Certified-partner-lite planned (free internal use + referral fee), not yet papered. |\n| Execution-stack vendors (n8n, agent runtimes)                   | **Directory presence only** | Marketplace listings planned as feature-adjacent technical content; no co-sell.                                                       |\n| Regional distribution (India CA networks, UAE free zones)       | **Parked**                  | Preserved in canon ([78]); explicitly deferred until regional activation gates met. No active outreach.                               |\n| Provider marketplace apps (HubSpot, Salesforce, Slack, Zendesk) | **Prepared, not live**      | HubSpot listing prepared; AppExchange scoped (multi-month review); Slack and Zendesk planned for post-launch.                         |\n\n**Bottom line:** No partnership is in active negotiation or onboarding. The discipline is intentional: partner work is ≤ 10% of founder GTM time, and formal programs only activate after the direct wedge is repeatable. The pipeline is a relationship pipeline, not a deal pipeline.\n\n---\n\n## 2. GTM Activities\n\n### Current Motion\n\n- **Phase:** P0 Prove → design-partner proof\n- **Primary channel:** Founder-led sales and content\n- **Audience:** Executive sponsors, operational leaders, IT/security/governance, ecosystem partners\n- **Category narrative:** _The Operational Capability Platform for the AI Era_ — governed fabric connecting people, AI surfaces, systems, Workbenches, and approved outcomes\n\n### What’s Live\n\n- Marketing site CTAs migrated to marketplace activation language (`Activate IntegrateWise`, `Explore the Spine Network`) — header and hero complete\n- 64 connectors catalogued in Neon fortress; 23 connectors in marketplace index (operational: 20, cognitive: 3)\n- IW-Spine-Network packaging and manifest alignment committed (`495a02950`, `d941a422d`)\n- Infrastructure registry complete (secrets, connectors, MCP, ADK)\n- OAuth release blocker implemented (test environment enabled, production gated)\n\n### What’s Gate-Blocked\n\n- **Technical release:** No-Go until:\n  1. `@integratewise` npm org access + authenticated package publish\n  2. Warning-free Cloudflare dry-run (currently 7–8 warning groups)\n  3. Strict test/production binding isolation (test/prod resources currently overlap)\n- **Public T1 launch:** No-Go until:\n  1. Technical gates pass and stabilize\n  2. 2+ permissioned proof cases with before/after evidence\n  3. Website surfaces (Platform, Workbenches, Capabilities, Ecosystem, Developers, Pricing) reflect current scope\n  4. Claims register verified; security/compliance materials current\n- **Paid acquisition:** Explicitly off in P0/P1\n\n### Launch Run of Show (D−21 to D+30)\n\n| Window       | Deliverable                                                                                                        | Owner                    |\n| ------------ | ------------------------------------------------------------------------------------------------------------------ | ------------------------ |\n| D−21 to D−14 | Lock product proof, platform navigation, demo/recording, developer path, security materials, claims, outreach list | Founder + Platform + PMM |\n| D−7          | Publish platform/category narrative via site, founder channels, newsletter                                         | Founder + PMM            |\n| D-day        | Platform overview + product tour; route audiences to proof surfaces                                                | Founder + PMM            |\n| D+1 to D+5   | One proof asset daily (Workbench, capability, ecosystem, developer, governance, continuity)                        | Founder + PMM            |\n| D+7          | Permissioned case material + honest operating learnings post                                                       | Founder + Product        |\n| D+14         | Launch retro + next 30-day operating plan                                                                          | Founder + all owners     |\n\n---\n\n## 3. Integration Status\n\n### Connector Catalog\n\n- **64 connectors** defined in infrastructure registry (Neon fortress)\n- **23 connectors** in marketplace index.json (operational + cognitive)\n- Connector lifecycle: `available → authenticating → authenticated → binding → syncing → operational`\n- Exceptional states: `stale`, `error`, `revoked`, `expired`\n\n### Marketplace Publication Targets\n\n| Channel                      | Status                                                    | ETA                 |\n| ---------------------------- | --------------------------------------------------------- | ------------------- |\n| HubSpot App Marketplace      | Listing prepared (copy, screenshots, security docs)       | At public launch    |\n| Salesforce AppExchange       | Requirements scoped; security review is months-long       | Post-launch quarter |\n| Slack App Directory          | Planned (notification/digest surface)                     | At public launch    |\n| Zendesk Marketplace          | Planned                                                   | Post-launch quarter |\n| ChatGPT Plugin Directory     | IW-Spine-Network Plugin + MCP packages built and packaged | Gated by Bridge GA  |\n| Claude Marketplace           | MCP server URL + OAuth flow ready in packages             | Gated by Bridge GA  |\n| MCP registries / directories | IW-Spine-Network MCP (19-tool server) ready               | Gated by Bridge GA  |\n\n### Wiring & Runtime Blockers\n\n- **10 broken Cloudflare service bindings** + **1 name collision** (`integratewise-mcp-connector` declared in both `services/mcp-connector` and `packages/integratewise-mcp-tool-connector`)\n- Core cognitive/knowledge/connector chains are severed until Plane 1 is fixed\n- 115 frontend `fetch()` call sites with inconsistent API base resolution (partial-breakage risk in production)\n- 8 shared library packages are island libraries (0 external importers)\n\n---\n\n## 4. Channel Performance\n\n| Channel                | Current Traction | Notes                                                                                                                                                  |\n| ---------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| Founder-led sales      | **Pre-pipeline** | 3 pilot profiles defined (mid-market SaaS CS, founder-operator, MuleSoft/Salesforce network). Target: 2–4 discovery calls/week from content by launch. |\n| Founder-led content    | **Building**     | 4 content hours/week budget; LinkedIn 70%, newsletter 20%, events 10%. Target: 500 subs before launch.                                                 |\n| Customer proof         | **Not ready**    | 0 permissioned outcomes recorded. Requires 2+ verified cases before T1 launch gate passes.                                                             |\n| Community / newsletter | **Nurture mode** | Subscriber quality + reply/conversation rate tracked; no volume targets in P0.                                                                         |\n| Marketplace            | **Pre-listings** | HubSpot prepared; others staged. Expected pipeline contribution ≈ 5–10% by end-2027.                                                                   |\n| Partners               | **≈ 0 pipeline** | Seed relationships only. KPI is partner-sourced pipeline ≈ 0 pre-Phase 2.                                                                              |\n| Events                 | **On-hold**      | Paused until proof gate passes. Dreamforce target for Q3 2027.                                                                                         |\n| Paid acquisition       | **$0**           | Explicitly off in P0/P1. Revisit only after activation, conversion, and retention economics are evidenced.                                             |\n\n**Financial targets (from Annual GTM Plan):**\n\n- Q3 2026 exit: 2 paying customers (8 design partners live), ~$20K ARR\n- Q4 2026: 4–6 customers, ~$50K ARR, public launch\n- Q1 2027: 10–12 customers, ~$150K ARR\n- Current state: technical rollout is No-Go, so 0 paying / 0 design-partner proof cases as of this brief\n\n---\n\n## 5. Next Steps\n\n### Immediate (Next 48–72 Hours)\n\n1. **Fix Cloudflare service-binding names** + resolve `integratewise-mcp-connector` collision — this unblocks the entire cognitive/knowledge/connector mesh.\n2. **Achieve warning-free test dry-run** and provision isolated test D1/KV/Queue/R2/Vectorize/DO resources.\n3. **Authenticate to `@integratewise` npm org** and run guarded publish workflow on the release commit.\n4. **Run the 4-step TruthLayer verification** (D1 buffer → Triage Bot → Human Approval → Entity 360 → Twin reads verified memory).\n5. **Audit connector count** — how many pass the 4-point production test (OAuth, creamy load, field mapping, delta sync)?\n6. **Decide Entity 360 demo format** — recommend static JSON (Option A) for launch to avoid live API instability on marketing site.\n\n### This Week\n\n7. **Book 3 pilot conversations** within 7 days of site going live:\n   - Mid-market SaaS CS team (HubSpot + Zendesk + Stripe stack)\n   - Founder/operator in personal network (run-your-business demo)\n   - MuleSoft/Salesforce ecosystem contact (integration-landscape angle)\n8. **Complete marketing CTA migration** — update `contact`, `why`, `product`, `business-ops`, `account-success`, `personal-ops`, `pricing`, `services`, `security`, `solutions/*` pages from “Get started” → “Activate IntegrateWise”.\n9. **Finalize demo/recording** showing a governed path (context → capability → human-approved receipt) + fail-closed refusal.\n\n### This Sprint\n\n10. **Deploy to test** in canonical order (pipeline → connector → mcp-connector → connector-sync → knowledge → continuity → intelligence → workflow → l2 → gateway), validate governed-action acceptance scenarios, and submit production evidence for founder approval.\n11. **Build Platform, Workbenches, Capabilities, Ecosystem, Developers, Resources, Pricing/activation surfaces** and reconcile every public claim with the claims register.\n12. **Publish HubSpot listing** at launch; Slack directory at launch; AppExchange and Zendesk post-launch.\n13. **Start/continue guided ecosystem activations** — do not schedule public T1 launch until the proof gate is complete.\n\n### Partnership-Specific (Seed Mode)\n\n14. **Maintain warm relationships** — send 1 thoughtful touchpoint/week to the 5 SI/architect contacts and 3 CS consultancy contacts. No formal program paper until ≥ 10 paying customers.\n15. **Co-author 1 piece** with a MuleSoft/Salesforce architect on _“integration health IS account health”_ — positions IntegrateWise as what SIs recommend after the integration project.\n16. **Partner KPI discipline:** track partner-sourced pipeline from now (expected ≈ 0); formal program activates only after 2 organic wins from a partner type.\n\n---\n\n_Sources: GO_LIVE_AND_GTM_PLAN.md, 48-partner-strategy.md, 49-marketplace-strategy.md, WIRING_INTEGRATION_MAP.md, ACTION_PLAN.md, annual-gtm-plan.md, LAUNCH_PHASE_ADDENDUM.md, founder-led-marketing.md, 12-connectors-integration-manager-and-spine-network.md, marketplace/index.json._\n"}