We are always working on improvements and we appreciate hearing from customers who have suggestions that would make our products more helpful.
Making a request
Whenever a client contacts us about a particular function they would find useful, which does not already exist within our products, we log this information as a ‘feature request’.
How we review requests
Following our internal feature request meetings, viable requests are selected and then considered for inclusion in our development schedule. This schedule is then mapped out based on a number of criteria:
- Demand for a particular feature.
- Ease of implementation.
- Impact on our overall client base.
- Special commission.
Features are often assessed as part of a larger development roadmap and even seemingly small changes may need to be considered as part of bigger strategic projects that may take some time. We tend to have a substantial list of feature requests at all times and this review process ensures that they are dealt with as fairly and efficiently as possible.
Commissioned development work
It is important to note that, as a rule, we do not perform custom development for individual clients on isolated databases.
All new features are considered as part of our complete product offering. Even specially commissioned development work is usually rolled out to our entire client base. This means feature requests need to be carefully considered as they will impact all our clients and new features often require beta testing before they are fully rolled out.
While this process can take some time, we always note down the name of the organisation who requested the feature, so that we can follow up with them as soon as we have any news from our team.
Finally, it is important to note that we reserve the right to decide when and if a feature request will be added to our development schedule. Unless something has been officially commissioned, in which case a schedule would have been agreed from the outset.