We now have our design system in newly organized highly detailed Figma.
I’m curious if - with respect to colors & text styles (not components) - that are all named specifically and have tokens inside Figma etc - we can use the co-pilot to bring these into the library (it’s pretty massive). If so … how?
So … I just wanna say … removing real pain points is way, WAY more important than “sorta almost kinda working but not really working and not ready yet but we will get there and it will eventually be awesome …”.
I know nothing … but if I did … I would probably say something like …
Ask your paying customers what their actual pain points are. (ever import icons in WeWeb? Branching?)
Do #1 AGAIN. Slowly. Let it sink in.
Address those pain points as 1st PRIORITY. Period. Full stop. Bring your paying customers as much joy as possible. THEY are your #1 sales funnel. They are worth more than ANY marketing budget.
Invite more paying customers into an actual BETA that lasts long enough to get meaningful data. Do NOT release until you have solid feedback and validation. Be careful who you invite into your beta. You need people who will REALLY kick the tires and be honest with you. The only feedback that matters at all is the NEGATIVE feedback.
WeWeb is an awesome product with massive potential. And I suspect the team is really passionate and busting their ass behind the scenes … but there are just so VERY many low hanging fruit pain points you could crush that would would make customers soooooo happy while you BETA big new “game changing” stuff. Most of us could care less about “game changing new stuff”.
We want less pain points. And we will naturally be pulled to the solutions with less pain and more support.
Rant over. Again … I know nothing.
For the record - more than happy to set aside time to beta test any UNRELEASED WeWeb functionality ALPHA / BETA builds and give you honest, unfiltered NYC feedback 
I test almost everything on the market FWIW.
I’m with you here, Mark. I’ve been doing digital transformation work with WeWeb as a core part of our toolkit for the past two years, and I plan to continue relying on it.
However, I don’t think the current AI features are addressing our most pressing needs within WeWeb yet. They’re interesting, but the real value will come from functionality that saves significant time and solves practical problems.
That said—and perhaps where the product strategy gray area comes from—we’re also starting to find value in tools like Bolt, Lovable, and Polymet. Currently, we use them earlier in our software creation process, primarily to quickly generate interfaces or mockups that facilitate client conversations. Precision isn’t as critical at this stage, allowing us to rapidly iterate on ideas. However, the end goal for us is to get stuff to a point where we design at a high fidelity in Figma, and then, develop in WeWeb.
From my experience, AI features that would truly boost productivity and long-term retention for myself include:
I’m starting to see some of these improvements emerge as part of Copilot 3.0—particularly with built-in AI features like workflow generation and variable creation—but I’d prefer the AI functionality to be applied more precisely and directly focused on solving these critical issues for our team.
These enhancements would genuinely improve usability and empower us to consistently deliver greater value to clients.
Amen.
We are ALL doing this now. And it’s foolish to think we won’t need to use other tools in the future because you (WeWeb) can do it all.
