Quick Base from my perspective.
April 27, 2018

Quick Base from my perspective.

Stephen Morrell | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Quick Base

We use Quick Base (QB) primarily to compile regional information in which we use this data to help manage business opportunities. We also use QB with RPA to help us systematically show the status of each sales rep, when they're available or unavailable, this helps us best serve our customers in a timely manner.
  • Low Code developments
  • API Calls
  • Webhooks
  • ODBC Connection
  • Query against data connections (i.e. once a table is built and connections are joined to other tables, the ability to query against those results manually, like SQL)
We have achieved this on a micro level being able to help small pocketed groups by providing a portal to have access to specific needs and information. Because we are local and not IT driven we've been able to conceptualize new needs, design an App, maintain the App, and provide service to an App much faster than if QB was maintained by IT. We are agile where IT has limited resources to be as agile.
None (SO FAR) but we're always looking to make sure we're using the best tool for our operations.
For a simple design, QB is amazing, it can literally be as easy as drag and drop. When keeping Apps on a basic level a person with no or little technical experience can develop a working functional App, Quickly, that suits their needs.
  • Building and deploying business applications faster
  • 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
Yes and Not Yet! For most of our apps we've been able to achieve these goals, and are continually fine-tuning them to match the ever-changing landscape of a business needs (QB allows us to be this agile). But we're still looking to build future apps that meet specific needs, we're just exploring the level of effort it would take to design these apps and if QB would be the right tool.
We constantly always update "Tweak" our apps. In our environment, the landscape changes all the time, with new alignments, customer server agreements, trends, products, educational developments and training. in our Climate we are always shifting, and QB allows us the agility and functionality to shift rapidly with in culture and environment. Because QB is very dynamic, it allows us to make these updates quickly and on the fly, and almost always these updates go as expected.
Well suited: Table, Form and Dashboard Designs

Less Appropriate (Needs help): ODBC Connections (built in), inability to write manual queries for advanced developers.

Using Quick Base

870 - It's a diverse group of people who all work within the medical device market. From sales training to business operations, we use Quick Base for a variety of business needs. We track regional information, sales rep availability, training sessions, and inbound requests just to name a few. We have dozens of apps deployed and used daily.
3 - All though Quick Base is a low code - no code platform, and not having to be a developer or coding guru, having a good understanding in math equations, some HTML knowledge, some Java knowledge, and base understanding of how relationship database structuring works, would greatly increase the development and deployment of apps. With that being said, even if one didn't have these skills, using Quick Base as a "Nube" won't be hindered.
  • Regional Data informaton
  • Inbound Requests
  • Rep Availability
  • Works with with RPA
  • Via ODBC connection makes life easier adding data in.
  • Data Integration into business operations.
  • Automated Information Requests
  • Working with Alexa App for Requests
  • Integrate data requests to SAP
With Salesforce being such a presence in business operations, we've had to "fend off" being asked to replace our QB apps with in-house/out of the box apps from Salesforce. With the cost of Quick Base and having to justify keeping it instead of Salesforce, it's been a challenge we've been fighting.
  • Initially we had a high ROI in that we were able to build and deploy quickly.

Evaluating Quick Base and Competitors

  • Existing Relationship with the Vendor
Originally QB was brought in by a different department (Marketing) but the 2 individuals that used QB were retiring and Marketing was not going to go forward with QB. Marketing approached us to see if we wanted to take over the licensing and product of QB and we did, and we've been using it for 4 years now.
We would had wanted to get some more specific training on the backend development of the Apps rather than the frontend (GUI) interface.

Quick Base Implementation

the integration was virtually seamless, with the exception of data loading.
Change management was minimal
  • End User buy-in
  • Department managers understanding of QB

Quick Base Support

We had an incident where we asked for help, scheduled a time for a conference call the support person never showed up for the call. It wasn't until a week or so later that we finally was able to get a response.
Quick Resolution
Knowledgeable team
Kept well informed
Support cares about my success
Difficult to get immediate help
Need to explain problems multiple times
We had a question about Automation and Webhooks at EMPOWER17, and was able to get immediate help at the tech bar.

Using Quick Base

It would be great to have a training on the basics of Webhooks.
Like to use
Easy to use
Well integrated
Feel confident using
Requires technical support
  • Table to table relationships
  • Dashboard design
  • Using buttons
  • No backend data querying
  • Not built in ODBC connection
  • Automation still needs more tweaking