Happeningout — Operating Platform for an LGBTQ TV Network

Happeningout is an LGBTQ television network. The operating reality of running a media network is heavier than the on-air side suggests: there's a production lineup to plan and schedule, events to organise (live, ticketed, panels, screenings, fundraisers), an audience to communicate with on cadence, a content surface (the public site, blog, editorial) that has to reflect the brand seriously, and sponsorship + revenue motion that runs alongside all of it. Generic CMS plus generic CRM plus generic events tool plus generic mailing tool doesn't scale — each piece carries its own copy of the audience, and the team spends as much time reconciling tools as running the network.

Happeningout engaged Linescripts to build the network's operating platform on Odoo — a set of purpose-built modules that handle production scheduling, event organisation, ticketing for live events, audience communication, the public site, and sponsorship sales as one connected stack.

The Challenges Happeningout Faced

• Production lineup planning across many tools. Programming a TV network means scheduling shows, talent, production blocks, and on-air slots. Doing that in spreadsheets and shared calendars leaves the planning team without a single view of the lineup.
• Events as their own parallel system. Live events — panels, screenings, fundraisers, ticketed gatherings — usually live in a separate event tool. Ticket sales, attendee records, and event finance reconcile back into the network's accounting manually if at all.
• Audience scattered across tools. Viewers, event attendees, ticket buyers, newsletter subscribers, sponsor contacts — the same person showing up across five tools as five records.
• Mailings that need to target audience segments precisely. A communication about a specific show or event needs to reach that show's or that event's audience — not a generic list maintained on a separate ESP that drifts out of sync the moment ticketing or events change.
• Public site disconnected from the operating layer. The customer-facing website is where the brand lives, but if it's a separate WordPress / static site, every content update means coordinating between the operating system and the site, and the schedule the public sees can drift from the production schedule the team works to.

How Linescripts Built the Solution

ls_organizer / ls_calendar / ls_project — production lineup operations

The production-side modules let the network's team plan the lineup, schedule production blocks and resources, and track production work in the same Odoo instance the rest of the operation runs from. The production calendar and the public-facing schedule are the same calendar — what the team works to is what the audience sees.

ls_ticket_booking — ticketed events as first-class records

Live events that need ticketing (panels, screenings, fundraisers, gatherings) are managed inside the same operating layer. Event configuration, seat or ticket inventory, customer-facing checkout on the website, and finance reconciliation all flow through the standard Odoo Sales + Accounting model. No separate event platform, no parallel ticketing SaaS, no monthly reconciliation against a third-party.

ls_mass_mailing — audience targeting tied to live records

Audience communication targets the actual audience records inside the platform. A mailing about a specific show or event queries the live data — attendees of that event, subscribers to that show's segment, buyers of that ticket type — rather than an exported list that ages out the moment someone unsubscribes or registers.

happeningout_website + ls_blog — public-facing content surface

The public-facing website and editorial blog run on a branded Odoo theme inside the same operating system. Content publishing, scheduled posts, editorial flow — all live in the platform that the rest of the operation runs from. No separate CMS, no marketing-tool reconciliation.

ls_sale + ls_timer_modification — sales motion + platform refinements

Sales-flow refinements aligned to the network's revenue motion (subscriptions, sponsorships, ticketed events, ad sales as relevant), plus small platform-level adjustments to make the operating system fit how a TV network actually works rather than how stock Odoo assumes a company works.

What Changed for Happeningout

• Production lineup, events, ticketing, audience comms, and the public site live in one platform. The marketing team does not maintain a separate CRM; the events team does not run a parallel ticketing platform; the editorial team does not run a separate CMS.
• One audience record across all the contexts that audience appears in. A viewer who buys a ticket, attends an event, subscribes to the newsletter, and shows up at a fundraiser is one record with one history, not five.
• Mailings target live audience data. Communication about a show or event reaches that show's or event's actual audience because the list is a query, not a separately maintained export.
• Public schedule = production schedule. What the team works to is what the audience sees — no risk of the website's listings drifting from the actual production calendar.
• Ticketed events reconcile to finance automatically. Ticket revenue lands in the same accounting model as everything else; no monthly reconciliation against a separate ticketing SaaS.

Closing

The platform looks like a set of modules from the inventory side — production lineup, events, ticketing, audience, public site, sales — but architecturally it's one operating system for an LGBTQ TV network, with the workflows the network actually runs implemented natively rather than stitched together from five SaaS tools. The team works in one place; the audience exists once; the schedule the public sees is the schedule the production team plans against.