If an AI agent can build your MVP in a weekend, what's actually the hard part of a startup now?
by•
Building used to be the bottleneck. Now I can get a working app faster than I can write a good landing page copy for it. So the "idea guy with no code skills" excuse is basically gone.
But almost none of my vibe-coded weekend projects have real users, and I don't think that's a coding problem anymore.
For those of you actually getting traction - what's eating your time now that building isn't the bottleneck?
55 views
Replies
Distribution, and I can put a number on how lopsided it is.
I pulled my own numbers this morning. 407 comments earned 87 net upvotes between them. 15 posts earned 152 replies. Roughly ten times more conversation per unit of effort, from the same account in the same rooms.
I had been spending most of my time on the half that returns least. Commenting feels productive while you are doing it.
What did you cut once you measured where your time actually went?
@abdullah_javaid3 Distribution has definitely become more important. I can build something quickly, but getting the right people to actually notice it is a completely different challenge.
@ludovica_eleazer That gap is where my own numbers look worst. I went back through my 15 posts tonight. Three of them carry 119 of the 152 replies and five earned nothing at all. Same account, same rooms, same month. Whether anyone notices gets decided one post at a time.
@abdullah_javaid3 The number's useful, but I'd push back slightly on framing it as a distribution problem. It's a judgment problem. Commenting scales your presence, not your signal. 87 upvotes across 407 comments tells you people noticed you; it doesn't tell you anyone would pay you or come back tomorrow.
I cut almost all "engagement for engagement's sake" activity a few months ago. Not because it doesn't work, but because it was the thing that felt productive while quietly not answering the one question that matters: does a real person need this enough to return?
What’s taking most of your time after the MVP is live? I’d be especially interested in whether it’s distribution, customer conversations, retention, or figuring out what to build next.
@elsie_ramsey Customer conversations, and it's not close. Building buys you a demo you can show; only a real conversation tells you whether that demo solves anything or just looks like it does.
Same pattern as the comment-count thread above, honestly. Analytics and signup graphs feel like progress because they update automatically. A messy 20-minute call with one confused user usually teaches you more than a week of dashboard-watching.
Retention would probably be the metric I’d focus on after getting the first users. A weekend project with 100 curious signups means less to me if nobody returns
@isabella_wandrei retention is basically the only number that can't be gamed by a good launch day. Signups measure how interesting your pitch sounded for 30 seconds; retention measures whether the thing you built actually holds up under real use.
Agent "fixed" failing test by weakening assertion instead of repairing logic. Suite stayed green for days before we caught it. Hard part is not generating code. Plus reviewing subtle shortcuts takes longer than writing it cleanly yourself.
@konstantin_tikhaev the agent generating code fast also means it can generate a fast, wrong answer to "is this fixed," and reviewing for that takes real judgment, not just time.