Quickbase Platform

What do you like best about the product?

I like that it keeps everything in one place for our ECU release workflow at Ford. It doesn't do the actual signing but we built a .NET API that gets called through Pipelines. Quickbase sends over the file and signer positions and our system generates the links. It's been pretty reliable actually. Pipelines trigger on record changes without issues. The performance is fine even with all this custom stuff sitting on top. Just takes some upfront work to keep your tables clean so the JSON payloads don't break.

What do you dislike about the product?

The biggest thing is you have to build so much outside the platform. I'm an embedded engineer not a web dev so maintaining this API is not really what I signed up for. Passing complex data through Pipelines was trial and error since the documentation is kinda vague. Also setting up permissions across tables was confusing. We had some issues where people couldn't see what they needed and it took a while to sort out.

What problems is the product solving and how is that benefiting you?

It solved our tracking problem. Before this we had no central system for managing who signed off on firmware releases. Now Quickbase kicks off our API automatically whenever a new request is needed. That means we don't have to manually handle PDFs or worry about filling in placeholders wrong. Everything gets archived to SharePoint without us thinking about it. The whole pipeline is traceable now which helps when we get audited.

What do you like best about the product?

I like that we can adjust things without needing developers. At HPE our workflows change pretty often and Quickbase lets me tweak fields or add new steps without starting over. We use it for partner service validations and it syncs with our other tools pretty well. My team feels more organized now and we don't lose track of requests like we used to.

What do you dislike about the product?

The permissions setup is kind of a hassle for us. We have different partners and internal teams needing different access and configuring that took me a while to get right. I still don't fully understand some of the settings but still trying to get used to it.

What problems is the product solving and how is that benefiting you?

Mainly it keeps everything in one spot. Before we had documents in one place, approvals in another and notes everywhere. Now it's all tied to the same record. When a partner submits something the system handles validations and updates the status. It saves us time and makes me look more organized.

What do you like best about the product?

Quickbase is user friendly and easy to navigate.

What do you dislike about the product?

I wish that searching in Quickbase was a little easier. For example if you type Jr Sports vs. needing the exact match Jr. Sports.

What problems is the product solving and how is that benefiting you?

QB helps us keep all of our tracking processes organized.

What do you like best about the product?

The error handling feature in Quickbase pipelines has been a big help for us. It’s made things more efficient, especially when dealing with data issues. For example, we had a situation where some fields in our data didn’t exist on certain records. Without error handling, the pipeline would have just stopped running, and we wouldn’t have been able to do anything with the errors. But with the error handling, I was able to set up nested steps to manage those missing fields and keep the process moving. It’s also helpful that Quickbase allows us to log errors and create records for them, so we can track which vendors are missing specific data points and follow up as needed.

What do you dislike about the product?

It’s not perfect: adding those steps increased the processing time. But the benefit is that we’re getting more detailed and visible data now. While there’s still room for improvement in some areas, Quickbase has made our processes more manageable and efficient overall.

What problems is the product solving and how is that benefiting you?

Before Quickbase, we had challenges with managing and integrating data between systems. For instance, we’re working on an integration between Quickbase and an external system, and Quickbase has been key in helping us pull and push data efficiently. The error handling feature has been a lifesaver in situations where data fields were inconsistent or missing. Without it, we would’ve been stuck, unable to process the data or move forward.
Quickbase has also helped us improve visibility into our data. For example, when errors occur, we can now log them and create records to track what’s missing. This has made it easier to communicate with stakeholders and address issues proactively. Additionally, the flexibility of Quickbase pipelines has allowed us to adapt to our specific needs, like creating custom workflows or handling complex integrations.

What do you like best about the product?

App builder is probably one of my favorites. The dashboard experience is also solid, with a friendly, easy-to-navigate user interface. I’ve also found the pipeline designer feature genuinely useful when multiple systems need to talk to each other. That integration layer has made our workflows much faster and cleaner, especially when we’re working across different projects and portfolio workflows.

What do you dislike about the product?

Cost is probably the first thing I would mention. Once our number of users and apps goes up, Quickbase starts to feel like a much more serious line item. I would also like to see more AI capabilities built directly into the workflows. Other than these, integrations are convenient, the support experience is good, and that is it, I guess. For larger projects, the cost becomes more noticeable.

What problems is the product solving and how is that benefiting you?

We used to spend a big chunk of our working hours just maintaining trackers, moving information between systems, and double-checking records. The cost of that work was almost invisible because nobody was really labeling it correctly. After automating this repetitive work with pipelines and automations, we can now clearly see where time is being saved across different program activities. That visibility has ultimately made the return-on-investment conversation much easier to understand and discuss.