- The app works end to end for one core action, even if other parts are rough.
- You can name a specific person and the moment they need the app.
- You are willing to contact people individually and read their replies yourself.
- You can watch whether someone completes the core action and returns.
English
From a shipped app to its first users
You vibe-coded the app. Now find the first 20 people who need it.
Building got fast; finding users did not. Before a launch post, write who the app is for, make sure search engines and link previews can read it, choose one place those people already talk, and talk to them one at a time.
Qualification boundary
Market to a person, not to the internet.
An AI builder can produce a polished app in an afternoon, so polish no longer tells anyone why to use it. Start only when you can name who should care and when.
- You want guaranteed downloads, reach, rankings or revenue from a launch.
- You plan to sell the app itself on a marketplace; that is an asset sale, not finding users.
- You need App Store optimization, Product Hunt, TikTok or influencer campaigns run for you.
- You want automated mass messages, fake reviews or posts that hide that you built the app.
Smallest complete workflow
Two weeks from a live URL to evidence about real users.
Run the steps yourself or bring the context into Soloop. Each step produces something you can check before the next one.
- 01
Write the one-sentence promise
Fill in: [App] helps [specific person] [do one job] when [trigger]. 'Everyone who…' or a list of three audiences means you are not ready to market yet. Talk to people about the problem first, or narrow the sentence until one person clearly fits.
- 02
Check what crawlers and link previews receive
Open your public page's source or use Search Console's URL Inspection, and paste the link into the channel you will use. Each page needs its headline in the HTML, a unique title and description, and a working preview image. Check your builder's current documentation rather than older advice: Lovable says new apps render on the server and older ones get pre-rendered copies for crawlers.
- 03
Choose one channel for two weeks
Pick the single place where your person already asks about this problem: a subreddit, an X search, a community, or people you already know. Read its rules on self-promotion first. One channel keeps your results comparable; spreading across five gives you five tiny samples.
- 04
Start 20 individual conversations
Reply to a specific question with a useful answer, or message someone who described the problem, and disclose that you built the app. Ask about the last time the problem happened before you share a link. A broadcast post is not a conversation.
- 05
Watch the first use, not the signup
Offer to help each interested person complete the core action once. Note where they stop. Fix the step that blocks first use before you contact more people; more traffic will only meet the same obstacle.
- 06
Count separately, then decide
Record replies, conversations, first use, unprompted return and payment as separate counts with names or codes. After two weeks, keep the audience if people return, narrow it if only one type of person does, or change the promise if nobody completes the core action.
Inspectable control
Example approval card — one useful reply on X
This is an illustrative task card, not a claimed customer result or completed experiment.
- Objective
- Answer one person who asked on X how roommates can split grocery costs, without turning the reply into an advert.
- Action
- Draft one reply that answers the question on its own, mentions the fictional Splitlist app once with its link and says the founder built it. Publish from the connected X account only after approval.
- Target
- One public thread found through research. No direct messages, follows, likes, other threads or other accounts.
- Acceptance
- The reply is useful without the link; it discloses the founder's connection; it adds no user counts or savings claims; it fits in a single post.
- Stop condition
- Stop if the person asked for no recommendations, the thread is about something else, or the reply would only make sense as promotion.
Copyable two-week first-users log
Keep each count next to the people behind it.
Illustrative example: Splitlist is a fictional shared grocery-list app built with an AI builder. Every number below is invented to show the format; it is not a customer result or a Soloop output.
- One-sentence promise
- Splitlist helps roommates who share one fridge settle who owes what after each grocery run.
- Crawl and preview check
- Page source shows the headline and a unique title; the X link preview shows the right image. The pricing page reused the home page title, so it was fixed before outreach.
- Channel and rules
- One shared-housing subreddit and X searches for people splitting groceries with roommates. Rules read on day 1: self-promotion only in replies that answer a question.
- Conversations, days 1–7
- 20 people contacted individually; 9 replied; 6 described their last grocery split in detail; 4 agreed to try the app.
- First use and return, days 8–14
- 3 of the 4 created a shared list and logged one grocery run; 2 came back for a second run without a reminder; 0 paid because no price was shown yet.
- Decision
- Keep the roommate audience, show a price before the next 20 conversations, and fix the invite step that stopped the fourth person.
Decision scorecard
Each stage answers a different question.
A stage reached does not prove the next one. Keep them apart so a busy launch day does not hide that nobody came back.
Readable
Public pages return their content, a unique title and a working preview to crawlers and link scanners.
Reply
A person responded to an individual message or reply. Attention, not interest in the app.
Conversation
They described a recent instance of the problem in their own words.
First use
They completed the core action once. A signup without it does not count.
Return
They came back to the core action without a reminder from you.
Payment
Money moved. Track it separately even when the numbers are tiny.
Research proof format
What the current sources say
Sources checked October 21, 2026. Builder documentation describes current behavior and can change; commentary describes opinions, not measured outcomes.
Lovable says new apps use TanStack Start, which renders pages on the server, and that older React and Vite apps get pre-rendered copies of published pages for verified search engines, social preview bots and AI crawlers.
Older claims that AI-builder apps cannot be indexed may no longer apply. Check what your own builder serves before rebuilding anything.
Lovable FAQGoogle processes JavaScript apps in crawl, render and index phases, still recommends server-side or pre-rendering, and notes that not every bot runs JavaScript.
Link previews and other crawlers matter as much as Google. Test the channel you will actually use.
Google Search Central · last updated March 4, 2026Commentary on earning money from vibe-coded apps stresses distribution, a narrow audience and putting a price on the product early.
Treat this as practitioner opinion. The workflow measures your own replies, use, return and payment instead of borrowing statistics.
TechRadar ProSoloop documents research, X posts and replies through a connected account, Gmail outreach, Reddit drafts and Google Ads after setup and payment.
Soloop can help with steps 1–4 and the log. It does not run app-store, Product Hunt or TikTok marketing.
Soloop product manual · updated September 24, 2026Current product boundary
Plan with what actually runs today.
This is a small-sample workflow for finding first users. It does not estimate market size, forecast launches or guarantee indexing, reach or revenue. The Splitlist example is fictional.
Research
LiveFind communities, threads and public discussions with sources, and check page metadata you supply.
X
Connected accountDraft posts and replies and publish through the connected account after you approve them.
Gmail
Connected accountPrepare and send individual messages within your account's permissions and limits.
Find relevant communities and prepare posts or replies for you to review and publish.
App stores, Product Hunt, TikTok
Not supportedSoloop does not submit apps, run launches or manage creator campaigns on these channels.
Reach and revenue
Not establishedNo page check or message draft guarantees indexing, impressions, users or payment.
Continue the loop
Use the next resource when the decision changes.
FAQ
Questions before the next move.
How do I market a vibe-coded app with no audience?
Borrow an existing one: find the place where your specific person already asks about the problem, read its rules, and answer individual questions with useful replies that disclose you built the app. Twenty real conversations teach more than one launch post to nobody.
Can Google index an app built with Lovable or another AI builder?
Often yes, but check rather than assume. Lovable's FAQ says new apps render on the server and older ones get pre-rendered copies for crawlers. For any builder, view the page source or use URL Inspection to confirm the content, title and description are present.
Should I launch on Product Hunt first?
A launch can bring a spike of attention, but it does not tell you whether the right person returns. Launch after you know who comes back, so you can describe the app in their words and point to real use.
Will Soloop post and message people for me?
With connected accounts and your approval, Soloop can publish X posts and replies and send Gmail outreach. For Reddit it prepares drafts that you post yourself. It does not run app-store, Product Hunt or TikTok campaigns.
Bring the product you already have
Bring your app and one audience.
Copy this brief and replace the brackets. Start with a project opens Soloop's homepage; paste the brief there. It is not transferred automatically. Review the research before approving any post or message.
My app is [URL], built with [builder]. It helps [specific person] [do one job] when [trigger]. Help me (1) check whether my public pages give crawlers real HTML, unique titles and working link previews, (2) find three places where these people discuss this problem, with links and each community's self-promotion rules, and (3) draft five individual replies or messages and one useful post for my review. Show sources and unknowns. Do not publish or send anything without my approval.Start with a project