Today I saw this at a YouTube video of young team working by slack with cursor and MCPs… for changes and updates of their site without even the engineer being there (good practice or not, they are moving and improving). While in my company we are stuck because of whatever bureaucracy and product definition. Don’t take me wrong I see the value of certain level of process but is a shift, I see how many are unlocking their creativity while others continue denying the transformation.
Velocity and ownership are all well and good, but the reason alignment is valuable is because a company has to maintain and fix all its products, regardless of who built them. How does that work at Lovable?
Whomever built things at first gets the first dibs at working/fixing. If that no longer makes sense, different person picks it up. It has been pretty seamless for now.
I have been working with a small team that ships fast and becoming more “AI native”. The problem that does not get answered in this hype of velocity is 1. Maintaining and improving what gets built and 2. Getting adoption. It not like our users can adopt new software every month. I would say building internal and replace existing tool will be different.
I would second these valid points and add, who addresses security, presentation, data management and the time consumed by users bouncing between different apps and tools that all look different (adoption), behave different, have different security criteria?
So when I read articles like this, I feel like the pieces that are left out are the pieces that likely have real impact but don't push the narrative forward.
couldn't agree more! this was a really fun read. and SPOT on. it's night and day difference between an ai-native company (employees) and a saas-era company (employees move MUCH slower).
Totally aligned on this. We're living the AI-native reality right now - our PM/UX team defaults to Lovable for prototyping, and it's completely changed our velocity. What you describe about ownership and autonomy really hits home. Our team builds instead of writing docs nobody reads or sitting through endless alignment meetings.
Having said that, do you have any runbooks or best practices for your team to follow when taking Lovable prototypes to production with minimal friction?
Fascinating perspective. From what I’m seeing in Peru (especially in financial services), corporations are still far behind on enabling innovation through AI. Bureaucracy and rigid processes make it incredibly hard to move fast or adopt an AI-native mindset. It makes me wonder how big the gap will be when these AI-native employees really start coming into the workforce. Thanks for sparking this reflection — will definitely be sharing!
great one! Although I don’t think that the culture stems only from being AI native, it’s an amplifier but not a direct root cause. In order to achieve this kind of dynamics you need to create a team of empowered hackers with a strong bias towards action and total autonomy. The companies like that existed before but rarely achieved such hyper growth while still at the hacker stage - this is where ai walks in as the key catalyst IMO.
The holy grail is to preserve it at scale - would love to see more reads on that every few company milestones :)
Great post, thank you! What do you believe is the future of (ux) research in these organisations? Typically the selling point is to reduce risk in investing in building efforts that don’t meet needs or aren’t built in the right way. This still exists, but to a lesser degree
This is a great bts of lovable. Thanks for sharing it, Elena. Is there a specific criteria Lovable uses to hire new employees ensuring they will be ai-native? Also are there any checks or and balances to ensure ai usage doesn’t go off rails?
48 here and AI first - not sure about build fast :) but I am breaking stuff...is that still ok?
You speak truth and pull no punches. Looking forward to moving at AI Native speed in the Enterprise.
Today I saw this at a YouTube video of young team working by slack with cursor and MCPs… for changes and updates of their site without even the engineer being there (good practice or not, they are moving and improving). While in my company we are stuck because of whatever bureaucracy and product definition. Don’t take me wrong I see the value of certain level of process but is a shift, I see how many are unlocking their creativity while others continue denying the transformation.
i'm not saying process is not needed. but process needs to be built up from the ground up, not forced from top down onto this new way of working...
Velocity and ownership are all well and good, but the reason alignment is valuable is because a company has to maintain and fix all its products, regardless of who built them. How does that work at Lovable?
Whomever built things at first gets the first dibs at working/fixing. If that no longer makes sense, different person picks it up. It has been pretty seamless for now.
I have been working with a small team that ships fast and becoming more “AI native”. The problem that does not get answered in this hype of velocity is 1. Maintaining and improving what gets built and 2. Getting adoption. It not like our users can adopt new software every month. I would say building internal and replace existing tool will be different.
I would second these valid points and add, who addresses security, presentation, data management and the time consumed by users bouncing between different apps and tools that all look different (adoption), behave different, have different security criteria?
So when I read articles like this, I feel like the pieces that are left out are the pieces that likely have real impact but don't push the narrative forward.
couldn't agree more! this was a really fun read. and SPOT on. it's night and day difference between an ai-native company (employees) and a saas-era company (employees move MUCH slower).
ps - I wrote some similar thoughts recently, where I talk about, what I call "AI-Native Workers": https://www.thesignal.club/p/why-building-ai-native-is-the-biggest
Totally aligned on this. We're living the AI-native reality right now - our PM/UX team defaults to Lovable for prototyping, and it's completely changed our velocity. What you describe about ownership and autonomy really hits home. Our team builds instead of writing docs nobody reads or sitting through endless alignment meetings.
Having said that, do you have any runbooks or best practices for your team to follow when taking Lovable prototypes to production with minimal friction?
I’m living through the same thing and can definitely relate.
Fascinating perspective. From what I’m seeing in Peru (especially in financial services), corporations are still far behind on enabling innovation through AI. Bureaucracy and rigid processes make it incredibly hard to move fast or adopt an AI-native mindset. It makes me wonder how big the gap will be when these AI-native employees really start coming into the workforce. Thanks for sparking this reflection — will definitely be sharing!
great one! Although I don’t think that the culture stems only from being AI native, it’s an amplifier but not a direct root cause. In order to achieve this kind of dynamics you need to create a team of empowered hackers with a strong bias towards action and total autonomy. The companies like that existed before but rarely achieved such hyper growth while still at the hacker stage - this is where ai walks in as the key catalyst IMO.
The holy grail is to preserve it at scale - would love to see more reads on that every few company milestones :)
The future is about to be evenly distributed 🚀🚀🚀🚀
Great post, thank you! What do you believe is the future of (ux) research in these organisations? Typically the selling point is to reduce risk in investing in building efforts that don’t meet needs or aren’t built in the right way. This still exists, but to a lesser degree
This is a great bts of lovable. Thanks for sharing it, Elena. Is there a specific criteria Lovable uses to hire new employees ensuring they will be ai-native? Also are there any checks or and balances to ensure ai usage doesn’t go off rails?
This was terrific.