The Booking Group — Tour Booking Management Platform for Broadway Touring

The Booking Group is Broadway's premier theatrical touring booking agency, operating from offices in New York City (1501 Broadway) and Durham, North Carolina. The agency books touring engagements for Broadway productions — Hamilton, Six, Hadestown, Chicago, The Wiz, Mrs. Doubtfire and roughly thirty other titles — into presenting venues across the United States. The operating layer of a touring booking agency is specific and unforgiving: a roster of touring shows, a network of presenting venues with different capacities and engagement formats, scheduling that has to make geographic sense for the tour, contract management across many venue relationships, and a financial framework (gross potential per city, success rate per tour) that the industry uses as its native vocabulary.

The Challenges The Booking Group Faced

• Generic CRM tooling doesn't speak theater. A booking is not a deal in a sales pipeline; it's a "wrap" — a contract for a tour at a venue for a specific week, in a specific city, with a specific gross-potential calculation. Forcing that motion into a generic CRM loses the industry-native data shape.
• Multiple tours, many venues, hundreds of wraps. Tracking which tour is wrapping which city in which week, across many concurrent tours and many concurrent venues, needs a data model that holds the tour ↔ city ↔ wrap relationship cleanly rather than as a flat spreadsheet.
• Two engagement formats with different operational logic. Full-week engagements (the tour books a venue for a full week) and split-week engagements (the tour splits the week across two cities) need different scheduling rules and different contract terms. The system has to know which is which and behave accordingly.
• Venue partners need a portal, not email threads. Presenting venues are partners in the booking, not external recipients of emails. They need controlled access to their relevant tour information without exposing the rest of the agency's confidential pipeline.
• Reporting in formats the touring industry uses. Financial reporting in the touring world lives in Excel — wraps, gross potential, success rates, schedules. The platform has to export to XLSX cleanly, not just render PDFs.

How Linescripts Built the Solution

Industry-native data model

Custom Odoo models built around the touring industry's native vocabulary:

• — represents a touring show, with full-week / split-week department type, success rate, and the count of associated wraps.
• — the booking contract itself, tied to a tour and a city.
• — per-city gross potential figure (the industry-standard ceiling of what a venue can earn for a show in that city), with weekly number of performances. Currency-aware via the city's currency.
• — first-class city model with state, opening / closing dates, currency, tour assignment. Built as an extension of the standard country / state hierarchy so geography is honest.

Full-week / split-week scheduling logic

Tours carry a week-department type (full or split) that drives the scheduling logic the platform follows. The data model knows the difference, so the workflow doesn't have to remember it on every booking.

Partner portal for venues

Built on Odoo's portal layer (the module depends on ): presenting venues can be invited as portal users and given controlled access to their relevant tour and wrap information. Multi-week wrap templates handle the multi-engagement case where a tour passes through a venue's region more than once. Public-facing templates handle the controlled create / edit flow.

Wraps reporting in XLSX

The bookings module depends on (third-party). A dedicated wizard exports wrap data into the Excel format the agency's financial workflow runs on. Import-wraps wizard handles the inbound direction — bulk-loading wrap data from spreadsheets the team already maintains.

Custom login + backend theme

The platform uses a custom login surface so the operating system is branded for the agency rather than landing on a stock Odoo login screen. The backend itself runs The custom modules so day-to-day administrative work feels modern.

What Changed for The Booking Group

• Bookings are tracked in the industry's native data shape. Tours, wraps, gross potential, full vs split week — the platform speaks the language the agency actually uses, not a generic CRM translation.
• Multi-tour, multi-venue scheduling has a real data model. The tour ↔ city ↔ wrap relationship is first-class; pipeline-level visibility across the full booking calendar exists without manual spreadsheet stitching.
• Venues are partners, not email recipients. Portal access gives presenting venues a controlled view of their relevant bookings without exposing the rest of the agency's confidential pipeline.
• Reporting + bulk import in XLSX. The financial workflow stays in the format the touring industry already uses — Excel — with the platform feeding it from a single source of truth rather than the team maintaining parallel spreadsheets.

Closing

Generic CRM tooling is built around a generic sales pipeline. Broadway touring booking is not a generic sales pipeline — it's a tour-and-wrap-and-gross-potential motion with its own vocabulary, its own scheduling logic, its own contract formats, and its own reporting expectations. The platform Linescripts built doesn't try to translate that motion into generic CRM terms; it implements the motion natively, so the agency works in the system rather than translating into and out of it.