Quickbase

My use case is fuel pricing. We've been developing an app with a consultant firm over the past year and a half, I would say, to build a platform that allows us to price fuel.

With real estate construction projects, site searches, facilities management, facilities, maintenance, leasing, and integrating different software together.

So we have multiple use cases, but primarily we have Quickbase as the core of the platform for acquisitions. We use Quickbase to query MLS and other data sources for properties that we are interested in buying. We use Quickbase to underwrite these properties using different APIs and formulas. We create a list of properties that we wanto to buy. We have workflows that we send to our teams for them to review the properties. They have approval and rejection workflows. They send those to clients for review, clients approve them. Then after that, we have workflows to make offers on these companies, on these properties. We buy the properties, then we go through our renovation process. We also run renovation in QuickbBase. And after that, we rent the properties and we use Quickbase to help us with the rental of these properties. We have an end-to-end integration.

We manage boarding and training services for canines, for dogs. And we have to keep track of all the information like a database of all the canines with the names, the microchip numbers, the training sessions, all ofthe information about the vendors and the medications, and everything related to the canines. Then, we have to keep track of the training sessions, which is another separate piece of information. Of course, we have to track boarding and the channels of different employees and I mean, it's a lot of information that we keep in the system.

We use it for our entire project management side of the business. From start to finish, from quoting to installing the goods, it's all managed inside of our database. Our accounting is also inside of it as well, so it's all intermingled and it's given us an edge over our competition because we can always add anything a client wants or needs. If we don't have it already, we can modify it to be able to produce whatever they need and it gives us an easy and quick way to deliver results.

We use Quickbase in our organization internally as well as externally. Here we use Quickbase as the integration of Quickbase with Quickbook online to fetch the data into Quickbase and create some useful analysis out of that data. We solve many business solutions as we track the data on a real-time basis like we create the different dashboards as our clients see it on regular basis based on the data of QBO (Quickbook online)

The biggest problem is in our insurance industry, the need for an agency management system is crucial for operations, for clients, and for accounting purposes. So we essentially use Quickbase to put together in one place all of our customers, all of our information, all of our revenue, all of our compliance, and all of our accounting.

We are solving the problem in clinical lab industry where a patient submits a sample to be tested at the lab. That sample undergoes a lot of processes. Ultimately, the result is generated on the equipment in the lab. We import the results in the Quickbase and we create a final report, and the PDF report that goes back to the patient.

We are an international company dealing with bevs of information coming from all sources at all different times. We use Quickbase to make sure we have a shared data pool to process the information before we hand it off to our users to summarize all the work that we get done. Really to handle large amounts of information coming from all different ways and make sure that everyone can see this good information at the same time.

We primarily use, or at least the part that I'm involved in, it as a sales portal. So all of our sales that we used to track through Excel spreadsheets, that we had to send around, are all loaded in. We also have links and resources and things like that. They can place orders, and we track shipments once those orders are placed. We reconcile, and we've got an RMA module built out. We've got a whole bunch of things and all geared towards a sale, like a third-party Salesforce.

We keep track of tasks that are incoming and we basically complete them through the application using automation tools.

The biggest thing it really does is help minimize the number of different systems that we're using. So instead of having 10, 15, 20 different systems, you're able to do everything in one single platform. And by doing so, it just minimizes. There's an old phrase of too many cooks in the kitchen, so it kind of takes all those extra cooks out and you can be sure everything's flowing right.

I've been using Quickbase for many years across many use cases. My function is finance, so my primary use case is going to be around the finance function. Managing my team around traditional finance and accounting tasks, whether it's budgeting and forecasting or audits or closing our books to approving expenses. Managing outside service providers. Quickbase has been a key tool in, you know, aggregating data, sharing data, workflow automation, just getting us organized bringing teams together that are in dispersed geographical locations. I can go on and on.

Ascena Consulting is a specialty tax consulting company. We focus on tax incentives for corporations. Most specifically the research and development tax credit. So any company that does anything that's innovative, they have an opportunity to at least look at the R&D credit. We document, calculate, monetize, and then provide support to them in the event of an audit. We make sure that the credit we generate for them can be used to reduce their tax liabilities.

We track work from our sub or through our customer. They issue us work and we manage it from start to finish. From inception, we build out work order packages. We price the work that we do. We do so many things in the system. We monitor quality, we monitor the actual tasking and pricing of it, we do environmental, there's so many different functions we use the product to track. And then we also track customer metrics. Our customer that we deal with, they have their own metrics that they use for us, and we have those same tracking features within the system.

We use the services for scheduling our tasks and our IQC reports and providing the data back to clients and using applications for automations.

The scope for my use case is having information just in time and in real time. I'm able to provide my clients with all the information they need and reporting out efficiently and effectively. With my team, we update the system from a completion standpoint, which produces Gantt charts, reports, and gauges, and the client is extremely happy with us because I tell them exactly what's going out in the field.

I collect data for our risk and safety team. The property manager sends me an incident for which I send them an incident submission link that I created so that it goes into a table, into my Quickbase that I can review before I actually create the incident. Some incidents turn into claims, some incidents become legal cases, and some incidents start out as an incident to a claim to a legal matter. So I'm keeping track of all those three things.

So, we have about 10 consultants that work on our customers and projects and they log their time. They log the projects and the tasks that they do for these customers and they log their time and the description of the work that they do. We use that to manage the projects and it ultimately translates into our billing.

We started using Quickbase as our publishing database, so basically it manages our entire publishing schedule. We're introducing a finance forecasting app. We have a contract app and we have a CRM app. All of our apps communicate with each other and manage all of the data throughout the organization.

It solves having a spot where everyone can see all of the information that is needed to move forward with publishing.

We collect data, we collect voter information and contact information for all the neighborhood councils in the city of Los Angeles. We use that information for contacting them.

Historically a scientist would go into the lab, measure something like a chemical, and then they would take the data and copy it into an Excel sheet. What we've done is we've created a tunnel to the cloud. So when they measure something, a file is outputted and we put it into AWS, and then we actually use the Quickbase API and then write it out to Quickbase, and then we dashboard their basic analytics and aggregate statistics, such as quality.

We use it for the most part for our customer relationship management. So pretty much everything that we do from our customers to get back to the office all runs through QuickBase, essentially. I think the biggest problem is if somebody gets brought into it without creating this from scratch there's not a ton of support yet to be able to help out without having to pay. Small companies don't really have the capability to pay for all that type of consulting, if you will. So a better way to get some consultation there, to help some smaller companies, would be awesome.

Track assets, time sheets, work orders, field change orders, all our internal processes are done through there.