Most billing platform evaluations fail before they start. This guide covers the 7 criteria, POC structure, and red flags that predict whether you'll regret your choice.
Evelyn Ly
Head of Marketing
A RevOps lead at a $6M ARR SaaS company migrates to a "best-in-class" billing platform. Six weeks later: broken proration logic, a Salesforce sync that fails silently, and two enterprise customers with incorrect invoices. The CEO is asking questions. The auditors are circling.
The platform was actually fine. The evaluation process was broken.
If you've read parts one and two of this series — [The Hidden Cost of Building Your Own Billing System] and [Buy vs. Build Revenue Infrastructure: The Question Finance Leaders Are Getting Wrong] — you've already decided you're buying. This is the guide for making sure you buy the right thing. Here's how to fix your evaluation process.
If you walk into vendor demos without completing this work, you'll let sales reps define your requirements for you. That's how you end up buying a platform optimized for their demo flow rather than your actual business.
Answer these questions before you talk to anyone:
Pricing models today: What do you actually sell? Flat annual contracts? Seat-based monthly? Usage-based consumption? Hybrid combinations? Milestone billing for implementation?
Pricing models in 18 months: Where's the product headed? If you're adding usage-based components or consumption pricing, that's a requirement now. Not later.
Contract complexity: How many active contracts do you have? What percentage include custom terms, special pricing, or non-standard provisions? If it's above 20%, you need a platform that handles exceptions gracefully.
Billing cycles: Monthly? Annual? Quarterly true-ups? Multiple cycles for different customer segments?
Where do errors actually occur? Be specific:
What does your team do manually every month that shouldn't be manual? Track these. They're your requirements.
What's your current close time? What percentage of that is billing-related? This is your baseline for measuring improvement.
Write this down. Share it with your team. Don't deviate during demos when a sales rep shows you a shiny feature you didn't ask for.
Must have: No native ASC 606? Disqualified. No Salesforce sync? Disqualified. Can't handle usage-based metering? Disqualified.
Nice to have: Advanced dunning workflows. Self-service customer portal. Sophisticated analytics.
Disqualifiers: Per-invoice fees above a threshold. Requires engineering for pricing changes. No multi-entity support when you have two legal entities.
These aren't generic "ask about integrations" checkboxes. They're specific criteria with specific questions and specific red flags. Use them.
Not just what you need today. What you'll need when you add a new product line or shift to consumption pricing.
What to look for: Can the platform handle hybrid pricing? Can your team (not engineering) make pricing changes without a deployment?
Red flag: Any pricing change requires dev work or a professional services engagement.
Question to ask: "Walk me through how we'd implement a usage plus seat plus overage model without a custom integration."
This is where most tools fail B2B companies. "We support rev rec" means nothing. You need native ASC 606 compliance that handles multi-element arrangements, contract modifications, and variable consideration.
What to look for: Waterfall logic that updates automatically when contracts change. Support for performance obligations that span multiple periods.
Red flag: They say "we support rev rec" but can't show you how a mid-contract amendment affects SSP allocation in real time.
Question to ask: "Show me exactly how your system handles a contract modification that adds a new product six months into a 24-month deal. How does the rev rec waterfall update?"
The licensing fee is maybe 30% of what you'll actually spend. Here's the full TCO framework:
Cost CategoryWhat's IncludedLicensingBase fee, per-seat costs, usage tiersImplementationVendor PS hours, your team's hours, consultantsMigrationData extraction, transformation, validationOngoing MaintenanceEngineering time for integration upkeepSupport TierWhat you actually need vs. what's includedIntegration CostsMiddleware, custom connectors, API overage
Benchmark: Implementation typically runs $15K–$80K in internal time at 50-person companies. If a vendor quotes you $3K for implementation, they're either underscoping or planning to charge you later.
Question to ask: "What did your last five customers at our ARR spend on implementation, all-in, including their internal team's time?"
Migration is the most common failure mode. It's also the one vendors downplay most aggressively during sales.
What migration actually involves: historical invoices, open AR balances, subscription state, rev rec waterfall continuity. You can't just flip a switch.
What your POC must test: Proration accuracy on imported subscriptions. Data import fidelity for custom fields. Historical reporting continuity so your CFO can pull a report that spans pre-migration and post-migration data.
Red flag: The vendor can't show you a migration runbook or connect you with a reference customer who migrated from your current system.
Question to ask: "Can we speak with a customer who migrated from [your current platform]? What broke during their migration, and how did you fix it?"
The sandbox demos fine. Production breaks at volume. This is the gap you need to close during evaluation.
What to look for: Native integrations vs. middleware-dependent connections. Sync frequency (real-time vs. batched). Error handling when syncs fail.
Critical integrations to validate: CRM (Salesforce or HubSpot), GL (NetSuite or QuickBooks), payment processor, data warehouse.
Red flag: "We integrate with Salesforce" but it's through a third-party connector with separate pricing and support.
Question to ask: "What's your documented API rate limit? What happens to billing jobs when the limit is hit at 10,000 invoices per month?"
At $3–10M ARR, you're betting on a platform you'll scale to $50M+ on. A re-platforming in three years costs more than getting this right now.
What to look for: Funding stage, runway, and whether the roadmap aligns with where your pricing is heading — usage-based, multi-currency, AI-native billing. Ask specifically about features you'll need in 18 months, not just today.
Red flag: Roadmap answers are vague or everything you need is "coming soon."
Question to ask: "What have you shipped in the last two quarters that a customer at our stage directly asked for?"
Most POCs are theater. The vendor controls the data, the scenarios, and the timeline. Here's how to run one that actually tells you what production will look like.
Week 1: Data fidelity and migration simulation
Import a representative dataset. Use real data if you can, anonymized if you must. Validate invoice accuracy on migrated subscriptions. Check proration math. Verify open AR balances match your source system.
Week 2: Workflow and integration stress test
Run a realistic billing cycle from start to finish. Sync to your CRM. Create a mid-cycle amendment on an enterprise contract. Run a rev rec report. Process a dunning scenario through to resolution.
Week 3: Edge case and load testing
Test your top three "this always breaks" scenarios. If you have usage-based billing, simulate a volume spike. Test multi-entity and multi-currency if you need them.
The best platform isn't the one with the most features. It's the one your team will actually trust at 4:30pm on the last day of the quarter.
Getting this wrong doesn't cost you the migration fee. It costs you six months of compounding errors, invoice disputes, and audit findings you have to explain to your board.
Book a 20-minute walkthrough to see how Measure connects contracts, billing, rev rec, and commissions in one system.
Billing and revenue automation that handles contracts, invoicing, revenue recognition, and commissions in one connected system. Book a demo to see how Measure works.
