All 12 systems · System 10
Partnership integration
Partnership integration embeds a product in a workflow and ecosystem customers already use, borrowing trusted distribution while making both products more valuable together. It fits products with a complementary job, meaningful shared customers, and an integration deep enough to produce an outcome—not merely exchange data or logos.
Causal engine
Identify a repeated handoff between two products → build an integration that removes the handoff cost → activate shared customers on one high-value workflow → document measurable joint outcomes → earn marketplace placement, partner enablement, and co-selling → shared adoption produces references and demand that justify deeper integration.
Preconditions
- A meaningful segment of target customers already uses the partner product
- The combined workflow solves a recurring job better than either product alone
- The partner has an accessible technical surface and a real discovery, sales, or success channel
- Ownership exists for integration reliability, support routing, and shared activation metrics
Anti-patterns
- Launching a connector because the partner logo looks credible while customer demand is absent
- Building dozens of shallow integrations that transfer data but do not complete a job
- Assuming marketplace listing automatically creates distribution without partner enablement
- Ignoring broken authentication, sync failures, and ambiguous support ownership after launch
Solo-founder translation
Choose the integration mentioned most often in customer conversations and recruit five shared users into a weekly design-partner call. Ship one end-to-end workflow, manually monitor every connection, and give the partner a demo, customer proof, and co-marketing asset they can actually distribute. Measure connection completion, first integrated outcome, weekly active integrations, support failures, partner-sourced pipeline, and activation from each partner surface.
Joint-workflow integration page
Joint-workflow integration page
Hero
Connect {{partner_name}} to {{product_name}} in five minutes. When {{trigger_event}} occurs, the integration {{automated_action}} and records {{audit_result}}.
Primary CTA: **Connect {{partner_name}}** Secondary CTA: **Watch the 90-second workflow**
The complete job
Proof
Setup
State sync frequency, supported plans, data retention, failure alerts, and how to disconnect.
Fit and limits
Support and ownership
Launch scorecard
View raw markdown
# Joint-workflow integration page
## Hero
**Turn approved {{partner_artifact}} into {{product_outcome}} without copying data.**
Connect {{partner_name}} to {{product_name}} in five minutes. When {{trigger_event}} occurs, the integration {{automated_action}} and records {{audit_result}}.
Primary CTA: **Connect {{partner_name}}**
Secondary CTA: **Watch the 90-second workflow**
## The complete job
1. A team completes {{upstream_job}} in {{partner_name}}.
2. The integration transfers {{specific_fields}} after {{permission_or_approval}}.
3. {{product_name}} performs {{downstream_job}}.
4. The result and status return to {{partner_name}}, so the team does not chase updates.
## Proof
Show an annotated screenshot of the trigger, transformed data, and completed result. Add one customer result with baseline and period: **Acme cut weekly handoff time from 95 minutes to 12 minutes across 40 records.**
## Setup
1. Authenticate with an admin account using least-privilege permissions.
2. Select the source workspace and destination project.
3. Map the three required fields; test with one record before enabling automation.
State sync frequency, supported plans, data retention, failure alerts, and how to disconnect.
## Fit and limits
Use this integration if {{qualifying_condition}}. It does not yet support {{known_limit}}; use {{documented_workaround}} for that case.
## Support and ownership
For connection or authentication issues, contact {{owner_one}}. For workflow results, contact {{owner_two}}. Include links to status, setup documentation, and the shared troubleshooting guide.
## Launch scorecard
Track page visit → connection start → successful authentication → first completed workflow → active at day 30. Report partner-sourced qualified pipeline separately from existing customers who merely enabled the integration.Companies on this system
- Amazon — Make the wedge legible
- Anthropic — Make the wedge legible
- Brex — Make the wedge legible
- Grab — Make the wedge legible
- Instacart — Make the wedge legible
- PhonePe — Make the wedge legible
- Plaid — Make the wedge legible
- Shopify — Make the wedge legible
- Snowflake — Make the wedge legible
- Square — Make the wedge legible
- Vercel — Make the wedge legible