Launch a Product Integration and Get the Platform to Care
Tests whether the integration solves a real shared-customer problem, writes the directory listing as a conversion surface, and plans how to earn platform attention and drive installs from your own base. Use it before or just after building an integration.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are a technology partnerships lead. Building the integration is the small part. Most integrations ship, get listed, and produce nothing, because nobody at the platform knows they exist and no customer has a reason to switch them on.
My product and the platform I am integrating with: {{product_and_platform}}
What the integration does for a shared customer: {{integration_value}}
How much is built, and what it has cost: {{build_status}}
My relationship with the platform today: {{platform_relationship}}
Who our shared customers are: {{shared_customers}}
Produce:
**Is the use case real?** State the shared customer's job in one sentence, and what they do today instead. Integrations that exist because the platform is big — rather than because a customer is doing something painful by hand — are the ones nobody installs. If {{integration_value}} does not survive this test, say so before I spend more.
**The directory listing is a landing page.** Treat the platform's app directory entry as a conversion surface, not a form: the one-line description that makes sense to someone who has never heard of me, a screenshot showing the outcome rather than a settings screen, setup time stated honestly, and the search terms people actually type inside that directory. Draft the listing copy.
**Earn the platform's attention.** Platform partner teams are measured on the retention and expansion of *their* customers. Frame my pitch in those terms and name what I bring: joint customers I can prove, a customer story with their logo on it, a segment they are trying to win, a workflow that makes their product stickier. Then list what to ask for in return, ranked by likelihood of a yes — usually directory placement, then a changelog or blog mention, then a webinar, then anything involving their sales team.
**Getting mentioned by their reps.** If the platform has a field team, the same rule applies as with any channel: they need a trigger, one sentence, and a person to call. Write those three things for their reps.
**Drive installs from my side.** Most integration adoption comes from the smaller partner's own base. Plan the in-product prompt, the lifecycle email to customers already using the platform, the help-centre article, and the onboarding step where the integration should be offered.
**Decide what success is, before launch.** Installs is a weak metric. Set targets for activated integrations, the retention difference between customers with and without it, and platform-sourced signups. Name the review date, and the condition under which I would deprecate it.