A few years ago, when working with certain no-code tools, we would encounter situations where the tools could not meet certain requirements. When we started, we had our priorities in order, and some of the things on our list were not able to be achieved, even with a high level of automation or scripting. We would reach out to the support team of that tool to see if that feature was coming anytime soon, and sometimes they would say, “Yes, it’s coming. It’s going to be here in the next three months. It’s going to come in the next six months.”
Then we hold on because the business is very insistent that they want to use a particular tool for a certain reason. So we set up what we can and wait for this particular feature while trying to make the best of the capabilities that we have.
Then we wait and wait and wait, and the months come, and then they say that this feature is not going to happen. It’s just not profitable, or it cannot be done, or it’s going to take a lot out of them to do it. Now we have made certain decisions around this promise of a feature or update, and most times, it’s not going to happen. There are very few tools or companies that say, “We’re going to bring this,” and they bring it in the time that they say they would.
Most of the time, these tools or businesses have their own roadmap pages you can go on and look at to see if these features are coming anytime soon. Sometimes the features will be “in progress” for months, going into a year or two, and they just don’t come. You cannot make decisions around what is going to be updated or what the sales or product team promised you because there’s a chance that it might not come. So you have a list of requirements, your non-negotiables list, what you’re not going to compromise on, and you look for tools that are going to fit those requirements or something very close to them at the moment. And you can work with that.