TSI paid to use dPlat for more than 12 years before we bought the company that makes it.
A recovery control layer is the operational architecture an organization uses to govern inventory, workflows, service providers, exceptions, evidence and performance across its revenue-recovery environment. dPlat is one concrete version of that layer: the place where accounts, routing rules, vendor performance and account history live in one system rather than in six portals.
dPlat is DebtNext‘s placement and vendor management platform, and TSI ran its own recovery operations on it. Our operations teams opened it every morning. Our analysts pulled placement and performance data out of it. Our clients’ recovery strategies ran through it. When we acquired DebtNext Software in September 2025, we already knew where every rough edge was, because some of them we had been working around ourselves for a decade.
That is a strange way to buy a company. It is also why we can talk about the platform without a script.
What does DebtNext software (dPlat) do?
dPlat is the system of record for a multi-vendor recovery program. If you place charged-off accounts with more than one agency, you have a coordination problem. Files go out. Payments come back. Accounts get recalled, disputed, bankrupt, deceased, or paid in full somewhere you weren’t looking. Multiply that by four vendors, three placement stages, and a compliance team that wants an audit trail for all of it.
dPlat holds that: placement routing, recall logic, data exchange with each agency, performance measurement stage by stage, commission reconciliation, and the full history of what happened to an account and when. It has been built for recovery management since 2003, which is a long time to spend on one narrow problem.
Today the platform manages $100M+ in monthly placements.
Where does the control layer sit?
Between the systems that create the debt and the people and systems that work it. Four layers, in order:
| Layer | What lives there | Who owns it |
|---|---|---|
| Systems of record | Billing, servicing, EHR, ERP, CRM | The creditor |
| Recovery control layer | Inventory, routing rules, workflow, vendor allocation, compliance controls, exceptions, media, disputes, performance, reconciliation, audit history | The creditor, running on dPlat |
| Execution layer | Digital communication, first-party operations, third-party agencies, legal, debt sale, human operators, AI agents | The creditor, its vendors, or TSI |
| Management layer | Performance, risk, compliance, net-back, optimization | The creditor |
dPlat is a concrete manifestation of the control layer. TSI is one of the operators that can run portions of the execution layer, when a client wants that. Those are two different purchases, and a client can make either one without the other.
Why does it matter that we used DebtNext software first?
Because the roadmap arguments were already settled before the deal closed.
Software companies do customer research. They run advisory boards, ship surveys, sit in on QBRs. All useful, and all secondhand. We had the firsthand version. For 12+ years, TSI felt the product the way a client feels it: at volume, under compliance pressure, on a Monday when a file didn’t land. We knew which reports people actually opened and which ones existed because somebody asked for them once in 2014. We knew where the workarounds lived, because our own analysts had built them.
TSI manages $64B+ in receivables and recovered $1.5B+ in calendar 2025. That is the operating context the platform now sits inside. The people funding the dPlat roadmap run recovery operations at scale every day, and they use the tools.
What changed at DebtNext, and what stayed the same?
dPlat is still dPlat. The DebtNext team runs it under Paul Goske, the product keeps its own name and its own clients, and clients who use the software without using TSI as an agency keep doing exactly that. Several do.
What changed is the balance sheet behind the roadmap and the depth of the operational input into it. A product roadmap at a small software company competes with payroll. A product roadmap inside a recovery organization that manages $64B+ in receivables competes with other line items.
How much control does the client keep in DebtNext software?
All of it, by design. The routing rules on dPlat are client-owned. A client configures them to their own placement policy, their own vendor scorecard, and their own risk tolerance, and the platform executes what they configured.
Around that sits the governance structure: independent oversight, led by former federal regulators. NIST-aligned controls under it. The same oversight structure that covers TSI’s recovery operations covers how the platform is administered.
Â
FAQ
Is dPlat collection software? No. Collection software runs the work inside an agency: dialers, letters, agent desktops, payment posting. dPlat sits a layer above that. It holds the inventory, the rules, the vendor panel and the account history, and it hands work to whoever executes it.
Can a client use dPlat without placing anything with TSI? Yes, and many do. That was true before the acquisition and it is true now. TSI has to earn placement volume the same way it earns it anywhere else.
Who sets the routing rules? The client. A client’s routing strategy is the client’s property, configured to their placement policy, their vendor scorecard, and their risk tolerance.
Â
Â