Run your HoneyBook booking season from one calendar

Build me an app I open to run my booking calendar for the season. I shoot and coordinate events, so the question I ask every single day is which dates I am holding, what they are worth, and which ones are still open. I want that answered on one screen, and I want to be able to book a new date without leaving it.

The main surface is a season calendar: a month by month grid running from the current month forward through the next twelve months, with a month picker or continuous scroll so I can move around. Load every booked project from HoneyBook with List Projects, following next_cursor until there are no pages left, and place each project on its event date. Color code each project by its project type and show the client name and the budget on the day cell. Under each month header, total that month's booked revenue by summing the budgets of the projects whose event date falls inside it, and show the count of booked dates next to it. Call out open weekend dates as gaps: any Saturday or Sunday in the season with no booked project should render as an obvious empty slot with a Book this date action on it, because weekends are the inventory that actually sells.

Overlay my Google Calendar on the same grid. Pull events with Google Calendar List Events for the visible date range, expanding recurring events into individual instances, and render them as a second layer on the day cells so I can see a personal commitment or a second shoot sitting on top of an event date. Let me choose which calendars to overlay using Google Calendar List Calendars, and remember that choice. Keep a warning strip pinned at the top of the page that lists every conflict, meaning any day that has a booked HoneyBook project and also has a Google Calendar event on it that is not the calendar hold this app created for that booking. Each conflict row names the date, the client and project type, and the colliding calendar event with its time, and clicking a row jumps the grid to that day. When nothing collides, the strip says the season is clear.

Every day cell has a Book this date panel that opens in place, for when a client calls to book. It takes the client name and email, the package, and the deposit amount, with the event date prefilled from the day I clicked and the project type and budget prefilled from the package I picked. On submit, the app does the whole booking in one pass: create the client with HoneyBook Create Contact, open the engagement with HoneyBook Create Project carrying the event date, project type and budget, issue the deposit with HoneyBook Create Invoice attached to that new project, and block the day with Google Calendar Create Event as an all day hold titled with the client name and project type. Show the four steps ticking off as they complete, and if one fails, tell me exactly which one so I know whether the project exists but the invoice does not. When it finishes, refresh the grid so the new booking and its hold both appear right away.

Add a Prep the week ahead button that kicks off a background agent. The agent reads the next seven days of HoneyBook projects from List Projects and the matching Google Calendar events from List Events, pairs each event date with its calendar entries, and writes a run of show brief for each event: the client and their contact details, the arrival or call time taken from the calendar event, the location, the balance still due against the project budget after the deposit, and a short what to confirm checklist covering things like timeline, second shooter, parking, meals and delivery date. The briefs land back in the app in a Week ahead view I read on the morning of, one card per event in date order, with the time of the run shown so I know how fresh they are. Keep the last set of briefs visible until a new run replaces them, and show progress while the agent is working.

Important constraint on the HoneyBook side. The only bulk read available is List Projects, alongside Get Company and Get Current User. There is no list invoices, no list contacts, no get project and no update project operation, and custom fields are not exposed through this integration. Every view in this app has to be derived from List Projects and the client, event date, project type and budget fields it returns. Do not invent HoneyBook endpoints. Cache the project list inside the app so moving between months does not refetch the whole pipeline, and give me a manual refresh button.

Persist a small editable list of my packages (name, default project type, default budget, default deposit) so booking a date is a couple of clicks rather than typing, and let me assign a color to each project type so the season grid matches how I think about my work. Also persist which Google Calendars are overlaid and the generated run of show briefs. This is a single operator tool, so it does not need roles or permissions.