Previously, we were using Smartsheet but we transitioned to QuickBooks because it offered a bit more functionality and advantages.

All of our previous custom solutions (MSSQL, .net, etc.) were very difficult and expensive to maintain, scale, and secure. We had a corporate goal of maintaining zero server hardware - and QuickBase met that requirement.

QuickBase was our entry into centralized, digital business systems. We build QuickBase applications for client companies of all sizes that often replace manual processes or legacy systems.

We used to keep track of our workload with Excel spreadsheets. This had limitations in many ways. The most obvious limitation was the inability to create different views of data for different needs. The other limitation was the inability to keep track of work in real time.

No

Prior to using QuickBase, we used Microsoft Excel and PowerPoint.

No, I did not use any different solutions. I took help from the Quickbase technical support team and it helped almost all the time.

Before QuickBase, the only thing available was Microsoft SharePoint and its eForms. These were tightly controlled by corporate IT so basically no one could use them. The existing eForms I've seen were so poor in functionality and user experience I would not use it for my team.

We found nothing that did it all for us in one cloud base solution. QuickBase does it all. If you can think it it can do it.

I have tried using Filemaker to create my solution, and MS Access, and a SQL database, all proved to be very cumbersome to work with, and required a deep knowledge in database architecture to accomplish what I really want to accomplish. I'm amazed that I was able to do it all myself in Quickbase. That's how easy Quickbase is.

We were using Microsoft Office for most data files and trying to utilize graph and communicate them over e-mail and powerpoints. We knew there was a better way.

Yes, but our previous solution was really no solution at all. It was really just a place-filler that had no place being where it was. We used Microsoft Word tables to keep track of our employee records.

We graduated from spreadsheets and MSAccess. We switched because we needed a web based solution.

We were previously using excel and so the need to switch to a better means of project management was felt by everybody. This was a service that we were somewhat familiar with from some of our clients and so was looked at first.

Yes, Excel. Too many versions in too many places.

Yes, we previously tracked our cases in Access and couldn't be any reporting on our results without exporting.

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.

We did not previously use a different solution. We evaluated it as the need to transition away from traditional application development became more apparent.

No I did not use a previous solution, I started using Quickbase in the beginning of the company. So there was no software package to switch from. This is much easier to use that MS access.

Yes, we used goldmine which was unstable , wasn;t user friendly , and poorly adopted. It was also an on premise solution which was a challenge to support.

Previous solution was spreadsheets, Buildertrend, Post-It notes, and Google calendars. We needed something that was entirely cloud-based and centralized. So short version, we did not have a solution in place.

We used excel and spreadsheets. It was slow and clunky and we had lots of data loss. We also had some processes on paper which was very inconvenient and inconsistent.

We previously kept only hard copies of all our quotes, now we can share them with sales reps digitally, or grant them QB access. In addition with our further expansion into other territories we are able to share information seamlessly.

We have used several other systems. We switched because QuickBase is so fast and flexible. It can keep up with our ever-changing processes. The total cost of ownership is an extremely good value.

We have been on Salesforce.com for the last 7 years, but it isn't as good a fit for a small business like ours. Too many limitations, too much programming overhead and complexity with Apex, unit tests, etc.

AS400

We used many different solutions before, including just using spreadsheets. Easy of use and its rapid turnaround for development is why we switched.

We are a database solution provider and consulting agency, so we have used a lot of different databases, both internally and for our clients.

No, for the way we use this, we have not switched from this platform. It has been considered to be replaced in the future, but the costs of abandoning have been prohibitive.

Yes. We used multiple different solutions, and we switched because QuickBase offered us the possibility of bringing disparate departments doing similar things that it would be good for everyone to know about into one system.

We did not have a previous solution before QuickBase. This software was brought in too help us organize our projects and make day to day things easier.

The previous solution was using spreadsheets being emailed around and edited by a single person. It was not a viable solution going forward.

The tool that was used most before QuickBase was probably Excel. QuickBase can definitely replace many Excel spreadsheets, but Excel will never go away.

Our systems were really old and we were converting from spreadsheets and old relational databases, so we didn't really encounter this. We switched because we were so out-of-date that we needed new solutions.

No, we previously were doing everything by hand and on paper. We grew quickly and it became no longer viable to conduct business that way.

We used paper reports and ticket logs. It was very time consuming. Now NO paper work and it has cut our time in half.

Yes, we tried Zoho as a Project Management app. It was too simple and lacked a lot of features that we needed.

We used spreadsheets. We were able to configure QuickBase to the way we do business.

Excel. Do I really need to explain why we switched. Excel will kill any business that relies on it for anything besides ... well anything.

Since I have been using this system, I knew the power of it.

Of late, it has improved a lot. This is one of the best tools for citizen development.

Used an in-house implementation team however switched over to the vendor due to the following benefits:

1. Low cost to serve

2. Ease of making changes to the application

3. Time to market was considerably reduced in comparison to previous solution

Yes, we used a standard database system that came with our other office software package.The system was cumbersome and was difficult to almost impossible to have multiple users on at one time.

We did have a CRM solution and switched because QuickBase provided a database that could be accessed anywhere and understood by staff, admin, IT, and executives. We wanted an easy place where executives and finance could view revenue easily

No.

We did not use a previous solution.

No, this is my first experience with low-code platforms for building apps.

Solutions like SmartSheet have vastly more limited functionality and flexibility than QuickBase.

Yes, Time to Market was a major factor as we as the self-service feature.

Many different solutions to suit many different business processes. We switched because it is a lot easier and cheaper to run one system instead of multiples.

Yes. It was a DOS-based database system that was only available on ONE computer in our home office, and it could NOT be accessed via the web.

I have used local ERP, SCM, MES, and Logistics application systems. But all are customized by an end user requirement and hard to consider providing standard/best practices, just function-oriented, and little have capability to suggest a roadmap.

We used Excel, but not the multi-user version.