The tools fraudsters use are evolving faster than most businesses can keep up. Deepfakes and sophisticated presentation attacks are no longer theoretical threats; they are actively being used to fool traditional security systems. If your current identity verification solution was built for a simpler time, you might have a serious security gap. This leaves many platform leaders asking a critical question: Can existing KYC/IDV vendors, such as Jumio, Onfido, and Veriff, be replaced without a full rebuild to counter these modern threats? The good news is that you don’t need to be stuck with outdated technology. A full system tear-down isn’t the only path forward. You can integrate advanced, targeted solutions to address today’s biggest risks while keeping your core infrastructure intact.
Key Takeaways
- Assess Your Vendor’s True Cost: Look beyond the price per check and calculate the total cost of your current IDV solution, including the operational expenses from manual reviews, lost revenue from frustrated users, and the risk of being unprepared for deepfake threats.
- Test New Solutions Without a Full Rebuild: You can avoid a complete system overhaul by using an API-first approach to run parallel tests. This lets you integrate new capabilities, like advanced liveness detection, and gather real performance data with your live traffic before committing to a switch.
- Prioritize Proven Technology and Flexibility: Choose a new partner based on their proven ability to stop sophisticated attacks, which should be confirmed by independent, third-party testing. A great vendor also offers flexible deployment options to create a secure, low-friction experience for your legitimate customers.
What Do Traditional IDV Vendors Offer?
If you’re running a platform that requires user trust, you likely already have an identity verification (IDV) vendor. These services form the bedrock of digital trust for many businesses, from fintech startups to global marketplaces. They typically focus on answering one fundamental question: Is this person who they claim to be? To do this, they offer a suite of tools built around three core functions: verifying official documents, using biometrics to match a user to that document, and helping you meet strict regulatory requirements. This traditional approach has become the standard for onboarding new users, creating a crucial first line of defense against basic fraud and helping companies satisfy legal obligations.
The process is probably familiar to you. A new user signs up and is prompted to take a picture of their driver’s license or passport. Then, they take a selfie to prove they are the person in the photo. Behind the scenes, the IDV vendor’s software analyzes the document for authenticity, compares the two images, and runs the user’s information against various watchlists. For many years, this model has been sufficient. It provides a tangible, document-based anchor for a user’s identity and a clear audit trail for compliance. Understanding what these traditional vendors do well is the first step in figuring out where they might be falling short in an era of more sophisticated threats.
Verifying Documents Across the Globe
The most common feature of any IDV service is document verification. This process involves asking your users to submit a photo of a government-issued ID, like a driver’s license or passport. The vendor’s technology then analyzes the document for signs of forgery, checks its data against official records, and confirms its authenticity. The goal is to provide a strong starting point for identity assurance. Many vendors specialize in verifying documents from all over the world, with some supporting thousands of document types across more than 200 countries. This global reach is essential for platforms with an international user base, ensuring you can onboard customers no matter where they are.
Using Biometrics and Liveness Detection
Of course, a valid ID is only useful if the person presenting it is the legitimate owner. This is where biometrics and liveness detection come into play. After scanning their document, the user is typically prompted to take a selfie or a short video. The vendor’s software then uses facial recognition to compare the user’s face to the photo on the ID. Liveness detection adds another layer of security by confirming the user is physically present, preventing fraudsters from using a static photo or a deepfake video to trick the system. This process is a critical step for KYC and AML compliance, as it connects a real, live person to the verified document.
Meeting AML and Compliance Needs
For many industries, especially finance, IDV is not just a good idea; it’s a legal requirement. Traditional vendors build their services to help businesses meet strict Anti-Money Laundering (AML) and Know Your Customer (KYC) regulations. These rules require companies to verify their customers’ identities to prevent financial crimes like fraud and money laundering. IDV platforms provide the necessary tools to perform these checks during onboarding. Many are designed to integrate directly with your systems, enabling you to perform live transaction monitoring and report suspicious activity as part of your broader KYC & IDV solutions. This makes them an essential partner in your compliance strategy.
Why Look for an Alternative to Your IDV Vendor?
Choosing an Identity Verification (IDV) vendor is a big decision, and for a while, the partnership might feel seamless. But the digital world changes fast, and the solution that worked for you last year might be holding you back today. Sticking with a vendor that no longer meets your needs isn’t a sign of loyalty; it’s a risk to your business, your customers, and your reputation. If you’re starting to feel the friction, it’s a good time to step back and assess if your current provider is still the right fit.
Recognizing the signs that it’s time for a change is the first step. Maybe your team is spending too much time on manual reviews, or your good customers are getting frustrated with the onboarding process. Perhaps you’re worried that your current system isn’t prepared for the next wave of sophisticated fraud. Or maybe the bills just don’t make sense anymore. These aren’t just minor inconveniences; they are strategic problems that can impact your growth and security. Let’s walk through some of the most common reasons why companies decide it’s time to find an alternative.
When Performance and Pass Rates Falter
Nothing is more frustrating than seeing legitimate customers fail verification. Low pass rates create a terrible first impression and can cause potential users to abandon your platform altogether. This also creates a huge operational headache for your team, forcing them to spend valuable time on manual reviews instead of focusing on higher-value tasks.
Many IDV providers have expanded their services to cover both onboarding and ongoing authentication. However, if your vendor’s performance is consistently poor and pass rates aren’t hitting your targets, it’s a clear signal to look elsewhere. Your business needs effective identity verification systems that can accurately approve real users without adding unnecessary friction. When your current solution starts blocking more good users than bad ones, it’s time for a change.
The Growing Threat of Deepfakes
The tools used by fraudsters are becoming more advanced every day. The growing threat of deepfakes has changed the game, making traditional liveness detection and document analysis less reliable. These AI-generated fakes can easily fool systems that aren’t specifically trained to spot them, putting your platform at risk of account takeovers, fraud, and manipulation.
If your current IDV vendor isn’t talking about how they are actively fighting deepfakes, or if their solution feels like a simple box-checking exercise, you have a serious security gap. You need a partner who prioritizes advanced detection technologies and is constantly evolving to stay ahead of attackers. Protecting your platform requires more than just basic verification; it requires proven defense against the most sophisticated threats out there.
When Your Pricing Model Stops Making Sense
A low price per check can be appealing, but it rarely tells the whole story. The true cost of your IDV vendor includes much more than the sticker price. You also have to account for the costs associated with failed checks, manual reviews, and the customer support hours spent helping users who get stuck in the verification process. If your pass rates are low, these hidden expenses can quickly add up.
If your monthly bills are unpredictable or the total cost of verification is creeping up, your pricing model may no longer be sustainable. A good partner offers a transparent and predictable pricing structure that aligns with the value they provide. When the cost of your IDV solution starts to outweigh its benefits, it’s a smart move to explore alternatives that offer a better return on your investment.
Can You Switch Vendors Without a Full Rebuild?
The thought of switching your identity verification (IDV) vendor can bring on a major headache. You might picture months of development work, endless meetings, and the daunting task of rebuilding your entire system from the ground up. The good news is, it doesn’t have to be that way. If you’re working with the right technology and a strategic partner, swapping out your IDV provider can be a surprisingly smooth process. The key is understanding when a simple switch is possible and when a larger overhaul is truly necessary.
The Power of an API-First Approach
An API-first design is your best friend when it comes to vendor flexibility. Instead of being locked into a single provider’s rigid software, an API-first approach allows you to plug new services directly into your existing workflows. Think of it as a universal adapter for your tech stack. This strategy is especially powerful for core business systems. For example, a well-designed identity verification ERP integration embeds identity checks directly into the platforms you already use for customer, vendor, and employee onboarding. This means you can switch to a new vendor with a compatible API without having to re-architect your entire operational foundation, saving you significant time and resources.
What Is a “Drop-In” Replacement?
A “drop-in” replacement is exactly what it sounds like: a new solution that can be slotted into your current system with minimal disruption. This is possible when a vendor has built their technology to be modular and compatible with common industry standards. For financial institutions, a strong KYC integration allows them to embed identity verification and risk scoring directly into their existing onboarding processes. When you switch to a new vendor that offers a true drop-in solution, the transition feels less like a massive construction project and more like swapping out a single component. Your user experience remains consistent, and your backend workflows continue to run smoothly with the new, improved service powering them.
Know When a Full Rebuild Is Necessary
Sometimes, a full rebuild is unavoidable, but it’s usually a sign that your business needs have fundamentally outgrown your technology. If your current system can’t support critical new capabilities, like ongoing authentication or advanced deepfake detection, simply switching vendors won’t solve the underlying problem. As compliance and security demands evolve, many platforms find that basic IDV is no longer enough. Modern Know Your Customer systems now require a more integrated approach to fighting fraud throughout the customer lifecycle. If your legacy architecture prevents you from adding these essential layers of protection, a rebuild may be the right strategic move to secure your platform for the future.
What Are the Real Integration Hurdles?
Switching your identity verification vendor, even with a flexible API, isn’t quite as simple as swapping out a lightbulb. While an API-first approach saves you from a complete system overhaul, you’ll still face a few practical challenges. Think of these not as deal-breakers, but as key items on your project checklist. Planning for these hurdles ahead of time is what separates a stressful, chaotic transition from a smooth, successful one. From aligning new tools with your existing workflows to making sure your compliance standards never waver, let’s walk through the main integration challenges you can expect.
Aligning Workflows and SDKs
Your first task is to make the new vendor’s tools feel like they’ve always been part of your platform. This involves more than just plugging in a new Software Development Kit (SDK). You need to ensure the new verification steps fit seamlessly into your user’s journey, whether that’s during onboarding or a high-risk transaction. A clunky or confusing experience can lead to drop-off and frustration. On the back end, you’ll need to map the new API endpoints to your existing business processes. For example, you’ll want to streamline compliance by ensuring the new verification data flows correctly into your CRM or ERP systems, keeping your customer records accurate and up-to-date without manual work.
Handling Gaps in Document Coverage
Not all IDV providers are created equal when it comes to the types of documents they can verify. Your current vendor might excel at handling a wide range of international passports, while a potential new partner may have a more limited library. These gaps in document coverage can leave certain segments of your user base unable to access your platform. Before you commit to a switch, it’s critical to audit the new vendor’s capabilities against your user data. This ensures the provider you choose can serve your audience today and support your growth into new regions tomorrow. This process is a fundamental link in the KYC value chain and protects your ability to onboard legitimate users from anywhere in the world.
Plan Your Data Migration and Portability
Moving years of historical verification data from one vendor to another is a delicate process. You need a clear plan for data migration and portability before you begin. Start by asking critical questions: Can you export your data from the current vendor? What format is it in? How will you map old data fields to the new system? A well-thought-out migration plan should include data scrubbing to ensure quality, test runs to catch errors, and a secure process for the transfer itself. This is also an opportune moment to review and strengthen your overall security framework, ensuring all historical and new data is protected. A successful migration maintains a complete, auditable trail of user verifications, which is essential for both compliance and customer support.
Maintain Compliance During the Switch
Your regulatory obligations don’t pause just because you’re switching vendors. You must maintain continuous compliance with standards like Anti-Money Laundering (AML) and Know Your Customer (KYC) throughout the entire transition. A gap in your verification or monitoring capabilities, even for a short time, can expose your business to significant risk. A smart strategy is to run your old and new systems in parallel for a brief period. This allows you to confirm the new vendor is flagging suspicious activity correctly before you fully decommission the old one. Strong KYC integration embeds identity verification directly into your workflows, helping you manage risk and meet your obligations without missing a beat.
Calculate the True Cost of Switching Vendors
When your current identity verification vendor isn’t cutting it, the temptation to jump to a provider with a lower price per check is strong. But a cheaper sticker price rarely tells the whole story. To make a smart switch, you need to look beyond the marketing claims and calculate the total cost of ownership. This means accounting for every expense, from obvious fees to the hidden costs of a poor integration or a compliance misstep. A thorough calculation protects your budget and ensures your new partner is a true asset, not a liability in disguise. Thinking through these factors will give you a realistic picture of what you’ll actually spend and what you stand to gain (or lose) with a new vendor.
Factor in Direct Costs
The price per check is just the starting point of your calculation. A vendor might offer a low initial rate, but what happens when the system can’t make a decision? You need to factor in the costs for every failed check and subsequent re-attempt. Many platforms also require human reviewers to step in when the AI falters, adding significant operational overhead. As one analysis points out, you have to consider the costs for human reviewers when the AI can’t make a decision. These expenses can quickly erode any savings from a lower per-check fee, especially if the new vendor’s pass rates are lower than what you’re used to. Don’t forget to also account for the one-time setup and integration costs, which can vary widely between providers.
Uncover the Hidden Costs
Beyond the direct fees are the hidden costs, which often carry the biggest financial risk. What is the price of non-compliance? Failing to meet regulatory requirements can lead to staggering fines that dwarf any savings you might have made on verification checks. The reputational damage from a compliance failure or a security breach can be even more devastating, eroding customer trust that took years to build. These are not just abstract risks; they are real financial threats. When a vendor’s system creates friction and causes legitimate customers to drop off, you’re losing revenue. The true cost includes the business you lose from a clunky, unreliable, or easily spoofed verification process.
How to Calculate Your Total Cost of Ownership
To get a true sense of the total cost, you need a more holistic formula. Start by looking for a provider that consolidates the services you need. Choosing a vendor that owns essential components like identity verification, biometrics, and sanctions screening ensures tighter integration and simpler compliance. This approach, as industry experts suggest, can significantly lower your total cost by reducing the complexity of managing multiple systems. Also, consider how the solution integrates with your existing platforms. A system that plugs directly into your ERP, for example, can streamline compliance and automate onboarding processes, saving you time and money in the long run.
How to Stay Compliant When Switching Vendors
Switching identity verification vendors brings up a major, non-negotiable concern: compliance. The thought of managing complex data privacy laws and financial regulations during a transition is enough to give anyone pause. But you don’t have to let compliance risks keep you stuck with an underperforming vendor. With a clear plan, you can maintain your legal and regulatory obligations without missing a beat. It all comes down to doing your homework before, during, and after the switch. This means getting a deep understanding of your data handling duties, ensuring there are no gaps in your AML and KYC processes, and thoroughly vetting your new partner’s certifications before you make the final decision.
Understand Your Data Handling Obligations
Before you move a single byte of data, you need a firm grasp on your responsibilities. Regulations like GDPR in Europe and CCPA in California set strict rules for how you handle personal information, and these rules don’t go on vacation just because you’re switching providers. Your first step is to map out your data. What information do you hold? Where is it stored? Who has access? Work with your legal and security teams to create a data migration plan that ensures sensitive information is protected at every stage of the transfer. This isn’t just about your new vendor’s security; it’s about your own internal processes for handling the move securely.
Ensure AML and KYC Continuity
For businesses in regulated industries, maintaining continuous Anti-Money Laundering (AML) and Know Your Customer (KYC) checks is critical. You simply can’t afford a gap in your monitoring. A lapse during a vendor transition could expose you to significant financial and legal penalties. The key is to find a new partner whose tools can be integrated smoothly into your existing systems. Modern KYC integration helps you embed identity verification directly into your onboarding and transaction workflows, ensuring your compliance processes remain uninterrupted. Since regulations are constantly evolving, your new vendor must also demonstrate an ability to adapt and keep you compliant long-term.
Verify Vendor Certifications Before You Sign
Think of this as your final due diligence checkpoint. Before you sign any contracts, ask for proof of your potential vendor’s compliance credentials. Don’t just take their word for it; request documentation for certifications like ISO 27001 for information security management and SOC 2 reports, which cover security, availability, and confidentiality. A vendor that readily provides these has a mature security posture. Choosing a partner that already follows important global privacy and security rules like GDPR and CCPA will make your transition significantly smoother and give you confidence that your compliance framework remains solid.
How to Choose Your Next IDV Vendor
Switching your identity verification vendor can feel like a huge task, but finding the right partner can completely transform your platform’s safety and user experience. The market is crowded with options, and it’s easy to get lost in feature lists and pricing tables. The best vendor for you won’t just offer a list of services; they will act as a strategic partner who understands your goals.
Think of this as more than a technical swap. It’s an opportunity to strengthen your defenses against fraud, streamline your onboarding process, and build deeper trust with your users. To make the right choice, you need to look beyond the sales pitch and evaluate vendors on the criteria that truly matter for long-term success. The following points are a great place to start your evaluation.
Prioritize Deployment Flexibility
Your users are not all the same, so your verification process shouldn’t be a one-size-fits-all ordeal. A rigid system that forces every user through the same high-friction steps can lead to frustration and drop-off. Look for a vendor that offers a flexible approach to deployment. The best solutions allow you to tailor the verification journey based on risk signals or user context.
For example, you might use a lightweight check for a low-risk action but require a more robust verification for a sensitive transaction. As one industry analysis notes, it’s wise to find vendors that can verify identities using various trusted sources or digital IDs. This adaptability makes the process smoother for legitimate customers while maintaining strong security where it counts most.
Look for Proven Deepfake Detection
In an era of sophisticated AI-generated fakes, a simple “blink-and-you’re-in” liveness check is not enough. Deepfakes and presentation attacks are becoming increasingly common, and your vendor needs to be equipped to handle them. Don’t just take their word for it; ask for proof that their technology works against modern threats.
The most reliable vendors submit their systems for independent testing. Look for solutions that have achieved a high level of Presentation Attack Detection (PAD) compliance from accredited labs. According to security experts, you should confirm a vendor’s liveness detection has been tested by an independent group, with iBeta Level 2 or 3 being a strong indicator of quality. This third-party validation gives you confidence that you’re protected from advanced spoofing attempts.
Compare Accuracy and Pass Rates
The ideal identity verification system strikes a delicate balance: it must be strong enough to stop fraudsters but seamless enough to welcome legitimate users. A system with poor accuracy can be just as damaging as one with weak security. If your vendor has high false rejection rates, you risk turning away good customers and damaging your brand’s reputation.
When evaluating potential partners, ask for transparent data on their pass rates. Dig deeper than the general numbers and inquire about performance across different demographics, document types, and regions relevant to your user base. A vendor whose systems were built from the ground up to handle a wide variety of global documents is often more reliable. Your goal is to find a partner who minimizes friction for good users while effectively identifying bad actors.
Ask About Transition and Migration Support
The thought of migrating to a new vendor can be daunting, especially when you consider the potential for downtime and disruption. A great partner will make this process as painless as possible. Before you sign any contracts, get a clear understanding of the support they offer during the transition period.
A vendor should provide comprehensive API documentation, dedicated technical support, and a clear migration plan. The goal is to make the switch feel less like a massive overhaul and more like a simple integration. The right partner will work with you to ensure the new system can be implemented without creating a confusing or broken experience for your existing customers. This hands-on support is often what separates an average vendor from a true partner.
Check for Technology Ownership
It’s important to know who built the technology you’re buying. Some IDV vendors are actually just resellers, bundling services from multiple third-party providers. While this approach can work, it often creates a disjointed experience and complicates support. When something goes wrong, your vendor may have to coordinate with several other companies to find a solution, leading to delays.
A vendor that develops its own core technology, from document reading to liveness detection, has much greater control over its product. This vertical integration typically results in a more cohesive user experience, faster innovation, and more responsive support. As a general rule, it’s better if a vendor builds its own tools instead of relying on a patchwork of partners. This full-stack approach ensures greater accountability and a more reliable, secure platform for your business.
How to Test a New Vendor Before Committing
You wouldn’t buy a car without a test drive, and you shouldn’t commit to an identity verification vendor without putting them through their paces. A polished sales demo is one thing; performance under the pressure of your actual business needs is another entirely. Before you sign any contracts, you need to conduct a thorough, real-world evaluation to see how a potential partner measures up. This process is about more than just checking boxes. It’s about gaining the confidence that a new vendor can protect your platform, your decisions, and your users from emerging threats like deepfakes and sophisticated fraud. A proper testing phase gives you concrete data to justify your decision and ensures you’re choosing a partner, not just a product. It’s your chance to see past the marketing claims and understand exactly how a solution will integrate with your workflows and impact your customer experience. A comprehensive test plan should focus on three critical areas: performance with live traffic, resilience against high-risk threats, and the quality of their support and accountability.
Run Parallel Tests With Live Traffic
The only way to truly know how a vendor will perform is to test them with your own customer traffic. Set up a parallel test, sometimes called an A/B test, where you route a small percentage of your live user onboarding sessions to the new vendor. This allows you to compare their performance directly against your current solution in a controlled environment. Pay close attention to key metrics like pass rates, user friction, and completion times. As experts recommend, you should test any potential vendor with your most challenging documents and in your riskiest markets. This isn’t about seeing the vendor at their best; it’s about seeing how they handle your reality.
Test High-Risk and Edge-Case Scenarios
While live traffic provides a baseline, you also need to intentionally test for the worst-case scenarios. Work with your team to create a library of tests that target specific vulnerabilities. This should include submitting known fraudulent documents, low-quality images, and even sophisticated injection attacks or deepfake videos to see if you can fool the system. A vendor’s true value is revealed by how it handles these deliberate attacks. Strong risk management requires embedding identity verification that can withstand these pressures directly into your workflows. Don’t forget to include edge cases specific to your user base, like uncommon ID types or users in challenging network conditions.
Evaluate Support, SLAs, and Accountability
Technology is only half of the equation. Your IDV vendor is a partner, and you need to know you can count on them when issues arise. Before committing, evaluate their support infrastructure. What are their guaranteed response times? Do you get a dedicated account manager or just a generic support email? You can even create a test support ticket during your trial period to measure their responsiveness and the quality of their answers. Scrutinize their Service Level Agreements (SLAs) to understand what happens if they fail to meet performance targets. A strong partner will offer clear accountability and expert support, providing compliance solutions that feel like an extension of your own team.
A Simpler Path to Integration With VerifEye
Switching IDV vendors can feel like a monumental task, and the thought of a full rebuild is enough to stop any project in its tracks. You’re likely worried about aligning complex workflows, migrating sensitive data, and the operational drag of retraining your team. But what if you could get the security and performance you need without tearing down your existing infrastructure? This is where a more focused, modern approach can make all the difference.
Instead of a monolithic, all-or-nothing system, VerifEye provides a powerful, targeted signal: proof of human presence. Our technology is designed to confirm that a real person is behind a device, giving you a reliable anchor of trust that you can integrate into your existing stack. Because VerifEye is built with an API-first mindset, it serves as a flexible component rather than a complete replacement. You can add its deepfake detection and liveness capabilities to your current onboarding flow or use it to re-verify users at high-risk transaction points.
This approach helps you move away from the slow, manual reviews that can bog down operations. By embedding real-time human verification directly into your workflows, you can automate critical business processes and strengthen compliance without adding frustrating steps for your legitimate customers. Integrating a solution like VerifEye allows you to enhance your security posture against modern threats like deepfakes while maintaining the systems you already have in place. It’s not about starting over; it’s about making what you have stronger, safer, and more resilient.
Related Articles
- The Ultimate Guide to KYC Verification Online
- What Is Third-Party ID Verification? A Guide
- 4 Best Anonymous Identity Verification Solutions
- 5 Best APIs for User Identity & Fraud Detection
Frequently Asked Questions
Is my current vendor’s liveness check really not enough to stop deepfakes? It’s a great question to ask. Many traditional liveness checks were designed to stop simple spoofs, like holding a photo up to the camera. Deepfakes are a different beast entirely. They are AI-generated videos that can mimic real human movement, making them very convincing to systems not specifically trained to detect them. You need a partner whose technology has been independently tested and proven to identify these advanced attacks, otherwise you have a significant security gap you might not even know about.
Realistically, how long does it take to switch to a new IDV vendor? The timeline can vary quite a bit, but it doesn’t have to be a year-long project. If you choose a vendor with a modern, API-first design, the technical integration can often be done in just a few weeks. The biggest factors influencing the schedule are your own internal planning, data migration strategy, and the complexity of your workflows. A well-planned transition that includes a parallel testing phase might take a couple of months from start to finish.
My current vendor is cheap per check. How can a more expensive vendor actually save me money? The price per check is only one small part of the total cost. You have to consider the money you lose when legitimate customers fail verification and abandon your platform. You also have to account for the salary hours your team spends on manual reviews for every failed check. A vendor with higher accuracy and better pass rates might have a higher sticker price, but they can save you a significant amount of money by reducing customer drop-off and freeing up your team’s time.
Do I have to replace my entire IDV system to use VerifEye? Not at all, and that’s one of its key advantages. VerifEye is designed to be a flexible component that can strengthen your existing security stack. You can integrate it into your current onboarding flow to add a powerful layer of deepfake and liveness detection without ripping out the document verification service you already use. You can also use it for ongoing authentication to confirm a real human is present during high-risk moments, like a password change or a large transaction.
What’s the first step to setting up a parallel test with a new vendor? The first step is to have a clear conversation with the potential vendor about running a proof of concept. You’ll want to define what success looks like by setting clear goals for pass rates and accuracy. Then, your technical team can work with their support team to get API access and route a small, specific percentage of your live traffic (say, 5%) to their system. This lets you gather real-world data and compare their performance directly against your current provider.