48 — Partner Strategy
Status: CANONICAL · Commercial OS
Owner: Founder
Last verified: 2026-07-21
Purpose
Which 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.
Target audience: Founder; future partnerships hire; investors (channel narrative).
1. Partner Thesis & Sequencing
| Phase | Gate | Partner focus |
|---|---|---|
| Now (pre-repeatable) | — | Seed only: relationships, one lighthouse services partner, marketplace listings prep (49) |
| Phase 2 (post 10 paying customers) | Direct motion repeatable (36 §4) | Activate MuleSoft/Salesforce ecosystem channel + CS consultancies |
| Phase 3 (post Series A) | Partner-sourced ≥ 2 wins organically | Formal program: tiers, enablement, margins; regional partners for 78 International |
2. The Four Partner Types (in priority order)
P1 — MuleSoft / Salesforce Ecosystem (the unfair advantage)
Why: founder's home turf — architect + CSM credibility, existing network, Dreamforce presence (63). SIs and architects in this ecosystem are our ICP's trusted advisors, and they live the integration-without-context pain professionally.
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.
Economics (Phase 2): referral 15% year-1 ARR · resell later, only with proven co-delivery.
Now: 5 architect/SI relationships warm; 1 co-authored piece ("integration health IS account health"); no formal program paper yet.
P2 — CS Consultancies & Fractional CS Leaders
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.
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).
Now: 3 relationships; 1 joint webinar per quarter target.
P3 — Execution-Stack Vendors (automation/agent runtimes)
Why: the handoff architecture makes n8n/Zapier/agent-runtime users natural adjacencies — we're the governed judgment in front of their hands (26). Their communities contain ops-minded buyers who already believe in tooling.
The play: technical integration content ("governed handoff to [X]") + directory/marketplace listings + community presence. Never co-sell dependence — they're feature-adjacent, not channel.
P4 — Regional Distribution (deferred with 78)
CA 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.
3. Partner Discipline (the anti-distraction rules)
- 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.
- No partner-led product commitments. Partner feature requests enter the same roadmap triage as everything else (69); no bespoke builds for a promised channel.
- 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.
- Partner-sourced deals run our methodology (36) — same qualification, same POV, same paper. A partner intro is a warmer S0, not a different sales process.
- 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.
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.
Related: 49 Marketplace · 50 GTM Strategy · 63 Events · 78 International