Building LinkCover – Day 3: Payment is live. No more building, time to sell.
The product is live. Payment works. Three templates. Dynamic URL in the browser mockup.
What changed since Day 1:
- Dropped Satori (WASM broken on Workers). Pure SVG instead. Response under 5ms.
- Added dark, light, and brand templates with a browser chrome around the image.
- Replaced waitlist with a live $7/month checkout (Lemon Squeezy + Grey).
- URL field so the preview shows the user's actual domain.
What I didn't build: auth, dashboard, analytics, rate limiting. None of that matters until someone pays.
Next 48 hours: outreach, Reddit posts, and seeing if anyone actually buys.
Live: https://linkcover-landing.vercel.app
Question for anyone who's been at this stage: how did you get your first paying customer when you had zero audience?
Trending on Indie Hackers
Good instinct skipping auth, dashboard, and analytics. Building those before anyone pays is the most common time sink I see with early-stage tools.
For first paying customer with zero audience, a few things that actually worked for me:
Find 10-15 people who manually do what your product automates. For LinkCover, that is anyone currently screenshotting their site and dropping it into Figma or Canva to make social preview images. Search Twitter/X for people complaining about og:image, open graph previews, or social cards looking wrong. DM them directly with a link. Not a pitch, just a short message: I built a thing that generates these automatically, would it save you time?
Reddit works but only if the post teaches something, not promotes. Write a short post about how og:image rendering actually works across platforms (the gotchas are genuinely interesting), and mention your tool at the end as disclosure. r/webdev and r/SideProject are decent for this.
Consider whether a one-time purchase option would convert better at this stage. First customers care less about monthly cost and more about whether the tool works. A one-time purchase removes the commitment friction entirely.
The 48-hour outreach sprint is the right call. Most tools die in the gap between building and selling, not because the product is bad.
Thanks for this — really actionable. The one-time purchase suggestion is something I hadn't seriously considered, but it makes sense. First-time buyers don't know if the tool is worth a subscription yet. Adding a $9 lifetime option today.
Also going to search Twitter for people actively complaining about broken og:image tags instead of cold outreach. The "find people already describing the problem" framing is a shift I needed.
Day 3 with payment live is a genuine milestone — most builders spend weeks on "I'll add Stripe later." The mental switch from builder to seller is the hardest one. Practical suggestion for this week: identify one specific person (not a vague "target user") and ask for a live demo call. First paying customers almost always come from a conversation, not a launch post.
"The mental switch from builder to seller is the hardest one" — this hit. Day 1-3 I was still thinking like a dev. Day 4-5 I'm finally thinking about distribution.
The live demo call idea is solid. Going to find one person this week and ask for 5 minutes instead of sending more cold emails. First customers come from conversations, not posts — noted.
Dropping auth, dashboard, and analytics until someone pays is exactly right. Most people build all of that before validating and wonder why nobody cares.
For the first paying customer with zero audience — the pattern that worked for me was going to places where people were already describing the problem and reaching out directly. Not posting about the product, but finding someone who just said "I wish X existed" and saying "I built that."
Reddit and Indie Hackers threads where people complain about the specific pain you solve are gold for this. The conversation is already warm before you say a word.
Good luck with the next 48 hours — curious to hear how the outreach goes.
"The conversation is already warm before you say a word" — this reframes everything. I've been doing cold outreach to people who never expressed the problem. Should be searching for "og image not showing" and replying to those people instead.
Appreciate you sharing what actually worked. The warm-problem approach is my next move.
Smart move on skipping auth and dashboards until you get actual validation, Hakim. So many founders get trapped building those features for weeks before realizing no one wants the core product. Getting that checkout live on Day 3 is pure indie hacker wisdom. Pure SVG with under 5ms response sounds amazing technically. Good luck with the outreach!
Thanks, appreciate that. The "don't build what nobody asked for" lesson took me a while to internalize. Now it's just outreach and waiting to see if anyone actually pays. The 5ms SVG part was a happy accident — Satori crashed, pure SVG saved the project.
Worth knowing — the /fix-sprint page updated this afternoon with the exact detail on what the fix includes, including a 7-day guarantee.
Before/after for the social proof gap:
outboundautonomy.com/fix-sprint?ref=fixsprint-linkcover
One thing I'd be careful with:
The first-customer question sounds like a distribution problem, but it may actually be a buyer-definition problem.
A lot of founders end up optimizing outreach before they've verified that the people seeing the product are the people most likely to pay for it.
Those look similar early on, but they tend to lead to very different decisions.
I wouldn't make that call casually in a thread.
Fair. I'm keeping the outreach going for now to get data, but I'll revisit the buyer definition at the end of the test. Appreciate the nudge.
Possibly.
The reason I'd still be careful is that some decisions become much harder to revisit once the data starts accumulating around them.
I wouldn't try to unpack that properly in a thread.
If you'd like the tighter version, drop your email and I'll put it together properly.
Appreciate the nuance, Aryan. I'll keep that in mind as the test data comes in. If I get stuck interpreting the results, I'll reach out.
The gap between your headline and the $7/mo ask is social proof — specifically, the absence of it. The whole visible page is: promise, then price. Nothing between them that says anyone else has used this. A first-time visitor landing cold sees the tool, hears the pitch, and then immediately a payment card with zero evidence that it does what it says.
One trust element above the pricing card closes that. A real user count, a single genuine quote from someone you've already shared it with, even "500 preview images generated" if you have that number. The product clearly works — the page just doesn't prove it yet.
For $49 I can fix that, plus your top 2 other conversion issues, in 48 hours. PR/diff you can review and merge. outboundautonomy.com/fix-sprint?ref=fixsprint-linkcover
Good catch on the social proof gap. I'll fix that. Not buying consulting before I have paying users, but appreciate the observation.