Lending Operations Automation
Software Deployment for SME Lenders: Best Practices
Today, agile software is essential for SME lending success. Discover the best practices to follow when selecting and deploying a new platform.
MCA Software Support: The Questions to Ask Before You Sign
Onyx IQ
Jul 10, 2026
When you're evaluating MCA software, it's easy to spend the whole time looking at features. That's what the demo is built to show you. But the moments that actually test the vendor come later.
A new hire builds a scorecard wrong and you catch it mid-funding. You've got a merchant ready to sign and the offer terms aren't set up right. A workflow got misconfigured a few weeks back and you're only seeing it now. In every one of those situations, what you need is someone who picks up and helps you fix it before it costs you the deal. Whether a vendor does that is the thing the demo won't tell you, so you have to ask.
Below are the questions that get the real support model out into the open, along with what a good answer sounds like and what should make you pause. Bring them into your next demo and make the vendor answer each one on the record.
Ask Who Responds to an Urgent Problem, and How Fast
Vendors answer this one with a feeling instead of a fact. "We have great support" and "we're very responsive" give you nothing you can hold them to. Get the mechanics instead.
Ask them: When I report an urgent issue during a funding run, what channel do I use, who gets it, and how fast will someone respond?
✓ Good answer
They name a specific channel you can reach during the workday, name the kind of person who responds, and give you a real response time.
△ Red flag
The only way to get help is a web form that drops your question into a shared queue. You've got a merchant ready to sign and something in the deal setup is wrong, and you're stuck waiting in the same line as every minor request. In funding, that wait costs you the deal.
Ask Whether Your Contact Is a Named Person or a Rotating Queue
"Dedicated customer success manager" is one of the most stretched phrases in software sales, so treat it as a claim to verify, not a benefit to accept. There's a real difference between a person who knows your account, your integrations, and your team, and a support desk where you re-explain your setup to whoever catches the ticket.
Ask them: Will I have a specific person assigned to my account? Can you tell me their name and how many other accounts they carry?
✓ Good answer
They give you a name without hesitating, and they can explain how that person stays on your account over time. The specifics show the relationship is real, not a title.
△ Red flag
The answer stays abstract. That's usually a shared queue with a nicer name, and the relationship you were promised disappears the first time you need it under pressure.
Ask What Escalation Looks Like When the First Contact Can't Fix It
Support is easy to fake during quiet business hours. The honest test is what happens when the timing is bad and the stakes are high at once, which in funding is most Friday afternoons. You want a problem to be able to climb past your first contact and reach someone who can actually change something in the system.
Ask them: If my assigned contact can't resolve something, who does it go to next? Does that path reach an engineer who can touch the product?
✓ Good answer
Support and engineering are connected. When you need something changed to fit how your shop runs, the people who answer your call can hand it straight to the people who build the platform, so it actually gets done.
△ Red flag
Support and engineering barely speak. Your request becomes a ticket that just sits there while your operation waits on an answer nobody owns.
Ask How the Team Is Built and How Close Support Sits to the Product
Headcount tells you less than you'd think. A large company can still route you to a call center where the person on the line has never funded a deal and can't change anything in the platform. What actually protects you is a support team that understands the lending business and sits close enough to engineering that a real problem reaches someone who can fix it.
A focused, diligent team that knows your account will out-support a big vendor where you're a case number every time.
Ask them: Who handles my support, how well do they know MCA, and how directly do they work with the people who build the platform?
✓ Good answer
A focused team where the people helping you understand funding and can escalate straight to engineering. You're a customer, not a position in a queue.
△ Red flag
A big support org where the first line can't change anything and the people who can are walled off behind tiers. Size without access doesn't help you when a deal is on the clock.
Ask What Actually Happens in the First 3-4 Weeks
Onboarding is support you experience before your first live deal, and it sets the tone for everything after. A vendor who hands you a login and a help-center link is telling you how the rest of the relationship will feel.
Ask them: Walk me through go-live week by week. Who owns it on your side, and what am I responsible for?
✓ Good answer
A clear timeline with named owners on their side, including setup, contract mapping, and introductions to your ACH and credit partners. It means they've done this enough times to have a repeatable process.
△ Red flag
Vague answers about "getting you set up." You carry the gaps into production and discover them one painful workflow at a time.
Ask About Their Honest Posture Toward Their Own Bugs
This one sounds least flattering to ask, so ask it plainly. No platform is bug-free, and any vendor who implies otherwise is either inexperienced or not being straight with you. What you want to hear is that they expect issues, welcome the report, and move fast to fix.
Ask them: When a customer reports a genuine defect, what's your turnaround? Can you give me a recent example of one you fixed?
✓ Good answer
They point to a real fix on a real timeline. A vendor comfortable saying "you'll find bugs, and here's what we do when you tell us" has a support culture that exists in practice, not just on the deck.
△ Red flag
They insist nothing ever goes wrong, or they can't name a single recent fix. They're selling you the reassurance and skipping the follow-through.
A Vendor's Answers Here Predict Your Next Three Years
Watch how a salesperson reacts when you start asking about failure. A weak support model gets defensive, because the questions expose what the pitch was built to hide. A strong one leans in, because every answer is a point in its favor.
Ask these before you sign. The wrong answer doesn't cost you anything during evaluation. It costs you months later, the first time you're under pressure and find out what "great support" actually meant.
How Onyx IQ Supports the Funders Who Sign
We wrote this guide because these are the questions we want funders to ask us. Here's how we hold up against each one.
A Named Person, Reachable the Way You Work
Every Onyx IQ customer is assigned dedicated customer success managers you can reach on Slack, phone, text, or email. You're not filing a ticket into a queue and waiting your turn behind cosmetic requests. You're messaging someone who already knows your account and your setup.
A Focused Team That Sits Close to Engineering
We're not the biggest vendor in the category, and that's the point. Our success managers know the funding business, and they sit close enough to our engineering team that a real problem reaches someone who can change the product instead of getting lost in a handoff.
You get people who know your name and your account, not a call center that routes you in circles.
Onboarding That Gets You Live in Weeks
Go-live runs roughly 2-4 weeks, and your success managers own it with you: system setup, contract mapping, and direct introductions to the ACH processors, credit providers, and verification partners you'll rely on. You start production with your ecosystem connected, instead of a login and a list of things to figure out yourself.
A Straight Answer About the Day Something Breaks
We tell prospects the truth: all software has bugs, and the measure of a platform is how fast the fix lands when you report one. That's the standard we hold ourselves to, and the standard we think you should hold every vendor to before you sign.