Skip to content
Insights from launching OpenAI for Coda
Share
Explore

Insights from launching OpenAI for Coda

The inside story of how we launched the OpenAI Pack
Key launch stats:
#6 in Product Hunt with 313 upvotes
67K Tweet impressions
270 Pack installs in the first week

PH Gallery BK-GPT3 (1).png

Here’s a short story of how we launched the , the launch strategy we used and all the templates and resources we used for this launch. Enjoy!

Key decisions we made before launching

Our “Why”: We believe that adding OpenAI’s powerful models to a flexible surface like Coda will empower thousands of makers to build custom workflows and save time at work.
Focus on the obvious use cases and on the problem we’re solving, not the Pack.
Reverse engineering: How would a good GIF/Video/Screenshot would look like and what do we need to make it happen?
Focus in business-oriented use cases rather than personal uses case (ie: how can OpenAI can save me time at work).
Do a big launch on Product Hunt and get hunted by Reid Hoffman who’s very bullish on AI.
Launch a competition as part of the launch to continue the growth loop.

Why this launch was successful

Launched on Product Hunt at 12:01 AM PST and ask (a recognized Hunter) to hunt our project.
Spencer poster a with 5 examples of how to use the Pack, focusing on the use case and not the Pack.
We spent a lot of time (probably 70% of our time) working on the that showcased how the Pack works.
We brainstormed 30+ different social media copies, we even asked GPT-3 to give us some ideas and we iterated and asked the team to upvote their favorite copy until we had something we all liked.
We asked influencers with large followings like
and to share.
Posted on .
Posted on .
We posted in 3+ Slack communities.
Build personalized solutions to grab influencer’s attention, for example to include this launch in his daily AI newsletter.

Get started with this template 👇




Are you launching your Pack and want help? Email us at

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.