CXO Group · delegate sales bandwidth · Aug 2026 – Dec 2027
Enter a proposed event date and table size. The answer tests the full campaign window against person-weeks available and free campaign slots — the same test the weekly table runs.
Read straight off the pipeline below. Every gap is expressed as headcount, with the date the person has to be productive by (not the date you start recruiting).
"Could still sell" is worked out for each month on its own — how many standard dinners you could land in that month if you chose to sell into it, given what is already committed. They are alternatives, not a running total: filling January's slots would draw on the same people February needs. A campaign spanning Christmas simply pauses, so January and February are sellable from a November or December launch.
Type the number of delegates confirmed straight into Booked on any event — here or on the pipeline below. Still required, pace needed and the projected final number all follow from it.
Bars are committed delegate-sales effort per week. The dashed line is the team's available person-weeks. Hover any week for detail.
The solid bar is how long the pair are actually tied up — it ends when the table fills, not at the dinner. The dotted line runs on to the dinner date. Overlapping bars are the weeks that compete for the same people.
Add every dinner you are considering, not just the confirmed ones — provisional dinners still consume the bandwidth you are trying to measure.
Set each person's weekly booking target on the roster below, then log what they actually booked. Targets automatically fall to zero over the Christmas shutdown and are de-rated for holiday.
Add a staff member any time — set the date they start and every week from that point forward recalculates. Allocation % is the share of their week available for dinner campaigns.
The rule this model is built on: 2 people take 2.5 weeks of work to fill a 25-person dinner, provided the campaign starts 8–10 weeks out. That is 5 person-weeks per dinner, spread across the campaign window.
How the project limit is counted: this limit is about how many campaigns somebody can juggle, so a campaign counts as at most one project however big the table — an 80-seat dinner is still one campaign, and its extra volume is charged to person-weeks instead. Small jobs count as a fraction: topping up 4 seats against a 25-seat baseline is 0.16 of a project, so one person can carry several top-ups alongside a full table without breaching the -projects-per-person rule. Nothing live counts as less than 0.10, because an open campaign always takes some attention.
Effort is scaled pro-rata for larger or smaller tables — a 50-person dinner is assumed to take twice the effort of a 25-person one.
Nothing is saved automatically. Use Save data (JSON) to keep your roster and pipeline, and Load data to bring it back next time.