Use Case
Announce an integration or partnership
Launch a new integration or partnership with a coordinated announcement, use-case content, and sales or partner enablement.
How it Works
Before you start
This use case works best when you've already set up some foundational elements in Quotient:
- Memories populated: Add your product overview and positioning so the Quotient agent can tie the integration or partnership to your core message.
- Details ready: Have the partner or integration name, what it does, who it's for, and any key benefits or use cases. Links to partner pages or docs help.
- Channels in mind: Decide whether you need blog, email, social, sales one-pager, partner-facing assets, or all of the above.
How to do it in Quotient
1. Start a conversation with the Quotient agent
Open a new chat and describe the integration or partnership launch. Include what you're announcing, who the audience is, and what deliverables you need. For example:
"We're launching an integration with [Partner]. Can you create a launch campaign for this? I need a blog post announcing it and explaining the main use cases, an email to existing customers, social posts for LinkedIn and X, and a one-pager for our sales team so they can talk about it in deals. Also a short partner-facing summary we can share with [Partner]'s team."
2. The agent creates the campaign and deliverables
The Quotient agent creates a campaign with a brief and tasks for each deliverable. The brief captures the integration/partnership value, key use cases, and messaging so every piece stays aligned. It can draft audience-specific variants — technical depth for developers, business value for decision-makers, and talking points for sales.
3. Provide the details
Share specifics so the content is accurate and on-brand:
- "The integration lets users [X]. The main benefit is [Y]."
- "We're targeting [segment] — emphasize time savings and fewer context switches"
- "Partner's positioning is [Z] — our messaging should complement that"
- "Sales needs to know: how to turn it on, who it's for, and how to handle 'we use a competitor' objections"
4. Review and publish
Review the blog, emails, social posts, and sales/partner assets. Coordinate with your partner on timing if you're doing a joint announcement. Publish the blog first, then email and social, and distribute the one-pager to sales and partner teams.
What you'll get
A typical integration or partnership launch includes:
- Blog post — announcement plus use cases, benefits, and a clear CTA (e.g. try it, read the docs)
- Email — to customers or prospects announcing the integration/partnership and why it matters
- Social posts — LinkedIn and X (and optionally Instagram) from company and optionally personal accounts
- Sales one-pager or battle card — what it is, who it's for, how to position it, and how to turn it on
- Partner-facing summary — short overview and key messages for the partner's marketing or sales team
Tips for better results
- Lead with the job-to-be-done. "Connect your CRM to Quotient in one click" is stronger than "We've partnered with Salesforce." Frame the announcement around what the user can do now.
- Give sales something they can use. A one-pager with 3 bullets, a link, and 2 objection handlers is more useful than a long blog. Ask the agent to keep the sales asset scannable.
- Align with the partner. If you're doing a co-launch, share your draft with the partner so messaging is consistent and you don't overpromise on their side.
- Use case over feature. Focus content on "here's how you use Quotient + [Partner] to get X done" rather than a feature list. That drives adoption and shares better.
- Plan a follow-up. Ask the agent for a short follow-up email or social post you can use 2–4 weeks later to re-surface the integration for people who didn't act the first time.
Get Started
We're launching an integration with [Partner]. Can you create a launch campaign for this? I need a blog post announcing it and explaining the main use cases, an email to existing customers, social posts for LinkedIn and X, and a one-pager for our sales team so they can talk about it in deals. Also a short partner-facing summary we can share with [Partner]'s team.