The problem
The work is real. The system is held together by one person.
An inquiry arrives by email. Someone keys it into a spreadsheet, builds a proposal in a word processor, guesses at a price, checks a wall calendar for the room, and tracks the deposit somewhere else. Every step is manual, and every step lives in a different place.
When that person leaves, the system leaves with them. The institution loses not a file but the working knowledge of how the work actually gets done. Fanfare turns that knowledge into infrastructure that outlasts any one employee.
The pipeline
One system, from first contact to closed revenue.
Every request moves through the same four stages. Fanfare runs all of them in one place, so nothing is rekeyed, nothing is lost between tools, and the whole pipeline is visible at a glance. And it does not stop at billed.
Inquiry
An interested group enters a structured request: dates, headcount, spaces, food and drink, housing. The inbox and the spreadsheet are gone.
Proposal
The request becomes a branded proposal in minutes, in your institution's identity, built the same way every time by every coordinator.
Booking
Spaces, dates, and closures resolve on a real calendar. The hold becomes a confirmed, priced booking against your actual rate card.
Billing
The booking carries through to an invoice and a paid deposit. Revenue is tracked where the request lives, not in a second system.
After the event
The line becomes a loop.
An invoice is where most tools end. It is where the value of Fanfare begins. The event happens, and the same system turns a satisfied client into next year's booking, on its own, before the memory fades.
Recap
A branded recap of their event, theirs to keep and to share.
Survey
Five questions. The 4.5-of-5 becomes a testimonial you can quote.
Photos & social
Event photos and ready-to-post graphics, co-branded so the client posts and tags you.
Check-ins
Thirty and ninety-day touches, drafted and sent on cue, never forgotten.
Rebooked
One tap opens next year's request. The loop turns, and the desk fills itself.
The strongest lead your team has next year is the client you already made happy this year. Fanfare is the only part of the stack that acts on it.
What it runs
Everything a request needs, built in.
Branded proposals
Every inquiry becomes a proposal in your institution's brand, generated in minutes rather than rebuilt by hand for each client.
Contract-derived pricing
Rates, taxes, parking, and fees computed from your real rate card, so a quote is right the first time and consistent across every coordinator.
RFP responses that win
When a group puts its event out to bid, Fanfare reads the RFP and drafts your response, so you compete for the business worth winning, not only field what arrives on its own.
Scheduling and billing
Spaces, dates, and closures in a true calendar, and invoices that follow the booking through to paid. One arc, one place.
The crew who run the day
Setup and teardown checklists, photo shot lists, and timed reminders reach the students and staff on the floor, so the plan on paper becomes the room your client walks into.
Summer residential conferences
Events and beds in one place, for the summer conference programs that other tools handle badly, expensively, or not at all.
Proof
Running today in a real conference services office.
Fanfare is not a concept. The full loop, from inquiry to invoice to the rebook after, is in daily use managing real events, real pricing, real revenue, and real clients coming back. That working installation is the proof, and it is the reference behind every walkthrough.
Why it lasts
An institution should not depend on one person to run its operations.
Fanfare is owned and operated by Sonate, hosted on Sonate infrastructure, and documented so any coordinator can run it. Your department keeps a named administrator and a defined fallback. The system, and the knowledge inside it, stay with the institution regardless of who holds the role.