After watching 248 deals play out across our sales pipeline, I have learned something uncomfortable about how collection agencies evaluate software.
Most agencies get it wrong. Not because they are careless. Because the evaluation process itself is broken.
I run a collections software company. I have a front-row seat to every deal we win and every deal we lose. We track the reason for every single lost deal in HubSpot. When I pulled the data and looked at the patterns, four mistakes kept showing up. They account for the majority of failed evaluations, not just for us, but across the industry.
Here is what the data actually says, and a framework for doing it better.
These come directly from our closed-lost deal analysis. 248 deals. Every loss reason categorized.
This is the most common pattern. Agencies tell us they "can't get off" their legacy portal. They know the technology is outdated. They know it is costing them. But the switching cost feels too high, so they stay.
I am going to be honest about this: switching costs are real. Migration takes work. There is a learning curve. But the question is not whether switching is painful. The question is whether staying is more painful over 3 years. Legacy portals that are not mobile-optimized, that do not support authenticated links, that cannot handle modern payment methods. Those are not just inconveniences. They are revenue leaks.
One of our clients put it simply: the portal link that takes consumers directly to their account to pay changed everything about how they operate. That is not marketing language. That is an operations leader describing what happened to their recovery rate when consumers could actually use the portal on their phone.
"Pricing analysis" shows up constantly in our loss data. An agency compares per-account fees across vendors and picks the cheapest one. Six months later, they are paying for three additional tools to fill the gaps, manually reconciling data between systems, and spending agent hours on tasks the platform should handle.
The real question is not "what does this cost per account?" It is "what does my entire technology stack cost, including the people and processes required to hold it together?"
When agencies consolidate fragmented tools onto a single platform, we have seen efficiency gains above 90% in reducing manual processes. That is not a rounding error. That is the difference between scaling with headcount and scaling with technology.
Some agencies look at the buy-vs-build question and decide to build their own portal or payment system. I understand the appeal. You control the roadmap. You do not depend on a vendor.
Here is the math most teams skip. Building a consumer self-service portal with payment processing, compliance guardrails, document signing, IVR (Interactive Voice Response), campaign management, and real-time reporting is not a one-time project. It is a permanent engineering commitment. You need PCI DSS (Payment Card Industry Data Security Standard) compliance. You need to handle ACH (Automated Clearing House) returns. You need Reg F (CFPB's Regulation F, implementing the FDCPA) frequency tracking. You need to keep up with state-level regulation changes.
We have 8 products and a full engineering team, and we ship 35+ features a year to keep pace. An internal build means you are committing to that same pace indefinitely, or accepting that your technology will fall behind within 12 months.
The fourth pattern: an agency picks a competitor because they have one specific feature. That feature solves a real problem. But 18 months later, the agency has the feature and nothing else, because the rest of the platform does not connect.
Collections software is not a feature contest. It is an architecture decision. The question is whether the platform connects consumer engagement, payments, compliance, communications, and reporting into one workflow, or whether you are buying another point solution that will need to be integrated with five other tools.
Here is the framework I would use if I were evaluating collections software for my own agency. These eight dimensions predict whether a platform will still be working for you in three years.
This is the single highest-value feature in modern collections. One agency reported that 70% of their payments now flow through their consumer portal. That number did not happen by accident. It happened because the portal works.
What to evaluate:
Consumers want to pay the way they pay for everything else. If your platform only supports one or two payment methods, you are adding friction to the one moment where the consumer is ready to resolve their account.
What to evaluate:
SMS, email, and phone should operate from one platform with one compliance engine. Not three separate tools stitched together with API calls.
What to evaluate:
Text messaging strategies as part of a broader consumer engagement strategy at one agency generated nearly 10,000 paid accounts. That is not because SMS is magic. It is because the messages linked directly to a portal that worked, and the whole workflow was connected.
Compliance in collections is not a checkbox. It is an operational discipline that runs every minute of every day across every consumer interaction.
What to evaluate:
This is the dimension most agencies under-evaluate. Your system of record (FACS, Latitude, CUBS, Cogent, or others) is where account data lives. Your collections platform should not try to replace it. It should sit on top of it as an intelligent layer.
The scale of the problem is worth understanding. According to Tratta's 2026 Reality Check survey of 74 industry leaders, 56.8% of organizations still operate with batch or partially integrated systems rather than real-time data sync. Only 13.5% of organizations have consistent maturity across all operational domains. That means most agencies have one area that works reasonably well and three or four that do not, usually because their systems were never designed to talk to each other.
What to evaluate:
We are not a system of record. We are the intelligent layer that sits on top of it. That distinction matters because agencies that rip out their SoR for a new platform face 6-12 months of pain. Agencies that add an engagement layer on top can go live in weeks.
Law firms processing 3,000+ documents per month through DocuSign know the cost adds up fast. When signing is delayed or disconnected from the payment flow, consumers drop off.
What to evaluate:
If your reporting runs on end-of-day batch files and manually compiled spreadsheets, you are making decisions on yesterday's data.
What to evaluate:
Per-account pricing is the most visible number and the least useful one for predicting actual cost.
What to evaluate:
Use this table when comparing platforms. The red flags column tells you when a vendor answer should concern you.
| Evaluation Question | Why It Matters | Red Flag |
|---|---|---|
| Can consumers access their account via authenticated link without creating a login? | Removes the biggest friction point in digital collections. Direct links convert. Login walls do not. | "Consumers need to create an account first." |
| Is the portal natively mobile-optimized? | The majority of consumers will access the portal from their phone. | Vendor shows you a desktop demo and says "it works on mobile too." |
| Does the platform handle ACH, debit, IVR, and digital wallets? | Payment method restrictions cost you completed payments. | Only supports credit card or requires a separate payment processor. |
| Are SMS, email, and phone campaigns managed in one system? | Fragmented communication tools create compliance gaps and manual overhead. | "We integrate with [third-party tool] for SMS." |
| Does the platform enforce Reg F frequency limits automatically? | Manual frequency tracking at scale is a compliance violation waiting to happen. | "Your team manages contact frequency in the SoR." |
| Does it integrate with your SoR via REST API with real-time sync? | Batch file transfers mean your engagement layer is always working on stale data. | "We support nightly file imports." |
| Can documents be signed within the consumer portal workflow? | Disconnected signing creates drop-off. Consumers who leave the portal to sign often do not come back. | Requires DocuSign or Adobe Sign as a separate integration. |
| Are dashboards real-time or end-of-day? | You cannot optimize what you cannot see until tomorrow. | "Reports are generated overnight and available by 9am." |
| What is the total cost including all tools needed to operate? | Per-account pricing hides the cost of the 4 additional tools you will need. | Vendor cannot give you a total-cost-of-ownership estimate. |
| How long does implementation take, and what does migration look like? | Long implementations have hidden costs in staff time, delayed ROI, and parallel system operation. | "Typical implementation is 4-6 months." |
If your team is considering building internally, run this test. Write down every capability in the checklist above. For each one, estimate the engineering hours to build it, the ongoing hours to maintain it, and the compliance risk of getting it wrong.
Then ask: is our competitive advantage in building collections technology, or in collecting? Most agencies exist to recover on accounts, not to become software companies. The agencies that built internally and later came to us spent 12-18 months learning that lesson.
Building is a legitimate choice for some organizations. But it is a permanent commitment, not a one-time project.
The agencies that get the evaluation right share a few traits. They evaluate architecture, not features. They calculate total cost, not unit price. They test the consumer experience, not just the agent dashboard. And they treat switching cost as a known quantity to plan for, not an excuse to stay on software that is not working.
The data from 248 deals tells a clear story. The agencies that made the best decisions were the ones that asked the hardest questions upfront.
If you want to see how Tratta handles these eight dimensions, request a demo. I will walk you through it myself.
Josh Allen is the CEO of Tratta, a collections software platform that serves as an intelligent layer on top of existing systems of record. He can be reached at tratta.io.
This content is for informational purposes only and does not constitute legal advice. Consult qualified legal counsel for compliance guidance specific to your organization.
