Latest / Cash Flow Conversations with Fexingo: Working Capital, Receivables, and Small Business Finance / How a Cash Flow Waterfall Reveals Hidden Working Capital
Transcript
- Lucas: Luna, I was talking to a friend who runs a boutique furniture maker in Portland — custom hardwood tables, chairs, the kind of stuff that sells for two to three thousand dollars a piece. He told me his cash flow looks fine on paper — he's profitable — but every spring he nearly misses payroll. Luna: Spring — that's when his retail clients are ordering for summer patio season, right? So revenue should be climbing, not cratering. Lucas: Exactly. Revenue climbs. But his problem is timing — the cash from those spring orders doesn't land until his customers pay, which is typically net 30 or net 60. Meanwhile, he's already bought the walnut and maple, paid his two shop employees, and covered the rent. The profit is real. The cash just arrives in the wrong order. Luna: So what's the fix? He can't make customers pay faster — he tried offering a 2 percent discount for early payment, but most of his clients are interior designers who just process invoices when they get to them. Lucas: Right, and that's where a cash flow waterfall comes in. It's a model — a simple one — that maps the sequence of cash movements through your business, layer by layer, based on priority. Most small business owners look at a cash flow statement, which tells you the net result after everything happens. The waterfall shows you the order of operations. Luna: So instead of just knowing you ended the month with twenty thousand dollars in the bank, you see that the rent came out first, then payroll, then the supplier payment, and whatever's left is what you actually have to work with. Lucas: Exactly. And the key insight is that the water — the cash — flows from the top of the waterfall down. If there's not enough at the top to cover the first layer, everything below it gets starved. So you need to structure your waterfall so the most critical obligations sit at the top. Luna: And for most small businesses, the top layer is operating expenses — payroll, rent, utilities, core supplies. Stuff you can't skip. Lucas: Right. Then the second layer is financial obligations — debt service, loan payments, credit line interest. And the third layer is discretionary — owner distributions, growth investments, savings. If you map out your typical month this way, you can see exactly where the cash gets thin. Luna: Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that kind of support is what lets us keep making episodes like this, ad-free, focused on practical tools. Lucas: Yeah, and we really appreciate it. It means we can spend time on specifics like this waterfall model rather than rushing through surface-level advice. So back to my furniture maker friend — when we mapped his waterfall, the problem became obvious. Luna: What did it show? Lucas: His operating expenses — payroll, rent, materials — come due on the 1st and 15th of the month. His receivables, on the other hand, cluster around the 25th. So for the first two weeks of every month, his cash balance is dropping, and he's borrowing against his credit line just to cover the basics. Then around the 25th, a bunch of checks hit, and his balance spikes. He's paying interest on that credit line for fourteen days a month — about three to four thousand dollars a year — just because of timing. Luna: So the waterfall reveals a structural mismatch. The fix isn't to get customers to pay faster — it's to align the timing of his outflows with his inflows, or to build a buffer that covers that gap. Lucas: Right. In his case, we looked at shifting some discretionary spending — like a quarterly materials order — to align with his receivables spike. He also negotiated with one key supplier to move from net 15 to net 30 terms, which pushed that outflow from the beginning of the month to the end. That alone saved him about fifteen hundred dollars in credit line interest per year. Luna: And the waterfall made those options visible because he could see exactly which layer was causing the bottleneck. Lucas: Exactly. Now, the model itself is simple. You can build it in a spreadsheet with three columns: the layer, the expected dollar amount, and the expected date. Start with operating expenses, then financial obligations, then discretionary. For each layer, list the specific items — payroll on the 1st, rent on the 1st, supplier payment on the 15th — and the dollar amounts. Luna: And then you compare that against your expected cash inflows — customer payments, maybe a credit line draw — and you see if the water reaches each layer. Lucas: Right. And the beauty is, once you have the structure, you can run scenarios. What if a big customer pays ten days late? What if you move a supplier payment to net 45? What if you take a small draw on your credit line at the beginning of the month instead of waiting until you're desperate? Each change shifts the waterfall. Luna: What about the furniture maker's spring crunch — did the waterfall help there too? Lucas: It did. We looked at his March, April, and May waterfall. The issue was that his biggest outflow — the annual insurance premium — hits in April. And that's also when he's buying materials for the summer production run. So his operating layer in April is enormous. Meanwhile, his receivables from winter orders are still trickling in. The waterfall showed that he needed to either pre-finance that insurance premium by spreading it over twelve months, or take a two-month credit line draw specifically for that quarter. Luna: So he ended up switching to monthly insurance payments and pushed his materials order to May, when the receivables from spring sales start landing. Lucas: Exactly. And now his waterfall is much more even across the year. He still has a dip in early spring, but it's manageable. The key was seeing the layers — not just the net cash flow. Luna: I like that this isn't about complicated financial engineering. It's about ordering your payments by priority and timing. Lucas: Right. And the waterfall is a thinking tool as much as a spreadsheet. Once you start seeing your cash flow as layers rather than a single number, you start asking better questions. Like, 'What's the most critical layer this month? Is it fully funded? If not, what can I do to protect it?' Luna: How often should a small business owner update their waterfall? Monthly? Lucas: I'd say at least monthly, but weekly during volatile periods. The furniture maker checks his every Monday morning for the upcoming month. He projects expected inflows and outflows for each week, and then he knows by Wednesday if there's a gap that needs attention. It takes him about fifteen minutes. Luna: And if there's a gap — say the operating layer isn't fully funded — what are his options? Lucas: He has three levers. One, push an outflow to a later layer — negotiate with a supplier, delay a non-critical purchase. Two, accelerate an inflow — offer a discount for early payment on a specific invoice, or factor a single large receivable. Three, bring in external cash — draw on a credit line, use a business credit card for a short-term expense. The waterfall tells him which lever to pull based on which layer is thin. Luna: That's really practical. And it's different from just looking at your bank balance and hoping for the best. Lucas: Totally different. Your bank balance is a rearview mirror. The waterfall is a forward-looking map. And because it's structured by priority, it forces you to think about what matters most. For the furniture maker, the operating layer is non-negotiable. He'll use any lever to protect it. But the discretionary layer — that's where he has flexibility. Luna: What about businesses with more erratic receivables — like a consulting firm that gets paid on completion of projects, not on a regular schedule? Does the waterfall still work? Lucas: It does, but you need to adjust. For lumpy receivables, I recommend using a rolling three-month average of inflows rather than a single month's projection. So instead of saying 'I expect fifty thousand in June,' you say 'my average monthly inflow over the last three months is forty-two thousand, so I'll build my waterfall around that.' Then you treat any upside as a bonus that flows into the discretionary layer. Luna: That cushions the volatility. And if the actual inflow is lower than the average, you've already built in some margin. Lucas: Exactly. And you update the average every month. Over time, the waterfall becomes more accurate because the average smooths out the spikes. The furniture maker now uses a trailing three-month average for his receivables, and it's made his spring planning much more reliable. Luna: So we've got the waterfall structure — three layers, prioritized. We've got the rolling average for lumpy inflows. We've got the weekly check-in. Is there anything else a small business owner should layer on top? Lucas: The next step is to combine the waterfall with a rolling 13-week cash flow forecast. The waterfall tells you the priority order; the 13-week forecast tells you the timing. Together, they give you a complete picture. But that's really a topic for its own episode. Luna: We'll save that for another day. For now, if you're a small business owner, try building a simple three-layer waterfall in your spreadsheet this week. Map out your operating expenses, your financial obligations, and your discretionary cash. See where the bottlenecks are. You might find a few hundred dollars of hidden working capital. Lucas: And if you want to dig deeper, we've covered related topics in earlier episodes — like how to use receivables aging reports to forecast shortfalls, or how a rolling 13-week forecast prevents cash crunches. Those are Episodes 15 and 31 in the feed. Luna: I'll add that the waterfall works best when you revisit it regularly. The first time you build it, it's a snapshot. By the third month, it's a dynamic tool. Lucas: Right. And as your business changes — maybe you add a new product line or take on a loan — you just update the layers. The structure stays the same.