Keeping the cap table intact is worth a future-revenue promise only when the promise has a hard ceiling, protects the core product, and leaves enough cash to survive if next year’s revenue arrives late. A founder should compare the full cost of that promise with dilution, rather than treating equity as the only expensive money.
At 6:18 p.m. on a Friday, Kwaku, an illustrative Accra SaaS founder, was still in his small office near Osu, holding his phone above a cooling bowl of waakye. The term sheet in his inbox offered cash without new shares. In return, the investor would receive an agreed share of next year’s revenue until a fixed return was paid.
He had until Monday morning.
His product handled recurring invoices for small distributors. Three customers were paying. Two pilots were close, though close had become a dangerous word. His engineer wanted to know whether the company could afford another month of work. Kwaku’s alternative was a priced equity round that would reduce his ownership before he had proved the product could sell consistently.
The revenue-share offer seemed cleaner. By Sunday night, it looked capable of taking the money he expected to use for payroll, support, and the product changes customers were asking for. If sales slipped, the company could end up underfunded at the exact moment it needed room to recover.
A clean cap table can hide an expensive obligation
Equity gives an investor a claim on the company’s future value. A revenue commitment takes money from the company while it is trying to create that future value. Neither is automatically better.
The useful question is: what must be true for this agreement to feel manageable six months from now?
For Kwaku, the answer was uncomfortable. Revenue would need to arrive from customers who had not signed yet. Renewals would need to hold. Payment delays would need to stay short. The business would need enough margin after delivery costs to pay the investor and still pay the people building the product.
That is a chain of assumptions, not a funding plan.
A capped revenue share can be reasonable when a founder already has predictable collections and clear margins. It becomes fragile when the money depends on a sales forecast, a new market, or a product change that has not reached customers. The clause may preserve ownership on paper while quietly narrowing every decision that follows.
The investor had not asked Kwaku to give up a board seat. They had asked him to make a claim on uncertain revenue feel certain.
Put the obligation into the bad month
Founders often model the good month because the good month makes the spreadsheet work. The decision should be tested against the month when one major customer pays late, a pilot pauses, and the team still needs salaries.
Kwaku opened a blank sheet on Sunday. He listed only cash he could point to: current contracts, cash in the bank, and committed expenses. He then added the proposed revenue share before adding any hoped-for expansion.
The result changed the conversation. The offer did not merely fund growth. It made a weaker sales month more consequential.
This is where a revenue-based deal needs plain terms that can survive pressure:
- Set a maximum total repayment, so a temporary financing decision cannot become an open-ended claim on sales.
- Define which revenue counts, especially if the company sells implementation work alongside software.
- Check whether payments pause below a cash threshold or during a genuine collection problem.
- Ask what happens if the business changes pricing, sells through a partner, or needs to raise equity later.
- Get clear on whether the investor has approval rights that could slow ordinary operating decisions.
These details can sound legalistic on a Friday evening. They are product decisions by Monday. A founder who must route every pricing change through a financing agreement has lost part of the roadmap, even with every share intact.
The same discipline applies when choosing customer revenue over venture capital. When Should an African AI Startup Choose Venture Funding Over Customer Revenue? starts from the same constraint: the source of money shapes what the company can build next.
Revenue promised away must not starve the roadmap
Kwaku’s most important number was not the valuation implied by the equity term sheet. It was the minimum monthly cash required to keep the product reliable for paying customers.
His customers were asking for improvements that would reduce manual follow-up. Those changes would not create a dramatic demo. They would make the software harder to replace. If the revenue share absorbed the cash for that work, he might keep a larger percentage of a smaller, more fragile company.
That is the trade founders miss when they frame the choice as control versus dilution. Control comes from room to make decisions. A company that cannot hire, support customers, or fix its product because next month’s receipts are already allocated has limited control, regardless of the cap table.
The overseas contract, the customer-funded build, and the financing offer can all create this pressure. Ama's customer contract. Six weeks to prove paid use without losing the roadmap. explores what happens when short-term cash begins to set the product agenda.
Monday should produce a counteroffer, not a reflex
On Monday morning, Kwaku did not accept or reject the term sheet as written. He returned with a narrower proposal: a lower revenue share, a fixed repayment cap, a payment floor tied to operating cash, and no claim on implementation revenue.
The investor might walk away. That possibility remained real. Without an agreement, Kwaku could face a smaller equity round, slower hiring, or a harder conversation with his engineer.
But he had turned an anxious choice into a specific one. He knew what he was willing to promise, what the company needed to protect, and which assumption would break the deal. The term sheet no longer sat in his inbox as an offer to preserve ownership. It sat on the table as a claim on the next year of work.
Comments
No comments yet.