Industry solution
Run every property, departure and guest conversation as one operation
Bookings, rooms, guides, events, guest messages and portfolio numbers, designed to hand off to each other across Burdenoff products.
The problem
Rooms sell while engineering has them out of order, guides are rostered from a group chat, room blocks are reconciled in spreadsheets and guest messages wait until morning, because each tool sees only its own slice.
Hospitality sells perishable inventory. A room-night or a tour seat that goes unsold tonight is gone, and one that is sold but cannot be delivered is worse. Hotel groups and tour operators run a property system per hotel, booking channels, a spreadsheet of guides, an engineering logbook and a WhatsApp inbox, and each of those tools knows only part of what the guest is about to experience.
Peak weeks expose the seams. A festival or conference compresses demand, sick calls arrive before the first departure, equipment fails overnight, and the front desk sells whatever the booking calendar says is open. Seasonal labor is hard to find, margins are thin, and the people who fix problems (engineers, excursions leads, night auditors) rarely look at the same screen as the people who sell.
Above the property, operations leaders need one view of occupancy, rate, rooms out of order and labor, and corporate travel buyers now ask for sustainability data per stay. Answering either usually means reconciling exports by hand, so decisions arrive a week after the problem did.
VP or Director of Operations, hotel group
One view of every property, fewer walked guests and surprises, and standards that hold across hotels in peak weeks.
General Manager
Their own property's occupancy, rate, guest messages and labor, without spending the morning before the weekly call reconciling spreadsheets.
Chief Engineer or Director of Engineering
Out-of-order rooms returned to sale quickly, preventive work on schedule, and knowing which equipment drives energy use.
Tour or Excursions Operations Lead
Every departure covered by a guide with the right language and current certificates, and sick calls handled in minutes.
Director of Sales and Events
Room-block pickup, cutoff and release decisions made from live event registrations rather than emailed rooming lists.
Front Office Manager
Guest questions answered quickly and accurately overnight, with allergies, complaints and refunds reaching a person.
A day in the life
Ines Okonkwo runs operations for six boutique hotels, from the 120-room Harborlight House to the 38-room Millrace Inn, plus Saltgrass Excursions, which runs kayak loops, heritage walks and food trails. The last week of August brings the harbor music festival, a two-day food-and-beverage summit at the flagship and every room on the coast in demand. This is that week, told chapter by chapter, with each gap set against how the products are designed to close it.
Monday, 10:50 pm
The fan coils on the third floor's east wing stop cooling. The night engineer logs it and tells the desk, but the rooms are still open in the booking calendar and two sell before midnight. At 1:15 am Ines gets the call: a family has been walked to Quaymark Lofts in a taxi the group is paying for. By morning, engineering, housekeeping and revenue each hold a different list of which rooms are out.
How this is solved: Out-of-order rooms that are still on saleTuesday, 5:15 am
Two guides text in sick. The 9:00 heritage walk has fourteen guests who booked it in Portuguese, and the 7:30 kayak loop needs a lead with a current water-rescue certificate. Kwame, the excursions lead, works through a group chat and a certificate spreadsheet, reaches Rafael, who speaks Portuguese, and learns at 8:40 that Rafael's guiding license lapsed in March. The walk leaves late, in English.
How this is solved: Guide rosters that match languages and certificatesWednesday, 2:00 pm
The summit's block at Harborlight House is eighty rooms; fifty-two are picked up and cutoff passed a week ago. Farah, the director of sales, has a registration export, three versions of a rooming list and a revenue manager asking whether to release rooms before the festival weekend sells out. Thirty-one delegates who asked for accommodation have no room booked, and nobody can say which of them still need one.
How this is solved: Room blocks for conferences and festival weekendsThursday, 11:30 pm
Wei, the night auditor, is alone at the Harborlight desk with a WhatsApp inbox that fills faster than he can answer: late check-in, parking, festival shuttle times, the pool. At 2:10 am a guest asks whether breakfast can be made without tree nuts; another says room 305 is warm again. Wei sees both at 5:50 am, between the night audit and the first checkouts.
How this is solved: Guest messages that pile up after midnightFriday, 8:00 am
The regional call opens with six spreadsheets in six layouts. Millrace Inn's RevPAR is down against the same week last year, and its general manager, Daniel, cannot yet say whether it is rate, the two rooms out of order or a wedding party that shrank. The call ends with an action to dig into it by Tuesday.
How this is solved: A portfolio view before the weekly regional callFriday, 4:30 pm
A corporate travel buyer's questionnaire arrives: carbon and water per occupied room-night for each property, method explained, due in ten days. The utility invoices sit with finance, water readings in the engineering logbook, room-nights in the property systems, and Pierline Hotel's gas bills for April and May are missing. Ines forwards it to three people and knows the answer will be an estimate.
How this is solved: Carbon and water per room-night for corporate RFPsNone of these moments is unusual; together they make an ordinary peak week. The design intent is that each becomes a hand-off between products instead of a phone call: a work order that takes a room off sale, a booking headcount that becomes a roster, a registration list that informs a release, a guest question answered from approved content, a nightly dataset that becomes the next regional call's console, and a meter reading that becomes an RFP answer.
Challenges and how they are solved
Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.
Challenge 1 of 6
At 10:50 pm the fan coils serving the third floor's east wing stop cooling. The night engineer writes it in the logbook and tells the front desk, but the rooms are still open in the booking calendar, and two sell to late bookers before midnight. A family arrives to a room that will not cool, and the night manager walks them to a sister property at the group's expense. Next morning the chief engineer's parts list, housekeeping's list of rooms to skip and the revenue manager's inventory are three versions of the truth, and nobody is sure which rooms are safe to reopen.
Walked guests, comped nights and poor reviews for a fault engineering already knew about, while repaired rooms sit unsold because nobody released them.
AssetHandler is designed to hold every guest room and its equipment (fan coil, shower valve, door lock) as assets. When engineering raises a work order against a room's equipment and marks the room out of order, AssetHandler is designed to call a FluidGrids webhook trigger with the room, the dates and the expected return. The workflow pushes the status to the property's PMS or channel manager where one is connected and reduces that room type's inventory on GGNomad for those nights. Housekeeping and the front desk are designed to see the same status on the out-of-order board. When the technician completes the work order and housekeeping passes the inspection, FluidGrids is designed to restore the inventory on GGNomad and the connected systems. The fault, the work order, the inventory change and the release sit in one audit trail.
Rooms leave sale on every connected channel when engineering takes them out and return when they are signed off, so the hotel stops selling rooms it cannot deliver.
AssetHandler
One board per property showing every out-of-order and out-of-service room, its linked work order, its expected return and whether its room type's inventory has been reduced for sale.
Works with GGNomad, FluidGrids
AssetHandler
Engineering's single work-order queue, where each room fault is raised, assigned to a technician and completed before the room can return to sale.
GGNomad
The property's booking queue on GGNomad, whose availability calendar is where out-of-order nights are designed to be closed.
Challenge 2 of 6
At 5:15 am two guides text in sick. The 9:00 heritage walk has fourteen guests who asked for a Portuguese-speaking guide, and the 7:30 kayak loop needs a lead with a current water-rescue certificate. The excursions lead scrolls a group chat and a spreadsheet of who holds what, calls the one Portuguese speaker he remembers, and only later learns that guide's license lapsed in the spring. Headcounts live in the booking system, certificates in a shared drive and hours in a timesheet, so the roster is rebuilt by hand every morning of peak season.
Departures run short-staffed or with a guide who should not lead them, overtime creeps up, and guests who booked a language get a different one.
GGNomad holds the bookings for every tour and activity departure, and each booking is designed to carry the date, party size and requested language. FluidGrids is designed to carry each morning's departures from GGNomad to CrewFoundry, which is designed to match each one against its skills graph (languages, licensed guiding, water rescue, first aid) and against availability and hours already worked, and to propose cover for any gap with the evidence behind it. The excursions lead approves before anything changes, and the published roster is designed to reach each guide's phone with the guest list and meeting point from GGNomad. When a departure's guide or language changes, a Botlit agent can let the booked guests know before they arrive. Certificates nearing expiry are flagged before the season rather than on the morning.
Each departure has a guide who speaks the language and holds current certificates, and a sick call becomes a quick reassignment instead of a morning of calls.
CrewFoundry
A roster of today's departures with guest counts from bookings, required languages and certificates, the assigned guide and suggested cover for every gap.
Works with GGNomad, FluidGrids, Botlit
CrewFoundry
The shared skills list, shown here holding field certifications for other trades, would hold guide languages, water rescue and first aid in the same way, with who holds each and at what level.
GGNomad
The tours and activities travelers book on GGNomad; each booking is designed to carry the date, party size and a requested language that the roster works from.
Challenge 3 of 6
A food-and-beverage summit at the flagship holds a block of eighty rooms. Cutoff passed a week ago and fifty-two rooms are picked up. The director of sales has a registration export, a rooming list that has arrived by email in three versions, and a revenue manager asking whether to release rooms before the festival weekend sells out across the coast. Thirty-one delegates who asked for accommodation when they registered have not booked a room; some will book late, some are staying with friends, and nobody can tell which from a spreadsheet.
Release too early and delegates find no rooms; release too late and high-demand nights sell at the last minute for less, while attrition terms get argued from memory.
EventfullyManaged carries the event's registrations, including who asked for a room, whether the hotel's events team runs the event or a partner organizer shares access. That list is designed to flow to a GGNomad room block, where FluidGrids brings in pickup from the property systems alongside GGNomad bookings, so each delegate who requested a room is matched to a reservation or flagged. The tracker is designed to follow pickup night by night against the block, the cutoff and the attrition line. Past cutoff, the hotel can return unpicked rooms to general inventory; the tracker shows which held nights are still worth a courtesy hold and how resold room-nights would offset the group's attrition, and proposes a release, such as fourteen rooms on Friday and Saturday. Sales approves or extends the hold, and EventfullyManaged can remind delegates first.
Sales and revenue decide on releases from one shared pickup picture, and delegates get a reminder before rooms go back on general sale.
GGNomad
Group room blocks tracked night by night against cutoff and attrition, matched to event registrations, with a release or courtesy-hold proposal a person approves.
Works with EventfullyManaged, FluidGrids
EventfullyManaged
The event's registrations and attendee list, which the room block is reconciled against so sales can see who requested a room but has not booked one.
Challenge 4 of 6
Between 11 pm and 6 am the night auditor, alone at the desk, receives dozens of WhatsApp messages: can we check in after midnight, where do we park, what time is the festival shuttle, is the pool heated. Buried among them is a guest asking whether breakfast can be made without tree nuts, and another saying their room is too warm again. The routine questions get slow answers, the two that matter are read at dawn, and the day team inherits a backlog with no record of what was promised to whom.
Slow replies before arrival, sensitive requests missed overnight, and a front desk that spends its night on questions the arrival guide already answers.
A Botlit agent is designed to sit on each property's WhatsApp and web chat channels and answer from that property's own knowledge base (arrival guide, parking, shuttle times, house policies), showing the passages it used and saying plainly when nothing matches. It is designed to read the guest's GGNomad booking and trip timeline for context such as arrival date and room type. Anything the knowledge base does not cover, and anything involving allergies, health, refunds or complaints, is designed to go to a named staff role rather than be answered. A room-comfort complaint can trigger a FluidGrids workflow, designed to open an AssetHandler work order for engineering. Every thread lands in the shared conversations inbox for the morning handover.
Routine questions get answers in minutes from approved content, and the few that need a person reach one with the booking attached.
Botlit
A per-property guest inbox where an agent answers routine questions with booking context and routes allergies, complaints and refunds to the right staff role.
Works with GGNomad, FluidGrids, AssetHandler
Botlit
Answers are designed to come only from the property's own approved content, show the passages used, and admit when nothing matches instead of guessing.
GGNomad
The guest's trip timeline and reminders, which answer many questions before they are asked and give the agent each booking's context.
Challenge 5 of 6
Every week, before the regional call, six general managers send their numbers (occupancy, average daily rate, RevPAR, out-of-order room-nights, labor hours), each in a slightly different spreadsheet exported from a different property system. The call spends its first half hour reconciling. When one inn's RevPAR slips against last year, nobody can say whether it is rate, rooms out of order or a wedding group that shrank until someone digs through exports later in the week.
Decisions wait on reconciliation, problems surface a week late, and general managers spend the morning before the call formatting instead of running their hotels.
FluidGrids workflows are designed to pull each night's occupancy and rate from the property systems and GGNomad, out-of-order room-nights from AssetHandler, and labor hours from CrewFoundry timesheets or the property's own timekeeping, and post them to keyed BigConsole datasinks. BigConsole renders a portfolio console with a property leaderboard and heatmap, designed for row-level security so each general manager sees their own hotel while the operations lead sees all six, and for threshold alerts when a figure crosses a line. A Botlit agent can query the console, so a regional director can ask why a number moved and get an answer that cites the console's figures.
The regional call starts from the same numbers, and a slipping property is visible the next morning with its out-of-order and group data alongside.
FluidGrids
Nightly workflows that gather each property's occupancy, rate, out-of-order and labor figures and post them to keyed datasinks that BigConsole reads.
BigConsole
The multi-location console pattern shown here for restaurants, applied to hotels: a property leaderboard and heatmap, designed so each GM is scoped to their own rows.
AssetHandler
The out-of-order board whose room-nights lost per property feed the nightly dataset, so a slipping RevPAR can be read against rooms that could not be sold.
Works with GGNomad, FluidGrids
Challenge 6 of 6
It is corporate RFP season, and a travel buyer's questionnaire asks each property for carbon and water per occupied room-night, with the method explained, due in ten days. Electricity and gas figures sit in utility invoices in the finance inbox, water readings in the chief engineer's logbook, occupied room-nights in the property systems, and one hotel's gas bills for two months are missing altogether. The commercial lead ends up estimating, and knows it, while engineering never learns which equipment drives the number.
Estimated answers weaken bids with buyers who ask for sustainability data, and the equipment behind the footprint goes unexamined.
EcoImpactHub is designed to hold each hotel as a site in its carbon ledger, with electricity, gas, fuel and water recorded against emission factors and verified line by line. FluidGrids is designed to import occupied room-nights per property from the property systems and GGNomad, so EcoImpactHub can express the footprint per occupied room-night, with meeting and event space separated out first, and flag gaps such as missing bills instead of filling them. AssetHandler reads the same EcoImpactHub metrics, so the chief engineer sees energy against the chillers, laundry dryers and pool equipment that use it and can plan work orders where they matter. The commercial lead exports RFP answers from verified lines, with the gaps shown.
RFP answers come from recorded, verified lines with the gaps visible, and engineering knows which equipment to work on next.
EcoImpactHub
Carbon and water per occupied room-night for each property, built from ledger lines with verification status, missing data flagged and an export for RFP answers.
Works with AssetHandler, FluidGrids, GGNomad
AssetHandler
Energy, water and carbon shown against the equipment that uses it, read from EcoImpactHub metrics, so engineering can see which assets drive the footprint.
How it fits together
Each step is one product doing one job and passing a specific record to the next: a departure list, a roster, room-nights, energy metrics, an out-of-order status, a nightly dataset. FluidGrids appears twice because it carries records between the others. The hand-offs describe how the products are designed to work together.
To CrewFoundry: Coming departures with headcount, party size and requested language, carried to CrewFoundry by a FluidGrids workflow
To FluidGrids: Published roster and labor hours per property
To EcoImpactHub: Occupied room-nights per property for the footprint calculation
To AssetHandler: Energy and carbon metrics that AssetHandler reads against each piece of equipment
To FluidGrids: Out-of-order status sent to a FluidGrids webhook with room number and expected return time
To BigConsole: Keyed nightly datasets per property
To Botlit: Console figures an agent can query and cite
Step 1 of 8: Bookings and departures
Products in this solution
Bookings and availability, with proposed room blocks
Built for hosts, hotel operators and tour operators on one booking spine for stays, tours and event tickets, with listings, bookings and host analytics, and an availability calendar with blackout dates on its roadmap.
Rooms, equipment and work orders
Designed to hold rooms and their equipment as assets across sites, with preventive schedules, one work-order queue and sustainability metrics read from EcoImpactHub.
Guide and crew rosters
A people platform for frontline and field teams, hospitality included, with skills attached to each person and time entries with overtime, and a skills graph and field-crew rosters in development.
Event registrations
Runs registrations with configurable forms, ticket types, agendas and meeting-room capacity for conferences and festivals, giving a room block a live delegate list to reconcile against.
Guest messaging agent
Channel connectors for messaging apps such as WhatsApp and for web chat, a shared conversations inbox, and agents designed to answer from your own knowledge bases with cited sources, content policies and routing between agents.
Automation between products
Visual workflows started by webhooks, schedules or API calls, with connectors and datasinks, designed to carry status changes between products and to feed nightly datasets into BigConsole.
Portfolio console
Governed multi-location consoles fed by FluidGrids datasinks and queryable by Botlit agents, designed for row-level security so each manager sees their own property, and for threshold alerts.
Footprint per room-night
A carbon ledger across Scopes 1 to 3 with emission factors, a draft-to-verified status on every line and site-level breakdowns that suit per-property hotel reporting.
All eight products run on Burdenoff Workspaces: one sign-in for managers, engineers, guides and sales, role-based access that scopes each person to their property, one audit trail across bookings, work orders and rosters, and one bill.
Concept gallery
15 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.
AssetHandler
One board per property showing every out-of-order and out-of-service room, its linked work order, its expected return and whether its room type's inventory has been reduced for sale.
Works with GGNomad, FluidGrids
AssetHandler
Engineering's single work-order queue, where each room fault is raised, assigned to a technician and completed before the room can return to sale.
GGNomad
The property's booking queue on GGNomad, whose availability calendar is where out-of-order nights are designed to be closed.
CrewFoundry
A roster of today's departures with guest counts from bookings, required languages and certificates, the assigned guide and suggested cover for every gap.
Works with GGNomad, FluidGrids, Botlit
CrewFoundry
The shared skills list, shown here holding field certifications for other trades, would hold guide languages, water rescue and first aid in the same way, with who holds each and at what level.
GGNomad
The tours and activities travelers book on GGNomad; each booking is designed to carry the date, party size and a requested language that the roster works from.
GGNomad
Group room blocks tracked night by night against cutoff and attrition, matched to event registrations, with a release or courtesy-hold proposal a person approves.
Works with EventfullyManaged, FluidGrids
EventfullyManaged
The event's registrations and attendee list, which the room block is reconciled against so sales can see who requested a room but has not booked one.
Botlit
A per-property guest inbox where an agent answers routine questions with booking context and routes allergies, complaints and refunds to the right staff role.
Works with GGNomad, FluidGrids, AssetHandler
Botlit
Answers are designed to come only from the property's own approved content, show the passages used, and admit when nothing matches instead of guessing.
GGNomad
The guest's trip timeline and reminders, which answer many questions before they are asked and give the agent each booking's context.
FluidGrids
Nightly workflows that gather each property's occupancy, rate, out-of-order and labor figures and post them to keyed datasinks that BigConsole reads.
BigConsole
The multi-location console pattern shown here for restaurants, applied to hotels: a property leaderboard and heatmap, designed so each GM is scoped to their own rows.
EcoImpactHub
Carbon and water per occupied room-night for each property, built from ledger lines with verification status, missing data flagged and an export for RFP answers.
Works with AssetHandler, FluidGrids, GGNomad
AssetHandler
Energy, water and carbon shown against the equipment that uses it, read from EcoImpactHub metrics, so engineering can see which assets drive the footprint.
Pitch kit
Burdenoff brings the tools a hotel group or tour operator juggles onto one platform and designs them to hand off to each other: GGNomad for bookings and availability, AssetHandler for rooms and work orders, CrewFoundry for guide rosters, EventfullyManaged for events, Botlit for guest messages, FluidGrids and BigConsole for the portfolio view, and EcoImpactHub for per-stay footprints. It is a pre-launch solution concept we want to shape with operators.
Questions
No. The concept assumes you keep the property management system and channel manager that run your front desk and distribution. FluidGrids is designed to connect to them through connectors and webhooks, pulling nightly figures and pushing status changes such as out-of-order rooms, while GGNomad sells alongside them and the other products cover the gaps between systems. GGNomad's own channel-manager connectivity is on its roadmap; which of your systems can be connected, and how, is something we would work through with you.
Burdenoff products are pre-launch and in active development. This page describes a solution concept: how the products are designed to work together for hotels and tour operators. Some surfaces shown, such as the room-block tracker and the departure roster, are new concepts we are proposing rather than shipped features. We are looking for operators who want to shape them with us.
No. The products are designed to scale from a single guesthouse or guide to a multi-property group. A small operator might start with GGNomad for bookings and availability and Botlit for guest messages, then add AssetHandler or CrewFoundry as the team grows.
Botlit agents are designed to answer only from knowledge bases you approve, such as your arrival guide and house policies, to show the passages they used, and to say plainly when nothing matches. You decide which topics always go to staff, such as allergies, health, refunds and complaints, and content policies are designed to block requests you do not want handled. Staff can read every conversation in the shared inbox.
Access is role-based and inherited from Burdenoff Workspaces. BigConsole consoles are designed to support row-level security, so a general manager can be scoped to their own hotel while the operations lead sees the portfolio, and changes to bookings, work orders and rosters are recorded in one audit trail.
EcoImpactHub is designed to calculate footprints from the activity data you record and the emission factors you choose, verified line by line, and to show missing data rather than fill it. How you present those figures to buyers, and which methodology you follow, remains your decision; the product does not certify any claim on your behalf.
Related domains
Consumer & LifestyleChallenges solved
How eight Burdenoff products are designed to work together for conference organizers, festival producers and meetup hosts, from ticket pacing to sponsor renewals.
Finance & BusinessChallenges solved
A solution concept for HR, staffing and workforce planning: skills-based hiring, bench redeployment, mandatory training, aggregate workload signals and one governed workforce plan.
Finance & BusinessChallenges solved
A solution concept for property businesses that connects listings, leases, maintenance, permits and portfolio yield across eight Burdenoff products on one shared record.
Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.
This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.
