Let's be honest. Your revenue-based financing deal is probably garbage.
I'm not trying to be a jerk. I'm trying to save your company. I've been the founder staring at a term sheet, so desperate for the cash that I'd consider signing almost anything. And now, as an investor in over 200 companies, I'm the one who sees the wreckage those deals can cause down the line. Too often, the culprit is a bad revenue-based financing (RBF) deal, signed out of haste or bad advice.
Just last month, I met with a SaaS founder. Great product, real traction, everything you want to see. But they were completely stuck. A few months prior, they'd taken an RBF deal that felt like a lifeline. It wasn't. They'd given up 15% of their MRR for a check that barely covered two months of salaries. By the time they came to me for their seed round, their cash flow was so choked we couldn't make the numbers work. It was a slow, painful death for a company that should have been a home run. It all started with that one bad deal.
The 2024 RBF Playbook is a Trap
I keep seeing the same tired advice on Twitter and in founder forums: "RBF is non-dilutive! It's founder-friendly!" That’s the 2024 playbook, and in 2026, it’s a death trap. The market isn't what it was. The cost of capital has shot up. And the way investors like me scrutinize your every move has intensified. Following that old advice is like trying to navigate the San Francisco Bay with a map of the London Underground.
The pitfalls are predictable, yet founders keep falling into them. I see deals with uncapped repayments, meaning you could pay back 5x, 10x, or even more of what you borrowed. It's insane. I see founders agreeing to give up a slice of their entire revenue, choking their own growth before it even starts. And the covenants... don't get me started. They're often so convoluted you'd need a team of lawyers to translate them. You might as well hand the lender a board seat and the keys to your apartment. When I see founders signing these deals, I just want to shake them. This isn't founder-friendly; it's founder-fatal.
My Story: The RBF Mistake That Nearly Killed My First Company
This isn't just a lecture. I’ve lived this nightmare. Early in my career, years before RemoteTeam or MovieLaLa, I was just another founder staring at the ceiling at 3 AM, wondering how I was going to make payroll. We had a product people loved, we had users, but we were burning cash like it was going out of style. A real venture round was on the horizon, but the horizon felt a million miles away.
Then an RBF lender appeared. They offered us what felt like a miracle: $100,000. To a desperate 20-something, that might as well have been a billion dollars. The price? Just 10% of our monthly revenue until they were paid back. It seemed so clean, so simple. We signed.
It wasn't simple. That 10% started as a papercut. Then, as we grew, it became a gaping wound. Every dollar we made, a dime went straight out the door. Money that should have gone into hiring engineers or buying ads was just... gone. When we finally got in front of VCs, they took one look at our financials and their smiles vanished. The RBF deal was a cancer on our cap table. It told them we were bad at managing money and willing to take desperate measures. We eventually got a deal done, but the valuation was brutal. That one signature cost us millions in dilution and years of my life in stress. It’s a lesson that’s been burned into my brain ever since.
The Investor View: Why I Pass on 9 out of 10 RBF-Funded Companies
Now I’m on the other side of the table, and I see a dozen pitches a week. When a deck comes across my desk and I see a messy RBF deal, it’s almost always an instant pass. I don’t see a savvy founder who found a clever way to get non-dilutive capital. I see a founder who was cornered and made a bad decision. I see a company that’s already carrying a heavy burden before it even starts the race.
VCs want clean cap tables. It’s not about being picky; it’s about managing risk. We need to know that our money is going to fuel growth, not to pay off some lender from a deal you signed a year ago. A bad RBF deal is a giant red flag. It complicates due diligence, creates legal headaches, and makes it impossible to accurately model the company’s future. Compared to a clean convertible note or a SAFE, a poorly structured RBF deal is a tangled mess. It tells me you’re playing checkers, and I’m looking for founders who play chess.
The Solution: The 2026 RBF Model
So am I saying all RBF is toxic? No. I’m saying the way it’s being done is toxic. It’s time for a new playbook. I call it the 2026 RBF Model, and it’s built on three non-negotiable principles.
Principle 1: The Ironclad Cap. This is my hill to die on. Never, ever, ever sign an RBF deal without a fixed repayment cap. A sane cap is between 1.5x and 2x the principal. You borrow $100,000, the absolute most you will ever pay back is $200,000. Period. It’s a simple backstop that aligns everyone. If a lender won’t agree to a cap, you get up and walk out of the room. It means they’re not looking for a partner; they’re looking for a sucker.
Principle 2: Growth-Tied Payments. Stop giving away a percentage of your total revenue. That’s just lazy. Instead, tie the repayments to your growth. Pay a percentage of your new monthly recurring revenue, or a slice of your gross margin. This turns the lender into a co-pilot, not a hijacker. They only make money when you’re actually growing. Their success is tied directly to yours.
Principle 3: Radical Simplicity. A good RBF deal should be boring. It should be as simple as a car loan. No weird covenants about your personal finances. No board seats. No warrants. If the term sheet is more than three pages long and you need a Ph.D. in finance to understand it, it’s a trap. The best deals are clean, straightforward, and let you get back to what you do best: building your company.
Case Study: How ‘Acme SaaS’ Nailed Their Pre-Seed with Smart RBF
This isn’t just theory. I advised a company—we’ll call them ‘Acme SaaS’—that did this perfectly. They had a killer product but a tiny team. They needed about $250,000 to hire two senior engineers and pour some gas on their marketing. VCs were sniffing around, but it was too early for a proper seed round.
Instead of taking the first predatory deal they were offered, they held out. They found a lender who understood the 2026 model. They got their $250,000 with a 1.8x repayment cap. The repayments were tied to 5% of new MRR, not the total. The agreement was a simple, two-page document.
The result? They got the cash, built their team, and hit their milestones without feeling like they were drowning. Six months later, their MRR had tripled. They had a line of Tier 1 VCs out the door, and they closed a clean Series A at a valuation that made their early investors very happy. They used RBF as a strategic bridge, not a desperate leap.
Conclusion: Stop Acting Desperate
Look, RBF can be a powerful tool. But the way most founders use it is a flashing neon sign of desperation. You get so fixated on the short-term cash that you sign away your company’s future.
Stop it.
Demand better terms. Do your homework. And if a deal feels even slightly off, have the courage to walk away. Your company is worth more than a quick check from a lender who doesn’t have your best interests at heart. The 2024 playbook is over. It’s time to start playing by the 2026 rules.
Frequently Asked Questions
What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 200+ startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
Do all experts agree with this view?
No, and that's fine. The best ideas in business are often contrarian. I share my perspective based on my experience and data, but I encourage you to seek out opposing viewpoints and form your own conclusions.
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.