Rakee Kumari

Every two-sided product has this moment: someone lands on your page and has to figure out which side they re on before anything else makes sense. One side has capacity to offer, the other wants access to it.

I ve cycled through three approaches and none of them feel solved:

Split hero, two CTAs. Clean in a mockup. In practice people read both columns, compare them, and stall. The decision gets heavier because you ve made it look like a decision.

One CTA, branch after signup. Converts better at the top. But a chunk of people pick the wrong path and have to back out, which is worse than stalling.

you want your AI agent to work without friction. you also want your platform to be secure. but here's the thing, those two goals are in direct conflict the moment a non-human actor shows up at your door.

most platforms weren't designed with agents in mind. so when an agent tries to access something, it either borrows a human's credentials which gives it too much, or gets blocked entirely which defeats the purpose.

Non-technical founder here, built my whole product with Claude Code. Everyone in this forum keeps saying the same thing UI and analytics get the "looks fine, ship it" treatment, but billing and auth get the paranoid line-by-line review. I've lived that.

Here's the twist though: my product IS the billing edge case. It's a tool that recovers failed subscription payments, so the entire thing lives in the messy world of declined cards expired cards, insufficient funds, bank 3-D Secure/SCA challenges that all look similar in the data but need completely different handling. Vibe-coding something where a wrong branch means someone gets emailed "your card was declined" when it actually went through was genuinely terrifying. I couldn't just trust the vibes.