Add-ons Process

1. Say hi. Reach out to express interest in building an add-on by filling out this form. Please know we get lots of interest but can only work with a few partners. If an add-on for your product is something we want to pursue, we will reach out to you.

2. Get the contracts signed. We have agreements that need to be in place to protect both parties.

3. Kickoff call. Your development team will meet with our development team over Zoom to get things started. We'll set up your developer account for add-on development and invite you to a shared Slack channel where we can easily support you while you work.

4. Build it! This part's up to you, but we want to be involved as much as is helpful here! Please don't hesitate to use that Slack channel to ask questions, verify assumptions, or make feature requests. We want to make the development process as seamless as possible.

5. Beta. You should find some of your users who are interested in the add-on to try it out. We don't have a hard and fast rule for the amount of time or number of users that the add-on should be in beta -- we just want you to be confident that it works well.

6. Final review. Before a wide release, we like to do one last check-in with our team and yours to see if there's any rough edges we'd like to see smoothed before launching the add-on.

7. Wide release. We'll work together to decide upon timing for a wide release and marketing push.

8. Iterate. If you want to make changes or add new features to the add-on, go for it! The staging and beta environments are here to help make that easier for you. No need for us to review every change you make, but we do like to hear about them, mostly just to celebrate with you.