You Built Everything. Nobody Came

More features felt like more value. It wasn't. Scattered is why nobody's using it, and the fix is constraint, most of it in your code.

I can spot it on a sales call inside five minutes. A founder built something real. Bubble, Lovable, Base44, Rork, a weekend of vibe coding. It works. And it does nine things.

I saw the first version of this when Bubble took off, and it's only gotten faster since. Founders went wild. They could finally build without an engineer, so they built everything. The logic felt right. More features, more value. Who says no to more. So they shipped all of it, and then they couldn't understand why nobody stuck around.

If that's you right now, the first thing to know is that it isn't your fault.

The freedom they sold you is the curse

Bubble, Lovable, Base44, Rork, and whatever launches next month all made you the same promise. Build anything.

Here's the part nobody says out loud. These tools make money when you keep building. Their business runs on your usage, your screens, your prompts, your hours inside the editor. Their incentive is your sprawl. The freedom they sell is the exact thing that buries your product, and they're paid to keep selling it to you.

You didn't make a discipline mistake. You used a tool built to remove the one constraint that would have saved you.

And it leaks money the whole way. Every time you fired off a prompt to fix something because you panicked. Every tweak here and there with no real reason behind it. A nudge to the layout, a color you second guessed, a redesign you ordered on a bad afternoon. Five cents here. Four dollars there. Forty five for the redesign. It sounds like nothing. When the app makes nothing, it's the most expensive habit you have. You're paying, by the prompt, to make the product harder to understand.

More features was never more value

Here's why all that building didn't make the product worth more.

A feature is only worth something two ways. It goes deep enough to be the best way to do that one thing. Or the specific person you're building for actually needs it. Most of those nine things were neither. They were shallow, and they were aimed at nobody in particular.

A feature your real user doesn't need isn't value. It's noise on the screen, one more thing to maintain, and one more reason the app can't say what it's for. You weren't adding value. You were adding fog, and paying by the prompt to do it.

Constraint is what cuts through

There are millions of apps. The ones that break out are not the ones that do the most. They're the ones that do a single thing so clearly that a stranger gets it in one sentence.

Focus is the whole game, and the tools you built on were financially motivated to talk you out of it.

This is the work I've done for fifteen years. Taking a scattered product and finding its center, then building the app so it can't drift off that center again. You know your customer. My job is to help you pick the one thing and own the engineering that points everything at it.

"Nobody's using it" is two problems wearing one costume

When the app stays quiet, the reflex is to blame reach. More ads, a growth hire, a TikTok push. Sometimes reach is the problem. Usually it's half the problem.

The other half is sitting inside the app, and it never shows up on an ad dashboard. It's what the app does in the first ten seconds. What it puts on screen one. Whether the thing a user came for is right there, or three taps down behind a menu full of the other eight things you built. Whether the notification three days later points at that thing or at nothing.

One half is messaging. Getting the right person to show up. The other half is product focus. Making sure the second they show up, the app points at the one thing they wanted. Your app is the funnel. Every surface says the one thing or buries it. Onboarding, the home screen, the empty state, the notification, the screen they land on when they return. If those surfaces don't all point at the same place, you don't have a marketing problem. You have an app arguing with itself, which is what nine features and no center always produces.

Founders treat the first half as a growth problem and the second as something that sorts itself out. It won't. It's a build decision, and on a vibe coded product nobody ever made it.

A paywall is a focusing tool, not a tollbooth

Most founders treat the paywall as something you bolt on at the end to start collecting. Used that way it's a tollbooth, and people route around it.

Used right, it's the sharpest question you have. What is the one thing someone is in enough pain about that they'd pay to make it go away. Answer that cleanly and you've found the center of your product. If you can't answer it, no amount of reach will help, because the thing you'd be driving people toward doesn't exist yet.

You still don't grow by nagging people to upgrade. You grow by solving the one pain so well that coming back is a reflex. The paywall just forces you to name that pain before you build around it.

What this looked like for one client

A client came to me with a utility app that did too many things. Real product, real build, going nowhere. Same pattern as everyone else.

We cut it down to one main feature. The single thing their best users actually opened it for. Then we put a paywall around that one painful problem, which forced the whole product to be honest about what it was for. Everything that didn't serve that pain came off the main path.

That fixed the product half. The messaging half was the ad creative. We iterated it until it stopped pulling in curious tire kickers and started pulling in the person who had that exact pain and stayed. Right person, focused product, one clear promise connecting them.

That's when the ad spend turned positive. Not before the focus. Because of it.

None of that is one job. Cutting the product is engineering. The paywall is engineering. Knowing which person to aim the creative at is judgment about a human you've met. You can't hand the whole thing to an ad agency, because most of it lives in the build.

Where AI fits, and where it doesn't

You can feel where this goes, because it's the same line I've drawn for five issues now.

AI is going to write your ad creative. It'll spin up the onboarding variants, draft the funnel, generate fifty versions of the home screen headline before lunch. Use it for all of that. That layer got cheap and you should treat it that way.

What it can't do is decide whether any of it works. It can't tell you which feature is the one your users came for, because it has never met your users. It can't tell you which person to aim the ad at, or which pain is worth a paywall. It doesn't know your best cohort came from one use case nobody planned for. It generates. It does not know your customer, and it does not know your business. Point all that cheap generation at the wrong feature and the wrong person and you've produced fifty polished ways to confuse the market faster.

AI isn't downloading your app. Humans are. The founder who knows their user's problem cold, says it in one clear line, and makes the whole product point at it is the one who breaks through in 2026. Everyone else is generating noise at scale and calling it growth.

Your move

If the app is quiet, run both halves before you spend another dollar on reach.

Product focus. Pick the one thing your best users actually open it for. Cut or bury the rest. Build the app so every surface points there and it can't drift back into nine features.

Messaging. Aim the creative at the one person who has that exact pain, and keep iterating until the people who show up are the people who stay.

The first is an engineering job that's been sitting unowned while you bought ads to send strangers into an app that doesn't point them anywhere. The second only pays once the first is done.

You don't have a traffic problem yet. You have a focus problem. More traffic just makes it more expensive.

The Cold Start, by Ken Vermeille. We build embedded senior engineering for product companies.

Forward this to your favorite founder.