u/Dynamo-06

I am not very technical so I've been using Lovable for quite some time now for my projects and I've realised that when I'm trying to make backend changes or I'm trying to fix bugs, the prompts still don't work even though I give proper structured prompts. It ends up telling me that the bug is fixed, but it is not fixed costing me credits. How do I make sure that the bug is fixed? Or how do I make sure that the feature that I'm trying to implement has been implemented correctly? (Sometimes it affects other parts of the app and I have to start again). I test extensively before publishing but it takes a lot of time to get it right sometimes and other times I am not able to make it work the way its supposed to.

Are you guys facing the same problem and what is the workaround that you have come up with?

I am not a coder but have always been a techie...I've tried the major vibe-coding platforms - Lovable, WeWeb, Emergent and Bolt. I ran into this problem that every vibe-coder eventually does: every time I used AI to build or fix something, at some point it touched code I couldn't read and I had no idea what else it quietly changed along the way.
That's why I started building this a visual, deterministic platform with my co-founder where AI never touches the code layer directly, only a fixed set of blocks, so you can always see exactly what changed and why.

I am looking for seasoned developers specifically to sit with it for 45 minutes and try to break it to figure out where the logic falls apart, where you wouldn't trust it, where it's obviously worse than just writing the code yourself. If you think the idea's bad, I'd rather find out now before we even decide to build it completely.
As a thank you for your time, I will send you a Rs.1000 Swiggy/Zomato voucher as a token of appreciation at the end of the meeting.

Comment if you're up for it and I'll DM you.

I am an airline pilot and a few years ago I tried to build a tool I required for my own work a duty-time calculator that was supposed to get a set of safety and scheduling rules right. I'm not an engineer but I understood the problem completely because I lived it every day. I knew every rule/ edge case and every exception.

I still couldn't build it and not because the logic was beyond me but because every tool I tried made me translate my problem into its language before I could do anything. I've tried the major no-code tools and I realised that I hit a ceiling on each one of them. The ones that could handle the complexity needed me to write code (I tried vibe-coding as well) or to hire someone who could. I understood my problem really well but the thing never got built.

That experience is why my co-founder and I have spent the last stretch building Ezyr.

The short version of what it is: a visual way to build real, operational software - the kind a business actually runs on with real logic and multiple users and that you can scale, customise, and maintain yourself, without getting boxed in or handed off to a developer the moment it gets serious. It's an early MVP. It's rough and it has bugs. I ain't here to sell you anything, there's nothing to buy. I'm looking for a small number of people to genuinely put it through its paces and tell me what they find.

Specifically, this is for you if: you've tried to build something operationally real on no-code or AI tools - real business logic, real users, the stuff that actually matters - and got stuck, hit the ceiling or got burned. Not landing pages and contact forms. The real thing that fell apart on you.

In return: early access and real input into where this goes while it's still early enough for that input to shape it. I can't promise a polished experience. I can promise your feedback actually reaches what we build next.

If you're this, then comment or DM me and tell me what you tried to build and where it broke. Let's talk :)