TL;DR
- Cold-start = two overlapping asymmetries: no reviews to earn trust, no traffic to earn reviews
- What worked, in order: long-tail SEO, community answers on Reddit, open-sourcing one small utility, cross-linking SKUs, a visible refund policy
- What flopped: X threads, Product Hunt, paid ads (CAC ~$120 on a $79 product), YouTube
- Brand search converted ~4x cold traffic, but only exists after months of the unglamorous stuff
- First 20 sales took three months. The next 80 took two.
You can ship the cleanest Expo starter on the internet, wire Supabase RLS by the book, and set up Stripe webhooks that never miss, and still watch your dashboard sit at zero for weeks. Getting our first 100 customers for Applighter was less about the code and more about a small number of distribution bets made after the code stopped mattering.
Why "just make a good template" doesn't work
Every founder selling code has the same theory: if it's good enough, developers will find it. They won't. Two things are true about the buyer's mind at the same time:
- A template is a risk purchase. A $79 template can burn $10,000 of engineering time if it's badly structured. Buyers want proof, not marketing copy.
- They're drowning in options. ThemeForest lists thousands of React Native templates, mostly five-year-old Redux samples with no backend. The category has burned every buyer at least once.
So the buyer's default assumption is this is another one. Your entire job before the first sale is breaking that assumption for people who've never heard of you.
Week 1 starting position
- Launch templates live: real, buildable Expo + Supabase apps
- $79 per single-app license
- Zero email list. Zero Twitter reach. Zero backlinks.
- One landing page built in a weekend
Week 1 revenue: $0. Week 2: $79. Week 3: $158. This is not a "made $10K in 30 days" post.
What actually worked, ranked by attributed first sales
1. SEO on very specific long-tail queries
We didn't chase "react native template." We ranked for:
- "React Native Supabase template with RLS and storage"
- "Expo EAS build cost calculator"
- "Streaming AI responses to React Native"
Low-hundreds monthly volume each. Nobody competes for them because they're too specific for big content teams. That's exactly why they convert: whoever searches that phrase has already decided to build the thing and wants the fastest way.
Our first 20 sales came from four blog posts in this category. Always the technical, specific, "we actually did this" posts. Never the "top 10 tips" ones.
The mechanism: specific Google query → post that solves it → "oh, they sell a template that already implements this" → click. Not glamorous. Very reliable.
2. Building in public in the right communities
Reddit was our second-biggest channel. But not r/reactnative: we got flagged as promotional twice there. What worked:
- Answering questions in r/expo with real technical answers that referenced our template as one of the options
- Long "here's how I built this" posts in r/indiehackers and r/SideProject
- Answering bug threads on r/Supabase where our stack overlapped
Rule learned the hard way: you can promote in a comment if you gave three comments of pure help first. Reddit's spam detection, human and algorithmic, is very good at spotting drive-bys.
3. Buying trust with a small open-source release
We open-sourced one piece of infrastructure: a Supabase migration generator plus the license-grant edge function pattern we use with Stripe. Went nowhere on GitHub in isolation. But it:
- Gave buyers a real GitHub org to click through and see we exist
- Turned into two Indie Hackers threads and one Hacker News mention (front page ~3 hours)
The HN mention alone drove three same-day sales and got us indexed for terms we didn't otherwise rank for.
4. Cross-linking SKUs
Each template page links to the others in a "you might also want" section. When one template started ranking, it dragged the adjacent ones up with it: same buyer intent, same domain authority pool. If you only have one product you can't do this, but it's a reason to build three related SKUs once the first one ships.
5. The refund policy is a sales tool
7-day, no-questions-asked, displayed on the pricing card, not buried in the footer. Refund rate to date: 3.1%. Conversion lifted noticeably when the badge became visible. Buyers of a $79 template are risk-buying; a visible refund is the cheapest possible risk reducer.
What flopped
| Channel | Result | Why we stopped |
|---|---|---|
| Twitter/X threads | ~150 impressions, ~0 clicks | Reach without buyer intent |
| Product Hunt | ~40 upvotes, 2 sales | One-day spike, no compounding |
| Paid Google Ads | CAC ~$120 on a $79 product | Terrible unit economics |
| LinkedIn posts | 3 sales | Not repeatable, worst noise ratio |
| YouTube tutorial | 200 views in 3 months | Production time too high for this stage |
Pattern: paid + broad intent loses at this price point. Organic + specific intent wins.
Month-6 funnel numbers
| Channel | Sessions | Conv. rate | Sales |
|---|---|---|---|
| Long-tail SEO (blog) | 4,200 | 0.9% | 38 |
| Direct + brand search | 1,100 | 3.4% | 37 |
| Reddit referral | 380 | 1.3% | 5 |
| Hacker News (one-off) | 2,100 | 0.14% | 3 |
| Twitter/X | 90 | 1.1% | 1 |
| Paid | 40 | 0% | 0 |
Two takeaways:
- Long-tail SEO wins on volume despite mediocre conversion, once you have 10+ ranked posts.
- Brand search converts ~4x, but it only exists as the compounding return on everything else.
You can't buy your way to that mix. You write your way to it.
What we sell against
For context on positioning (this is what breaks the "just another UI kit" objection): full React Native + Expo source on a current SDK, complete Supabase backend with schema/RLS/storage/edge functions, working AI integrations with real API contracts, Stripe-powered license grants that provision the repo on payment, NativeWind + TypeScript throughout. The full catalog is at Applighter if you want to see how the pages are structured; steal whatever works.
A typical ThemeForest listing is UI screens, mocked data, no backend, unclear licensing. Beating that bar is easy on paper and hard in practice, because your first buyers have no way of knowing you're different.
The checklist if we started over
- Ship one template. Not a catalog. One, undeniably good.
- Write four blog posts about specific problems it solves, like "streaming OpenAI responses in Expo without dropping frames."
- Analytics before launch. Search Console, a privacy-respecting analytics tool, a UTM convention.
- Open-source one small utility. Your credibility artifact.
- Show up in 2-3 communities regularly. Not in bursts. Get known before you sell.
- Visible refund policy on the pricing card.
- Wait. SEO compounds at month 3-6. Quitting at month 2 because "nothing is working" is where most people lose.
What cold-start really means
It's not that you have no customers. It's that you have no evidence: no reviews, no case studies, no referrals, no rank. Every channel that scales in month 12 requires evidence that doesn't exist in month 1. The whole game of the first 100 sales is building evidence faster than your runway burns. Everything else is downstream.
Anyone else selling dev tools or templates as an indie? What was your first channel that actually produced a sale (not impressions, a sale)? Drop it below. I'll trade notes on anything we tried.
Top comments (0)