Binding Constraint

PacedRevenue · 21 August 2026

The binding constraint is the revenue gate with the lowest Gate Efficiency. It is the diagnosis: everything downstream of it is a symptom rather than a cause. Where two gates tie, the binding gate is the earlier one in causal order, because an upstream constraint manufactures downstream symptoms.

What it looks like in practice. In the whitepaper's worked example, the binding constraint is Embed at 50%: the engine yields 12.7%, and lifting Embed alone to its benchmark moves the yield to 25.5%. Fix that one gate and the whole engine's output doubles, on the same pipeline and the same headcount. The symptom showed up as a soft number and an urge to buy more funnel volume, and the gate responsible was nowhere near either.

What it is not. The binding constraint is not the gate with the worst raw conversion rate: raw rates carry different base rates, which is what normalising removes. The ancestor is the Theory of Constraints, where every system has one governing constraint; the gate model adds the finding instrument, five normalised efficiencies that make "weakest" a measurement rather than an argument.

Where it comes from. Defined in The Revenue Debt You Cannot See, with the tie-break and second-constraint rules in the PACED scoring model.

Related terms. PACED Yield, the product the constraint caps; Revenue Debt, the price of leaving it standing; the Ghost Champion and the Churn-Masking Illusion, two ways a gate stays weak while looking fine.

The free PACED diagnostic names your binding constraint in fifteen questions.