- Allows users have anytime/anywhere access.
- Ability to create the box to fit your workflow. You are not forced to fit into someone’s box or idea of how your company should be run
- Fits small and large companies
QuickBase deficiencies are only filled by third-party developers. For example, we need a third-party to create and save a document in PDF, MS Word, or MS Excel format. The document saving capability is probably the feature that we most often have to procure from an outside provider.
We have been developing on QuickBase for ten years.
Being a cloud platform, there will always be momentary downtime. However, QuickBase stability and reliability has always been good.
Maintenance is generally scheduled when traffic is minimal and is communicated to users well in advance.
Scalability is one of the key QuickBase features where you are able to start small and add feature sets to your application as needed.
Your application and ability is only limited by your own imagination. The sky is the limit with QuickBase. If you can dream it, QuickBase can do it.
QuickBase empowers its users with product help and an open API. They also have great documentation about how to use the API functionality and how the “coding” is different from other programs.
One of the core goals of QuickBase is to build a community of “citizen developers”. QuickBase is a platform which is considered low-code or no-code. You do not have to be a programmer to build or maintain the system.
We use QuickBase as a system to run our business. It started out as a simple CRM and grew into a ticketing system, asset management, and scheduling tool.
Previous to QuickBase, we used custom fields in QuickBooks, Outlook, Excel, sticky notes, employee memory, and everything else that did not work in concert with each other.
We used what was cheap, easy, and right in front of us. This became an option that was not in the best interest of the company. It was neither scalable for the growth of the company nor helpful for the sanity of the employees.
Our setup was pretty straightforward. We knew what we were doing wrong and knew what was missing with the other systems. We had a plan.
For companies that try to implement QuickBase and do not have agreement on internal processes, the development and setup can be that much harder.
The pricing for QuickBase is pretty straightforward, It is based on a per user/per month licensing fee.
The licensing fee is not dependent on user usage. The best way that we describe it to potential users is like getting your driver’s license.
The DMV charges the same for a driver’s license for both a person that just uses it to drive to church on Sunday and carpools or walks to work during the week, and for another person who drives hours each and every day.
At the end of the day, both are paying the same amount for the privilege of being able to drive the car.
QuickBase is the same. If you are in the system once a week and just use it to view reports, or if you are the plan administer and have QuickBase as your main focus day in and day out, the cost is the same.
Since we came from a multiple tools environment with holes in our process and systems that a truck could drive through, we knew when we saw QuickBase that it was like nothing else out there. It was almost an instant light bulb of knowing that we were at the right spot.
If you are looking to implement QuickBase, make sure that you have a vision and your team is aligned.
You do not need to know how to build the vision, but you need to know what the end result is. More importantly, your team needs to be aligned with that vision.