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