See which HoneyBook packages and seasons make you money

I run a one or two person creative business and I only reset my prices once or twice a year. Build me an app that tells me which of my packages and which seasons actually make money, because HoneyBook only shows me basic revenue and I end up rebuilding the same spreadsheet every time I think about raising prices.

The main screen is a profitability table built from HoneyBook. Use List Projects to pull every project, following next_cursor until there are no more pages, and group the results two ways at once: by project type, which is my package, and by the month of the event date. For each package and month, show how many projects I booked, the average budget, and the total booked value, with a total row per package and a total column per month. Default to the last 12 months and give me a date range control plus a toggle that rolls months up into seasons, since that is how I actually think about the year. Use Get Company for the studio name in the header.

Every number in that table has to be clickable. Clicking a count, an average, or a total opens a panel listing the exact projects behind it: client name, project type, event date, budget, and current stage, sorted by event date. I never want to see a figure I cannot trace back to the projects that made it.

Next to the booking numbers, pull the real money from QuickBooks Online. Use Query Entities to fetch Purchase, Bill, and Invoice records over the same date range as the table, and use Run Reports to run a Profit and Loss for the matching period. Show total income and total costs for the period, list the biggest expense categories underneath, and let me click any expense category to see the individual purchases and bills inside it.

Then show an estimated margin per package type. Costs I can tie to a package, through the vendor or the expense category, get charged to that package directly. Anything left over is shared overhead, and I want a setting to either spread it across packages by share of booked value or leave it out of the margin entirely. Whichever is in play, label it on screen in plain words such as shared costs spread across packages by revenue share, so I know I am reading an estimate rather than gospel. HoneyBook never tells you which project an expense belongs to, so include a small mapping screen where I connect QuickBooks expense accounts and vendors to my package types once, and save that mapping in the app so it sticks.

On each package row put a Review this package button that starts a background agent. The agent gathers that package type's HoneyBook projects across the last few seasons with List Projects, pulls the matching costs and income from QuickBooks with Query Entities over each season's date range, runs a Profit and Loss with Run Reports for each of those periods, works out the effective margin per project for that package, and describes how the margin has moved season over season. It then writes a pricing recommendation: raise, hold, or retire, with a suggested price, the reasoning in plain language, and the specific numbers it leaned on. The recommendation gets written back into the app as a saved review, stamped with the date it was written and the period it covered, and the review lists the projects it was based on so I can click through the same way as the table.

Add a Reviews section listing every saved review, newest first and grouped by package, so I can open last spring's review next to this one and see whether I actually acted on it. Each package row on the main table should carry a small badge showing its latest recommendation and how old that review is. While an agent is running, show that the review is in progress on the row it was started from.

Two hard constraints to build around. First, the HoneyBook integration only offers List Projects as a bulk read, plus Get Company and Get Current User. There is no invoice list, no contact list, and no time tracking data, so everything on the HoneyBook side has to be derived from the project budget, project type, event date, and client fields returned by List Projects. Do not build an hours based profitability view. All cost data comes from QuickBooks. Second, HoneyBook custom fields are not available through this integration, so the package is whatever the built in project type field says. Show me a plain list of the project types the app found, with counts, so I can spot ones that are named inconsistently and fix them at the source.

Keep the whole thing in plain language, because I am the owner and not an accountant. No jargon, never a percentage without the dollars beside it, and every card should say in one sentence what it means, for example: weddings booked in June brought in 42,000 dollars across 6 projects, about 7,000 dollars each, with roughly 2,900 dollars of costs behind each one. Round money to whole dollars. If a package has too few projects to compare seasons honestly, say that on the row instead of drawing a trend from two bookings, and if a number cannot be worked out, say why instead of showing a zero.