Knowing What Capital Costs Is Not the Same as Knowing Whether to Deploy It

The Deployment Return Threshold — The Governance Standard That Determines Whether Every Draw Your Business Makes Is Working or Consuming

SERIES CONTEXT

This article is the second in the True Cost of Money Series — a three-part series that establishes the governing framework for SMB capital deployment in the current rate and credit environment. It is published on the Capital Source thought-leadership platform and is written for financially literate SMB operators, CFOs, and business owners who are actively managing capital deployment decisions in an elevated rate environment. Article One established that rate is the wrong governance instrument and introduced Capital Velocity, the Capital Velocity Index, and Stall Cost as the correct measurement framework. This article develops the operational discipline that follows: the Deployment Return Threshold — the governance floor that determines whether any capital deployment is productive or destructive at the cycle level. Article Three will deliver the complete capital structure solution.

KEY POINTS

1. Article One established that rate is not cost — True Cost of Money is the aggregate of financial cost, opportunity cost, and operational impact measured at the cycle level. Article Two establishes the governance discipline that follows: every deployment decision must be measured against the Deployment Return Threshold — the minimum cash return per operating cycle a draw must generate to remain above the destructive boundary.
2. Most businesses know what their capital costs in approximate terms. Almost none have calculated whether specific deployments are generating enough cash return within the operating cycle to justify that cost. That gap — between knowing cost and governing deployment against it — is where capital base erosion happens silently.
3. The Deployment Return Threshold applies differently across instrument types. For variable rate facilities it is expressed as a minimum CFADS requirement per cycle. For fixed-cost instruments it is expressed as a minimum incremental revenue requirement per advance. The formula differs. The governing principle is identical: deployment that does not clear the threshold is destructive regardless of how competitive the rate appeared.
4. Federal Reserve analysis of small business credit conditions and academic research on working capital deployment efficiency consistently indicate that businesses that set explicit deployment return thresholds and govern draw decisions against them generate materially better capital productivity outcomes than those managing by rate or availability alone.
5. The businesses that navigate elevated rate environments successfully are not those that found the lowest cost of capital. They are those whose deployment governance ensured that every draw cleared the threshold that separates productive from destructive — draw by draw, cycle by cycle, instrument by instrument.

DEFINITIONS

Deployment Return Threshold (DRT) — the minimum cash return per operating cycle a capital deployment must generate to remain above the boundary between productive and destructive. Expressed as the sum of True Cost per Cycle plus NWC Floor Maintenance Requirement per cycle. A deployment generating cash return above the DRT is preserving or building the capital base. A deployment generating cash return below the DRT is consuming it — regardless of the rate at which the capital was borrowed.

Deployment Return Ratio (DRR) — the ratio of cash return generated by a specific deployment to the Deployment Return Threshold for that deployment. A DRR above 1.0 means the deployment is productive. A DRR below 1.0 means the deployment is destructive — consuming the capital base at the rate of the shortfall below 1.0 per cycle.

Incremental CFADS — the additional cash flow available for debt service generated specifically by a capital deployment, above the baseline CFADS the operating cycle was already producing before the deployment. The correct denominator for evaluating fixed-cost instrument deployments — not aggregate CFADS, but the specific cash the deployment produces above the existing baseline.

THE GAP BETWEEN KNOWING COST AND GOVERNING DEPLOYMENT

Article One established the measurement problem: most businesses are managing capital cost with the wrong instrument. APR is an annualized abstraction. True Cost per Cycle is the cycle-level reality. The gap between those two numbers is where rate exposure compounds invisibly.

Article Two addresses the discipline problem that follows. Knowing what capital costs at the cycle level is necessary. It is not sufficient. The sufficient condition is governing every deployment decision against a specific threshold — a minimum return requirement that every draw must clear to remain on the productive side of the boundary.

Most businesses do not have this threshold. They have rate awareness. They know their facility is at prime plus 2.5 percent. They know their factor rate is 1.33. What they do not know is whether the specific inventory purchase funded by the last draw, or the specific order fulfilled by the last advance, generated enough cash within the operating cycle to cover what that draw cost per cycle and maintain the NWC floor simultaneously. That is the question the Deployment Return Threshold answers.

