Beyond the four days — cases for the book · CFOs
Subtitle: Knowing Your Terms as Well as Your Product
The invoice had been ready for eleven days. Nobody had sent it.
He found it on a Monday, in the shared folder, numbered and complete: the second milestone on a custom test line for a large manufacturer, 184,000, the biggest single line his engineering firm had ever written. Twenty-three people, a mid-sized industrial economy, eight years since he had founded it. The first milestone had been paid — seventy-one days after the due date, without a word of explanation.
He asked his head of delivery why the second one was still sitting there.
"Because if we send it now, they'll read it as pressure. The next project is being decided this quarter."
He asked his finance lead the same question.
"Because if we don't send it, we're short for payroll in five weeks. I've already asked two suppliers to wait."
Both were right. That was the problem.
Cash is oxygen. Without it, a company does not breathe. And bills do not wait.
He had read, years earlier, that deferred payment was never itself the danger — vagueness and irresponsibility were. He had nodded, the way one nods at proverbs. Now he pulled the contract and read the payment clause as if for the first time: "payable upon acceptance of Milestone 2." Acceptance by whom? Against what? By when? The clause named no person, no test, no date. He had extended a loan of 184,000 to a company forty times his size, with no term and no interest, and called it a sale.
Deferral is not the problem. Vagueness and irresponsibility are.
He wrote three numbers on the whiteboard. The price on the invoice: 184,000. The real price, once he counted four months of carrying it on the credit line: roughly 179,000. And the price of the relationship if he behaved like a creditor: unknown, and larger than both.
Then he did what he should have done at the start. He called the client — not the project manager, who had gone quiet, but the plant's finance director, whom he had never met. He did not threaten. He asked how the acceptance was going, and whether anything on his side was holding it up.
There was a pause. Then: "Honestly? Nobody here knows who signs off on your milestones. The engineer who scoped it moved to another site. Your invoice isn't stuck in a drawer. It's stuck in a question."
Collection is not a fight. It is a conversation — and the real one begins with the agreement at the start, not when the deadline passes.
He offered a solution rather than a reminder: a one-page acceptance protocol — three measurable tests, a named signatory on each side, a date. In return he proposed splitting the open amount: sixty percent on signature, the rest fourteen days after the tests passed. The finance director signed on Thursday. The first sixty percent arrived the following week. The engineer who ran the tests said it was the first time a supplier had told him exactly what "done" meant.
That could have been the end. Instead he went back to his own list.
Two suppliers had been asked to wait because his client had made him wait. The morning after the client's money landed — and only then, which was its own confession — he paid them in full: a small machining shop and a controls integrator, forty days late between them. He told each of them why. If you have agreed to pay in thirty days, pay on the twenty-ninth. That is how reputation is built. He had let a debt owed to him become a debt he owed to others, and had not noticed he was now the one being irresponsible.
Then he rewrote the offer for every future project. A thirty percent advance on signature. Milestones with acceptance criteria written into the proposal, not discovered afterwards. Two payment terms priced openly: fourteen days at the quoted price, sixty days at the quoted price plus the cost of carrying it. The credit he had been giving away for free now had a name and a number on the page, and a client could choose it or not.
His sales lead worried it would make the firm look expensive. "It makes us look like a firm that knows what its work costs," he said. "A price that is too low makes people ask what the catch is. Our catch was that we were financing them and pretending we weren't."
The manufacturer's next order came back with the sixty-day option chosen, the carrying cost on the line above the signature. The sales lead read it as a loss. He read it differently: the same client had taken the same credit for nothing and returned it seventy-one days late; now it had chosen it, knowingly, at a price, with a named signatory and a date. The credit had not gone away. It had become a term.
He kept the old invoice, printed, in his desk drawer. Not as a trophy. On the back of it he wrote one line in his own hand, for the next time someone in the firm was afraid to send an invoice: We knew our machines to the last bolt and never knew our terms. Knowing when the money moves is as much our trade as knowing how the machine runs — and we had left that day blank.
Anchor: "deferral is not the problem — vagueness and irresponsibility are"; collection begins with the agreement, not the deadline; the best collection is the one you never have to ask for; price as a signal; reputation worth more than the invoice. Live exercise: each participant writes their own standard payment clause on a card from memory, then answers three questions — who accepts, against what, by when. Most cards fail at least one; that is the case in the room. Trap to resist: letting the session drift into hard collection tactics and leverage. The founder never threatened; the turn came from a protocol and a phone call. Keep the room on terms and character, not on pressure. On the ending: the client chose the priced sixty-day term — ask the room whether that is a loss or the first honest price the firm ever charged for credit it had always been giving.
A question for the table, a disagreement, what you would have done. The case lead reads every comment; the ones the table takes up enter the chapter as questions from the room, with your name.