Partnership & acquisition thesis

Partnership thesis

Last updated 5/24/2026

Partnership Thesis

Why Partner

Colony is the command interface for the ZoomProp GTM Agentic Stack — a unified CRM-plus-agent-control-plane that replaces the patchwork of point solutions (CRM, sequencer, call recorder, content scheduler, onboarding tracker) that sales teams currently operate. Its value to a partner lies in three structural facts derived directly from the codebase:

Deep, bi-directional integration surface. Colony already maintains a KMS-encrypted per-org vault (api_keys table, referenced in docs/phase1/action_plans/03_api_keys_and_integrations_vault.md) that stores partner credentials. Every org that adopts Colony becomes an addressable integration endpoint for the partners whose systems are already wired in: Pipedrive (CRM sync, action plan 06_pipedrive_integration.md, bi-sync tested in docs/phase2/testing/02_e2e_pipedrive_scraper.spec.ts), Unipile (LinkedIn + email outreach, docs/phase1/action_plans/07_unipile_integration.md), Resend (transactional email delivery, docs/phase1/action_plans/08_resend_integration.md), Google Workspace (Drive for Gemini Meet Notes ingestion, Gmail, Calendar — docs/phase2/action_plans/13_gmail_integration.md, 14_calendar_integration.md), and Notion (Knowledge Core sync, docs/phase2/action_plans/15_notion_kc_sync.md).
Durable orchestration creates stickiness that benefits platform partners. Colony's agent runtime runs on Inngest durable functions (architecture diagram in README.md), meaning every prospect discovery → qualification → message-generation loop is event-sourced and observable via Langfuse. Partners who provide data (SerpAPI, Google Places) or communications infrastructure (Unipile, Resend) receive durable, high-volume, structured API calls — not ad-hoc one-off queries.
The Deployment Kit creates a repeatable co-sell motion. On every Closed-Won deal, Colony's onboarding agent auto-generates an 8-asset Deployment Kit (docs/phase1/action_plans/26_deployment_kit.md) that includes a KPI dashboard, rollout calendar, and stakeholder map. Any partner whose product is referenced in that kit gains recurring, account-level visibility at the moment of maximum customer engagement.

Partner Profiles

Partner Type	Shared Incentive	Integration Surface	Risk
CRM Platform — Pipedrive	Colony drives deal-stage progression and enriches Pipedrive records with ICP scores, custom fields defined in `docs/phase1/runbooks/pipedrive-fields.md`; more active records = higher Pipedrive seat value	Bi-directional sync tested in `docs/phase2/testing/02_e2e_pipedrive_scraper.spec.ts`; LeadBooster scraper in `docs/phase2/action_plans/02_pipedrive_leadbooster_scraper.md`; colony writes to Pipedrive pipeline stages via the `api_keys` vault	Pipedrive API rate limits trigger per-org circuit breakers (`docs/phase1/action_plans/22_circuit_breakers.md`); API schema changes break field mapping defined in `docs/phase1/runbooks/pipedrive-fields.md`
Communications Infrastructure — Unipile	Colony's 5-angle outbound sequences (signal-, pain-, referral-, pattern-break-, insight-led) and T1–T5 cadences generate sustained, high-volume LinkedIn + email send volume through Unipile	Unipile search extension (`docs/phase2/action_plans/06_unipile_search_extension.md`), multi-channel sequence engine (`docs/phase2/action_plans/23_multi_channel_sequence_engine.md`), HOT reply queue; per-org credentials in `api_keys`; setup documented in `docs/phase1/runbooks/unipile-setup.md`	Deliverability risk is shared — Colony implements sender mailbox rotation (`docs/phase2/action_plans/25_sender_mailbox_rotation.md`) and email warmup (`docs/phase2/action_plans/19_email_deliverability_and_warmup.md`) to protect Unipile reputation
Data / Enrichment — SerpAPI + Google Places	Colony's prospect agent queries both to resolve firmographic signals; higher Colony adoption = higher API call volume for these providers	SerpAPI integration in `docs/phase2/action_plans/04_serpapi_integration.md`, tested in `docs/phase2/testing/04_e2e_serpapi.spec.ts`; Google Places in `docs/phase2/action_plans/03_google_places_integration.md`, tested in `docs/phase2/testing/03_e2e_google_places.spec.ts`; both called from the discovery orchestrator (`docs/phase2/action_plans/10_discovery_orchestrator.md`)	Volume-based cost exposure for Colony's customers if match quality is low; mitigated by the anti-ICP hard pre-filter (`docs/phase2/action_plans/16_anti_icp_hard_prefilter.md`) and matching algorithm (`docs/phase2/action_plans/08_matching_algorithm.md`)
Google Workspace (Strategic Platform)	Colony ingests Gemini Meet Notes from Google Drive, syncs Gmail and Calendar, and pushes notifications to Google Chat (`docs/phase2/action_plans/20_google_chat_push.md`); Colony makes Workspace the operational backbone of a sales team	Google Drive ingestion for recording intelligence (`docs/phase1/action_plans/09_google_drive_integration.md`); OAuth scope expansion in `docs/phase2/action_plans/12_google_oauth_scope_expansion.md`; GCS bucket `gs://colony-assets` provisioned via `infrastructure/gcp/storage.tf`; entire platform deployed on Cloud Run + Cloud SQL (`infrastructure/gcp/cloud-run-runner.tf`, `infrastructure/gcp/cloud-sql.tf`)	Google OAuth scope approval process for Gmail/Calendar is a launch-gate risk; partially mitigated by `docs/phase2/runbooks/02_workspace_manual_steps.md`
Knowledge Management — Notion	Colony's Knowledge Core (10-domain pgvector store) can surface and sync content to/from Notion workspaces, making Colony the AI layer on top of existing Notion documentation	Notion KC sync in `docs/phase2/action_plans/15_notion_kc_sync.md`, tested in `docs/phase2/testing/15_notion_kc_sync.spec.ts`; fixture data in `docs/phase2/testing/fixtures/notion-blocks.ts`	Notion block schema changes break the sync adapter; content duplication risk if bidirectional sync is not idempotent
Observability / LLM Monitoring — Langfuse	Colony streams every agent tool call through Langfuse; Langfuse gains a high-value reference customer demonstrating multi-agent, multi-turn observability at production scale	Platform-level credentials stored in GCP Secret Manager (`infrastructure/gcp/secrets.tf`); LLM client and observability setup in `docs/phase1/action_plans/05_llm_clients_and_observability.md`	Vendor concentration risk if Langfuse pricing changes; mitigated by the fact that Sentry is a parallel observability layer already wired in

