Chalmsy for hotels, venues & hospitality
Event spaces, group bookings, standing contracts with the florist and the production company — a venue's paperwork is half sales, half stewardship. Chalmsy quotes the enquiry or the event RFP, takes the signature, raises the invoices and keeps the books, in the house style, without a spreadsheet in sight.
Quoting, the hospitality way
Hospitality quotes differently: an agreed figure per week, per month or per season — negotiated, rounded, and not to be "helpfully" recalculated by software. Chalmsy treats an agreed number as sacred.
| Exclusive use — great barn & courtyard | included |
| Ceremony room & licensing | included |
| Three-course wedding breakfast · 110 | included |
| Evening reception until 1am | included |
Enquiry to settled account
A branded intake form on your own site asks the hospitality questions — date, space, covers, budget — and lands each enquiry on the pipeline with the email thread attached once you connect Google. Or paste the organiser's RFP and send back a costed proposal the same afternoon.
Chalmsy drafts the event proposal or the standing contract from the enquiry, in the tone your best correspondence already set — reviewed and sent by a person, always.
The organiser, their finance team, your banqueting manager — everyone works from the same live proposal through their own private link, and the changes stay on the record.
Weekly hire, monthly maintenance, seasonal contracts — the agreed rate carries onto every invoice, each one sent from your own email address, and the ledger keeps count.
Coordinators see bookings and run-of-day; the money stays with the people who own it. Roles are set per person, not per department seat licence.
Receipts photograph in, the ledger stays categorised, and each trading entity keeps a live P&L of its own — with closed months locked so reported numbers stay reported.
Some of these follow the plan: intake forms join at Studio, bookkeeping at Practice, multi-entity at Atelier — the pricing grid has every line.
Why it's fluent
Chalmsy grew up inside a working floral & events studio whose clients include hotels — which is why it understands the standing contract, the all-in fee and the house that must never see a supplier's software brand on its own paperwork. Your documents wear your identity, not ours.
Hospitality asks
Yes — Chalmsy runs on one. It's how your proposals and invoices go out from your own address rather than a no-reply robot, how your enquiry threads sit beside the booking they belong to, and why there's no Chalmsy password for anyone to steal. A Gmail or Google Workspace address is all it takes. If your business email lives on Microsoft or elsewhere, Chalmsy isn't for you yet — we'd rather say so now than after you've moved.
Yes. Separate trading entities live in one workspace with their own tax treatment, currency and books, kept properly apart on every document a client receives. Multi-entity support is part of the Atelier plan.
No. Hard-input pricing exists for exactly this: the figure you negotiated is the figure on the document, and AI polish can tidy the wording but cannot touch a number.
We answer that honestly: tenant data is isolated at the database level, sign-in is Google-only with no stored passwords, and we're not yet SOC 2 certified — the security page says exactly what's in place and what isn't.
It drafts the event proposal from the enquiry, keeps the client record current from the email thread, reads the receipts your team photographs, and prepares the polite chase when a quote sits unanswered — a person approves every send.
Stay calmsy
Start free, load one enquiry, and see the proposal drafted in the house voice before the site visit is over.
