So You Vibe-Coded an App. Now What?

You did the thing. You had an idea on a Tuesday, you opened an AI coding tool, and by the weekend you had a real app. Auth works. The database is wired up. It is deployed at a URL you can actually send to people. A year ago this would have taken you months or a small team. You did it alone, fast, and it feels a little like magic.

Then the high wears off and a quieter question shows up. Now what? You have a working product and a dashboard that says zero users, zero dollars, and no one on earth who knows it exists. This is the moment nobody makes a video about, and it is the moment that actually decides whether this becomes a business or another tab you stop opening.

Where does the money actually come from?#

The money does not come from the app. The app is just the mechanism. The money comes from a person deciding that the pain of their problem is bigger than the price you are asking, and handing you money to make that trade. Every step before that is you trying to find those people and confirm the trade is real.

A specific person with a painful problem
        |
   they hear about you (a conversation, a post, a referral)
        |
   they try the thing you built
        |
   it removes enough of the pain
        |
   they decide it is worth the price
        |
        v
   they pay you  ->  revenue

Read that chain top to bottom. Notice that the code you are proud of is one small box near the middle, and every box around it is about people, problems, and reach. When a solo app fails, it almost never fails at the "it works" box. It fails at "a specific person with a painful problem" (you guessed at a problem nobody actually has) or at "they hear about you" (real problem, but you have no way to reach the people who have it). If you want the longer version of how these pieces connect into revenue, where online money comes from walks the whole chain.

The move this week is to work that diagram backward. Instead of starting from your app and hunting for someone to use it, start from a person you can actually reach and work toward whether your app removes enough pain that they would pay.

How it actually works#

The mechanic that turns a weekend project into a business is embarrassingly old-fashioned: you talk to people one at a time until the picture gets clear. Not a survey. Not a launch tweet. Conversations.

It works because a real conversation gives you three things a dashboard never will. You learn whether the problem is real and how much it hurts. You learn the exact words people use for it, which becomes your marketing copy for free. And you occasionally get the most valuable signal there is, someone asking "wait, can I actually use this," which is a buying signal wearing a question mark.

The reason this beats broadcasting when you are starting from zero is simple math. You do not have an audience, so a post reaches almost no one. But you can start ten conversations today with people who already have the problem, and ten focused conversations with the right people teaches you more than ten thousand impressions from the wrong ones. Validate your idea before you build covers the discovery side in depth, and the nice thing is you can run that validation and your actual product at the same time now, because the product already exists.

A simple example with numbers#

Let me make this concrete with a clearly hypothetical scenario. None of these numbers are a promise or a typical result. They are just here to show the shape of the thing.

Say you vibe-coded a small tool that turns a messy spreadsheet of client invoices into a clean monthly report. You decide the narrow user is freelance bookkeepers who serve small local businesses, because you happen to know two of them.

You spend a week finding and messaging bookkeepers, one at a time, in a couple of niche communities and through those two contacts. Imagine you reach 30 people. Ten reply. You have real conversations with six of them. Four say the problem is annoying but they live with it. Two say it eats a Sunday every month and they would genuinely pay to get that Sunday back. One of those two, after seeing your tool, pays you a hypothetical $29 for the month.

That is one paying customer and $29. It looks like nothing. It is not nothing. You now know the exact segment that feels the pain, the words they used ("it eats my Sunday"), the two objections the others raised, and that at least some people will pay. That is worth more than a thousand anonymous signups, because it tells you exactly what to build next and exactly who to say it to. Get your first 10 customers is the natural next read once you have proven the first one is possible.

What you need#

You need less than you think, and most of it is not technical.

Required. A working version of the app (you have this). One narrow user you can actually describe and reach. A list of 20 to 40 specific people or places where those users hang out. A way to take payment, which for a first sale can be as simple as a Stripe payment link. And a couple of hours a day for conversations and follow-up.

Optional. A rough landing page that explains the problem in the user's words. A simple way to track who you talked to and what they said (a spreadsheet is fine). A short demo video.