Section One: The Deployment Return Threshold — What It Is and Why It Matters

The Deployment Return Threshold is the minimum cash return per operating cycle that a capital deployment must generate to remain above the destructive boundary. It is not a target. It is a floor. A deployment above the floor is productive. A deployment below the floor is consuming — extracting more from the capital base than the operating cycle is returning to it.

The DRT has two components that are non-negotiable simultaneously.

True Cost per Cycle is the carrying cost of the deployment — what the draw costs in dollars over the period it is outstanding. For variable rate instruments this is Draw Balance × (Annualized Rate ÷ 365) × CCC. For fixed-cost instruments this is the Per-Cycle ACH Extraction. Both figures must be calculated against the actual CCC of the business — not an assumed or generic figure.

NWC Floor Maintenance is the working capital the operating cycle must preserve above the minimum liquidity threshold through the full duration of the draw. A deployment that covers its True Cost per Cycle but compresses the NWC floor to do it is not productive. It is servicing debt from working capital — the structural failure condition the Inflation Series established as the most consequential and most invisible governance failure in SMB capital management.

Together these two components define the floor. A deployment that generates cash return above both simultaneously is productive. A deployment that fails either is destructive — even if the rate appeared competitive, even if the instrument was structured correctly, even if the income statement shows adequate EBITDA coverage.

This is where most businesses are operating with a measurement gap they do not know they have. They are comparing draws to their rate, not to their DRT. In a benign rate environment the gap between those two numbers is narrow enough that rate comparison produces acceptable outcomes. In an elevated rate environment the True Cost per Cycle has risen materially — and every deployment that was marginal at prior rates may now be below the DRT without any visible signal that the threshold has been crossed.

Section Two: Applying the DRT Across Instrument Types

The Deployment Return Threshold applies to every capital instrument in the stack. The formula differs by instrument type. The governing principle is identical.

Variable Rate Facilities

Representative SMB Manufacturer-Distributor

This draw must generate at least $90,356 in cash return within the 72-day cycle to remain above the threshold.

Same rate. Same CCC. Same NWC floor requirement. The DRR is determined entirely by what the deployment is funding and what that specific deployment generates in return.

This is the governance discipline most businesses are not applying. They are drawing against available borrowing base without calculating whether each specific deployment is above or below the DRT. In a low-rate environment that approach is survivable. At current rates, a deployment that was marginal at prior rates may now be below the DRT without any change in how the business is operating.

Fixed-Cost Instruments

Representative SMB Distributor

The advance must generate at least $219,600 in Incremental CFADS within the 72-day cycle to clear the DRT.

Not because the factor rate was too high. Because the deployment was not generating the incremental return that justifies the instrument’s cost structure. RBF is a bridge and stretch instrument priced against incremental opportunity. When deployed as foundation capital covering baseline working capital needs, the DRR on that deployment cannot clear the threshold regardless of how competitive the factor rate appears.

Section Three: The Full Stack DRT — Governing the Aggregate

Individual draw-level DRT assessment is necessary. It is not sufficient. A business that governs each instrument individually may still be running a destructive aggregate stack if the combined cost of carrying all outstanding obligations exceeds the combined Incremental CFADS the operating cycle generates.

The Full Stack DRT is the aggregate threshold: the sum of True Cost per Cycle across all variable rate draws plus Per-Cycle ACH Extraction across all fixed-cost instruments plus NWC Floor Maintenance. If aggregate CFADS per cycle falls below this aggregate threshold, the full capital stack is consuming the operating cycle regardless of how each individual instrument scores on its own.

Federal Reserve research on multi-instrument business credit structures and academic literature on working capital management in tightening rate environments consistently indicate that compartmentalized assessment — evaluating each instrument against its own cost rather than against the aggregate threshold — is the primary source of undetected capital base erosion in businesses operating with mixed capital stacks.

This is where many businesses discover they are in a more pressured position than the income statement suggests. A business showing adequate EBITDA coverage may simultaneously be running a Full Stack DRT deficit — because the instruments in the stack are collectively extracting more from the operating cycle than the cycle is generating in Incremental CFADS. That deficit does not appear as a loss. It appears as a slow compression of the NWC floor, a tightening of available borrowing base at the next review, a working capital position that is marginally tighter each cycle without a clear single cause.

