Quickbase work for a national nonprofit
December 06, 2021
Quickbase work for a national nonprofit
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Quickbase
We use Quickbase for a wide range from HR & Financial, to team management and trackers as well as data analysis and recruitment.
- Customizable
- Flexible
- Quick
- Standard across applications
- Removing [native features] for use cases[.]
- Javascript
- Advanced features to use outside of the applications[.]
Do you think Quickbase delivers good value for the price?
Not sure
Are you happy with Quickbase's feature set?
Yes
Did Quickbase live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Quickbase go as expected?
Yes
Would you buy Quickbase again?
Yes
[It's] pretty easy once you have a set of people who have builder knowledge to get something out there. The real issue comes when a builder and management team also use real [end-user] feedback to make a product that is liked by the people who will be using it most. Unfortunately, builders are often a little too in the weeds for that. That is why we needed to implement an oversite/implementation team [that] can work with the builder.
- Workato and Google Sheets
[Works mostly] in conjunction with those two items.
- Building and deploying business applications faster
- Improving our ability to drive insights from our data
- Improving collaboration across one or more teams
- Solving a specific business challenge
- Building and deploying an application (or multiple applications) that meets our exact needs
We have 500 staff across the country. Having everything online and standardized so that they can access it wherever they are is important. It also means we can train people and have materials on how to use our systems standard for all of our staff. We have staff managers in California overseeing staff in Pennsylvania because they get [real-time] updates on their staffs [to] work as well as any HR needs.
[It's] hard for people to wrap their mind around table relationships. Which is the main barrier. It takes a decent chunk of time to maintain applications if the builder has left the organization and it isn't documented well which it usually isn't.
I update applications regularly. I recently updated an entire application by making a copy of it, making substantial structural tweaks and changes because of the increased features of [QuickBase] and our security systems allowing us to work more natively in the application. This allowed me to make changes without shutting down the application, then transfer the remaining data that happened while updating the app and lastly moving all of our users over without most users even noticing they were actually in a different application. The [end-user] experience was one of an upgrade vs a brand new app.