Nice to have, and genuinely not needed yet. A polished brand, a logo, a pricing page with three tiers, a waitlist, a Product Hunt launch, and any of the growth tactics you have bookmarked. All of that is premature until one real person has paid you.

The skill you actually need to build this month is not coding, it is talking to strangers about their problems without pitching. That feels harder than shipping the app, and for most builders it is. It is also the whole game.

What it costs#

In dollars, close to nothing. Hosting for a small app is often free or a few dollars a month, and a payment link costs you only a percentage of money you have not made yet. You do not need paid ads and you should not run them yet, because ads amplify a message, and you do not know your message works.

The real cost is different and heavier. It is the discomfort of putting your thing in front of people and hearing that they do not care. It is the ego cost of learning your favorite feature is irrelevant and the boring one is the reason someone would pay. Budget for that, because it is the part that stops most people. If money is genuinely your constraint, how making money online works lays out why the cheap-to-start paths still cost you time and rejection instead.

How long it takes#

Do not let anyone sell you a fixed timeline. What actually controls the speed is how narrow your user is and how directly you can reach them. A tightly defined user you already have access to can produce a paying customer in a week or two. A vague "anyone who works online" user can burn months and never get there, because you cannot find "anyone."

A reasonable rhythm for the first 30 days looks like this. Week one, pick the narrow user and write down the problem in their words. Week two, build your list and start conversations, aiming for a handful of real ones. Week three, keep talking and start asking the people who lean in whether they would use it, then let them try it. Week four, ask for money from the ones who are clearly in pain. The goal is not ten customers by day 30. It is one, plus a clear read on whether more exist.

What beginners usually get wrong#

The most common mistake is treating the working app as the finish line. It is the starting line. Shipping felt like the hard part, so it is tempting to believe the hard part is done. It is not.

The second mistake is building for everyone. "It is for anyone who manages projects" is not a user, it is a fog. You cannot find, message, or convince a fog. Picking a narrow first segment is the single highest-leverage decision here, and going narrow feels wrong precisely because it feels small.

The third mistake is hiding behind more code. The dashboard says zero, that feels bad, and the fastest way to feel productive again is to open the editor and add a feature. It is a very comfortable way to avoid the actual work, which is talking to people who might tell you no.

The fourth is confusing signups and likes with demand. Free interest is cheap and lies. The only vote that counts is a payment. Someone who says "cool, I would totally use this" and never pays has told you nothing.

How I would start#

If this were my weekend project, here is the exact sequence I would run.

First, I would write one sentence: "This is for [very specific person] who struggles with [very specific problem]." If I could not fill in the blanks with a real, reachable person, I would treat that as the actual problem to solve before anything else.

Second, I would make a list of 20 to 40 specific people or places (communities, forums, group chats, people I already know) where that person exists. Names and links, not categories.

Third, I would start conversations, not pitches. I would ask about the problem and how they handle it today, and I would shut up and listen for the words they use. Cold DMs that are not spam is worth reading before you send the first one, because the difference between a message people answer and one they ignore is mostly about leading with them, not you.

Fourth, when someone clearly has the pain, I would show them the app and let them try it on their real situation. Fifth, for anyone who lit up, I would ask for the sale plainly: "It is [price] a month, want me to set you up?" The first yes is the whole month's goal.

What I would not do#

I would not run ads. I would not build a waitlist. I would not add a second feature until the first one has been paid for. I would not spend three days on a logo or agonize over pricing tiers, because I do not have a customer to price for yet. I would not do a big public launch, because launching to an audience you do not have is just shouting into an empty room, and it wastes the one launch you get. And I would not keep the app a secret while I "polish it," because polish is often just fear wearing a productive costume.

Close#

Building the app was the part that used to be impossible and is now almost easy. That is genuinely worth being proud of, and it is also the reason the working app cannot be your edge anymore. The edge is finding the person who needs it and reaching more people like them, and that part is still fully manual, still uncomfortable, and still where almost everyone quits.

You are closer than you think. You have the thing most people never finish. What is left is not more building, it is the courage to put it in front of real people and ask an honest question. Start with one narrow user and one conversation today. When you are ready to turn that into paying customers, the first-customers plan is where this goes next.