From Side Project to 12,000+ Travelers: The iWanteSIM Growth Story
Quick Answer: iWanteSIM started as a weekend side project to solve a personal travel pain point — expensive roaming charges. By building in public, listening to early users, and iterating rapidly, it grew into an eSIM platform serving over 12,000 travelers across 150+ countries without paid advertising.
Introduction: The $12 Coffee That Started Everything
It was a Tuesday in Lisbon. I had just landed, opened my phone to check Google Maps, and watched my carrier charge me $12 for 30 seconds of data. Not for a download. Not for a video. Just for loading a map.
That was the moment. Not the moment I decided to build something — the moment I realized millions of people were getting robbed every day by roaming fees that belong in 2005, not 2024.
I had heard about eSIM technology. Embedded SIMs — no physical card, instant activation, local rates. But every provider I found felt like a bank: complicated pricing, hidden fees, and a UX that screamed "we don't care about you."
So I built iWanteSIM over a single weekend. I didn't know if anyone would use it. I didn't have a marketing budget. I just knew that $12 for a map was absurd, and I was done paying it.
What Is eSIM and Why Does It Matter for Travelers?
eSIM stands for "embedded SIM" — a programmable chip built directly into your phone that lets you download carrier profiles over the air. No physical SIM card. No hunting for airport kiosks. No cutting SIMs with scissors (we've all been there).
For travelers, eSIM is transformative:
- Instant activation: Scan a QR code and you're online before you leave the terminal
- Local pricing: Pay what locals pay, not $12 for a map
- Dual SIM capability: Keep your home number active while using local data
- No physical waste: No plastic cards to lose or dispose of The technology has been around since 2016, but adoption exploded in 2020-2024 as Apple, Samsung, and Google made eSIM standard across flagship devices. Today, over 3.5 billion eSIM-enabled devices are in circulation globally, and the eSIM market is projected to reach $16.3 billion by 2027.
The First Build: A Landing Page and a Prayer
Weekend one was simple: a landing page explaining what eSIM was, a few regional data plans, and a Stripe integration. I used Next.js because I knew it, Tailwind because I didn't want to think about CSS, and Vercel because deploys took 30 seconds.
I didn't build a dashboard. I didn't build analytics. I built one thing: a way for someone to buy an eSIM plan and receive a QR code in under 60 seconds.
Then I posted it on Reddit's r/digitalnomad and r/travel with the title: "I built a tool to kill roaming fees. Here's what I learned."
The response? Brutal. Honest. And exactly what I needed.
"Why would I trust some random site with my phone?"
"Your pricing table is confusing."
"Can I use this in Japan? What carriers?"
"Do you have an affiliate program?" (That one surprised me.)
I answered every comment. I fixed the pricing table that night. I added a "How it Works" section. And I got my first 47 signups — not customers, just emails — but 47 people who cared enough to tell me what was wrong.
Finding Product-Market Fit: Listening to the Right People
Here's the thing about "product-market fit" — it's not a moment. It's a gradient. You inch toward it with every conversation, every canceled subscription, every support ticket that makes you wince.
My first paying customer came two weeks later. A software developer from Berlin flying to Tokyo for a conference. He bought a 5GB Japan plan for $12.50. I made about $3 in margin.
I sent him a personal email: "Hey, thanks for being our first customer. Any feedback?"
He replied with a Loom video. Seven minutes of him walking through the purchase flow, pointing out friction I had normalized. The confirmation email looked like spam. The QR code was too small to scan easily. The "activation instructions" assumed he knew what "APN" meant.
I fixed all of it. I added a "first-timer" guide. I made the QR code bigger. I rewrote the email in plain English.
Then I did something that changed everything: I asked if I could share his feedback (anonymized) in a blog post. He said yes. That post — "What Our First 10 Customers Taught Us" — became our most-shared content for six months.
Key insight: Early users don't just want your product. They want to feel like co-founders. Treat them that way, and they'll bring friends.
Building in Public: The Growth Engine Nobody Talks About
I started sharing our numbers on Twitter (now X) and Dev.to. Not just the wins — the struggles too.
"Week 6: 127 customers, $892 revenue. Still not profitable. Here's why."
"We just lost our first enterprise customer. Here's what we learned."
"I spent 4 hours yesterday debugging a QR code issue. Turns out it was a caching problem. Here's how we fixed it."
Building in public did three things:
- Trust: When you're transparent about your process, people trust you with their money
- Feedback: Developers and travelers started DMing me feature ideas and bug reports
- Distribution: Every post brought 50-200 qualified visitors who already understood our value By month four, we had 2,000 customers. Not from ads. From being honest about what we were building and why.
The Technical Pivot: From MVP to Platform
The original architecture couldn't scale. I knew it would break eventually, but "eventually" arrived faster than expected when a TikTok influencer mentioned us in a "travel hacks" video. Traffic spiked 40x in 48 hours.
The server didn't crash — the database did. Postgres on a $20 DigitalOcean droplet wasn't built for concurrent QR code generations. Lesson learned.
We rebuilt the core in three phases:
Phase 1: Infrastructure
Migrated to a managed PostgreSQL instance, added Redis for caching, and implemented rate limiting. Cost went from $20/month to $180/month. Revenue was $4,200/month by then, so it felt like a win, not a panic.
Phase 2: API Architecture
We needed to support multiple eSIM providers for redundancy. I built an abstraction layer that normalized different provider APIs into a single internal interface. Now we can swap providers without touching customer-facing code.
This matters more than it sounds. When one provider had an outage in Southeast Asia last March, we routed 100% of traffic to a backup in 90 seconds. Zero customer impact.
Phase 3: The Dashboard Nobody Asked For (But Everyone Uses)
Users kept asking for "usage tracking." I resisted — it felt like feature creep. But I built a simple dashboard anyway: data used, days remaining, signal strength by country.
Usage rate among active customers jumped 34%. Turns out people just want to know if they're about to run out of data before a Zoom call. Obvious in hindsight.
Scaling to 12,000+: What Actually Moved the Needle
Here's what worked and what didn't, with numbers:
ChannelInvestmentCustomersCACBuilding in public (Twitter/Dev.to)~10 hrs/week~4,200$0SEO content (travel guides + eSIM explainers)~8 hrs/week~3,800$0Referral program (15% credit for both sides)~2 hrs setup~2,600$2.10Paid ads (Google, Meta)$4,200 spent~412$10.19Paid ads were a waste for us. Our product isn't impulse-buy friendly — it requires education. Organic content and word-of-mouth outperformed by 20x.
The real growth multiplier: We started writing destination-specific guides — "Best eSIM for Japan," "How to Stay Connected in Bali," "Data Plans for European Train Travel." These rank for long-tail keywords, answer specific questions, and convert at 3x our homepage rate.
Our blog now drives 40% of organic traffic. Not because we're genius marketers, but because we write what we wish existed when we were travelers.
Biggest Mistakes and What They Cost Us
I've made plenty. Here are the expensive ones:
Mistake 1: Ignoring Support Response Time
For our first 1,000 customers, average response time was 18 hours. Not because we were lazy — because support was "async" in my head. In customers' heads, it was "they don't care about me."
We added Intercom, built a help center with 40 articles, and set a 2-hour response SLA. CSAT went from 72% to 94%. Churn dropped 40%.
Mistake 2: Pricing Too Low
We underpriced by 30% for six months, thinking "cheaper = more customers." It attracted price-shoppers who churned after one trip. We raised prices, added a "premium" tier with priority support, and revenue per customer increased 60% with zero growth loss.
Mistake 3: Not Localizing Early
60% of our traffic comes from non-English speakers. We launched with English-only and lost conversions in Germany, Japan, and Brazil for a year. Adding German and Japanese increased conversion rates by 22% and 18% respectively.
Key Takeaways
- Start with a real pain point you personally experience — not a market opportunity, a problem that annoys you
- Your first 100 customers teach you more than any analytics dashboard — talk to them, email them, learn from them
- Building in public is free marketing — share the journey, not just the wins
- Organic content outperforms paid ads for products that require education
- Technical reliability matters more than features — when someone's boarding a flight, they need that QR code to work
- Raise prices before you think you should — undervaluing your product attracts the wrong customers
- Localize early — the internet is global, and English-only is leaving money on the table
Frequently Asked Questions
What is an eSIM and how does it work?
An eSIM is a digital SIM embedded in your phone. Instead of inserting a physical card, you download a carrier profile via QR code. It activates instantly and lets you use local data plans while traveling without removing your home SIM.
Is iWanteSIM only for frequent travelers?
No. While frequent travelers save the most, anyone who travels internationally even once a year benefits. Business travelers, digital nomads, and vacationers all use iWanteSIM to avoid roaming charges.
How does iWanteSIM differ from buying a local SIM card?
Local SIMs require finding a store, showing ID, and physically swapping cards. iWanteSIM activates before you land, works in 150+ countries, and lets you keep your home number active on dual-SIM phones.
Can I use iWanteSIM with any phone?
iWanteSIM works with most phones manufactured after 2020, including iPhone XS and newer, Samsung Galaxy S20+, Google Pixel 3+, and newer Android devices. Check your phone's settings for "Cellular" > "Add eSIM" to verify compatibility.
What happens if I run out of data mid-trip?
You can top up directly through the iWanteSIM dashboard without reinstalling anything. Most plans allow instant top-ups, and you'll receive an updated QR code if needed.
Is eSIM safe to use for banking and sensitive apps?
Yes. eSIM uses the same encryption standards as physical SIMs. iWanteSIM partners with Tier-1 carriers that provide secure, encrypted connections. We never store or access your personal data.
How did iWanteSIM grow without paid advertising?
We focused on building in public, creating useful travel content, and delivering exceptional support that generated word-of-mouth referrals. Our referral program incentivizes sharing without requiring a marketing budget.
What's next for iWanteSIM?
We're expanding our coverage to include more local carriers in Africa and South America, adding group plans for travel companies, and building API access for travel apps that want to offer eSIM as a feature.
Conclusion: Build What You Wish Existed
Twelve thousand customers later, the lesson is still the same one I learned over that $12 coffee in Lisbon: build something that solves a problem you actually have. The rest — marketing, growth, scaling — flows from that foundation.
iWanteSIM isn't a unicorn. It's not even a venture-backed startup. It's a side project that grew because the problem was real, the solution was honest, and the people building it gave a damn about every customer.
If you're thinking about starting something, my advice is simple: don't wait for the perfect idea. Wait for the problem that makes you angry. Then build the smallest thing that fixes it.
Everything else is just iteration.
Want to try iWanteSIM for your next trip? Browse plans for 150+ countries and stay connected without the roaming shock.



Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.