Why is Cavewire not building the feature I want?

Community feature requests

The sheer number of requests shows us just how much our customers want Cavewire to be an important part of running their businesses. They’re willing to take the time to write up what they need, comment details about their situation, and then add their vote. All these requests and changes have added up — especially when you consider the various business sizes that use Cavewire!

Community feedback is important to the team, with hundreds of requests completed so far. However, it’s not the only factor considered. Despite popular belief, there’s also no countdown to development when a request is added — some things take time, and everything has to be prioritised.

Emails to Support

Emails to direct members of the Cavewire team may take longer to be addressed because they are not funnelled through the ticket request process. The process has been set up to help you so that we can most effectively gather the information and our support team can quickly follow up. Tracking all of the requests in the pipeline is much easier when we can refer to the tickets that have been submitted. It is also improves the visibility of the information trail related to the request. We have found in the past that there can be miscommunication when various emails to different team members are all relating to the same request.

Scalability and our platform

Not only do we want to develop beautiful software, but it has to run effectively too. Developing a platform that easily supports features for a large number of people is important. So is reducing technical debt that comes with software of a certain age. Cavewire has been evolving for many years, and while we could update certain modules, we need to remember that earlier adopters of those modules have defined their business processes around the way it currently works.

What can we realistically do

The Cavewire team is growing, but we still have a finite number of developers and there are only so many hours in a day. Teams need to take all of the above into consideration, think about how much work it’s going to be, and then what they can achieve.

Sometimes we can’t develop what everyone wants, but that’s not for lack of trying! This is tough, but we work really hard to make Cavewire better for you. So please keep the conversation going.