Erika

Vibe coding is fantastic for getting something working fast - but there's always a point where it starts to struggle.

For me it was when I tried to add proper auth to a project that didn't have it baked in from the start. The AI kept suggesting patches instead of a real solution, and eventually I was chasing one fix into the next.

As a solo dev, I can't afford to ship something and then realize it's unprofitable. But estimating token usage before launch is hard.

Do you just... guess? Build a prototype first? Or is there an actual way to forecast what users will actually cost you?

Hey everyone, I'm the founder of OsmO.

Quick story on why I'm here: I kept missing calls that actually mattered (a callback from a clinic, a client trying to reach me) because they were buried under spam and robocalls I'd long stopped answering. The habit of just letting it ring was quietly costing me real things.