I have read all those reviews. There is a lot of crap in there that is not important. What is important is it seems you guys are in a good place, potentially in the black. You have a board to report to, and for the moment can make some smart daily decisions for the company without too much push back from the VCs and board until you get some more money, whether it be a bridge loan, a complete buy out, or the same VCs educate themselves on what Dgraph really is. You can’t really talk about that, nor can you share the P&Ls with anyone, which is expected. That is all fine and dandy, but also means growth is limited, and focus is important.
Others have spoken about marketing and getting more money, which you know is something to be strived for.
What is important, is getting back the trust of your users. One person paying $40 a month is not going to change anything for the company. However, one person reading 10 different users’ posts about the frustrations of Dgraph, may could lose hundreds of thousands a year for Dgraph. That person would recommend Dgraph for other projects, and the cycle continues. One out of say 20 $40 a month user, upgrades to enterprise, making Dgraph money, and 20 $40 a month projects (which could be one user), could be equal to 1 or 2 enterprise users. Every user counts. We know this, but it needs to be said.
I also read that it seems you have been disorganized in choosing when and which features to implement. This is great for innovation, bad for focused progress. While I can’t speak for the team issues, I can confirm this is the second biggest issue for your users. We want discuss for problem solving, but you NEED github to not only track issues, but to track features. Obviously, everyone agrees.
So, again, focus and gaining back user trust…
I think by now you know where you want Dgraph to go. This thread as been extremely important in that. Write out your plan for the next 6 months. Stop ignoring posts from your users, and start building trust back. I have asked 3 times when v21.12 will be on the cloud since you created this post, and I have been ignored. I have dozens of unanswered posts (not even related to feature requests), and I have had at least 3 broken promises from marketers, managers, and programmers. I think it is hard for me, Anthony, and others to ignore the temptation to write about frustrations. We want Dgraph to succeed, we don’t want a trace of frustration in the forums, but we also want to be real with everyone, especially so management can DO SOMETHING about it, instead of creating more traces of problems.
Bringing the critique sandwich back around, I believe in this product. Despite 2021 (Dgraph’s 2020), 2022 should be a good year. It truly does seem Manish wants to head in a good direction, due to the layoffs the company is very still-alive, and while the future seems slow, it seems like there will be a future. However, Manish, you need to always keep your users happy going forward, or there will be easily preventable problems. This is what you need to do IMHO:
- More communication (on the right path so far)
- Acknowledge questions, even if you don’t know the answers yet or can’t answer yet (my personal pet peeve)
- Github for issues AND features (I think you have your answer)
- Roadmap (even if it is slow slow slow slow, and it changes 10x a month)
That’s basically it. We need to know things are moving forward, despite the ups-and-downs with internal problems.
That is how you can lead this company going forward, and gain more money and followers.