Founder, your $80M backlog is not $80M revenue.
It is a claim on future execution. Between the signed number and the collected cash sit four distinct risks, and a diligence process will price every one of them whether you have or not.
The four risks inside a backlog
Delivery risk. Can you execute at the pace the contract assumes? An $80M backlog deliverable over two years implies a delivery capacity the company may never have demonstrated. The contract was signed against a plan. Diligence checks it against history.
Margin risk. Was the contract priced to win, or priced to make money? Large contracts in competitive tenders are routinely won at margins the company would never accept in a spreadsheet exercise. A backlog full of priced-to-win contracts converts into revenue and losses simultaneously.
Working capital risk. Who finances the gap between delivery and payment? Delivering the backlog consumes cash before it generates cash: people, materials, subcontractors, all paid before the client pays. The bigger the backlog, the bigger the gap. Growth against a large backlog is a working capital demand, not a working capital source.
Timing risk. In MENA specifically, large government and enterprise contracts can run 12 to 18 months between award and first cash. The award announcement and the first collected dirham are separated by mobilization, milestones, acceptance procedures, and payment terms that were never going to be 30 days.
The three questions a reviewer asks
When a CFO or an investor reviews your backlog, they are not reading the total. They ask three questions:
What is your historical conversion rate from backlog to recognized revenue? Not the contracted schedule. The actual history: of everything signed two years ago, what share became revenue, on what delay.
What is your average cash collection cycle? From invoice to cash, by client type. Government cycles and enterprise cycles are different numbers, and blending them hides the problem.
How concentrated is the backlog? One client at 60% of the backlog means the backlog’s real risk profile is that client’s payment behavior, not the company’s execution.
The synthetic worst case
An $80M backlog with 60% concentration in one client, 18-month payment cycles, and no bridge financing in place is not a growth story.
It is a liquidity problem. The company has contractually committed to spending money for 18 months against a receivable from a single counterparty. If that counterparty slips a quarter, the backlog does not protect the company. The backlog is what kills it, because the cost base was scaled to deliver it.
What investor-grade backlog reporting looks like
The founders who handle this well present backlog the way a reviewer will read it anyway: total signed value, expected recognition schedule by quarter, historical conversion rate, concentration by client, cash collection assumptions by client type, and the working capital requirement implied by the delivery plan, with its financing identified.
That last line is the one that separates a growth story from a liquidity risk. Revenue backlog with unfunded working capital is a commitment, not an asset.
Know the difference before your investor does.