The Full Stack DRT analysis makes the cause visible. And when it does, the governance response is instrument-specific: identify which draws are below their individual DRT, which instruments are deployed against the wrong function, and which components of the stack require recalibration. That sequence — not a rate negotiation, not a relationship conversation, but a deployment governance correction — is what restores the Full Stack DRT to productive territory.

FORENSIC STRESS TEST: WHAT IS YOUR DEPLOYMENT RETURN THRESHOLD?

Draw-Level DRT Assessment

1. Have you calculated the True Cost per Cycle on your current outstanding variable rate draws at current rates and your actual CCC?
2. Have you identified the specific revenue or margin generated by each draw within the operating cycle — not aggregate revenue but the return attributable to the specific deployment?
3. Is the Deployment Return Ratio on each draw above 1.0 — is the deployment generating more than the DRT requires?

Fixed-Cost Instrument DRT Assessment

1. Have you calculated the Per-Cycle ACH Extraction on any fixed-cost instruments against your actual CCC?
2. Have you identified the Incremental CFADS generated by the specific deployment funded by each advance — the cash above baseline, not aggregate CFADS?
3. Is the DRR on each fixed-cost advance above 1.0 when measured against Incremental CFADS rather than aggregate CFADS?

Full Stack DRT Assessment

1. Have you calculated the aggregate DRT — the sum of all per-cycle carrying costs plus NWC floor maintenance across the full capital stack?
2. Does your aggregate CFADS per cycle clear the aggregate DRT while keeping the NWC floor intact?
3. If the aggregate DRT is not being met, have you identified which specific draws or advances are below threshold and what the governance correction looks like for each?

Instrument Purpose DRT Assessment

1. Are any draws against variable rate facilities funding overhead or routine operating costs that do not generate specific cycle-level revenue attributable to that deployment?
2. Are any fixed-cost advances deployed against baseline working capital needs rather than against specific incremental revenue opportunities?
3. If any instrument is deployed against the wrong purpose, have you identified the governance correction — instrument purpose realignment, not rate negotiation?

FREQUENTLY ASKED QUESTIONS

What is the Deployment Return Threshold and how is it different from a standard debt service coverage ratio?

The Deployment Return Threshold is the minimum cash return per operating cycle a capital deployment must generate to remain above the destructive boundary — calculated as True Cost per Cycle plus NWC Floor Maintenance Requirement. It differs from a standard DSCR in three critical ways. First, it operates at the cycle level rather than the annual level. Second, it incorporates the NWC floor maintenance requirement as a non-negotiable component — a deployment that covers its carrying cost but compresses the NWC floor to do it is still below the DRT. Third, it is deployment-specific — it measures the return attributable to the specific use of the capital, not aggregate revenue or EBITDA. Federal Reserve analysis of small business credit conditions and academic research on working capital deployment efficiency consistently indicate that cycle-level, deployment-specific return measurement is materially more predictive of capital base health than annual coverage ratios.

Why does the DRT use Incremental CFADS rather than aggregate CFADS for fixed-cost instruments?

Because fixed-cost instruments are priced against the incremental opportunity they fund, not against the baseline operations of the business. A factor rate advance at 1.33 is structured to be productive when it funds a specific purchase order, contract, or inventory purchase that generates incremental gross margin above what the operating cycle was already generating. When measured against aggregate CFADS — which includes cash generation from all existing operations regardless of whether the advance contributed to it — the assessment systematically overstates the return on the deployment. A business with $400,000 in aggregate CFADS per cycle that takes a $300,000 advance for routine working capital may show an adequate ACH Serviceability Ratio against aggregate CFADS while the actual Incremental CFADS attributable to that specific deployment is near zero. The DRT analysis using Incremental CFADS reveals the deficit that aggregate CFADS analysis conceals.

How does the Full Stack DRT reveal risks that individual instrument assessment misses?

