Item: Quickbase
Rating: 10
Author: Stephen Morrell

Overall Satisfaction with Quick Base

Use Cases and Deployment Scope

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.

Pros and Cons

Pros

Low Code developments
API Calls
Webhooks

Cons

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)

Alternatives Considered

None (SO FAR) but we're always looking to make sure we're using the best tool for our operations.

Likelihood to Recommend

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

Users and Roles

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.

Support Headcount Required

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.

Business Processes Supported

Regional Data informaton
Inbound Requests
Rep Availability

Innovative Uses

Works with with RPA
Via ODBC connection makes life easier adding data in.
Data Integration into business operations.

Future Planned Uses

Automated Information Requests
Working with Alexa App for Requests
Integrate data requests to SAP

Likelihood to Renew

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.

Return on Investment

Initially we had a high ROI in that we were able to build and deploy quickly.

Other Software Used

Automation Anywhere, JitBit Help Desk

Evaluating Quick Base and Competitors

Products Replaced

Key Differentiators

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.

Evaluation Lessons Learned

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

Implementation Rating

the integration was virtually seamless, with the exception of data loading.

Implementation Details / Implementation Partner

Implemented in-house

Implementation Phases

Change Management Lessons

Change management was minimal

Implementation Issues

End User buy-in
Department managers understanding of QB

Quick Base Support

Support Rating

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.

Quickbase Customer Support Pros and Cons

Pros	Cons
Quick Resolution Knowledgeable team Kept well informed Support cares about my success	Difficult to get immediate help Need to explain problems multiple times