Working on subscriptions. Realizing how much infrastructure hides behind “just add recurring billing.”

I’ve been deep in subscription support this week, and it’s been a good reminder that “subscriptions” are never just a pricing toggle.

It touches everything. Database models, product sync, checkout logic, webhooks, access control, customer dashboards, emails, and even how you validate carts so users don’t end up in broken states.

What’s made this work especially satisfying is that all of this data lives where the user already operates. Subscription state, access, and lifecycle aren’t hidden behind an external admin panel. They’re visible and understandable directly inside Notion.

Part of why I’m pushing this now is that I think subscriptions might reduce the commitment hurdle for early users. Building or switching an entire store is a big ask. Subscriptions and event-level commerce feel like a way to let people start smaller and grow into the platform.

It’s a lot of work for something users will experience as “this just works,” but that’s kind of the point.