Desktop
Work directly on Kite.ai.
Announce launches and updates
You shipped it. I make sure people hear about it.
I prepare the launch page, emails and posts before the day, release them together, and turn every update your team ships into an announcement.
Get started free7-day free trial
You
We're launching the recycled cast iron wok on March 3. Can you plan it?
KiteHere's the plan, working back from March 3. Every piece is ready for your review the week before.
Launch planDraft
| Piece | Where | Ready by |
|---|---|---|
| Positioning and messaging | Doc | Feb 10 |
| Launch page | Your site | Feb 17 |
| Announcement email | Mailchimp | Feb 24 |
| Launch-day posts | LinkedIn, Instagram | Feb 24 |
Approve planAsk for changes
What I do. I run the launch, and every update after it.
Set the goal and the message
We agree what the launch should achieve, then I write the positioning every other piece is built from.
Build the launch page
A page on your site built to turn launch traffic into that goal, plus updates to your homepage and pricing.
Release everything together
The announcement, emails and posts are ready ahead of time, and go out on launch day with one approval.
Announce every update
I read what shipped in GitHub, Linear or your changelog and turn each release into changelog entries, emails and posts.
One month of changes, announced where it matters.
Ironbark’s changes this month
- Engraving on every skillet.
- A faster checkout on phones.
- A fix to a shipping label bug.
Engraving is here
- A changelog entry that says what customers can now do.
- A customer email and two posts, each written for its channel.
- The checkout and bug fix go in the monthly roundup.
- I sort every change by how much it matters to a customer.
- Release notes in customer words, not code words.
- Big releases get their own announcement, small ones a roundup.
Ironbark Cookware is an example business.
Built on real data
- GGitHub
- LLinear
- MMailchimp
Google Analytics
I read what your team shipped from GitHub, Linear or your public changelog. After each announcement, I check page views and email results to plan the next one.
How it starts. Three steps to your first result.
- 1Connect your tools
Connects to your tools
Connect where your team tracks its work and where you announce it. On a Kite site, I publish the launch page directly.
GLML
- 2Tell me the goal
Tell me the launch
What you're launching and when, or ask me to announce everything that shipped this month.
- 3Approve the work
Approve everything in one list
You review the messaging first, then every piece in one list before launch day.
Your AI marketer.Wherever you work.
At your desk? Open Kite.ai. Away from your laptop? Use Kite in your phone browser. Prefer to work in Slack? Kite works there too.
Phone browser
Keep work moving on the go.
Slack
Bring Kite into your team's conversations.
Tell me what you're launching. I’ll plan everything back from the date.
Start your 7-day free trial and get your launch plan.
Get started freeQuestions. Before you start.
How far ahead should we plan a launch?
Three to four weeks suits most feature launches, and six weeks or more suits a new product. That leaves time to approve the messaging before the other pieces are built from it.
Does it work if my site runs on Webflow?
Yes. I publish the launch page and site updates through Webflow, Contentful, Sanity, Storyblok or self-hosted Payload, or directly on a site I host for you.
Should we announce small updates and bug fixes?
Yes, together. Small fixes belong in your changelog and a monthly roundup email, and bigger releases get their own announcement.
We use neither GitHub nor Linear. Does that work?
Yes. I work from your public changelog, release notes and docs, or from a plain description of what shipped.
Can I work with you in Slack?
Yes. You can work with me at kite.ai in your browser, on desktop or phone, or in any channel of your own Slack.