Skip to main content

Product Marketing and Launches

Tell Kite what is shipping and when, and it gets the launch ready before the code is.

How a launch runs​

  1. Tell Kite about the release in a thread: what changed, who it is for, and when it lands. Paste the pull request description or the release notes if you have them.
  2. Kite prepares the assets and posts them in the thread:
    • A product or feature page, written in language search engines can find, built as a draft on your site.
    • An announcement, ready for your blog and your connected social networks.
    • An email campaign, ready to send.
  3. You read it once. Reply with changes, or with "ship it."
  4. Kite publishes the page, sends the email, and posts the announcement to the networks you have connected.

Your team merges the pull request. Kite launches the release.

Keeping launches on a rhythm​

If you ship on a schedule, set up a workflow so Kite runs the launch checklist each time, or trigger it from a webhook when a release goes out. See Initiatives, reports, and workflows.

Why this matters for lean teams​

On most small teams, launch marketing happens after the engineering work, if it happens at all. With Kite, shipping a feature and telling customers about it happen in the same week.