So much cool stuff, but I’m gonna be a party pooper and say I’m really excited for branching.
I hope this enables not-solo developers to scale safely. Any hints on what the branching features we be like?
2 Likes
Personally, if I were WeWeb, I would have taken a page out of Xano’s playbook and built out skills, agents, and an MCP server that allows your AI model and IDE of choice to interact directly with WeWeb to build out the UI, workflows, etc.
I know you guys tried to tackle AI yourselves, but the world is changing far too fast right now for that to work with the resources you have available. You need to be agnostic nowadays with the leading model sometimes changing on a weekly basis.
Right now there’s not a great solution where you can build a majority of the UI and logic with AI, but then fine-tune in a familiar, easy to use visual editor.
WeWeb could easily fill that void if you leaned in, which I do believe was the original intention. At the time it was probably a bit too early with the models available at the time. But the models are here now, and WeWeb is stuck on the sidelines.
I love the platform and the potential, but I question the direction at times. For example this decision to spend many months on a backend when there are plenty of other amazing backends that offer easy integrations and have large teams to constantly ship new features.
I could somewhat see the target market you were trying to appeal to, but with Claude Code and everything that is coming out every day and week, that pool of customers is shrinking by the day. It’s just easier to do many things fully via AI now than spend hours or days working around WeWeb errors with very limited documentation and support.
Really disappointed to hear that SSR was not prioritized when it was clearly the number one request from countless people on the live stream. I would be really curious to see those survey results.
Also this is probably the first company I’ve ever dealt with that had zero interest in selling an enterprise plan. It was always “check back in X months, we can’t take on new enterprise clients or fix existing bugs right now.” No proactive follow-up. So I would circle back only to hear about some new initiative that had the entire team heads down for months again, which would inevitably get delayed. Rinse and repeat.
I say all of this because I actually want to see WeWeb win. The foundation is there. The opportunity is there. It just needs the right focus before the window closes.
5 Likes
Thanks for your message! I know it may feel like we are “stuck on the sidelines” since we haven’t released anything meaningful in months, but that is because what we are working on now will be a complete revolution for our product and for the no-code/AI space in general. It takes time.
No model today is powerful enough to understand and use WeWeb as-is. The only way to make it work is through a complex agentic system that we are currently building. Xano, fortunately for them, doesn’t have to deal with the front-end which makes their lives much easier.
The first results are very promising and once we have a functional AI system in our product, we will finally be able to fill the void you are talking about. Later, we will be releasing a headless CLI for agents to use WeWeb in autonomy. It is going to be great.
As for the backend, this will be optional and won’t affect users who prefer other options. However, offering a plug-and-play backend directly within the product is clearly critical to our vision and will make the lives of the vast majority of new users far simpler.
The whole team is heads down, and we should be able to pull back the curtain on the new AI and full-stack experience in Q2. I hope it won’t disappoint.
Finally, regarding enterprise contracts, we sign new ones every quarter, some of them quite large. However, we make it clear that we can’t provide custom development or dedicated support. These large clients typically purchase many seats / apps, along with custom SLAs for security and compliance. For support, they work with a network of partners we connect them with and contract directly. If this is of interest to you, feel free to reach out to me directly at raphael@weweb.io.
3 Likes
Thanks for the detailed response Raphael, genuinely appreciate you taking the time.
Excited to hear about the AI and full-stack direction. I’ll be watching Q2 closely and rooting for you guys.
On the enterprise side though, I want to clarify because I think there may be a disconnect. We were never looking for custom development or dedicated resources. We were running into confirmed WeWeb bugs that were development blockers that would take weeks or months for support to resolve, and with 2,000+ internal employees using a WeWeb app daily, that would be a real problem at our scale.
Support told us that bugs were prioritized based on how many users they impacted, and that enterprise customers would get priority on bug fixes along with Slack-based support. So we said great, let’s do it. Were told to wait a few months because the team was heads down on one initiative. Checked back, told to wait again for another initiative. Replied to one of your posts about a year ago where you mentioned having resources to onboard enterprise clients like us, so I immediately reached out to sales. Sales came back and said sorry, we know Raphael said that but we still don’t have the capacity.
It sounds like the enterprise plan may have evolved since then into something more focused on seats, SLAs, and partner networks. That’s totally fine if that’s the direction. But I wanted to share that experience because the original ask was pretty straightforward and we just never got past the waiting stage despite multiple attempts over a long stretch of time.
Again, I say this because I want to see WeWeb succeed. The platform has a ton of potential and I’m hopeful the AI work pays off in a big way for you guys.
1 Like
Super clear, thanks for sharing your feedback, and sorry about the mess. If you’re still considering a custom agreement, feel free to drop me an email and I’ll take it forward with you personally.
Thanks a lot for your support, it’s greatly appreciated!