What we changed after our first 500 merchants

Getting to 500 merchants taught us more about product-market fit than all our pre-launch research combined. Here's an honest account of what we got wrong, what we got right, and the one feature we almost shipped that would have been a disaster.

What nobody used

We built an elaborate analytics dashboard for our launch. Subscriber growth charts, cohort retention tables, download frequency heatmaps, per-file engagement metrics. We were proud of it.

After 90 days, we looked at our own analytics to see which of these merchants were actually using. The answer was humbling: 78% of merchants visited the dashboard once and never returned. Of the 22% who came back, 80% of their time was spent on one screen: the subscriber count and current MRR.

What everybody asked about

Our support queue was dominated by two questions: how to pause a subscriber's account without cancelling, and how to give a specific subscriber a discount without affecting all subscribers.

We hadn't built either feature because we didn't think they were common enough to prioritize. We were wrong. Individual subscriber management — the ability to comp a subscription, extend a trial, or pause billing for a subscriber going through a rough patch — turned out to be the feature that differentiated good merchant-subscriber relationships from transactional ones.

• Individual subscriber pause: added in sprint 8
• Per-subscriber discount code: added in sprint 9
• Complimentary access (zero-cost subscription): added in sprint 10
• Subscription gifting: added in sprint 12

The feature we almost shipped

Six weeks before launch, we nearly shipped a feature called 'Smart Drip' — an AI system that would analyze subscriber engagement and automatically optimize content release timing to maximize retention. We had a working prototype and were ready to flip the switch.

The problem we caught in user testing: merchants couldn't explain to their subscribers why they were receiving content at different times than other subscribers. 'Our algorithm decided you should get this today' is not a satisfying answer. The feature created support tickets and confusion that offset any retention benefit.

“The best product decisions aren't about what you can build. They're about understanding what creates trust between your merchants and their subscribers.”

What we're building next

The two most common feature requests from our 500 merchants are native Shopify POS integration (so they can sell subscriptions in person) and a public API for connecting to email marketing platforms beyond our current Klaviyo integration. Both are on the roadmap for Q2 2026.