# Separate responsibilities. One shared launch.

All stories are fictional. They do not describe specific people, companies or projects. Any resemblance is coincidental.

Two companies prepare a joint launch. One owns the product and integration; the other handles the audience and support. Each team follows its own plan. Late in the process, materials depend on unconfirmed features and support does not know what users were promised.

## Where we could start

I would check how separate commitments combine into one launch. I would prepare either the missing shared sequence or a review of dependencies requiring joint decisions.

## What you would have

A joint-launch readiness review with required decisions and owners.

## Participants

The launch owners from each organisation.

## Roles and decisions

Specialists confirm readiness; authorised participants make the launch decision.

## Factual experience, separate from the fictional story

Keiss Media: Managing digital campaigns: client requests, estimates, budgets, suppliers and delivery.
https://apiperson.com/experience/#work-keiss

Realore: International licensing and distribution of existing games, including partner work.
https://apiperson.com/career/

[There are separate plans, but no shared one](https://apiperson.com/clients/joint-launch/no-shared-plan/)

[A shared plan exists, but dependencies slip](https://apiperson.com/clients/joint-launch/dependencies/)

[Book a 30-minute call](https://calendar.app.google/4FrxQkHkAZ32PkzA9)

mailto:apiperson.com@gmail.com