Every funder can feel whether the shop is fast, but almost none can prove where the speed goes. The best analytics measure two things and measure them relentlessly: deal velocity, how much funded dollar volume the pipeline produces per day, built from deal count, conversion rate, average advance, and cycle length; and conversion, the survival rate at every stage from inquiry to funded, led by the submission-to-funding ratio. An MCA CRM that timestamps every stage change computes both continuously, which turns “we feel slow this week” into “documents are taking three days longer than they used to, on paid-source leads only.”
Speed is not vanity in this industry; it is the product. Merchants apply to several funders at once, and the shop that qualifies, documents, and funds first wins the margin. This guide covers the velocity formula applied to cash advance, the conversion funnel in numbers, how to slice both by source and team, and how to turn the measurements into a weekly management ritual.
The short answer is timestamps turned into math. Concretely, the platform should deliver:
• Stage timestamps on every deal, so time-in-stage is a fact rather than an opinion
• Average days in each stage, with an exceptions list for deals stuck past threshold
• Conversion rate at every stage transition, not just end to end
• A velocity metric expressed in funded dollars per day
• Full cycle length from inquiry to funding, tracked as a trend
• Speed to first touch and contact rate on fresh inquiries
• The submission-to-funding ratio as the headline conversion number
• All of the above sliced by lead source, rep, ISO partner, industry, and product
The last bullet matters more than it looks. Averages hide everything; segments reveal everything. Velocity that looks healthy overall can be carried entirely by referrals while paid sources bleed quietly.
The standard sales formula translates cleanly to funding: velocity equals the number of qualified deals in the pipeline, times the conversion rate, times the average advance, divided by the cycle length in days. The output reads as expected funded dollars per day, which is the most honest single description of a funding operation’s engine.
A worked example makes it concrete. Forty qualified deals in the pipeline, a twenty-five percent conversion to funded, an average advance of sixty thousand dollars, and a twenty day cycle: forty times point two five times sixty thousand is six hundred thousand dollars, divided by twenty days, thirty thousand dollars of funded velocity per day. Every planning conversation in the shop becomes arithmetic on those four variables.
The formula’s real gift is diagnosis. Raise the count with better lead flow, raise the advance size with bigger deals, lift conversion by fixing a weak stage, or shorten the cycle by attacking a queue, and velocity rises. The four levers are the entire improvement agenda, and the analytics exist to tell you which lever is currently the cheapest to pull.
Stage timestamps reveal the pipeline’s friction map. Average days in Contacted, Documents, Underwriting, and Offer show where the hours accumulate, and in most shops two stages dominate: document collection and underwriting queues. The exceptions list, deals sitting past a chosen threshold, is the operational output that turns this analytics into daily work.
Before the funnel even starts, the first clock decides much of it. Time from inquiry to first contact, and the contact rate that follows, determine how much of the pipeline you get to convert at all, because contact rates fall sharply in the first hours after an inquiry lands. Measured by source, this metric routinely exposes that some sources are being answered in minutes while others wait half a day.
Conversion analytics are the survival curve of the pipeline. A purpose-built MCA CRM computes the rate at every transition, inquiry to contacted, contacted to qualified, qualified to submitted, submitted to offer, and offer to funded, so the weak link is visible instead of guessed. The submission-to-funding ratio, the share of submitted deals that actually fund, is the headline number because it captures underwriting, pricing, and offer acceptance in one figure.
| Funnel Transition | What It Measures | Healthy Signal | Diagnostic Question |
|---|---|---|---|
| Inquiry to contacted | Speed and coverage | Same-day contact | Which sources are slow to answer? |
| Contacted to qualified | Lead quality and script | Consistent across reps | Is the data bad or the call weak? |
| Qualified to submitted | Process discipline | Days, not weeks | What sits between them? |
| Submitted to offer | Underwriting speed | Decision in days | Where is the queue backing up? |
| Offer to funded | Acceptance and closing | High acceptance | Are terms competitive? |
| Overall pull-through | The whole engine | Trending up | Which stage moved this period? |
Loss data belongs beside the win data. Every dead deal should carry a disposition, declined, unresponsive, funded elsewhere, too new, bad data, because the reason a deal died is the raw material for fixing the stage that killed it. A shop that dispositions its losses learns; a shop that deletes them repeats.
Sales pipeline analytics only earn their keep when they segment. The same funnel, cut by lead source, typically shows referrals converting at multiples of cold paid sources; cut by rep, it separates coaching problems from process problems; cut by ISO partner, it shows which relationships deliver fundable files versus submissions that die in underwriting. Industry and product cuts add concentration and pricing views.
The comparison is the diagnosis. If one rep’s deals stall in Documents while everyone else moves through, that is a coaching conversation. If every rep’s deals stall in Documents this week, that is a process or staffing problem. Same metric, different slice, completely different meeting.
Velocity trends complete the picture. A single week’s number is weather; the rolling trend is climate, and the trend is what tells you whether last quarter’s fix actually held. Comparing current cohorts of deals against their predecessors at the same stage of life is the cleanest way to know if the engine is genuinely improving.
Measurement becomes management through ritual. A weekly velocity review, built from the same dashboards every time, looks at the four levers, names the weakest stage, and assigns one fix with an owner. Then it checks last week’s fix against the data, which is the step most shops skip and the step that makes the ritual compound.
| Symptom | Likely Cause | First Fix |
|---|---|---|
| Slow first touch on fresh inquiries | Coverage gaps, no auto-acknowledgment | Automated cadences on intake |
| Long underwriting queues | Staffing or submission spikes | Prioritize by age, measure decision time |
| Low offer acceptance | Pricing or presentation | Compare terms against funded peers |
| Deals stuck in Documents | Manual chasing | Checklists with automatic reminders |
| Weak pull-through from one partner | File quality | Feedback loop or tier the relationship |
Benchmarks deserve one honest sentence: the most useful benchmark is your own history. Generic industry numbers vary too much by product mix and deal size to steer by, while your own trailing trend tells you exactly what changed and when. Set your baseline, set a target per lever, and let the segments argue about the causes.
The prerequisite is discipline in the data. Stages must change when the work changes, not when someone remembers, which means the workflow has to make stage updates the path of least resistance. Dispositions must be mandatory on dead deals, and timestamps must be enforced by the platform rather than trusted to memory. Analytics on tidy data steer; analytics on lazy data mislead.
If standing up the full measurement stack sounds like more than you want to configure alone, Contact us and we will build the velocity and conversion analytics around your pipeline stages, sources, and partners, with the weekly review views ready from day one. The goal is a single screen that answers how fast and how well, in numbers everyone trusts.
Platforms such as ConvergeHub track stage timestamps and conversion natively, so velocity, time-in-stage, and pull-through come from the pipeline the team already works in rather than from a side export. The measurement arrives with the workflow instead of after it.
It is funded dollar volume produced per day, calculated as qualified deals times conversion rate times average advance, divided by cycle length. It compresses pipeline size, quality, deal size, and speed into one honest number. Rising velocity means the engine is improving; falling velocity means one of the four levers moved.
It is the share of submitted deals that actually fund, also called pull-through. It captures underwriting decisions, pricing, and offer acceptance in a single figure, which makes it the headline conversion metric. Tracked by source and partner, it also grades the quality of what you are being sent.
Start with stage timestamps and compute two families: time metrics, days in stage and full cycle length, and conversion metrics, the rate at each stage transition. Combine them into velocity, then slice every number by source, rep, and partner. The platform should do the math; the team should do the interpretation.
There is no universal number, because product mix and deal size move the answer. Well-run shops fund clean files in days, but the benchmark that steers is your own trailing cycle length by stage. Watch the trend, not a stranger’s average.
Yes. Stage timestamps, time-in-stage, conversion by transition, and pull-through come from the pipeline data natively, with views configurable by role and segment. The numbers describe the pipeline your team actually works.
An MCA CRM earns its analytics by turning timestamps into two truths: how fast the engine runs, velocity in funded dollars per day, and where it leaks, conversion at each stage transition led by the submission-to-funding ratio. Slice both by source, rep, and partner, review them weekly, and assign one fix with an owner until the trend moves. Speed is the product in this industry, and speed that is measured gets managed.
To see your pipeline measured this way, schedule an appointment with ConvergeHub. We will configure the velocity and conversion views against your stages and sources, set the baselines, and build the weekly review screen your meetings can run on. The speed is already in your deals; it is time you could see it.
