Buildium loves collecting feedback on how we're doing. We do our best to be receptive to all suggestions.
If you think that we could save you a ton of time with a specific task and we could handle something better, please let us know and make a suggestion!
To make a suggestion:
- Navigate to Help & Support > Suggest a feature.
- Search for ideas similar to what you had in mind.
- If you can find what you were looking for, add your support and join the conversation.
If you cannot find anything that feels right, create a new idea. Please give as much detail as possible.
Write a great suggestion
A good feature request has three parts:
- An introduction to the situation and how you handle it today.
- Your suggestion on how Buildium should work differently.
A specific example that you've recently encountered. Bonus points if you can provide a sample, screenshot, or video of what you're looking for.
Remember, other customers can see your suggestions and vote for them, too. A well-written feature request is a searchable and easy-to-find feature request. If you can, take a few extra moments to bring your idea from good to great.
It would be great if we could perform our property inspections out in field with the ability to add pictures, check off rooms/items, and report current issues. These inspections would need to appear on the main web application as well.
Thanks for your consideration!
Will you build my suggestion?
If you think it's a good idea, then we're happy to consider it. The suggestion example above was a real request from our users, so Buildium partnered with Happy Inspector to provide an integrated property inspections solution you can use on the go.
We're always working on something new. Most of the time, our product development schedule is booked months in advance. We do our best to keep our feedback forum up-to-date so you know what's coming soon.
Each and every suggestion that's posted to our idea exchange is reviewed by a member of our design team. If necessary, we'll categorize the suggestion and combine it with similar requests. It's not uncommon for us to ask a few questions just to make sure we get to the heart of the issue.
Our product teams meet on a regular basis to determine what's going to be built next. We do not have an exact formula to determine priority; here are some loose guidelines:
- Is there an adequate work around in the system today?
- How many customers have asked for this specific feature?
- How many customers have asked for similar features?
- Does the feature request expose a bug?
- How much time will it take to build?
The amount of support is an influencer, but it's not the sole decision point. Sometimes, we have to build a cool feature in preparation for an even cooler feature that's planned for a later release. Most of the time, we'll combine a lot of ideas into a single enhancement - much like you might combine a few errands into a single weekend trip.