A guide for MCA funders
BEFORE YOU CHOOSE
Choosing the right platform
The right platform is the one built for how MCA operations actually work. Here's how to tell.
What staying on spreadsheets costs as volume grows
Before you weigh what a platform costs, run what your current setup is actually costing you.
| At your current volume, count what you're spending on: | Honest answer |
|---|---|
| Hours per week your submissions rep spends building deal files by hand | _____ hrs × _____ weeks = _____ |
| Hours per month your ops manager spends rebuilding the syndicator report | _____ hrs × _____ /hr = $_____ |
| Hours per month spent reconciling ACH records against your spreadsheet balances | _____ hrs × _____ /hr = $_____ |
| Deals delayed or lost last quarter because approval was too slow | _____ deals × avg margin = $_____ |
| People hired in the last 12 months specifically to handle manual data work | _____ headcount × annual cost = $_____ |
Add those up. That's what staying costs at your current volume. At 2x volume, every number roughly doubles.
What to confirm before you sign with any platform
Not every platform marketed to MCA funders was built for MCA operations. Some are generic CRMs with MCA features bolted on. Others handle origination well but were never designed for daily ACH servicing or syndicator reporting.
- Full lifecycle in one system
Origination, underwriting, funding, ACH servicing, collections, syndication, and portfolio reporting should all run inside the same platform on the same deal record. Every tool boundary is a place where data has to be reconciled manually. - Direct ACH processor integration
The platform should connect directly to your ACH processor and sync automatically. If your ops rep still logs into a separate portal to set up payment plans or check daily returns, the core servicing problem isn't solved. - No-code scorecard configuration
Your head of credit should be able to update FICO thresholds, NSF tolerances, and industry restrictions without filing an engineering ticket. If every credit policy change requires a developer, your underwriting box will always lag behind your risk appetite. - MCA-native, not MCA-adapted
Platforms built for MCA from the ground up handle factor rates, daily ACH, holdback adjustments, and renewal logic as built-in workflows. Platforms adapted from generic LOS or CRM tools handle them through configuration that often breaks on mid-contract changes. - Audit trail on every decision
Every approval, decline, override, payment change, and collection action should be timestamped and logged against the deal record with the rule set that produced it. If you can't pull a full audit trail on any deal in one click, you have a compliance exposure. - Dedicated support contact, not a ticket queue
You need a named person who knows your operation and can be reached directly when something breaks. A general intake form means you're a ticket number when your ACH sync fails on a Monday morning. - Realistic implementation timeline
A platform built for MCA should get you live in 2–4 weeks for a standard operation. If a vendor's implementation timeline starts at 3 months before any deals run through it, the platform wasn't built for how MCA operations actually work.
What to ask every vendor in the demo
Most demos focus on what the software can do in ideal conditions. These questions surface how it behaves in the conditions you actually operate in:
| Ask this | What the answer tells you |
|---|---|
| If a merchant requests a holdback adjustment on day 12, how does that get handled inside the platform? | If the answer involves any manual step outside the system, mid-contract servicing is not fully built. |
| Can I see what happens when an ACH payment fails overnight? | Watch whether the failed payment automatically routes to a collections queue or requires someone to log in and find it. |
| If my head of credit changes a FICO threshold today, which currently funded deals were approved under the old rule? | Tests audit trail depth. If they can't show you a versioned history of scorecard changes mapped to decisions, the compliance layer is weak. |
| Who is my dedicated contact after go- live, and what's their direct line? | If the answer is a support portal or a shared inbox, support will be slow when it matters. |
| Can I export all my deal data, and in what format? | Tests data portability. A vendor who makes this hard is designing lock-in into the product. |
| Show me a syndicator statement generated directly from the platform | If they can't show you a live example, syndicator reporting is either manual, limited, or not yet built. |
YOU NOW HAVE A PLAN
Ready to see your business without the spreadsheets?
The prep work in this guide is what most MCA shops skip. It's also why most migrations take longer than they should. You're ahead of that now. Book a walkthrough of Onyx IQ and we'll show you exactly how the platform handles the lifecycle you just mapped — automatically.
Book a Demo