Hi @callmevlad,
It’s 11:30pm here, I’m finishing working on a site and saw your reply, so I cannot not take a bit of extra time to follow up right away…
First, @jmkriz is absolutely right you know ? and also why I said in my original message that “my trust is gone. I don’t believe in your roadmap anymore”…
You are correct saying there’s too much to respond to in one message, that’s fair to say, and I don’t think that’s expected. We’re all adults and realise you can’t answer to every single grievance.
But allow me to give you a step by step feedback on your answer. I know it’s easy for me to do, as I speak to you directly, but trickier for you as by answering here, you speak to thousands.
I’m generally not a fan of this type of communication as it can feel like crude criticism, but it’s been a long day and it’s easier for me to do it this way. I want to do this in fair spirit and to help you understand where after reading your message, I think you might still be mistaken / there might still be some misalignements.
Indeed, this moto currently can’t be defended…
“Livelihood” is a critical point here. We’re not on Webflow like teenagers are on Facebook. We’re using Webflow to make a living . We’re all professionals and we know what we’re talking about here (technically and commercially). We’re your point of contact with the final customer and when we push requests to you, it’s because we get them from our market. Being aligned with our market is what allows us to earn a living. So if you can’t help us reach this alignment, we lose our customers, you lose yours, the relationship breaks - which is what happened (please note I purposely said “happened” and not “is happening”…).
First important hiccup here. You need to have one… Admittedly it won’t be highly detailed and have every single feature you guys might be working on, but the critical basic features everyone’s crying about here, I’d expect that to be on a clear roadmap now… If it’s the only thing JZ does, that should be it.
Apologies if I read this wrong, but to me what you’re talking about here is either addressing the symptoms instead of the problem or should be in the point 3 about Customer Support.
My original point here was about development priorities and the actual development speed. I’ll save you the hiring of those Webflow advocates or whatever you call them. That’s a bad corporate answer to this issue and money out the window. You want to know your customers priorities ? Just get JZ to check the freaking Wishlist !!! It’s all been there for years !!!
Now that I saved you all this money, you can use that to hire more developers that will actually do the work.
Also as a general business advise, avoid hiring too many “middle men” like that. They’ll get your company bloated…
Ok, I agree with what you’re saying here. But I think you should still consider quick wins if technically possible. The situation is clearly bad and every little helps.
Also I’m a bit surprised you’re just forming the team to focus on that now…
Lead time ? This is important, especially if you want your Enterprise proposition taken seriously (Oh, and think about dedicated hosting for Enterprise too… just sayin’).
That can’t come soon enough… and hopefully it will be more an announcement than an update…
Yes, of course, but you can get your current developers to focus on features important to customers… which I feel is not currently the case.
Action’s all that’s left…
Hopefully it’s clear that this aims to be constructive feedback, and not just easy criticism.
If something’s not clear, just ask.
Thanks for (finally) taking the time to reply.