From 0 to 1 Paying User: Cold-Starting a Vibe Project Is Interviews, Not Marketing
AI made building 10x faster but not finding users. Your first paying user almost never comes from Product Hunt or a viral tweet — it comes from 20 one-on-one interviews. What to ask, and how to turn 'interesting' into payment.
A counterintuitive conclusion first: in the vibe coding era, an indie developer's scarcest skill isn't building the product — it's finding the first person willing to pay. AI drove build costs near zero, so the bottleneck moved upstream: you used to worry about not being able to build it; now you worry nobody wants it. And the way to get the first paying user hasn't changed in a decade: not posting, but talking.
Why 20 interviews
The number isn't made up. Five interviews get you politeness, ten start showing repeated patterns, and only past twenty can you separate real pain from fake demand. Key rule: don't interview friends — friends only say "looks nice." Go where target users actually hang out — niche communities, Slack/Discord groups, local meetups — and find people actively suffering from the problem.
Ask only three kinds of questions: how do you solve this today (understand existing alternatives), when exactly did this annoy you last week (demand concrete stories, not abstract opinions), and what outcome would you pay what amount for (anchor willingness to pay). Never ask "what do you think of my idea" — the most useless question ever; everyone says it's great and forgets by tomorrow.
Three levels from "interesting" to payment
Hearing "interesting" in an interview counts for nothing. Real validation signals come in three levels. Level one: they offer to introduce someone else with the same problem (referral willingness). Level two: they'll spend 30 minutes trying your rough demo (time investment). Level three: they'll prepay, even at a half-price presale (money vote). Only level three validates the demand.
Here's the vibe coding era's unique edge: interviews-to-demo used to take weeks; now AI lets you ship a clickable prototype the same night and send it over the next day. Compress the interview–prototype–feedback loop under 48 hours and your learning velocity is 10x everyone else's. This — not writing code per se — is the loop AI should actually accelerate.
The first paying user's profile
Don't think "target segment"; think "that specific person." The first paying user usually has three traits: deep enough pain (the problem recurs weekly), budget (personally affordable or reimbursable), and tolerance for roughness (willing to use a half-baked product). Your first ten users are essentially co-creators: give them founder discounts, a private channel, direct say over the roadmap — they're paying not just money but the patience to grind the product into shape with you.
On pricing, don't overthink user number one. Pick a price "slightly expensive but quotable" — say $19/month or $199/year lifetime. Too cheap attracts freebie hunters; too expensive and you can't say it with a straight face. Remember: the first paying user's meaning isn't revenue, it's proving the proposition "someone will pay for this problem." Get that one, and users two through ten are just replication.
The most common ways to die
Number one: "build first, find users later" — three weeks of AI-crafted polish, a social media launch, 50 likes, zero payments. Number two: "performative interviews" — asking five friends, all saying it's great, concluding demand exists. Number three: "free users as validation" — "we already have 200 free users" — free-user behavior barely predicts willingness to pay; stop fooling yourself.
One line: in the AI era everyone builds fast; the unglamorous work of finding users is the real moat. Go talk to 20 people first, then come back and write code.
Related articles
Every vibe project eventually needs scheduled jobs: daily syncs, expired-order cleanup, billing reconciliation, scheduled reports. AI's first version is usually setInterval — fine for dev, fatal in production. This guide maps four scheduling options, cron expressions and timezone traps, idempotency, distributed locks against overlap, failure retries and alerting, run-log observability, and cron endpoint auth — plus a launch checklist.
Every vibe project hits the same moment: a list page firing a dozen DB queries per load, the database melting under modest traffic. This guide starts from the three-question caching mindset, then layers HTTP cache headers, Next.js data caching, Redis application caching with key design and the penetration/breakdown/avalanche defenses, and AI result caching (semantic cache, prompt caching), plus invalidation strategy and a launch checklist.
Traffic is moving from the search box to the AI answer box. A vibe coder ships a product in a week — and nobody finds it. This guide turns the SEO fundamentals (sitemaps, JSON-LD, Core Web Vitals) and the new AI-discovery toolkit (llms.txt, per-page Markdown versions, FAQ schema, agent-readable pricing and API docs) into a shippable 30-day checklist. The core judgment: how well you document sets your product's ceiling in the agent economy.