Mutual Value

BR-001 / Pipedrive: Colony's ICP-scoring and 9-stage pipeline management actively increases the number of deals progressing through Pipedrive, improving Pipedrive's core engagement metric (deal velocity) while giving ZoomProp a CRM that reflects agent-generated intelligence rather than manual data entry.
BR-002 / Unipile: Colony's T1–T5 sequences, HOT reply queue, and multi-channel engine (docs/phase2/action_plans/23_multi_channel_sequence_engine.md) create consistent, high-quality send volume that validates Unipile's LinkedIn + email infrastructure at scale, while Colony customers gain deliverability infrastructure they would otherwise have to build themselves.
BR-003 / Google Workspace: Colony transforms Workspace from a passive document store into an active GTM intelligence layer — Meet recordings become CRM signals, Drive becomes the knowledge corpus for pgvector retrieval, and Cloud infrastructure (infrastructure/gcp/) underpins the entire deployment — making Google the preferred enterprise deployment target for Colony.
BR-004 / Langfuse: Colony's multi-agent streaming architecture (GTM Orchestrator → Campaign Orchestrator → 8 specialists) generates rich, structured LLM traces that Langfuse can use as a public reference case for multi-agent observability, while Colony teams gain the cost-attribution and prompt-quality tooling defined in docs/phase1/action_plans/05_llm_clients_and_observability.md.
BR-005 / SerpAPI + Google Places: The discovery orchestrator (docs/phase2/action_plans/10_discovery_orchestrator.md) consolidates what would otherwise be fragmented ad-hoc enrichment calls into a structured, auditable pipeline — giving data partners predictable, high-quality traffic and giving Colony customers enriched prospect records with a documented matching algorithm (docs/phase2/action_plans/08_matching_algorithm.md).

First Partnership Motion

Run a Pipedrive co-sell pilot with one shared enterprise prospect over 30 days.

The minimum viable experiment requires no new code: Colony's Pipedrive integration is already production-ready (docs/phase1/action_plans/06_pipedrive_integration.md, bi-sync tested in docs/phase2/testing/02_e2e_pipedrive_scraper.spec.ts, custom fields documented in docs/phase1/runbooks/pipedrive-fields.md). The motion is:

Week 1 — Credential provisioning. A joint prospect connects their Pipedrive API key into Colony's per-org vault (api_keys table). Colony's Playwright-based LeadBooster scraper (docs/phase2/action_plans/02_pipedrive_leadbooster_scraper.md) runs against their existing deal data; the discovery orchestrator (docs/phase2/action_plans/10_discovery_orchestrator.md) surfaces 20 net-new ICP-matched prospects via SerpAPI + Google Places enrichment.
Week 2–3 — Sequence execution. The GTM Orchestrator drafts T1–T3 outbound messages for approved candidates (approval queue documented in docs/phase2/action_plans/09_candidate_approval_queue.md). Colony writes deal records back to Pipedrive as contacts progress; the anti-ICP pre-filter (docs/phase2/action_plans/16_anti_icp_hard_prefilter.md) prevents noise from polluting the CRM.
Week 4 — Deployment Kit delivery. On any Closed-Won deal, Colony's onboarding agent auto-generates the 8-asset kit (docs/phase1/action_plans/26_deployment_kit.md) referencing Pipedrive as the system of record. The KPI-XXX dashboard included in the kit becomes the joint success artifact shared with the Pipedrive partner team.

Success criteria (KPI-001): ≥15 net-new Pipedrive contacts created by Colony agents with ICP score ≥ 70 (matching algorithm, docs/phase2/action_plans/08_matching_algorithm.md), and ≥1 deal progressed to Stage 5+ in the 9-stage pipeline within the 30-day window. This is measurable entirely within existing Colony analytics infrastructure (docs/phase1/action_plans/18_analytics_agent.md) and the daily brief (docs/phase1/action_plans/23_daily_briefs.md) without requiring any new instrumentation.