Three tools, on the three decisions that cost a venue money: capture the inquiry without retyping it, work the right one first, and know the margin before the discount is offered.
79% of event RFPs are won by one of the first three responders. Source: Cvent
An RFP arrives as an email. Somewhere in it are the dates, the delegate numbers, the space requirement, the catering, the budget and the deadline. Today someone reads it, works out what it is asking for, and retypes it into the system. Then the team works whatever is at the top of the inbox, and quotes a discount without knowing what it does to the margin.
Three tools, in the order the work happens: Copilot turns the email into a structured inquiry. Lead scoring decides which one to work first. Cost Analyzer shows what the deal is worth before it is offered. All three run on the same records as everything else.
For the wider picture of how Thynk thinks about AI in venue businesses, see Thynk AI. This page is about what the product does today.
AI driven email to structured inquiry and booking, in the language the client wrote in, checked before it reaches your pipeline.
Inbound email · structured inquiry · routed to the right owner
Copilot reads the inbound email and extracts what a coordinator would extract: client and contact, dates and flexibility, delegate numbers, the spaces or setup implied, catering, AV, budget signals and the response deadline. It creates the inquiry against the right account, deduplicated against what you already hold on that client. Where the request is simple and the rules allow it, it can go further and draft the booking.
The typing is already done when your team opens their laptops. It works overnight and at weekends, which is when a good share of RFPs are actually sent.
An inquiry written in German is read in German, and so is one in Dutch, French, Italian or Spanish. Dates written the local way, setups named the local way, and the difference between a firm request and a polite question about availability. For a venue in the DACH or Benelux markets this is usually the whole decision.
Nothing reaches your pipeline unchecked. Required fields present, dates plausible, the account matched rather than duplicated, and anything the AI was unsure about flagged for a person. Your team sets what passes straight through.
Every inquiry scored, the day’s priorities in a morning brief, and a reason attached to every score.
Morning brief · scored inquiries · the reason behind every score
Forty inquiries arrive over a weekend. Worked top-of-inbox first, the one that matters, a 500-delegate congress from a client who booked with you last year, gets answered on Wednesday.
Lead scoring ranks every inquiry from 1 to 5. It weighs several things at once rather than one: how real the request looks, how well it fits the venue and the calendar, what it is worth, and what your history with that client says. It learns from what actually converted, so the scoring gets closer to your business the longer it runs.
The score is not a black box. Open it and you see the signals behind it in plain language, which is what makes a sales team willing to trust the order of their day. A morning brief opens with the priorities, each with a line explaining why and a recommended action, plus what changed since yesterday and which high-value inquiries are going stale.
People stay in charge. Bulk conversion exists for the inquiries whose decision is already on the record, but it checks eligibility and waits for a human to confirm. Duplicate detection flags the same piece of business arriving three ways and shows what it is double-counting in the pipeline, and a person resolves it. Routing, ownership and the pipeline itself live in CRM & Sales.
A live event-level P&L, and a scenario modeler that lets sales test a decision before making it.
Event P&L by service line · scenario sliders · staffing planner
Two events with the same revenue can have very different margins. Without cost sitting next to revenue, a venue optimizes for the wrong thing: it chases the events that look biggest rather than the ones that pay.
Cost Analyzer turns the booking into a live event-level P&L: revenue and margin by service line, cost of goods, venue commissions and allocated overhead, down to net event profit. It reads the booking rather than a spreadsheet somebody maintains, so the number is current while the event is still being sold.
The scenario modeler is the part a seller uses. Move the slider and see what an 8% discount does to the margin before it is offered, not at close-out six weeks later. A staffing planner does the same for labor: change the shape of the team and watch the cost line move.
This page is about having the number at the moment the decision is made. Forecast against actuals, how cost reaches the invoice, and profitability after the event live in Event Financials.
A German association emails on Thursday evening: a two-day annual meeting for around 400 people next October, plenary plus six breakouts, dinner on the first night, three date options, responses by the following Wednesday. Nobody is at a desk. It becomes a structured inquiry anyway, in German, with the three date options in the right fields and one thing flagged because the dinner headcount was ambiguous.
By Monday it is one of forty. It is also the one at the top of the morning brief, ahead of the thirty-nine that arrived after it, because the association booked with you two years ago and those dates are soft in the calendar. The brief says why in a line.
The seller checks the flag, confirms availability and builds the quote. The client asks for 8% off. Before answering, the seller moves the slider: margin falls from 31% to 26%, and the staffing plan is where the difference actually lands. They offer 5% and hold the catering package, and the event is still worth taking.
Response sent before lunch on Monday. Not because anyone worked the weekend, but because the typing, the sorting and the arithmetic were already done.
The wider position: institutional AI, what it needs from your data, and where venues should expect it to go.
Read more →Where the scored inquiry lands: routing, ownership, the pipeline and the account behind it.
Read more →Where cost meets delivery: forecast against actuals, actualized charges and the invoice.
Read more →Dashboards, pace, utilization and profitability across every event, not one at a time.
Read more →What response time, priority order and a defensible discount look like day to day.
Read more →The governance underneath: who can approve what the automation produced, and what is recorded.
Read more →A 45-minute call with the team. Bring a handful of real inbound emails, in whatever language they arrived in, and the last event where the discount turned out to cost more than anyone expected.
Operate hotels too? See the Thynk hotels platform →
