Quickbase Review
June 26, 2023

Quickbase Review

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Quickbase

We use QuickBase in primarily two different use cases. our company operates contracts with federal, local, and state government. So we manage our clients, our job seekers, predominantly it could be students. And so we manage them through all the services that we provide. So in one sense, we're managing people. So that's, that's probably 75% of how we use it. And the other would be just processes-oriented operations management performance reporting reviewing documents site reviews and all of the approvals and quality assurance touches that we have with that process.
  • I would say managing our participant expenses. We have thousands of transactions a day where we're helping individuals, whether it's childcare vouchers, transportation vouchers, clothing, things of that nature.
  • And it allows us to process the requests and have the workflow approvals embedded within the process so that we're protected also and making sure that we're utilizing the funds appropriately. That's probably one of the huge successes that we have.
  • And another would just be more on the process-oriented side, just making a lot of paper and spreadsheets go away, you know, just giving everybody visibility of the data and then just having a process that people can appreciate because it's simple, yet effective.
  • For a while, but now this is improving. It's been the dashboard experience. So it previously having a dynamic filter that would allow all of the data on a dashboard to be influenced wasn't possible. That's been overcome.
  • One of the areas that we're still struggling with is pulling up data from a child table that is text into the parent table. We've had some creative ways of working around the issue and now with the report query, there is hope that we're gonna be able to circumvent that. But that's been a bit of a sticking point for us pulling up text data in a child table from a specific repetition or iteration.
  • And then probably lastly, just a lot of our data entry is very elongated. There are a lot of fields that have to be entered. one of the comments that we received from the field is just the layout of the forms themselves. You know, they can be busy at times. there are ways to mitigate that, but that's an area that hasn't been a strong suit.
  • It's been a challenge for us to quantify. But I can tell you that some of the things that we do, the people that are are internal customers, if you told them that were taken away, a QuickBase wasn't gonna be available to, to serve the function, it would really, they would screen bloody murder. A particular example is we have a financial process where we accrue. We reconcile between accrued versus build and it used to be a very laborious spreadsheet-oriented process. And now it's very visual, transparent, and easily understood, even though it's quite complex. And to go back would be, you'd probably have people quitting their jobs.
We have, I think at times, we build faster than it's probably good for us because it does lend itself to solving solutions so quickly. Sometimes the documentation takes a backseat. So I would definitely say even with a limited number of builders it's quite effective in impacting our stakeholders, our internal staff in terms of making whatever they're doing or have asked for more efficient.
I haven't been a practitioner of other products, but I have taken a glimpse at them. One of them that comes to mind is the service. Now, the way that we use QuickBase is it's more suited, better suited. and I have used a couple of others over the years or, or had them pointed out to me but I don't recall what their names are.

Do you think Quickbase delivers good value for the price?

Yes

Are you happy with Quickbase's feature set?

Yes

Did Quickbase live up to sales and marketing promises?

Yes

Did implementation of Quickbase go as expected?

Yes

Would you buy Quickbase again?

Yes

I think it's well suited for processes that have a two or three-table level of complexity where it's transaction oriented. It has a definitive start and definitive end when the record's done it's just a record and it's historic. It works well in that way. One of the areas where maybe it's not so well suited would be electronic signature required, in other words, it doesn't have that feature embedded in its native functionality. So it's a challenge because we have to find a solution outside the system.