How Did We Start Building Treasury Infrastructure?

Five years ago, Hudson wasn't thinking about treasury infrastructure, or even banks. We were thinking about consumers trying to get back on their feet.

Specifically, the operational chaos sitting inside the consumer debt restructuring industry. Hundreds of thousands of people in repayment programs, each trying to pay back their creditors on restructured terms. Every agreement had its own rules, its own timeline, its own conditions for when funds could move. And a financial institution in the middle, holding the funds, with no real infrastructure to manage what was flowing through those accounts.

We were the technology that made it work — for the institution.

What Consumer Debt Restructuring Taught Us

When you build treasury management infrastructure for a money servicing business processing small transactions for hundreds of thousands of consumers at once, you learn things quickly.

Each consumer had their own sub-account. Their own balance. Their own rules governing when money could move to repay a creditor. When a restructuring agreement was finalized, a formal letter confirmed the terms were satisfied and funds could be disbursed. Early on, someone at the financial institution read each letter manually, matched it to the right account, and triggered the payment.

That works for ten accounts. It does not work for 700K.

So we built a system — embedded inside the financial institution's operations — that reads incoming documents automatically, pulls the relevant data, matches it to the right account, and moves money based on pre-set rules. No one in the middle doing it by hand. We added payment rails directly into the platform, so when a rule fired, the payment went out. No logging into a separate system or manual initiation.

By the end of it, we had treasury infrastructure purpose-built for a financial institution managing high-volume, rules-based money movement on behalf of complex client relationships. It looked niche on paper but was solving something much bigger.

When We Saw the Same Problem in Commercial Banking

The problems we hear regional banks dealing with today — sophisticated client relationships, manual reconciliation, back-office overload on specialty accounts — looked remarkably similar to what we'd spent five years solving for financial institutions in the consumer repayment space.

Property managers collecting rent across hundreds of units, needing to separate security deposits by property and report on each one. Law firms holding client funds across dozens of active cases, each needing its own sub-account and audit trail. Municipalities with strict regulatory reporting. Construction lenders disbursing draws tied to inspection milestones.

And occasionally, ones that catch you off guard — like a research institution managing government grants across dozens of scientists, each with their own allocation, their own milestones, their own compliance requirements. They were tracking it all in Excel. A $10 million government fine later, they needed a better system.

Different use case. Same infrastructure.

What the Platform Does

We sit on top of a bank's existing systems. We don't replace the core, touch the online banking portal, or disrupt existing treasury services. We handle the relationships that are too sophisticated for the core to manage alone.

Here's how it works. The bank keeps one master account at the core — clean, simple, one line on the balance sheet. Everything underneath it lives in our sub-ledger. Every client, property, case, or project gets its own virtual sub-account with a real balance and a full transaction history.

This is the part that surprises people — sub-accounts are fully routable. Funds don't need to land in a master account and get sorted out later. A property manager can send rent directly to the sub-account for a specific building, or a law firm can receive a settlement payment directly into the sub-account for that case.

The month-end reconciliation that used to mean someone manually matching transactions in a spreadsheet? Mostly gone.

Rules handle the logic automatically. A 45-day review window before a disbursement. A revenue split between physicians in a practice group. A construction draw that only releases after an inspection clears. These aren't custom builds — they're configurations. Once the rule is set, the system runs it.

And everything is tracked. Every transaction, every rule that fired, every user action. Reporting isn't a manual quarterly project — it's a scheduled output delivered automatically in whatever format the client or regulator needs.

What This Means for Banks

The clients creating this complexity are already in your portfolio.

Property management groups with growing books. Law firms whose escrow needs keep expanding. Specialty deposit clients whose regulatory requirements don't fit neatly into any existing workflow. Most banks above $3 billion are already serving some version of these clients — just doing it the hard way. As those clients grow, the back-office load grows with them. And the ones they can't service operationally? Those relationships walk out the door.

What makes these accounts worth fighting for isn't just the revenue — it's that the deposits are sticky. Funds that have to sit at the bank because the process requires it don't leave when a competitor offers a better rate. The switching cost is baked into the operations themselves.

Banks have had two ways to manage that: hire people, or turn the business away. Neither one scales.

We've heard that story more than once. It's part of what brought us here.

The treasury infrastructure we built for financial institutions in the consumer repayment space — automated document ingestion, sub-account management at scale, rules-based money movement — turns out to be exactly what banks need to say yes to every relationship. Different clients, different industry. Same underlying problem.

We already know how to solve it.