Each seat cross-examines another seat's case. Then each one says whether it holds or changes its vote. In this meeting, no seat changed its vote.
The Counsel questions The First-Principles Engineer
You say factoring releases cash rather than adding debt. Read the agreement before you believe that. If it is with recourse, every invoice the developer fails to pay comes straight back to you, so it is debt with extra paperwork. Second, many construction subcontracts restrict assigning what you are owed. Check yours first, or you breach the very contract you are trying to collect on. Third, factors usually notify the debtor, so both contractors learn you are short of cash in the middle of a payment dispute. Fourth, once the invoices are assigned, who serves the payment claim and runs adjudication? You may have handed away your strongest lever. And "scales with receivables" cuts both ways: retentions, disputed sums and amounts open to set off are often excluded. Find out what can actually be advanced before you call this the answer.
Holds RESHAPEbecause enforcing the payment claim first and then funding only the confirmed gap still protects both the cash floor and the order book.
The Compounder questions The First-Principles Engineer
You call it a virtue that factoring grows as the developer pays later. That is the flaw, not the feature. You would be tying more of your funding to the one counterparty already failing you. If the factoring is with recourse, a disputed invoice lands back on your books at the worst possible moment. You also do not know the advance rate, so nobody can yet say the facility closes your SGD 1.7m gap at all. And "close to the bank's cost" misses the point. The fee is charged on every invoice for as long as the delay lasts, while a loan is a known sum, borrowed once and repaid. Borrow a fixed amount to protect payroll, serve payment claims to shorten the 120 days, and price future bids for slow money. Never let your cash supply grow with a debtor's bad habits.
Holds RESHAPEbecause nothing argued here makes open-ended factoring on a concentrated, slow debtor safer than a known loan backed by legal pressure on the debt.
The Systems Sceptic questions The First-Principles Engineer
Seat E says factoring scales with the receivables, so the later the developer pays, the more you can draw. That is the flaw, sold as the feature. A facility that grows as one developer pays slower ties more of your company to one counterparty every week. A serious factor caps exposure per debtor, and with a third of revenue behind one developer you may hit that cap early. If the deal is with recourse, every invoice the developer fails to pay comes back to you at the worst moment. "Probably close to the bank's rate" is a guess. Nobody here knows the advance rate or the days to cash, and those decide whether payroll in five weeks is covered. Ask three things first: with or without recourse, the limit per debtor, and the days to first cash. Then serve the payment claims.
Holds RESHAPEbecause the attack confirms my view: factoring only helps if it is non-recourse and the factor takes the developer risk, and that still has to be confirmed in writing.
The Institution Builder questions The First-Principles Engineer
You call it a feature that factoring grows as the developer pays later. From where I sit, that is the danger. Every extra week of lateness lets you advance more paper against one developer, so your funding rises exactly as the credit behind it gets worse. That is concentration with a growth engine attached. You also skip the two numbers you do not have: the advance rate and the days to cash. Payroll lands in about five weeks. A facility that pays most of the invoice in week six does not close your 1.7m gap. Before payroll, get a committed bank line sized to that gap, because that money is certain and you are the one who controls it. Serve payment claims to shrink the receivable. Factor only invoices the factor will take without recourse, and only after you have read the assignment terms.
Holds RESHAPEbecause nothing here shows factoring gets cash in before payroll or limits exposure to the developer, and survival needs both.
The First-Principles Engineer questions The Systems Sceptic
The bottleneck is not who carries the risk. It is days to cash, and payroll lands in about five weeks. Eight weeks of cover at SGD 0.9m a week is SGD 7.2m, so you are about SGD 1.7m short today, before any further slippage. Non-recourse factoring means a factor has to underwrite a developer nobody here has assessed. That is the slowest paper on the table, and you have no advance rate and no days to cash for it. A refusal under deadline tells you about one factor's appetite this month. It does not tell you what the revenue is worth. Treating that refusal as a reason to stop bidding puts a third of revenue, and the SGD 30m order book, at the mercy of one phone call. Fix the clock first. Price the risk once payroll is safe.
Holds RESHAPEbecause the binding constraint is still cash timing, and the fastest fix is a committed line plus a statutory payment claim.