Product Mechanics

How revenue-based
financing really works.

Goliath Underwriting Desk · March 18, 2026

Revenue-based financing sits in the space between a merchant cash advance and a traditional term loan. It borrows mechanics from both, fits a specific kind of business almost perfectly, and is structurally wrong for several others. Here is how the product actually works, who it fits, and where it falls short.

Revenue-based financing — RBF — emerged in the early 2010s as a financing structure for SaaS and ecommerce companies whose revenue was real and predictable but whose balance sheets didn't fit traditional bank underwriting. The product has since matured into a serious capital category, with structures suited to companies between roughly $1 million and $50 million in annual revenue. The mechanics are different enough from both MCAs and term loans that the comparisons tend to mislead more than help.

The structure, plainly

A revenue-based financing deal is a single lump-sum advance, repaid as a fixed percentage of the merchant's monthly revenue until a defined repayment cap is reached. The lump sum is the advance amount. The percentage is the revenue share. The cap is the total dollar amount the merchant will ultimately repay, expressed as a multiple of the advance.

A concrete example: a SaaS company with $300,000 in monthly recurring revenue takes a $500,000 RBF advance at a 1.30 cap with a 7% revenue share. Total repayment is $650,000. Each month, the funder collects 7% of the company's revenue. At a steady $300K MRR, that's $21,000 per month, retiring the cap in about 31 months. If MRR grows to $400,000 by month 6, the monthly remittance rises to $28,000 and the cap retires faster — perhaps by month 22. If MRR contracts, the monthly drops and the cap retires more slowly. The cap dollar amount does not change.

Why the cap is the key number

The most important thing to understand about RBF is that the total cost is fixed at origination. There's no compounding interest, no penalty for slow retirement (within reason), and no acceleration unless the merchant defaults on the underlying obligations. The variable is the time-to-retire, which depends on actual revenue performance.

Caps for established businesses (24+ months of operating history, verifiable monthly revenue over $200K) typically land between 1.20x and 1.35x. Earlier-stage or higher-risk profiles see caps from 1.35x to 1.50x. Anything over 1.50x is rare on a true RBF structure and usually indicates the deal is closer to an MCA in spirit even if the contract calls it RBF.

The effective annual cost depends on the time-to-retire. A 1.30 cap retired over 12 months is roughly equivalent to a 30% annual interest rate; the same cap retired over 24 months drops to roughly 15% on an annualized basis. RBF is structurally cheaper for businesses with stable or moderately-growing revenue than for businesses experiencing rapid contraction.

Monthly settlement vs daily debit

The cadence difference between RBF and an MCA is the most operationally meaningful distinction. An MCA pulls every business day — roughly 21 debits per month — which creates constant cash flow pressure but limits any single bad payment event to one day's revenue. An RBF deal settles monthly, usually on a fixed day (often the 5th, 10th, or 15th business day of the month), with a single large ACH covering the prior month's revenue share.

That single-day monthly hit is structurally larger than any daily debit but predictable and reconciled against actual revenue. The merchant connects an accounting platform — QuickBooks, Xero, NetSuite, or a revenue platform like Stripe, Shopify, or Recurly — and the funder pulls the prior month's revenue figure directly from the source. The percentage is applied to that verified number and the ACH executes.

For SaaS and ecommerce businesses, this is materially easier on operations than a daily MCA. The CFO sees one large monthly settlement instead of 21 daily pulls. Forecasting becomes cleaner. The business runs without the constant cash flow tension that defines life on a daily MCA. The trade-off is the larger single hit each month and the requirement to maintain enough operating cash to cover the settlement date comfortably.

What RBF underwriters look at

The underwriting model for RBF is different from MCA underwriting and different from a bank's. Bank statements still matter, but they're secondary. The primary inputs are revenue stability, revenue growth trajectory, gross margin, and customer retention metrics.

For a SaaS business, RBF underwriters specifically look at: monthly recurring revenue trend over the trailing 12 to 24 months, net revenue retention (a measure of how much of last year's revenue is still being generated by the same customers this year), gross margin (RBF underwriters generally want 50%+ gross margin), customer acquisition cost relative to lifetime value, and the concentration of revenue across the customer base (no single customer should represent more than 20% to 30% of revenue).

For an ecommerce business, the metrics shift to: monthly revenue trajectory, repeat customer rate, average order value, contribution margin after ad spend and fulfillment, and inventory turnover. A clean ecommerce file with 18 months of Shopify data and consistent contribution margin can close in 48 hours.

The accounting platform connection is non-negotiable for most RBF lenders. Read-only API access lets the funder verify revenue at the source, which is what enables the underwriter to size offers larger than an MCA could against the same business. The trade-off is that businesses with informal accounting or revenue flowing through multiple disconnected accounts have a longer underwriting path regardless of the underlying strength.

Who RBF fits

RBF is best-suited for businesses with the following structural features: recurring or near-recurring revenue, verifiable through an accounting or revenue platform; gross margins above 50%; 12 or more months of operating history; revenue concentration that doesn't depend on a single customer; and growth plans that benefit from non-dilutive capital rather than equity.

The cleanest fits are SaaS companies with predictable MRR, ecommerce businesses with proven repeat-customer dynamics, subscription product or service businesses (subscription boxes, software, content), and certain professional services firms (agencies, consulting practices) with retainer-based revenue. These businesses share the trait that next month's revenue is highly predictable based on this month's customer base.

Who RBF doesn't fit

RBF is structurally wrong for several categories. Cash-heavy retail — restaurants, convenience stores, certain auto service shops — doesn't fit because revenue isn't cleanly verifiable through an accounting or processor platform without significant manual reconciliation, and the monthly lump remittance creates cash flow stress that daily MCA debits would actually mitigate.

Project-based businesses with lumpy revenue (contractors, custom manufacturing, construction services) struggle with RBF because the monthly revenue share can be punishing in a month with two large invoice deposits and trivial in months with no completed projects. The cadence doesn't match the business model.

Pre-revenue or early-revenue businesses can't qualify because RBF underwrites against trailing revenue. A 3-month-old SaaS company with $30K MRR may have a beautiful trajectory but doesn't have the data to spread a 12-month underwriting. For these businesses, a smaller MCA or a startup-specific facility is the realistic option until enough data accumulates.

RBF vs MCA vs term loan

The honest side-by-side: an MCA funds in 24 to 48 hours, pulls daily, sizes against trailing 90-day deposits, and carries factors typically 1.20x to 1.50x. A term loan funds in 2 to 6 weeks, has a fixed monthly payment regardless of revenue, sizes against credit and historical financials, and prices typically 7% to 30% APR. RBF funds in 2 to 7 business days, settles monthly against actual revenue, sizes against trailing 12-month revenue, and prices via a cap (1.20x to 1.50x) with revenue-flex timing.

The right choice depends on what the operator needs. An urgent cash need with no time for accounting integration: MCA. A long-term, low-cost facility with balance sheet strength to back it: term loan or SBA. A growing business with clean revenue data, no time to wait six weeks, and a strong desire to avoid the daily debit grind: RBF. The product fits a real space, and operators who match their funding to their actual business shape will compound the right capital structure over years.

RBF FAQ

Questions worth answering.

Take the field

Your next chapter is one
application away.

Five minutes. No credit pull. No obligation. See what you qualify for and decide on your own terms.