Running Full Isn't the Same as Having Money

I sleep fine. The anxiety isn't the kind that keeps you up — it's the wide-awake kind, where I look at a production schedule that's booked solid and, in the same breath, work out where the end-of-month payments are coming from.

A pile of receivables. A pile of payables. Work never stopping, machines barely idle. That should be good news, and still I can't settle. Running at capacity and having money are two different things, and what sits between them is payment terms.

This post isn't for anyone else. It's for me: lay the fears out one by one and see which ones are actually real.

1. First, tell the two apart: a business problem, or a financing-the-customer problem

Companies rarely die from not making money. They die on the day they can't make a payment. The two look alike and call for opposite responses.

Here's my actual shape: orders are there, capacity is full, receivables rising, payables rising. That isn't "nobody wants what I make." That's me funding my customers' timelines out of my own pocket.

Once that's clear, the moves change:

• On receivables, stop staring at the balance. Stare at the aging and the rhythm. The balance is one frightening number; the aging is something you can act on. Who's past 60 days, past 90? Who always pays, but only after a call? Who keeps stretching it far enough that I should think hard before taking their next order?
• Split payables into three piles: due this week, negotiable terms, and has room. Wages, taxes, and critical suppliers are the untouchable pile. Most of the rest is more negotiable than it feels.

One undifferentiated blob of "I owe a lot" hangs over you all day. A sorted table costs you a busy afternoon. Between anxiety and work, the gap is one act of sorting.

2. The laser cutter isn't spending money — it's changing how the money gets paid

My hand shook the day I placed that order. That much money, at the tightest point.

But look at it another way: what that money buys isn't a machine. It buys out, in one payment, the overtime, the outsourced cutting, and the waiting-for-a-slot that I would otherwise pay every single month from here on.

The argument I use on myself isn't "how long to pay it back." Payback math is too easy to turn into self-comfort — I get to pick both the numerator and the denominator. The harder questions:

• Same batch of plate: how many fewer people? How many fewer days?
• Jobs I couldn't take before — thickness, tolerance, volume, lead time — can I take them now?
• The cutting I send out: how much of it comes back in-house?

And the timing is right. You add capacity while you're full, because there's work to feed it. Waiting until orders drop before improving throughput — that's the gamble.

The day it lands, don't just take photos. Run a real job on it and measure the cycle time against how we do it today. Until there's a number, everything said about that machine is just mood.

3. The system that ate my energy wasn't one we use ourselves

The system that consumed most of me these past two months was built for someone else — data collection and monitoring on the equipment and production-line side. Heavy to build, deeply invested in.

It wasn't wasted. The tuition was real: I move visibly faster now, because I already know which holes I don't need to fall into twice — what to build first, what I should never write myself, which features nobody ever clicks.

But here's what took me a long time to admit: capability grows wherever the energy goes. However well that system was built, it never saved my own shop a single minute.

Our own side never actually stopped. Two attempts so far. One did project-level margin analysis — did this project actually make money, at which step, and how do costs spanning several months get collected and allocated. The other only ever got the technical foundation laid; it never grew into a whole thing.

The one I'm building now has a smaller, more honest goal: let me know, at any moment, how much work is on hand, where each order stands, whether material is complete, and what shape this month's cash in and out is taking.

Which is to say: take the table from section 1 out of my head, put it on a screen, and let it update itself.

One line took me a long time to see plainly:

What actually generates the anxiety isn't that the numbers look bad. It's that I don't know the numbers.

Fear of a vague thing has no ceiling. A specific number, at worst, is annoying. So half the value of this system is efficiency, and the other half is knowing where I stand.

This time, it serves me first.

4. The shortest possible list for end-of-month me

• One fixed time each week, look at exactly three numbers: cash collected this week, must-pay next week, receivables past 60 days.
• Collections aren't begging. They're a process — with a cadence, an owner, and a record.
• First week the cutter is in, measure cycle time. Not by feel.
• The system does one job: make those three numbers stop being hand-calculated. Everything else waits.
• The rest can wait a little longer.

Finally

Orders booked solid, cash tight, equipment in transit, a system still being built — all four at once isn't light. But they're four parts of one sentence:

This business is growing, and growing costs money up front.

The situation actually worth fearing is the other one: machines idle, books clean, nothing to be anxious about. That kind of quiet is the one that kills you.

This kind is the discomfort of being busy.

Build the table, collect the money, get the machine running.

Get the numbers straight first. Then we'll talk about being afraid.