Individual instrument assessment compares each draw or advance to its own cost. That assessment is necessary but insufficient because all instruments compete for the same CFADS pool. A business with three instruments each individually above their own threshold may still be running a Full Stack DRT deficit if the aggregate cost of carrying all three exceeds the aggregate CFADS the operating cycle generates above the NWC floor. Federal Reserve research on multi-instrument business credit structures and academic literature on working capital management in tightening rate environments consistently identify compartmentalized assessment as the primary source of undetected capital base erosion. The business looks adequate instrument by instrument while the full stack is consuming the operating cycle in aggregate. The Full Stack DRT makes the aggregate picture visible by treating the entire stack as a single governance unit.

What is the correct governance response when a draw is below the DRT?

The response depends on which component of the DRT the deployment is failing. If True Cost per Cycle has risen above what the specific deployment generates — meaning the rate environment has outpaced the return profile of the deployment — the governance correction is either to recalibrate the draw size, improve the deployment’s return through better revenue targeting, or recalibrate the capital structure against the Rate-Adjusted Borrowing Base. If the deployment is below the DRT because it is funding the wrong purpose — routine working capital from an RBF instrument, overhead from a revolving draw that cannot attribute specific revenue — the governance correction is instrument purpose realignment, not rate negotiation. The instrument must be redeployed against a purpose whose return profile matches its cost structure, or replaced with an instrument whose cost structure matches the operating cycle function being funded.

How does the Deployment Return Threshold connect to the capital structure solution in Article Three?

Article Three develops the Velocity-Adjusted Capital Structure — the capital stack design principle that ensures every instrument in the stack is sized, sequenced, and structured against the Deployment Return Threshold rather than against nominal availability, rate comparisons, or income statement-based coverage ratios. The DRT analysis Article Two establishes is the diagnostic foundation: it identifies which draws are below threshold, which instruments are misaligned, and what the aggregate stack gap looks like. The Velocity-Adjusted Capital Structure is the solution architecture that closes those gaps — not by finding cheaper capital but by structuring the capital stack so that every instrument is deployed against the purpose whose return profile clears the DRT at current rates and current CCC.

CONCLUSION

Knowing what capital costs is not the same as knowing whether to deploy it. Article One established the measurement framework — True Cost per Cycle, Capital Velocity Index, Stall Cost — that replaces rate as the correct instrument for evaluating capital cost at the cycle level. Article Two establishes the governance threshold that turns that measurement into a deployment discipline: the Deployment Return Threshold, the minimum cash return per cycle every deployment must generate to remain on the productive side of the boundary between building and consuming the capital base.

Most businesses have rate awareness. Almost none have threshold governance. In a low-rate environment that gap is survivable. In an elevated rate environment where every draw costs materially more per cycle than it did at origination, a deployment that was marginally productive at prior rates may now be below the DRT — consuming the capital base cycle by cycle without a visible signal on the income statement.

The Deployment Return Threshold does not change what capital costs. It changes what you do about it — by establishing the specific return requirement every deployment must meet, the governance framework for evaluating whether each instrument is deployed against a purpose whose return profile clears that requirement, and the diagnostic discipline that reveals when the full stack in aggregate is consuming rather than preserving the capital base.

That discipline is the foundation of the capital structure solution Article Three delivers.

If your business is making draw decisions based on availability and rate without calculating whether each specific deployment is generating enough cash return within the operating cycle to clear the Deployment Return Threshold — that gap is compounding against your capital base every cycle you leave it unmeasured.

Capital Source works with business owners and CFOs to establish the DRT for every instrument in the stack — calculating True Cost per Cycle on variable rate draws, Per-Cycle ACH Extraction on fixed-cost instruments, Incremental CFADS on specific deployments, and the Full Stack DRT against aggregate CFADS and NWC floor requirements. That analysis tells you not just what your capital costs but whether each deployment is working or consuming at the cycle level.

Article One: The True Cost of Money Is Not the Rate — And It Is Not the Factor

SMB Credit Tightening Series   Credit Tightening Series Hub Article

SMB Inflation Series   Inflation Series Hub Article

STRATEGIC DISCLOSURE

Capital Source is a commercial capital advisory firm. This article is produced for informational purposes and represents the firm’s analytical perspective on current macroeconomic and credit market conditions. It does not constitute financial, legal, or investment advice. Businesses evaluating capital structure decisions should engage qualified advisors with direct knowledge of their specific operating circumstances.