Launched a tiny eSIM side-product on top of my existing SaaS in one day (0 new backend, reused everything)
I run sms-florin, a small SMS-verification/phone-rental service. Last week I noticed a gadget store I follow (George Buhnici's GB.ro) has a companion eSIM site built entirely with Claude, piggybacking on their existing Shopify checkout. That made me realize I already had 90% of the infra needed for the same kind of product: Stripe checkout, a webhook handler, an email-delivery pipeline.
So I signed up as a reseller with an eSIM aggregator (PikaSim — no setup fee, no minimum order, ~10% margin at zero volume), picked 5 destinations travelers actually ask about (UK, Turkey, USA, Europe regional, Thailand), and wired their API into my existing Stripe webhook. Guest checkout, no account needed — pay, get a QR code by email, done.
Built and shipped in a day. First real paid order (my own test purchase) went through end to end: Stripe → webhook → aggregator API → QR code delivered.
It's flo-voice1.com/esim if you want to see it or roast the pricing.
What I'm stuck on now: distribution. The product works, but I have zero organic customers past my own test order. If anyone's done cold outreach or content that actually worked for a travel-adjacent product, I'd genuinely like to hear what moved the needle for you.
The one-day launch is impressive, but the interesting test starts now that the product works.
Curious what you learn from the first customers about whether the existing audience transfers at all.
Fair question — honestly still finding out. Zero real customers beyond my own test purchase so far, so I can't say yet whether the sms-florin audience transfers at all — different intent (privacy/verification vs. travel). My guess is it mostly won't and this needs its own distribution, but I'd rather learn that from data than assume it. Will report back once there's something real to report.
That’s fair. It’ll be interesting to see whether the existing audience transfers once you have enough real customer data.
Cheers, will report back once there's real usage data, good or bad.
Makes sense. I’ll be interested to see what the first real usage data says, especially given the different intent between the two products.