The date is the thing you sell, and you hold only one of each.

How the work runs

The path this business already walks.

Written for Barns, halls, estates, restaurants with a private room and small hotels that let their space for weddings, parties and company events, run by a small office and a duty manager on the night.

Steps marked for approval wait for a person. Andiamo SMB is not yet offered to customers; the parts each step leans on, and how far along they are, are listed further down.

1. Availability

   The answer that matters is whether the date is free

   An enquiry is a date before it is anything else, and the reply either offers that date or offers the ones around it. Holding the date asked for, who is asking and what they are planning on a record from the first message keeps the answer out of a mailbox thread that only one person can search. The reply itself is drafted for you and waits until you have read the exact wording. The diary that decides the answer is still yours: bookings here hang off the hours a team member publishes rather than off a room, so the master calendar for the building sits outside the workspace.

   Human approval
2. Show round

   People decide on a building by standing in it, usually at a weekend

   A viewing is a request for a time against whoever is hosting it, taken from the hours that person publishes, and it lands on the record that already holds the date being asked about. Whether they turn up is settled over text: they can confirm or move it by replying to one, and the booking updates from that reply. Automatic replies stay switched off. Keeping those slots in step with the team's calendar is designed and not built, so a show round booked here still has to be read across to whatever the duty team works from.

3. Hold

   A date becomes a booking when the deposit lands and the terms are agreed

   Until money changes hands a held date is a courtesy, and the cost of getting that wrong is a date sold twice with no way back. What turns it is a priced offer the booker can read and choose from, a deposit against that offer, and terms they have signed: the hire period, what the fee covers, cancellation, damage. Proposals with options sit in the portal and wait for a person to approve the wording; delivery is still being built. Sending terms for signature is designed and not built, so that step happens off to the side today. Once the deposit clears, the event can become a card the duty team can see, carrying a starter checklist.

   Human approval
4. Quiet months

   Most of a booking's life is silence you are carrying a liability through

   Between the deposit and the month of the event the building hears nothing, and the work in that gap is small enough to drop: the balance date, the supplier insurance, the tasting, the point at which somebody should ask whether the plan has changed. Follow-up drafts are prepared and queued for a person to approve or reject, and sending the approved ones is not built yet. Tasks with an owner and a due date on the booking itself are designed and not built, and so are prepared balance reminders for a person to release.

   Human approval
5. Final details

   The numbers arrive late and move the bill with them

   A month or so out the booking stops being a date and becomes a plan: the head count, the table layout, the ceremony and service timings, the menu and the dietary requirements, which drinks sit on the tab and which are paid for at the bar. Almost all of it arrives later than you asked and most of it changes what is owed. Collecting it as forms the booker fills in through the portal keeps the answers attached to the booking rather than buried in a chain of replies. Recording each change with the price adjustment it triggers, held for approval, is designed and not built, and so is one record per event that every task, document and message links to.

   Human approval
6. Access

   The people you have to schedule are not the people you employ

   The florist wants the room the evening before, the band needs the doors open at a set hour, the caterer wants the kitchen from the morning, and the building has to be clear by the time written into your terms. None of them work for you and all of them are bound by your windows. From one description of the day the workspace derives a logistics view of setup, the service blocks and breakdown, and alongside it an experience view for the people whose day it is. That generator is exercised in tests; saving the schedules for a business is switched off by default and sending them out is not built, so today it produces something you read and pass on yourself. Assigning your own duty team to an event by role, with their availability visible, is designed and not built.

7. Close out

   What actually happened decides the closing bill

   The final bill is rarely the quoted one: the bar ran on, a room was held past the hire period, fewer people came than were catered for, something was damaged. The duty manager knows all of it and is the least likely person to sit down and write it up. A spoken handover becomes proposed changes to the record that wait for someone to apply or reject them, and the review screen for those is not built yet. The closing invoice is raised against the same booking, and the booker can pay it by card or see their payment history by signing in with an emailed link. Connecting a payment account and emailing invoices are still being built.

   Human approval