Planning an integration launch with another vendor

An integration launch rests on two dependencies: the connection works, and both partners describe it the same way. Agree on a launch owner on each side before setting an announcement date.

Treat the shared checklist as the joint launch plan. Put the announcement date at the top, then enter an agreed calendar date and an owner for every task; the sources do not prescribe fixed lead times.

Plan the work in sequence: technical acceptance and security review first, then support training and listing or solution-page approval, followed by customer communications. Keep the announcement date provisional until the launch checks are complete.

Each launch owner coordinates their side, collects task updates and open decisions, and confirms the joint go-live or pause decision with the other owner. Give each checklist task its own owner so the two launch owners can see who is responsible for completing it.

Test installation on a fresh eligible account, including an ordinary workflow and a failure case such as a permission change or delayed sync. Atlassian’s marketplace launch guidance calls for checking the install path and listing before promotion; check trial and licensing behaviour as well.

Use the checklist to track listing or solution-page approval. For each claim, record the exact feature, required plans, supported products, data direction, screenshots and approved wording, along with its version and reviewer.

Keep one shared claim register and record changes in it. Have both launch owners approve each claim before either partner publishes it; neither team should promise functionality the other has not released.

Choose a small number of channels that reach users with the integration need. Options include the marketplace listing, an internal product launch email, an external customer email, social media, a press release, a blog post or partner channels.

Coordinate the publish times and support coverage for the selected channels. Record who handles enquiries and the support contact and coverage each partner can provide; train support before launch.

Before go-live, agree what rollback action is available and who can call for it. A failed install path, trial or licensing check, or supported workflow is a reason to pause promotion; either launch owner can call the pause, and both should agree before resuming after a fix and retest.

If a technical issue appears after launch, pause the affected claim and update both partners’ pages promptly. Atlassian advises preparing for support enquiries, responding quickly to early requests and making quick fixes for issues reported by first adopters.

For post-launch measurement of installations, activation, clicks and registrations, use the separate measurement guidance.

Key Launch Metrics to Track Post-Launch