{"slug":"strategy/business-strategy/48-partner-strategy","title":"48 — Partner Strategy","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/48-partner-strategy.mdx","bytes":5621,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Founder\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nWhich partnerships matter, in what order, and the discipline that keeps partnerships from becoming a distraction. Stage truth: partnerships amplify a working motion; they never substitute for one. Until the direct wedge is repeatable, partner work is _seeding_, not _scaling_.\n\n**Target audience:** Founder; future partnerships hire; investors (channel narrative).\n\n---\n\n## 1. Partner Thesis & Sequencing\n\n| Phase                                  | Gate                                                                    | Partner focus                                                                                                                        |\n| -------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |\n| **Now (pre-repeatable)**               | —                                                                       | Seed only: relationships, one lighthouse services partner, marketplace listings prep ([49](49-marketplace-strategy.md))              |\n| **Phase 2 (post 10 paying customers)** | Direct motion repeatable ([36 §4](../07-sales/36-sales-methodology.md)) | Activate MuleSoft/Salesforce ecosystem channel + CS consultancies                                                                    |\n| **Phase 3 (post Series A)**            | Partner-sourced ≥ 2 wins organically                                    | Formal program: tiers, enablement, margins; regional partners for [78 International](../13-operations/78-international-expansion.md) |\n\n## 2. The Four Partner Types (in priority order)\n\n### P1 — MuleSoft / Salesforce Ecosystem (the unfair advantage)\n\n**Why:** founder's home turf — architect + CSM credibility, existing network, Dreamforce presence ([63](../11-marketing/63-events-strategy.md)). SIs and architects in this ecosystem _are_ our ICP's trusted advisors, and they live the integration-without-context pain professionally.\n**The play:** position IntegrateWise as what SIs recommend _after_ the integration project — \"you connected the systems; now connect the context.\" ArchitectIQ angle (integration-landscape intelligence) gives them a diagnostic tool that opens their own client conversations.\n**Economics (Phase 2):** referral 15% year-1 ARR · resell later, only with proven co-delivery.\n**Now:** 5 architect/SI relationships warm; 1 co-authored piece (\"integration health IS account health\"); no formal program paper yet.\n\n### P2 — CS Consultancies & Fractional CS Leaders\n\n**Why:** they design CS processes for exactly our ICP; a consultant recommendation converts at champion-strength. Our product makes _their_ deliverable (a working CS operating model) demonstrably better.\n**The play:** certified-partner-lite — free internal use (their own client books run on us: Customer-Zero-by-proxy) + referral fee + co-marketing (webinars [61](../11-marketing/61-webinar-strategy.md)).\n**Now:** 3 relationships; 1 joint webinar per quarter target.\n\n### P3 — Execution-Stack Vendors (automation/agent runtimes)\n\n**Why:** the handoff architecture makes n8n/Zapier/agent-runtime users natural adjacencies — we're the governed judgment in front of their hands ([26](../04-product-marketing/26-capability-fabric-story.md)). Their communities contain ops-minded buyers who already believe in tooling.\n**The play:** technical integration content (\"governed handoff to [X]\") + directory/marketplace listings + community presence. Never co-sell dependence — they're feature-adjacent, not channel.\n\n### P4 — Regional Distribution (deferred with [78](../13-operations/78-international-expansion.md))\n\nCA networks (India) and free-zone authorities/coworking ecosystems (UAE) — the canon's multi-market channels, preserved and explicitly parked until regional activation gates are met. No investment now beyond keeping the relationships alive.\n\n## 3. Partner Discipline (the anti-distraction rules)\n\n1. **Partner time-box (pre-Phase 2): ≤ 10% of founder GTM time.** Every partner hour is a direct-selling hour spent; the wedge pays for everything.\n2. **No partner-led product commitments.** Partner feature requests enter the same roadmap triage as everything else ([69](../12-corporate/69-product-roadmap-story.md)); no bespoke builds for a promised channel.\n3. **Prove-then-program:** a partner type gets formal paper (agreements, margins, portal) only after 2 organic wins from that type. Programs formalize what's working; they don't conjure it.\n4. **Partner-sourced deals run our methodology** ([36](../07-sales/36-sales-methodology.md)) — same qualification, same POV, same paper. A partner intro is a warmer S0, not a different sales process.\n5. **Channel conflict pre-empted:** direct-named accounts list maintained from Phase 2; referral registration first-in-first-credited; disputes resolved for the customer's experience, always.\n\n**KPIs:** Phase-gates hit before program spend · partner-sourced pipeline (tracked from now, expected ≈ 0 pre-Phase 2 — honesty in the dashboard) · Phase 2: partner-sourced ≥ 15% of pipeline; partner deal win-rate ≥ direct (quality bar); time-box compliance.\n\n---\n\n**Related:** [49 Marketplace](49-marketplace-strategy.md) · [50 GTM Strategy](50-gtm-strategy.md) · [63 Events](../11-marketing/63-events-strategy.md) · [78 International](../13-operations/78-international-expansion.md)\n"}