Concept case studyHospitality · Events & venues
From hand-built quotes to a reliable enquiry-to-event workflow.
How NairobiX would automate the repetitive steps between an event enquiry and a delivered event — holds, quotes, deposits, confirmations and briefings — while leaving the judgment with the events team.
Concept engagement — illustrative scenario, not historical client results.
Quote
Quote · Two-day leadership workshop
- Conference package · 40 guests × 2 days
- Full day
- Breakout rooms
- 2
- AV & projection
- Included
- Provisional hold
- Expires Fri 17:00
Reviewed by coordinator · ready to send
Hold expires in 48 hours
Workshop · 12–13 March · Owner: Amina K.
No response to the quote sent 3 working days ago. Decide: extend the hold, follow up, or release the dates.
- Industry
- Hospitality · Events & venues
- Focus
- Workflow automation
- Reading time
- 9 min
02The context
A business that works — up to a point.
Consider a hotel on the edge of Nairobi with conference rooms, a garden venue and a restaurant. Events — corporate meetings and workshops, weddings, private functions — are a significant part of its business, handled by a small events team.
Enquiries arrive by email, phone, WhatsApp and a website form, often with incomplete details. Each becomes a conversation about dates, numbers and packages, then a quote built from a spreadsheet template, then follow-up, a deposit, a function sheet for the kitchen and operations, and a final invoice that reflects what changed on the day.
The team is good at events. What wears it down is that every event repeats the same administrative pattern — and every step of it is done by hand.
What already works
- A venue people like to use
- Packages that sell
- A team that delivers events well
- Returning corporate clients
What the team manages by hand
- Building each quote from a spreadsheet template
- Checking room availability across several calendars
- Chasing quotes and deposits
- Typing function sheets and briefing the kitchen, AV and housekeeping
- Reconciling the final invoice against changes on the day
03The problem
Not a lead problem. A system problem.
This is not a demand problem. It is an operations problem that shows up as slow quotes, lost bookings and tired people — and it follows exactly the kind of repeatable pattern a system can carry.
Capture
Enquiries arrive through four channels, usually without dates, numbers or event type.
Days are lost gathering the basics before a quote can even start.
Availability
Function-room availability is spread across several calendars.
Slow answers, and the risk of double holds.
Quoting
Each quote is rebuilt by hand from a template.
Quotes are slow and inconsistent, and pricing errors creep in.
Follow-up
Quotes and deposits are chased when someone has time.
Provisional holds block dates for weeks without a decision.
Coordination
Function sheets are typed and emailed; changes travel by phone.
The kitchen and operations may be working from outdated details.
Reporting
There is no record of enquiry-to-booking conversion or why events are lost.
The hotel cannot see which event types and sources are worth pursuing.
Recognise some of this in your own business?
04The opportunity
The opportunity is to standardise the pattern every event follows, automate the steps that are pure routine, and give the team its time back for clients and for the events themselves.
Before anything is automated, the process has to be written down: the stages every event passes through, the information needed at each, and the decisions only a person should make. Most of the value of this engagement comes from that step — automation is how the agreed process then runs reliably.
The order of work follows the pain: structured enquiries and availability first, then quotes and holds, then coordination and reporting.
01
Attention
02
Capture (focus of this engagement)
03
Qualify (focus of this engagement)
04
Nurture
05
Convert (focus of this engagement)
06
Deliver (focus of this engagement)
07
Retain
08
Measure (focus of this engagement)
Where this engagement concentrates first, within the NairobiX growth system.
05The system design
The architecture, layer by layer.
The proposed architecture has eight layers. Several of them are simply the team's existing process, made explicit and connected. Select a layer to explore it.
- Why it exists
- A complete enquiry can be answered the same day; an incomplete one starts a week of back-and-forth.
- What moves through it
- Event type, dates, guests, budget range and contact.
- What happens next
- The enquiry becomes an event opportunity in the CRM.
- Why it exists
- One place for every event and every returning client, instead of inboxes and spreadsheets.
- What moves through it
- Event details, client, owner and stage.
- What happens next
- Availability is checked for the requested dates.
- Why it exists
- Holds that expire deliberately release dates for other clients instead of blocking them indefinitely.
- What moves through it
- Room, dates, hold status and expiry.
- What happens next
- A quote is prepared from the chosen package.
- Why it exists
- Consistent, correct quotes in minutes — with a person checking every one.
- What moves through it
- Package, quantities, price and terms.
- What happens next
- The quote is sent and follow-up is scheduled.
- Why it exists
- A clear, prompt confirmation turns a provisional booking into a committed one.
- What moves through it
- Deposit status and confirmed details.
- What happens next
- Event coordination begins.
- Why it exists
- Every department works from the same, current details.
- What moves through it
- Menus, set-up, timings, final numbers and changes.
- What happens next
- The event is delivered; changes on the day are recorded.
- Why it exists
- The end of one event is the best moment to secure the next.
- What moves through it
- Final charges, feedback and rebooking interest.
- What happens next
- Outcomes flow into reporting.
- Why it exists
- It shows which events are worth pursuing, and where the process slows down.
- What moves through it
- Everything above, summarised.
- What happens next
- Packages, pricing and marketing are adjusted on evidence.
Layer 01 of 08
Structured enquiry
An enquiry form and WhatsApp flow that ask for date, event type, guest numbers and rough budget up front.
- Why it exists
- A complete enquiry can be answered the same day; an incomplete one starts a week of back-and-forth.
- What moves through it
- Event type, dates, guests, budget range and contact.
- What happens next
- The enquiry becomes an event opportunity in the CRM.
Every business needs a different version of this architecture.
06Before / after
From a disconnected pattern to a connected one.
The same people and much of the same technology — organised as one system instead of several.
Before · current operating pattern
- Email inbox
- Phone notes
- Spreadsheet quote templates
- Function sheets typed and emailed
- Several room calendars
The same pattern, rebuilt by hand for every event.
After · designed future-state system
- 01Structured enquiry
- 02Event CRM
- 03Availability & holds
- 04Quote
- 05Deposit & confirmation
- 06Coordination
- 07Post-event
- 08Reporting
The pattern written down once, then run reliably.
An architectural comparison of operating patterns — not a record of measured results.
07The customer journey
One customer, through the designed system.
What the customer experiences at each step, and what the system does behind it. Names and details are illustrative.
What the customer experiences
What happens in the system
01
Discover
Customer
An HR manager planning a two-day leadership workshop finds the hotel through a colleague and a search.
System
The conference page carries a tagged link and the source is recorded.
02
Enquire
Customer
She completes a short form: dates, 40 guests, workshop, rough budget.
System
A complete enquiry creates an event opportunity with an owner.
03
Hold
Customer
Within working hours she hears that the dates are available and provisionally held until Friday.
System
The function-room calendar shows the hold and its expiry.
Event · Leadership workshopHold- Dates
- 12–13 March
- Guests
- 40
- Room
- Acacia Hall + 2 breakouts
- Hold expires
- Fri 17:00
04
Quote
Customer
The same day, she receives a clear quote built from the conference package.
System
The quote was generated from the enquiry and reviewed by the coordinator before sending.
Quote
Quote · Two-day leadership workshop
- Conference package · 40 guests × 2 days
- Full day
- Breakout rooms
- 2
- AV & projection
- Included
- Deposit to confirm
- On acceptance
Reviewed by coordinator · sent
05
Follow up
Customer
Three days later, a short, personal follow-up from the coordinator.
System
A task was created when the quote went unanswered; the coordinator decided what to say.
Follow up: leadership workshop quote
Due today · Owner: Amina K.
No response in 3 working days. Hold expires Friday. Decide: follow up, extend the hold or release the dates.
06
Confirm
Customer
She accepts, pays the deposit and receives a confirmation with next steps.
System
Deposit recorded; the hold becomes a confirmed booking.
07
Prepare
Customer
A week before, she's asked to confirm final numbers and dietary needs.
System
The function sheet is generated and each department receives its tasks; changes create a new version.
08
Deliver
Customer
The workshop runs. A late change to lunch timing is handled on the spot.
System
The change is recorded, so the final invoice matches what happened.
09
Measure
Customer
Afterwards she receives the final invoice, a feedback request and an offer to plan the next one.
System
Reporting shows time to quote, conversion by event type and why events were lost.
Enquiry → booking by event type · layout
Corporate workshops
Conferences
Weddings
Private functions
Illustrative layout — not data
08The technology layer
Technology, chosen last.
The hotel's property management system stays the source of truth for bedrooms and billing; how far it can be connected depends on the integrations it offers. The events workflow sits alongside it.
Proposed stack · example architecture
Each technology fills a capability the system design called for. Remove the requirement, and the tool goes with it.
CRM & workflows: Zoho CRM
Availability: Google Workspace calendars
Messaging: WhatsApp Business Platform
Web platform: Next.js
- Business requirement
- System design
- Technology
CRM & workflows
Zoho CRM
Event CRM · Follow-up · Reporting
Role
Event opportunities, client organisations, stages and workflow automation.
Why it fits
Stages, rules, tasks and document generation are standard features — no custom software needed for the core workflow.
Availability
Google Workspace calendars
Availability & holds
Role
One shared function-room calendar, including provisional holds.
Why it fits
A single calendar the whole team already knows, readable by the CRM's workflows.
Messaging
WhatsApp Business Platform
Enquiry · Confirmation · Coordination
Role
Enquiries, confirmations and reminders on the channel many clients prefer.
Why it fits
Utility templates for confirmations and reminders; conversations logged against the event.
Web platform
Next.js
Structured enquiry · Quote
Role
The structured enquiry form and a clean, shareable quote page.
Why it fits
Collects complete enquiries and presents quotes clearly on any device.
Illustrative technology choices for this concept scenario. They are not a record of a client implementation, imply no partnership with any vendor, and are not the only suitable stack.
09The automation layer
Rules first. Then workflows. Then automation.
This scenario is where the difference between process, rule, workflow and automation matters most. The process is agreed first; the rules are written down; only then do the workflows run automatically.
- Process
- The sequence of work the business agrees to follow.
- Rule
- A condition written down — “if no reply in three days”.
- Workflow
- A rule connected to the actions it should cause.
- Automation
- The workflow running without anyone starting it.
- Technology
- The tools that carry it out.
Enquiry to provisional hold
- Trigger
An event enquiry is submitted.
- Rule
Date, guest numbers and event type are present; if not, ask for the missing details.
- Action
Check function-room availability; create the event opportunity and a provisional hold with a five-day expiry.
- Notification
Assign a coordinator and notify them.
- Follow-up
Acknowledge the client: dates held, and when to expect a quote.
- Human
The coordinator reviews the request and chooses or adjusts the package.
- Measure
Record time from enquiry to quote.
10Designed outcomes
What the system is designed to improve.
01
Faster, consistent quotes
Package-based quotes prepared in minutes and checked by a person.
02
Fewer pricing errors
Quotes built from standard packages, not retyped templates.
03
Holds that expire deliberately
Dates are released or extended by decision, not by neglect.
04
One current version of the event
Kitchen, AV and housekeeping work from the same function sheet.
05
Less routine administration
Reminders, confirmations and briefings run from the booking.
06
Visibility of what converts
Conversion by event type and source, and reasons events are lost.
07
More repeat corporate business
A prompt to plan the next event at the right moment.
08
A foundation for self-service
Once packages and rules are clear, clients could later check availability online.
Design objectives the system is built around — not measured client results.
11Measurement framework
What we would measure.
No invented numbers — a plan for knowing whether the system is working, set before it is built.
Acquisition
- Enquiries by source and event type
- Where event demand comes from.
- Complete enquiries
- Share arriving with date, numbers and type.
Conversion
- Enquiry → quote
- And time taken.
- Quote → confirmed
- By event type and source.
- Lost reasons
- Price, dates, capacity, no response.
Operations
- Time to quote
- From complete enquiry to quote sent.
- Holds expired without decision
- Should fall towards zero.
- Changes after final sheet
- And whether departments were notified.
Client
- Post-event feedback
- Collected for every event.
- Corporate rebooking
- Clients booking a further event within a year.
System
- Workflow exceptions
- Steps that failed or were overridden.
- Quote corrections
- Generated quotes the coordinator had to change, and why.
12The human layer
Where people stay responsible.
Technology supports people who make decisions.
Hospitality is judgment and warmth. The workflows carry the paperwork; the events team keeps every decision that shapes the client's experience and the hotel's margin.
What the system does
- Automation places holds, sends reminders, generates quotes and function sheets.
- The CRM keeps every event and every returning client in one place.
- Reporting shows which events convert and where the process slows.
What the team decides
- Pricing exceptions and discounts
- Whether to extend a provisional hold for a valued client
- Tailoring a package to an unusual request
- Handling on-the-day changes and complaints
- Building relationships with corporate clients
13What we would build
One system, built in stages.
01
Strategy
Event process mapping, stage design and standard packages.
02
Digital
A structured enquiry experience and clear, shareable quotes.
03
CRM
Event opportunities, client organisations and stages.
04
Automation
Holds, quotes, reminders, deposits, confirmations and function sheets.
05
Analytics
Conversion by event type and source, time to quote and lost reasons.
06
Later phase
AI — later
Drafting function sheets from coordinator notes and summarising client requirements, reviewed before use.
Components of one system, built in stages and connected to each other — not a list of separate services.
In this scenario, the events team doesn't need to work harder. It needs the pattern it repeats every week to be written down once — and then carried by the system.
14 · The next step
Your business probably has a different version of this problem.
Every business has a different starting point. The right system depends on your goals, requirements, customers, processes and existing technology.