Walk into any factory and the operations team can tell you, to the unit, how much product they've committed to ship over the next ninety days. They call it backlog. Walk into any B2B SaaS company and the CFO can tell you the same about subscription revenue. They call it ARR or contracted ARR or some flavor of pipeline.
Walk into a paint-and-sip studio or a candle bar or a winery tasting room and ask "how much revenue is on the calendar for the next ninety days," and you'll get a blank stare. Not because the data doesn't exist, it does, in the booking software, but because nobody's been tracking it as a metric.
That's strange. Every confirmed booking on your calendar is exactly the same thing as a manufacturer's backlog: revenue you've committed to deliver, at a known date, for a known amount. The reason this industry doesn't track it is mostly accidental, booking software wasn't built by people who think in operations metrics, but the cost of not tracking it is real.
This post makes the case for two numbers we wish we'd been measuring at Cork & Candles three years ago.
The metric
Backlog = total revenue on the books for future-dated bookings.
That's it. Take every booking on your calendar with a date after today, sum the booking values (including deposits collected plus expected balances), and you have your backlog number.
For Cork & Candles, on any given Monday, backlog is somewhere between $35,000 and $65,000 depending on the season. We didn't know that until we started tracking it. We knew "this week is busy" or "next month is quiet." We didn't know in dollars.
The reason the dollar number matters more than the gut feel: it's directly comparable across time. "This week is busy" doesn't tell you whether you're up 15% from this time last year. "Backlog is $58,000" does, if you have last year's number.
The companion metric
The number that's more useful than backlog alone is backlog replenishment.
Backlog replenishment = (new bookings added) − (bookings hosted) − (cancellations), measured weekly.
If you're adding more bookings than you're hosting plus canceling, you're growing. Your backlog goes up week over week. If you're adding less, you're shrinking, even if your top-line revenue this week looks fine.
Backlog is a snapshot. Replenishment is the rate of change. Together they tell you where you are AND which direction you're moving.
The story this combination tells:
- Backlog up, replenishment positive. You're growing. Your pipeline is healthy. Now's the time to add capacity or raise prices.
- Backlog up, replenishment negative. You're consuming pipeline faster than you're refilling it. Looks fine this month, going to feel different in three. Time to look at marketing spend.
- Backlog flat, replenishment positive. You're at equilibrium but trending in the right direction. Steady state.
- Backlog down, replenishment negative. You're shrinking. Both signals agree. This is the moment to investigate, not next quarter.
The single most useful question this framework answers is "are our marketing dollars producing future revenue, or are they just covering the bookings we're hosting this week?" Most operators can't tell the difference. Replenishment makes it visible.
Why these two beat any single-number metric
Most operators in this category measure "bookings this week" or "revenue this month." Both are reasonable backwards-looking metrics. Neither tells you anything about the future.
The problem with looking only at current-period revenue: it lags. By the time your weekly revenue is down 20%, your replenishment rate has been negative for six weeks. You're catching the problem after the train has already left the station. Backlog and replenishment let you see the problem in week one, when it's a 5% blip. Not in week six when it's a five-figure hole.
The problem with looking only at total bookings: it doesn't separate volume from value. You can have your highest-bookings month ever and still be in trouble, if those bookings are all small public classes and your high-value private events have dried up. Backlog in dollars catches that. Bookings count doesn't.
How to use it for staffing
The single most practical use of these metrics: deciding when to hire.
Most operators hire reactively. The room is busy for three weeks in a row, you panic, you post a job. By the time you've hired and trained, the rush is over.
If you're watching backlog, you see the rush coming three to six weeks before it arrives. Backlog goes up. Replenishment is positive. The bookings on the calendar for next month are 30% higher than last month at the same point.
That's your hiring signal. Not the busy week itself. The trend that produces the busy week, before it arrives.
The same logic works in the other direction. If backlog is trending down and replenishment has been negative for a month, that's your "don't extend the offer to the part-time instructor" signal. Before payroll becomes a problem.
How to use it for marketing spend
The other practical use: deciding whether your ads are working.
Most operators look at "ad spend → bookings this week" to decide if a campaign is worth it. The problem is the bookings this week reflect ads from two or three weeks ago, plus organic traffic, plus repeat customers. Disentangling the signal is hard.
The replenishment metric does it for you. If replenishment is positive while you're running ads, the ads are net adding to your future pipeline. If replenishment is flat, the ads are replacing churn but not growing the business. If replenishment is negative, the ads aren't keeping up with your hosting rate, and either you're losing customers or the ad strategy isn't working.
This is the test that tells you whether to scale spend, hold, or cut. It's a single number derived from data you already have.
The seasonality wrinkle
The honest caveat: backlog and replenishment are noisy week-to-week. Holiday weeks distort the picture. So do private-event clusters and slow seasons.
The fix is to compare year-over-year, not week-over-week. Backlog this week compared to backlog the same week last year is the meaningful comparison. Same with replenishment.
If you're a new business without last-year data, the next-best is rolling four-week averages instead of weekly snapshots. Smoother. Less reactive. Better for catching real trends instead of holiday noise.
The Excel version, before you have software for it
We tracked this in Excel for about eighteen months at Cork & Candles before we had software that surfaced it natively. The minimum-viable version:
A row for each week. Three columns: opening backlog, bookings added that week, bookings hosted plus canceled that week. Closing backlog = opening + added − (hosted + canceled). Replenishment = added − (hosted + canceled).
That's the whole spreadsheet. Twenty minutes once a week to update. If you do nothing else from this post, build this spreadsheet for your venue. You'll learn things about your business that the dashboard in your booking software doesn't tell you.
What we built into ArtistryHost
ArtistryHost surfaces both as a real-time dashboard widget. The widget on the main dashboard shows today's backlog, the four-week trend, and replenishment for the current week with year-over-year comparison when we have the history.
The version we was running in Excel at Cork & Candles was correct but two weeks late. The dashboard widget catches the trend the day it changes.
The other thing we'll do, once we have enough operators on the platform, is publish anonymized backlog benchmarks by vertical. A paint-and-sip studio with $40,000 in backlog will be able to see whether that's high, low, or normal compared to the median in our customer base. That benchmark doesn't exist anywhere in this category today. We'll be the first.
The meta point
The bigger principle here is that this category has been operating without the metrics that every other category considers table stakes. Manufacturing has backlog. SaaS has ARR. Restaurants have covers and average check. Experiential venues have... vibes.
The first venue in any given market that starts measuring future-pipeline revenue the way other industries do gets a real edge. They make better staffing decisions. Better marketing decisions. Better pricing decisions. Better hiring decisions.
The data has been sitting in your booking software all along. Somebody just has to make it visible.