Partnership best practices
How to run partnerships so they produce installs rather than calls.
Pick partners by adjacency, not by size
The partner worth having solves the problem your merchants hit immediately before or after yours. A big app in an unrelated category sends traffic that does not convert; a small one adjacent to your workflow sends traffic that does. Use the Directory to find them, and publish your own profile so they can find you.
Make the first ask small
Open with something that costs the partner nothing to say yes to — a docs cross-link, a mention in an onboarding email, a shared help-centre article. Bundles and revenue share are a second conversation, not a first one. Track the ask as an activity so it does not get lost in a DM thread.
Put a date on everything
Every activity in CoreX carries a deadline, and partnerships:remind-deadlines
raises a reminder before it lapses. Partnerships die from drift far more often
than from disagreement — a dated commitment on both sides is the single highest
-leverage habit here.
Agree what "done" looks like before you start
Write the deliverable into the activity: "blog post live on their site, linking to our listing" beats "co-marketing". When the partner marks their side delivered, the activity records it, so the state of the relationship is a fact rather than a recollection.
Measure the channel, not the relationship
Give each partner a distinct referral link through Affiliates and read installs and revenue per link. A warm partnership producing nothing should be demoted without hard feelings; a quiet one producing installs should get more of your time.
Renew or retire on a cadence
Review the partner list quarterly. Keep the ones with attributable installs, re-scope the ones that stalled, and close the rest. A directory full of dormant partnerships makes the live ones harder to see.