DEV Community

Jim L
Jim L

Posted on

I Killed My Subscription Price Because Nobody Buys a Monthly Plan for an Anniversary Gift

I launched songmemento.com with a $19.99/month subscription as the only way to pay, and it took less time than I'd like to admit to realize that was the wrong model for what the product actually is.

The tool turns one specific memory into a custom AI-generated song: you answer three short questions (who it's for, the memory, the occasion), get a free ~15-second preview generated from your actual answers, then pay for the full track. The occasions people were describing in testing were things like a proposal, an anniversary, a specific birthday. Those are events that happen once or twice a year for any given person, sometimes once ever. Asking someone to commit to a recurring monthly charge for a gift they need exactly one time is a mismatch between the pricing model and the actual use case, and I built that mismatch myself by defaulting to "SaaS pricing" without checking whether this was actually a SaaS.

I switched to a one-off price of $1.80 per song, with a $13 bundle (about $1.30/song) for anyone making more than one, wedding favors or a batch of birthday gifts across a year. The subscription still exists but it's no longer the lead offer; one-off is what the checkout flow pushes toward now.

The engineering side of that pivot was smaller than the business-reasoning side, which is worth saying plainly: dropping a subscription-gate check and adding a single-purchase Stripe flow is a day of work, not a rebuild. The actual full track renders in roughly 60 seconds after purchase using the ACE-Step model on Replicate, and that part of the stack didn't change at all. What changed was entirely upstream: I'd built pricing around what's easy to bill (recurring revenue is nice on paper) instead of around when the customer actually has money-in-hand intent, which for a gift product is right at the moment of the occasion, not on a monthly cycle.

I'll be honest about where this still sits: real user numbers are near zero, this is a few-days-old build-in-public project, and I'm not going to pretend otherwise with fake testimonials or usage stats. The free preview is a real render of your own answers, not a stock demo, and that part I'll stand behind regardless of pricing. If you're building a gift or occasion-based product and defaulting to subscription pricing because that's what every SaaS starter template ships with, it's worth asking whether your actual purchase moment repeats monthly or not before you commit to that model.

Top comments (0)