Backlog vs pipeline

Backlog and pipeline answer different questions. Backlog is the value of work that is contracted but not yet delivered or recognized: signed, funded, owed to the company. Pipeline is the value of opportunities still being pursued and not yet won. Backlog is a near-certainty (subject to delivery and cancellation terms); pipeline is a probability-weighted hope. Treating them as one number is the most common revenue overstatement diligence corrects.

The clean presentation keeps them in separate columns and qualifies each. Backlog: contract value, expected delivery schedule, cancellation and acceptance terms, and whether the customer’s funding is in place. Pipeline: staged by likelihood (qualified, proposal, verbal, etc.), with a blended conversion assumption and an honest age (a deal that has sat at “proposal” for a year is not really pipeline). The quality questions are familiar from quality-of-revenue work: how concentrated is the backlog in one customer, are the contracts cancellable for convenience, and does the pipeline conversion assumption match the company’s own history.

For a deep tech company the trap is double. Much of what gets called backlog is really conditional: pilots that convert only if a milestone is hit, contracts contingent on a grant landing, orders with long acceptance gates. And much of the pipeline is non-commercial interest (research collaborations) mislabelled as sales. The credible founder reports a small, clean backlog, a realistically staged pipeline, and the gating conditions on both, rather than a single headline number that diligence will immediately decompose.