+ Be sure about each answer first—unclear choices here often cause + trouble at settlement later. Tap an option to save it for this show; + the workspace uses these when you calculate. +
+ + )} ++ Saved: {answerAsString(answers[q.id])} +
+ )} ++ + Click to review clarifying questions and payout signals. +
+ )} + {clarificationsSettled && level === "high" && ( ++ Open anytime to edit answers or re-read payout signals. +
+ )} ++ AI scan of deal notes — not a final settlement. +
+{error}
+ ) : review ? ( ++ Be sure about each answer before you move on—if these stay + fuzzy, they often turn into settlement problems later. Tap + an option to save your choice on this show (the workspace + picks these up when you calculate). +
++ {clarificationEmailError} +
+ )} + {clarificationEmailBody && ( ++ Review returned no structured fields. +
+ )} ++ Worksheet UI only — figures below are for layout and do not run + production settlement logic. +
++ {row.helper} +
+ )} ++ Net ticket revenue = sum of lines tagged Gross minus sum of + lines tagged Fees (from ticket_sales captures in the database). +
++ No expense lines yet. +
+ ++ {row.helper} +
+ )} + {scaled && ( ++ Deductible is below actual because of hospitality cap + and/or total expense cap (Settlement logic). +
+ )} +
+ From deal expense_cap. When
+ set, if the sum of all deductible lines (after hospitality
+ pooling) is higher than this amount, each line is scaled so the
+ total equals the cap — used in net revenue and final payout.
+
+ From deal hospitality_cap.
+ Same proportional split across hospitality lines.
+
+ Example: “Walkout not triggered — breakeven not reached” +
++ {finalPayout === artistShare && artistShare > guaranteeForVs + ? "Percentage share is above guarantee — payout uses the share." + : finalPayout === guaranteeForVs && guaranteeForVs > artistShare + ? "Guarantee is above percentage share — payout uses the guarantee." + : "Share and guarantee tie at this preview — payout uses that amount."} +
+ )} ++ + {artist?.name ?? "—"} + + · + {formatShowDateFull(show.date)} +
++ {filtered.length} artists who have played The Crescent in the last 24 + months. Bucketed by frequency. +
++ You're looking at our product as Mariana, lead booker at The + Crescent. The product works. It's also visibly mediocre in + places. Both of those things are true on purpose — this is the + substrate for your case study. +
++ + Read your case study brief first. + {" "} + It explains the problem you're solving and the principles + we're evaluating you on. This page is just orientation inside + the product itself. +
+
+ data/dispute-thread.md
+
+ .
+ + Settlement isn't one problem. It's several adjacent ones — + deal modeling, audit trails, real-time prediction, the 2am + walkthrough conversation, post-show agent communication. Pick one + slice (or a tightly coupled pair). Take it deep. Don't try to + fix the whole thing. +
++ Your case study brief explains what we're evaluating you on. + We'll talk about your slice in person — what you picked, what + you cut, what you cut deliberately, and what you'd ship next. +
+ + {/* Data skepticism hint */} ++ Real venue data is messy. Fields drift, prose contradicts structured + values, statuses don't always match the underlying reality, and + patterns hide across many shows that look unremarkable in isolation. + What the UI shows you isn't always what the data says — and + neither is necessarily what actually happened. We'd encourage + you to read the data closely, query it directly, and bring + skepticism to anything that seems too clean. +
+
+ {file}
+
+ + {desc} +
++ Aggregate metrics for The Crescent. The numbers the CEO is watching. +
+
+ “Our settlement experience is the place we are most clearly
+ losing on craft. Our customers love us in spite of it, not because
+ of it.”{" "}
+
+ Read the full memo
+
+ At The Crescent, {unsupportedPct}% of deals — Vs deals, % of net, and + door deals — are deal types the in-app tool can't settle. + Across all customers, only about 18% actively use the tool at all. +
++ {r.settlementStatus.disputed ?? 0} of {r.totalSettlements} past + settlements ended in some form of dispute — either a withheld + signature or a back-and-forth that altered the final number. +
++ Where the {r.totalSettlements} settlements at The Crescent currently + sit. {inFlight} are still in flight — drafted but not yet paid. +
++ Venue costs taken off the top before artist payment. The most + frequent source of settlement disputes — exactly the seam in the + Coastal Spell thread. +
++ Comp tickets given away across all shows. Whether comps count toward + gross is a deal-by-deal call — and a recurring source of friction. +
+
+ bonuses_json
+
+ . An unknown number more sit only in the deal-notes prose.
+
+ bonuses_json
+
+ . The in-app tool only reads structured bonuses — anything
+ in the prose below is invisible to it.
+ | Category | +Count | +Face value | +Counts toward gross? | +
|---|---|---|---|
| + {COMP_LABELS[c.category] ?? c.category} + {c.notes && ( + · {c.notes} + )} + | +{c.count} | ++ {formatMoney(c.faceValue * c.count)} + | ++ {c.countsTowardGross ? ( + Yes + ) : ( + No + )} + | +
| Category | +Description | +Amount | +
|---|---|---|
|
+ {e.category}
+ {e.absorbedByVenue && (
+ |
+ {e.description ?? "—"} | +{formatMoney(e.amount)} | +
| Total (passed through) | +{formatMoney(totalExpenses)} | +
+ The artist team has flagged recoup line items. This settlement cannot be finalized until the dispute is resolved. +
+
+ Greenroom's in-app settlement tool was built early in the
+ company's history, when most deals were flat guarantees.
+ About 18% of customers actively use it; the other 82% — including
+ most of the larger venues — default to spreadsheets. The CEO has
+ flagged this as the company's biggest craft gap.{" "}
+
+ Where to start
+ Mariana would do this on a Google Sheet at 2am tonight. The inputs + are below — but the math doesn't happen here. +
++ Mariana's home view. {reversed.length} shows over 24 months.{" "} + {settledCount} settled + {disputedCount > 0 && ( + <>, {disputedCount} disputed + )} + . +
+