How do you run a product launch in one AI project?

Why organise launch work in one place

Organise launch work in one place because launch work scattered across chats loses its decisions. A launch runs for weeks and touches positioning, content, sales enablement and internal updates; when each piece starts in a fresh chat, someone re-explains the audience and the date every time, and small differences creep in.

In Pebbles Ai, create a project from the chat sidebar with New project and file every launch chat in it. With memory on, Project memory brings the launch's goals, audience, timelines and decisions into each chat in that project. Projects are private to their owner.

What goes on a go to market launch checklist

A go-to-market launch checklist covers the decisions before launch day, the assets for it and the follow-through after it. Agree the first two items before anyone writes a word of copy.

• Positioning: who it is for, the problem and the one-line claim you can support.
• Audience: the segments and accounts you will tell first.
• Assets: the announcement, emails, posts and a short internal brief.
• Enablement: what sales and support need to answer questions.
• Launch-day plan: who posts, sends and answers what, and when.
• Follow-through: the conversations you will start in the weeks after.

How do you see the launch plan before anything runs

Switch to Plan mode, and the assistant lays out the steps while queuing every outside action instead of running it. Describe the launch goal to the Strategy assistant and inspect the steps it proposes; a Slack post or a Notion page write stays queued until you decide.

When the plan looks right, switch to Manual to approve each action as it comes, or to Auto to let them run without asking. Template send and calendar delete still ask in every mode.

How do you bring Notion, Slack and Jira into a launch project

Bring Notion, Slack and Jira in through Settings, Connections, so the assistants can work where the launch already lives. An admin connects Notion and shares the launch pages, and adds the Pebbles bot to the launch channel in Slack.

For Jira, each person connects the Atlassian server from the Pebbles Ai MCP catalogue with their own sign-in, and the Marketing and Strategy assistants can then use its tools in chat; the catalogue may change. Whatever a server returns is treated as data, never as instructions to your assistant.

Which assistant should handle which part of the launch

Give positioning and the plan to the Strategy assistant, launch content to the Marketing assistant and questions about how Pebbles Ai works to the Guider. All three can work in the same project.

An assistant can delegate work to another from inside the chat, so a positioning discussion can turn into draft announcement copy without starting over.