Day 4: Multi Product

"Yeah, I'll ship it by the evening" John said confidently.

Famous last words.

The Hydra Effect

Last month, a customer asked if they could run two separate product subscriptions but keep them synced. Sounded reasonable. After all, we're in the business of making complex pricing models simple.

24 hours later, our DMs to each other looked like this:

• "Wait, what happens if someone upgrades mid-cycle?"

• "How do we handle product transitions across groups?"

• "If they cancel one product but not the other...?"

Each solution spawned three new edge cases. The hydra was alive and well.

I was literally writing code on a transatlantic flight with spotty WiFi when I realized: this wasn't just another feature.

Introducing Product Groups

Today, we're excited to launch Product Groups - a new way to handle multiple product subscriptions, because sometimes, your software is making so much money that users won't settle for just one pricing plan.

Think about companies like Notion. They have their core workspace plans (Free, Plus, Business) AND their AI add-on plans. Two separate product lines that need to work together seamlessly.

Typically, this has been really hard to implement

1. Managing multiple products and subscriptions per customers and potentially having them billed multiple times per cycle

2. Feature tracking is a lot more complex now, because you need to check which plan the user is in for each group, and map that to the right features

3. Having to build a ton of upgrade and downgrade flows for the different sets of plans

Of course with Autumn you can set it up in minutes. Here's how: