Non-Dilutive R&D Tax Bridge Capital: Preserve Your Cap Table Under Section 174

The Dilution Math of Raising Equity for a Tax Bill

The dilution cost of raising equity for a Section 174 tax bill can be calculated precisely — and it is almost always more expensive than the tax bill itself over any horizon beyond 18 months.

Consider a SaaS company valued at $5M raising $150K to cover a Section 174 obligation. At that valuation, $150K represents 3% of the company. At a $20M exit — which is modest for a SaaS company that reached $5M valuation — that 3% is worth $600K. The $150K tax bill was funded by giving away $600K of future exit proceeds.

At higher exit valuations, the math worsens. At a $50M exit, the same 3% dilution is worth $1.5M. The true cost of the equity-funded tax bridge, measured at exit, is 10×–15× the face value of the tax liability. No RBF factor rate approaches this cost.

Founders who understand this calculation do not raise equity for tax liabilities. They use the cheapest non-dilutive instrument available — which is RBF for SaaS companies — and preserve their cap table for strategic purposes.

How Non-Dilutive RBF Bridges the Section 174 Gap

A non-dilutive RBF bridge for Section 174 operates identically to any RBF advance: capital is advanced against MRR, repaid as a percentage of future revenue, and retired over 10–18 months. The difference is the use case — the advance is deployed directly to the IRS rather than to growth initiatives.

The advance amount is sized to match the Section 174 liability. The lender receives a use-of-funds statement from the CPA or tax attorney confirming the liability amount. This documentation verifies that the advance is resolving a specific, documentable obligation — which reduces underwriting risk and often improves factor rate terms.

The factor rate on a Section 174 bridge for a qualified SaaS company ranges from 1.12× to 1.25×. On a $150K advance, the total repayment is $168K–$187.5K. The IRS penalty for underpayment — approximately 8% per year plus potential late fees — combined with the cash flow disruption of a depleted reserve, makes the RBF option less expensive than non-payment in almost every scenario.

The non-dilutive structure means the company's ownership is preserved exactly as it was before the tax liability arose. No new stakeholders. No equity negotiation. No cap table changes that require board approval or investor consent.

Cap Table Implications: RBF vs Equity Round

The cap table implications of an equity round versus an RBF bridge are not symmetric. An equity round creates a permanent structural change to company ownership. An RBF advance creates a temporary liability that disappears completely upon repayment.

From an investor relations perspective, these outcomes are categorically different. A VC investor conducting due diligence for a Series A will see a clean cap table if the Section 174 bridge was funded with RBF. If the bridge was funded with equity, the VC will see an unexplained dilution event — and will ask about the circumstances, the valuation used, the anti-dilution rights granted, and whether the new investor has any special rights that could affect the Series A terms.

Employee option pool management is also affected. An equity round for a tax liability dilutes the option pool, reducing the effective value of every outstanding option. For a company trying to attract and retain engineers — who hold significant equity — a preventable dilution event affects recruiting and retention directly.

The RBF bridge has no option pool impact. It does not trigger anti-dilution provisions. It does not create a new investor with information rights or pro-rata participation rights. It is the structurally correct answer to a problem that the equity round turns into a structural liability.

Structuring the Bridge for Maximum Cap Table Protection

Cap table-optimal structuring of an RBF bridge for Section 174 focuses on two variables: advance size and repayment speed. Smaller advances with faster repayment minimize the window during which the liability exists on the balance sheet.

The advance should be sized to exactly cover the Section 174 liability — not padded for general operating expenses. Lenders will approve larger advances, but additional debt beyond what is needed for the tax liability adds balance sheet risk without corresponding cap table benefit. Discipline in sizing is a governance best practice.

Accelerated repayment is available with most RBF lenders without prepayment penalty. Operators who experience an MRR growth event during the repayment window can accelerate payoff — reducing the remaining balance, the total interest-equivalent cost, and the time the liability appears on the balance sheet before an investor review event.

Timing the bridge relative to funding rounds is also relevant. Closing an RBF advance 12–18 months before a planned Series A — and fully repaying before the data room opens — ensures the liability never appears in investor diligence. This is the cleanest possible outcome for cap table integrity.

Frequently Asked Questions