Built From Inside the Operation: The Quandis Founding Story

Most software companies study an industry from the outside, then build for it. Quandis started the other way around. When Eric Patrick and Kevin Cassidy began building software for financial services in 2003, they were already inside the operations they meant to fix. They knew the workflows and the compliance requirements. They knew how servicers worked with their attorney networks. Above all, they knew where the process kept breaking.

It’s a story we don’t tell often enough, so here it is.

The pattern they kept seeing

Again and again, they saw sophisticated organizations running critical work on disconnected systems. Hand-offs were manual. Processes held together at low volume and came apart as volume grew. Every missed step showed up later as rework, a delay, or a compliance exception.

The tools on the market didn’t help much. Some were too generic to handle the complexity of regulated servicing work. Others were too rigid to adapt when regulations changed, and regulations changed constantly. A team could either bend its process to fit the software or keep working around it by hand.

Nobody was building the fix, so they built it themselves.

Built for the industry, not adapted to it

Quandis was designed for the specific problems financial services operations actually face. It wasn’t a horizontal platform with a financial services module added later. It was built from the ground up for regulated, document-heavy work that depends on partners.

That focus shaped everything that followed:

• Attorney reporting. Attorney Data Reporting (ADR) gave attorneys a way to report case status on Freddie Mac loans. Later, the Default Reporting Application (DRA) did the same for Fannie Mae loans.
• Compliance searches. Bankruptcy Search monitors court records through PACER. Military Search verifies active-duty status for SCRA, and later MLA, compliance.
• A platform underneath it all. QBO grew through successive generations into the orchestration platform our products run on. It gives every case its workflow, documents, tasks, deadlines, decisions, and audit trail in one place.
• AI inside the workflow. AI models are governed steps within the process, and QDocs brings intelligent document processing to the same platform.

Each of these products started the same way, with a problem our team had seen up close.

Why the origin still matters

The founding idea is still how we work today. Every compliance check we’ve automated, every workflow we’ve built, and every integration we’ve mapped comes from more than two decades inside these operations. We speak the language, and we know what’s at stake. We know what a missed SCRA check or a misclassified bankruptcy filing actually costs an organization.

That kind of knowledge can’t be built overnight. Another platform can’t copy it by adding a financial services module. It shows up in small details, such as a deadline that’s tracked automatically or a document that reaches the right attorney without a phone call. It shows up when a regulatory change can be handled with a configuration change instead of a rewrite.

Still in the room

Mortgage servicing is one of the most regulated, document-heavy, partner-dependent operations in the United States. More than 20 years there have proven the approach. The same platform now supports credit unions and insurance, because the core problem is the same: complex work, strict rules, and many parties who all need to stay in step.

We’ve been in the room since 2003, and we’re still there. Read more about the Quandis story, timeline, and values.