
Partner Enablement
Part of Integration partnership marketing
Creating an accurate joint solution page
A joint solution page should let a customer decide whether two products work together for their use case. Lead with the task and outcome, then explain the …
Who the page is for and what it has to do
The reader who lands on a joint solution page already knows both products. They are not learning what a workflow tool or a CRM is. They run one of the two and want a narrow question answered: does this integration genuinely work, and what would it do in their setup?
That reader is evaluating, not browsing. HubSpot's guidance to its app partners describes marketplace visitors as shoppers who rely on transparency and detailed information to compare products before deciding. A page that reads as marketing collateral gives them nothing to compare.
The page's job is narrow. Let a technical or operational buyer confirm quickly that the two products work together, and show where the join sits: which records, fields and events cross from one product to the other.
Nail down the facts before anyone writes copy
Both partners agree on one shared fact sheet before a word of copy is drafted. It covers what the integration does, which editions and plans it supports, the prerequisites, the setup steps, and who owns support for which part.
Every claim on the page is then checked against that document. This is what stops a joint page drifting into claims neither engineering team would stand behind — half-supported editions, features still on a roadmap, limits that only appear at scale.
Atlassian's listing principles put the same idea in customer terms: a clear, complete, customer-focused listing helps a customer see what an app does, why it matters and whether it fits their needs.
Omitting the basics costs installs. HubSpot's partner guidance notes that a listing missing key details, such as a setup guide or a demo video, can affect whether a customer selects an app as a solution.
Impact of missing key details on marketplace listings
- Missing setup guide
- Can reduce customer selection rate
- No demo video
- Reduces trust and decision confidence
- Vague compatibility info
- Leads to failed installs and poor reviews
Naming, tagline and summary that describe the joint solution honestly
Where the listing sits in a partner marketplace, that marketplace's rules govern the name. Atlassian's limits are 60 characters for the app name, 130 for the tagline and 250 for the summary, which is the text used in search results to give deeper context than the tagline.
Lead with brand identity and core value rather than search terms. Atlassian tells partners to avoid keyword stuffing — repeating "Jira" or "Confluence" several times is the example it gives — and to work keywords in naturally instead.
Some words are barred outright in Atlassian listings: "Atlassian", "plugin", "beta", "add-on" and "app". A name also must not begin with an Atlassian product name, so the convention is "Time Tracker for Jira", not "Jira Time Tracker".
Atlassian's own illustration contrasts "SuperFlow Pro-Ultimate Jira Automation Workflow Manager Tool" with "SuperFlow — Automate Jira Workflows". The second states an outcome; the first stacks category terms and gives a buyer nothing to act on.
Effective vs. ineffective naming examples (based on Atlassian guidelines)
- Ineffective name
- SuperFlow Pro-Ultimate Jira Automation Workflow Manager Tool
- Effective name
- SuperFlow — Automate Jira Workflows
Show the joint workflow, not two products side by side
This is the section that makes the page a joint solution page rather than two brochures stapled together. Describe the flow end to end: what happens in the first product, what appears in the second, and what the user no longer does by hand.
Attach a problem to each use case. Not "sync your tickets", but the specific manual step the integration removes, who was doing it, and how often it had to be done.
Name the objects that move — records, tickets, contacts, fields, attachments, status changes — and their direction. If the sync runs one way only, say so plainly, because the reader will build their process around that answer.
Prove the claims with visuals and a short demo
Screenshots should show the integration running inside the real interface, not as a standalone marketing graphic. Atlassian's guidance is 1840×900 px for primary highlight images, with a caption of up to 220 characters on every screenshot explaining what the reader is looking at.
Atlassian recommends video kept under 30 seconds, showing the app solving a real problem rather than a marketing montage, because users rely on live demonstrations of how features work.
Blurry or generic marketing slides erode trust, per the same guidance. A plain screenshot of a working sync does more for a technical buyer than a stylised diagram of one.
Compatibility, setup and support, stated plainly
Spell out the supported editions and plans and the prerequisites a customer must meet before installing. Vague detail here turns into failed installs, refund requests and poor reviews, so state the boundaries rather than leaving them to discovery.
Walk through setup in order: what the administrator installs, what permissions or credentials are needed, what is configured in each product, and how to confirm the connection is working.
Name who handles support and how. Say which partner a customer contacts for install problems and which for sync failures, and make sure the route matches what the page promises.
Test the install path and the trial and licensing behaviour one final time before launch — a step Atlassian includes in its go-live guidance for marketplace partners.
Keep both brands intact and get sign-off
Apply the naming and trademark conventions of both partners, not only the one hosting the listing. Product names are written the way each company writes them, and neither logo or wordmark is used in a way its owner's trademark policy does not allow.
Avoid phrasing that implies an endorsement, partnership or ownership that does not exist. A reader should never come away thinking one product is made, sold or supported by the other company.
Run the draft through a joint approval step. Each side signs off on the specific claims made about its own product — editions, prerequisites, limits and support boundaries — before the page is published.
Atlassian's launch guidance also points partners to its trademark policy covering Google Ads campaigns, which governs paid activity that uses brand terms.
Localise, review and keep it accurate over time
Where a meaningful share of the audience works in another language, translate the page. HubSpot's partner guidance says localised listings are shown first in search results for customers who have set that language as their account's default, and are included in language-based app collections.
Set a review trigger rather than relying on a calendar date. A new edition, a deprecation, an API change, a pricing change or a shift in the support model on either side is a reason to reopen the page.
Keep the shared fact sheet versioned alongside the page, so the next reviewer can see what changed, when, and who approved it.
Watch how readers behave and refine the copy
Track installs, trial-to-paid conversion and the support questions that arrive after installation. Conversion from trial to paid is an explicit focus of Atlassian's launch guidance for marketplace partners.
Support questions are the most direct test of the copy. A question that arrives repeatedly about setup, editions or scope marks a line on the page that is not doing its job.
Refine the wording towards the terms customers actually use in those questions, while keeping the value-first framing. Atlassian also notes that fast responses to early support requests and quick fixes shape a listing's initial reviews and ratings.



