Bookings is the value of customer contracts signed during a period. It is recorded on the date the agreement is executed, before any invoice goes out and before any service is delivered. It measures what the selling system closed, nothing more.
As a formula:
Bookings = sum of committed contract value signed in the period, under one documented bookings policy
The policy is the metric. Whether bookings counts total contract value or annualized value, how renewals and expansions are treated, and what happens on cancellation all have to be written down. Two companies can both report "bookings" and be counting different things.
Bookings versus billings versus revenue
The three top-line metrics separate cleanly by timing:
- Bookings: a contract is signed. A commitment now exists.
- Billings: an invoice is issued. Cash is now requested. See the
billings guide for the calculated-billings formula and its traps.
- Revenue: the service is delivered. Value is now earned and recognized
under accounting rules.
Wall Street Prep notes that bookings can describe a SaaS company's growth profile better than GAAP revenue in multi-year contracts, because recognition spreads the value across the delivery period long after the sale happened. That is exactly why bookings is also the easiest metric to inflate.
A worked example
A customer signs a two-year, $240,000 contract on March 15, billed annually up front, service starting April 1.
- Bookings in March: $240,000 if the policy counts TCV, or $120,000 if it
counts annualized value;
- billings in the period of the first invoice: $120,000;
- revenue in April: $10,000, one month of delivery;
- deferred revenue after the first invoice: the invoiced but undelivered
balance.
One contract produces four numbers on four schedules. A dashboard that adds any two of them together is broken.
Definition pitfalls
- counting verbal commitments, unsigned proposals, or pilots as bookings;
- mixing TCV-based and ACV-based bookings in one series;
- double-counting renewals as new bookings without a new, renewal, and
expansion split;
- ignoring cancellation and downgrade terms: a booking with a 30-day out
clause is not the same commitment as a firm annual term;
- reporting bookings growth while term lengths stretched, which raises
TCV-based bookings with no change in annual value;
- letting sales report bookings from CRM amounts that finance never
reconciles.
How an operator should use bookings
Bookings sits in the Measurement pillar of the Tenbound Pipeline Architecture Standard: it is the output edge of the selling system, read before invoicing and delivery add their own timing.
Use it to answer one question: how much new commitment did the machine produce this period, and from where? Segment new logo, renewal, and expansion. Reconcile the total against countersigned contracts, not opportunity fields. Then read it upstream against pipeline velocity to see whether the commitment trend was built by more opportunities, bigger deals, better win rates, or faster cycles. Bookings tells you what closed. The pipeline metrics tell you whether it will happen again, and the finance metrics downstream tell you when the commitment turns into cash.