Quickbase

We have been able to make a ton of manual email and paper processes digital. We use Quickbase as an approval form for assets as well as an ordering form for content.

QuickBase is amazingly adept at allowing my organization to design and implement new applications and getting them in the hands of our staff. Tweaks can be made as you go, and you do not have to waste the time for development. Your solutions can be responded to in a matter of weeks, days, or hours, instead of months with other development work.

Yes we have achieved this benefit because it is a cloud based software and easy to use.

Definitely, our whole company used Quickbase for procurement. This is an end to end solution right from creating an order, to having it approved, to tracking shipments, and reconciling invoices.

I would say that QuickBase met its goal of building, deploying, and maintaining a customized business application in our case. Prior to using the software we were relegated to jury-rigged workaround methods of retaining our data, such as saving them in documents or spreadsheets. Obviously this method was sub-optimal and QuickBase worked much better.

Having the ability copy functionality and pull it into other applications helped with deployment. This allowed for a quick turn around of app development of days instead of weeks.

We started out using QuickBase for our job management and it has grown exponentially. We use it for:

Asset Tracking
Account Management
Sales Quotes, Sales Orders, and Invoicing
Job Management
Employee Management (including tracking Time Management)
Interoffice tasks
(Too much to list)

Our organization has achieved this. There have been some failures, some applications that probably shouldn't have been built in the first place, but most are used and have increased efficiency for us. The failures seem to have deployment problems, primarily. When you build a QuickBase application, you typically don't have a kick-off meeting and then celebrate going live with a party. You just build it, then you immediately start testing, rolling it out, fixing problems, adapting it to change or requests, etc. So if you have to overcome some sort of user reluctance, or enemies somewhere in the organization, it can be more difficult. That is not QuickBase's fault, of course. On the plus side, if a project fails, the sunk costs are much smaller, too.

We solely use our custom built applications within Quickbase.

We were able to get QuickBase up and running much more quickly and cost-effectively than it would have been if we had to get developers to build us a custom application from scratch.

Yes, but we are not to the finish line yet. We have added efficiency to processes like requesting website changes and design material, which was our primary goal. While creating these workflows we identified many other areas we could improve our internal processes, finding the time to build and test has been the challenge.

We have been successful in creating and deploying custom applications using QuickBase and the user adoption has been very seamless. Whenever we have instances where an old process or application is no longer fitting the needs of the practice, we now look to QuickBase first to determine if the business need can be solved by creating a new application in QuickBase before considering higher priced and more proprietary applications.

We have slightly customized already existing applications which has worked well for us.

Quickbase has definitely made it simple. We were able to add the important fields of information into our tracker template and delete anything that wasn't very important to us. We are able to pull large amounts of data at a moments notice and able to keep a back up to protect our company.

That statement we have found to be very untrue. It is not easy, fast or inexpensive to customize. We created our custom application around 10 years ago but as we lost the individuals familiar with Quickbase it has stagnated and our attempts at improving it came back too costly. In fact we are actively looking back to in house alternatives that would better suit our needs as well as reduce cost.

We have built all of our own custom apps and use most of the apps daily. I would like to grow our use of Quickbase but our technology department prefers SharePoint and has actively discouraged any other departments to use QuickBase.

We have achieved these objectives to the effect we currently desire. There continues to be a lot of capacity for the what the system could do for us, however we haven't yet had a need to explore those functions.

Being a new employee for this company, I found out quickly that when a project is going on it is a necessity to create new applications on the fly. Through templates it really allows for you to create the apps on the spot and tweak them to the customers needs.

Varoius ITIL processes are executed by using Quickbase database applications.

We have achieved this benefit but are evaluating simpler options such as Smartsheet.

Yes, it has improved effectiveness of managing diligence and integration tasks across multiple functions.

Yes. Data driven application development has never been easier.

Sharing relevant information across multiple users has become easier and more efficient. This helps especially in tracking work done, assigning resources, and managing priorities. Managers are able to get a quick overview of projects that are completed, on track, or delayed and they can assign resources as needed.

Yes, we have been able to build many applications that support our team's efforts.

By implementing Quick base, my department has been able to better plan for upcoming purchases, but it also allows the manager the ability to see the requests that are coming in and reject them before they begin to be worked on if needed. We are still evolving the app we created so that it can be used interdepartmentally. Many of our colleagues now want to use Quick base because it has been so helpful in streamlining our processes and communications with one another.