Co-Marketing With Integration Partners That Serves Users
Partnerships · 10 min read ·
Joint announcements work when they help users do something new. How to plan, write and measure co-marketing with integration partners.
Joint announcements have a poor reputation. Two companies publish matching posts that say they are excited to partner, include two logos and a quotation from each chief executive and tell readers nothing they can use. The users who read them wonder what has changed for them. The honest answer is often: nothing yet.
Co-marketing is better when it starts from the user. If two products connect in a way that lets someone do something they could not do before, then a joint guide, a joint demonstration or a joint announcement is a service. It tells people about a capability and shows them how to use it. This guide covers how to plan and run that kind of co-marketing with integration partners, honestly and at small scale.
What it is
A strategic alliance is an arrangement between companies to pursue shared goals while remaining independent. Co-marketing is one way such alliances show up in public: shared guides, joint webinars, cross-listing, mutual mentions, joint case notes.
For small products, co-marketing is attractive because it shares costs and reach. Each partner brings a different audience that already trusts them, and word of mouth passes more readily when it comes from a source that people know. But it needs real substance to work. Without a working integration and a clear benefit, it is just noise.
Start with the user's gain
Before planning anything, write down the user's gain in one sentence.
- "Now you can send each approved invoice to your accounting tool without retyping it."
- "Now meeting notes arrive in your task manager as tasks with owners."
If you cannot write it, wait. If you can, everything else follows. The sentence becomes the headline, the opening of the guide and the test of every piece of content: does it help the reader do this?
Make sure it works first
Co-marketing amplifies whatever is there. If the integration is flaky, the amplification is of the flakiness.
- Test the integration end to end, with real accounts on both sides, including a newcomer to both products.
- Document the setup, with screenshots, and have someone outside the team follow it.
- Agree how to handle problems: a shared contact, response times and who users should ask.
- Check limits and costs: which plans, permissions and fees apply, so that you can say so honestly.
- Confirm that both sides are happy with the facts. An integration page should be consistent in both partners' words.
Launch only when both sides are confident that a user can succeed.
Agree on goals and roles
A short written plan prevents misunderstanding.
Goals. What do you each want: new users, activations, awareness among a specific group? Be realistic and specific. "Fifty set-ups in the first month" is better than "lots of exposure".
Audience. Who is it for? Be precise about the user group.
Assets. What will be made: a guide, a short video, a landing page, a changelog entry, a social post, an email.
Roles. Who builds, writes, reviews, publishes and answers questions. Who holds the final version of each asset.
Timing. Dates for review and for publication, with allowance for delay.
Rules. How each company's name and logo will be used, who approves wording and how corrections are made.
Data. What information is shared, if any, such as the number of users who connected. Be careful about customer data, and follow privacy law: do not share personal data without a lawful basis and clear user consent.
Costs. Who pays for what, if anything.
One page is enough.
What to make
Several forms of content work well, in rough order of usefulness.
A joint setup guide. A step-by-step walkthrough, with screenshots, hosted on each partner's site or on one and linked from the other. The most useful piece, because it helps people succeed.
A short demonstration. A video or animated walkthrough of the connection in use, with captions and a transcript.
An integration page on each site, consistent in facts, linking to the other.
A worked example. A realistic scenario, "how a small agency saves two hours a week", based on actual use, with permission.
A joint announcement. A short post that states the user's gain, links to the guide and says who it is for. Not a press release.
A joint session. A short live walkthrough with questions, if both audiences would enjoy it.
A mention in your changelog and your updates to users.
Avoid padding. Each piece should help someone do something.
Writing it well
A few principles keep joint content honest and useful.
- Lead with the user's gain, not the partnership.
- Use plain words. "Connect" is clearer than "synergise".
- Say what it does and does not do. Limits are part of honesty.
- Name each company accurately, and avoid implying more than exists: an integration is not an endorsement or a merger.
- Write for each audience separately. Partner A's readers know Partner A well and Partner B not at all, and vice versa. Introduce the other gently.
- Provide a clear first step, a link to the guide or the setup page.
- Keep it short. A short post and a thorough guide beat a long post.
- Make it accessible: descriptive headings, text alternatives for images, captions for video and sufficient contrast, following accessibility guidelines.
- Disclose commercial arrangements, such as paid referrals, where required.
Where to share it
Use each partner's own channels, and the ones where the shared audience gathers.
- Your site and email to existing users.
- Your partner's site and email, if they agree.
- Communities around both products, following their rules.
- Directories and stores: update both listings to mention the connection, and list in the right categories.
- Newsletters and sites that cover the area.
- Social channels, where people actually look.
Word of mouth, the informal sharing of recommendations among people, is the aim. The most effective sharing is by satisfied users, so make it easy for them: a short, clear description they can pass on.
Timing and cadence
Do not make a single splash and vanish.
- A soft start: release the integration, test with a small group and fix problems.
- The announcement: publish together on an agreed day.
- The follow-up: a week later, share a tip or a user's story.
- A month on: a short review and perhaps a deeper guide.
- Ongoing: keep the guide current, and mention the integration in relevant content.
Spacing out the effort makes use of the same work more than once and avoids overwhelming support.
Measuring
Decide how to measure before you publish.
- Tag links with a source label for each channel and partner.
- Count visits to the guide and the integration pages.
- Track set-ups: how many people connect.
- Look at activation and retention for those users compared with others.
- Note support questions, their number and themes.
- Collect comments, where public.
- Share the results with your partner, openly.
Use what you learn to improve the guide and decide whether to continue, deepen or stop.
Common mistakes
- Announcing before it works.
- Focusing on the partnership rather than the user.
- No clear first step.
- Inconsistent facts across the partners' pages.
- Overclaiming, such as "official partner" when there is none.
- One-sided effort, with one company doing all the work.
- Ignoring support, so users hit problems and nobody owns the answer.
- No measurement, so nothing is learned.
- Vanishing after launch.
A worked example
A small meeting-notes tool and a task-management app have built an integration that turns action items into tasks. The two founders agree on the user's gain: "Action items from your meeting notes land in your task list, with owners and due dates, in one click."
They test with eight shared users and fix two problems. They write a one-page plan: goal of fifty set-ups in the first month, roles, a publication date and a simple rule that each approves the other's description. They produce a three-minute captioned demonstration, a setup guide with screenshots and a short post for each site, each written for its own audience.
They update their directory listings, adding the connection to each description. They publish on a Tuesday morning, and each emails its users with a short note. A week later, each posts a user's story, with permission.
In the first month, the guide receives 1,100 visits. Seventy-four people set up the connection, and nearly two-thirds are still using it after a month, a higher rate than average for either product. Support gets eleven questions, mostly about permissions, so the teams add a line to the guide. They share the numbers with each other, agree that it worked and plan a second guide for a more advanced use. No quotations from chief executives were needed.
Questions makers ask
Is it all right to co-market if the partner is much bigger? Yes, but expect them to move slowly. Provide ready-made assets, and respect their rules.
Should we both link to each other? Usually, since it helps readers. Make sure links are accurate.
What if the integration is rough? Fix it first, or label it beta and be honest.
Do we need a contract? A short written agreement is wise, especially for data, branding and exit.
Summary
Good co-marketing begins with a sentence about what users can now do, backed by an integration that works. Agree on goals, audience, assets, roles, timing, naming and data in one page, then make a setup guide, a short demonstration, consistent integration pages and a brief joint post. Write for each audience in plain words, state limits, disclose commercial arrangements and make it accessible. Share through each partner's channels and the communities in between, follow up after launch and measure with tagged links, set-ups, activation and retention.
Questions and answers
- What is co-marketing?
- Joint promotion by two or more companies of something that involves both, such as an integration, a guide or an event.
- What makes a good co-marketing announcement?
- A real, working capability, described in terms of what users can now do, with clear steps to try it.
- Who should write the announcement?
- Each partner should write for its own audience, using agreed facts, and link to the other.
- How should we split the work?
- Agree roles in advance: who builds, who writes, who publishes where and who handles questions.
- How do we measure success?
- Track visits, set-ups, activation and retention of users who came through the joint effort, using tagged links.