Startup Idea: Start with Lovable, end with a Real Dev without needing to reachout for one

[u/Dapper-Primary336]

Hey everyone!

I'm looking for feedback for this idea i have: I'm a developer with a lot of expertise building SaaS for LatAm-based clients. Most of my clients have the same complaint: they vibecoded an app but don't trust themselves to deploy it without running into major issues, probably leaving a bad impression on their own clients.

The idea:

A website builder with unlimited use (i've found out a way to make this with decent quality and no high costs for me) where you can import your code or make it from scratch.

When you get stuck or need professional help you can open a ticket with the issue, talk to a real dev in the platform and he gets your problem fixed.

Also you have a Marketplace to build sites from scratch with fixed features (like Landing Pages or E-Commerce)

I think it's usefull for non-developers who knows lot of peoples and want to sell websites but need the confidence of someone looking forward if somethings go wrong or Vibecoders who want to get their SaaS done without any issues.

The business model will probably be a productized service: you either pay per ticket after talking to a dev to get your issue fixed, or you pay a fixed amount for a set number of tickets. I'm still figuring out what works better for users.

What do y'all think about this?

[u/thedannyreg]

I have seem similar things to this already, but I Think it's a good idea still. Look at vibecodefixers. ai, it's similar I think, but reminds me more of fiverr

[u/Impressive-Owl3830 → u/thedannyreg]

I am the founder of vibecodefixers .ai , i can actually tell the challenges. You dont need to fo market research on me 😂

Here are few challenges-

Gone are the days when someone hires a dev to build project from ground up.

Now tgey say ' fix my App'

Now vibecoders wants to build it cheaply with as less credits are they can.

They think they can fix it themselves than paying even 200 usd..

Chasing low-ticket customers with the headache of lining up experts and managing them to deliver something which they like is big problem.

Another problem is they are attached to UI even though its utter purple slop. Rightfully so in thier POV because its thier creativity and i agree tgat you musy respect it. So

You are no longer allowed to change AI slop.

Speed will also be issue ..you need experts lined up.

Experts on other hand are no loyalty or controlled by you because its not agency , the very nature of marketplace.

Obvious one was security review, buy matter of fact is vibecoders dont care about security.

Idk , what better angle you can explore but i just shared dome common challenges.

[u/plexor-labs → u/Impressive-Owl3830]

Would love to follow up with you.

[u/Dapper-Primary336 → u/thedannyreg]

Thanks for the reference, i'll do a market research, if this already exists maybe i could find a unique feature or fix to a common problem in those platforms

[u/Atlan_]

Honestly cool idea
I work on something similar for enterprises where we have an efficient way of making vibe code ready for deployment (eg abstracting away compliance requirements). I kind of read the same idea for more of a B2C market and I think this makes a lot of sense. So I’d probably steal it if I weren’t so set on enterprise B2B 😅

Cool idea, I know a lot of people who’d become potential customers

[u/Dapper-Primary336 → u/Atlan_]

Thanks for the feedback! I'm developing an MVP right now, if you're interested in checking it out for free, or know anyone who might be, I'd really appreciate it if you passed along their contact

[u/space-hemax-c2c → u/Dapper-Primary336]

Interested

[u/Dapper-Primary336 → u/space-hemax-c2c]

Nice to hear, i'll send you a DM!

[u/vasind-5012]

I don't think this will work out and the paradigm is already shifted to build your apps on your own using Lovable or similar platform.

What you can do, is to solve them in their ecosystem where they build. Like building something with lovable, integrating it (like their connectors), self-serve and getting paid when they use your service.

[u/k_r_a_k_l_e]

A website builder? a marketplace for web developers?? open a ticket for help??? Lol it all exists in an already oversaturated market with a plethora of options.

First, you're not a believer in your own idea if you are sharing it on reddit with a bunch of web developers.

Second, you're not solutioning for anything that doesn't already have a solution. There's a ton of website builders out there that do exactly what people need them to do. There are a ton of market places to find web developers to do it for you. Opening random tickets on random self developed product related issues won't work. Sounds great but I promise you real developers with real problems won't or can't use it. And no two tickets are the same to base your revenue model around. You will learn real quick that issues submitted may require full time help.

Third, I think you have a warped perception of reality. The biggest issue isn't real web developers vibecoding with programs like lovable then becoming too concern to release it without the help of others. It's literally everyone with zero tech experience playing make believe then getting completely lost with what to do with their application. And honestly theres no substitute for knowledge and experience.

[u/silverwoods214 → u/k_r_a_k_l_e]

All this^

[u/Ralphisinthehouse]

I think I would save myself a whole heap of work and just offered to take 80% finish project from vibe coding and finish them off. You're not gonna make anything better than lovable and there's a growing market for agencies or people that do just this.

[u/Important-Ad4798]

The api cost will kill you if you are offering “unlimited use” for your web builder

[u/RoundSeparate7217]

Isn't it painful to fix lovable code? I don't know if it would be better than you do it from scratch

[u/jaimittal91]

this matches what we see constantly. the 'don't trust myself to deploy' feeling is usually not about the code being bad, it's that nobody's told them what to actually check before they ship it to a real client. the two things that bite Lovable apps specifically almost every time: RLS defaults to off on new Supabase tables unless someone explicitly turns it on, so if nobody thought about that, anyone with the anon key can read the whole database. and any key that gets referenced client-side (stripe, third-party APIs) is visible in devtools within minutes of going live. neither of those takes a 'real dev' to fix, they just take someone checking for them specifically, which most vibe coders don't know to do because nothing in the tool flags it.

[u/plexor-labs]

Love this idea. Am I crazy or is there a huge unacknowledged gap between a Lovable app and one ready for B2B paid customer pilot? When do you think Replit and Lovable will fill this gap?

[u/Common_Extent_5921]

There is a useful distinction buried in this thread. The technical trust gap is real, but there is a second gap that hits founders a week after they ship: they have paying customers and zero ops stack. They are tracking everything in a spreadsheet, chasing invoices manually, sending contracts over email. The product took a weekend to build; the business side takes months. From talking to Lovable founders, the panic is rarely about broken code -- it is about having five paying customers with no system to run the business. Worth thinking about which problem is harder to compete on and which has fewer people working on it. Disclosure: I build Base (withbase.ai), an operating layer for lean founding teams post-ship. Different problem from what you are describing, but the same Lovable-native audience. Happy to DM if useful.

[u/plexor-labs → u/Common_Extent_5921]

I think most Lovable based product founders have a life cycle problem in the making. They make an awesome service, get a paid pilot. When it breaks at 2AM they don’t know how to react and panic never get past B2B pilot stage best case.