
building @vibedraft_app - the Agentic GTM Engine: https://teapaw.org/t.co/T5EMemxynl vibe coding myself to financial freedom. learnings and lessons a long the way.
Boston
Joined December 2023
- Tweets12.4K
- Following3.2K
- Followers2.2K
- Likes12.6K
i interviewed 125 founders about how they landed early customers.
the ones who grew fastest didn't send cold traffic to a landing page, they replied to real threads and let people click through on their own.
a landing page converts strangers once they're already curious. a reply converts someone still deciding.
which one actually gets you a first paying customer: the perfect landing page, or the reply that meets someone mid problem?
asked 125 founders where their first buyer actually came from.
the ones pitching in indie hacker subreddits were selling to other builders, not buyers.
the real buyers showed up in product hunt comments and show hn threads, admitting what was still broken in their stack.
that admission is the lead, not the subreddit post.
most founders pick a channel last, once the product's already built and all that's left is deciding where to post the launch.
i keep wondering if that's backwards, if channel should shape what gets built in the first place.
does channel choice matter before an audience exists, or is it irrelevant until there are readers to push something to?
Ricky retweeted
Replying to @Shraddhaship
One way would be through constantly searching for people talking about the pain that your product solves!
Monitor pain keywords and terms across Reddit, X etc and then reach out to those people by replying, or Dming.
Thats called the Pain Finder playbook on VibeDraft.
There are other playbooks as well, like listening to your competitors social media and go after the people that are responding to their social media posts.
Another playbook would be creating blog posts around your niche for SEO and AEO. One thing to do is search what your product does in ChatGPT and Claude. Notice and take notes on what gets cited in terms of solutions or articles. Take those articles and capture the keywords and the discussion topics and create your own blog posts around those. Keep monitoring the AI search and optimize each day or week until you get cited.
This and more is what I’m building in VibeDraft. Repeatable playbooks that can be automated to drive customers to your product.
the person who needs your product never types your product's name into search. they type the problem, in plain words, frustrated.
find that exact thread. answer it straight, no link, no pitch.
mention what you built only if someone asks what you used. by then the room already trusts you.
before replying to a dm about your product, run three checks:
- does their bio name an actual problem, or just the word founder with nothing behind it
- does their link lead to something live, or a dead page and a year old waitlist
- are they asking what you built, or already trying to sell you something
skip the first two checks and you'll spend an hour talking to someone who's not buying, just angling for a follow.
4 shipped products took 3 full rewrites before one of them had a paying customer behind it.
v2 always looks safer than v1. neither one has ever shipped you a customer by itself.
unfinished code with people watching wins over perfect code with nobody there.
ship the rough version while someone's still looking.
karpathy built a youtube clone in ~2 hours this weekend
he got tired of clickbait recs, so he built a site with only the videos hacker news commenters keep telling each other to watch
here's how he did it:
1. grabbed the full hacker news archive from hugging face
→ every story + comment since 2006, ~43M comments, free to download
2. had claude filter it
→ kept only comments linking to youtube
→ ran a cheaper model (sonnet) over them to drop spam and keep real recommendations
→ ~40K comments → 6,454 videos across 150 topics
3. pulled video metadata from the youtube api
→ his one manual step: creating a google cloud api key
4. had claude build the ui
→ youtube-style layout
→ thumbnail = a frame from the middle of the video, not the clickbait one
→ "for you" recs with no login, stored in your browser
→ keyboard shortcuts
5. shipped it
→ he booted a vps and bought the domain
→ gave claude the ip and said "update, secure, harden, deploy"
6. published the data
→ one zip so anyone can point their agent at it and build their own version
his total hands-on work: an api key, a server, a domain
the pattern:
trusted community + public data dump + cheap model as a filter = a curated product in an afternoon
so what else can this be done for?
books hn recommends?
tools indie hackers actually use?
podcasts? papers? github repos?
what would you build with it?
most of my week used to get split across x, reddit, and whatever directory felt urgent that day. none of it compounded.
picking one channel and sitting in it for a full quarter feels like leaving reach on the table, right up until it doesn't.
which single platform are you locking in for the next 90 days, and what almost pulled you somewhere else instead?
i shipped 4 products before one of them got a paying customer. each rewrite felt safer than the last.
rough code with people watching beats perfect code with one name on a waitlist.
the audience is the asset. the codebase is just packaging.
pick which one you're actually building.

