← All Reports
Business Nervous System Diagnosis
Sensing Degraded |
Pipeline visibility is partial. Artist availability and deal status exist in the founder’s spreadsheets and her memory, but not in a shared real-time surface that staff can read and act on. Round-by-round deal state — which proposal is in round two, which is awaiting a countersignature, which has a calendar conflict that hasn’t been resolved — is trackable only by talking to the founder or opening the last document version. The information exists, but it is scattered across artifacts rather than legible at a glance. |
Signaling Degraded |
Staff can relay information, but cannot generate the next document in a deal without founder involvement. When a venue manager calls to confirm a booking, staff take a message. When a client requests a revision on a round-two proposal, staff cannot produce round three independently — because the template is not wired and small copy-paste errors in round-three documents have downstream consequences (wrong fees, wrong dates, wrong artist riders). The signaling is not absent. It is gated by production capacity. |
Processing Degraded |
The founder processes deals well and has unusually thorough documentation of her own offer process. Three rounds of proposal, each round a slightly modified version of the last, ending in a signed contract, an invoice, event docs, and calendar entries across multiple calendars. The documentation is real. The bottleneck is that executing it is a copy-paste exercise across seven artifacts per deal, and the founder is the only person disciplined enough to run it cleanly every time. Processing capacity, not judgment, is the ceiling. |
Deciding Degraded |
Staff have documented authority on the margins — scheduling initial calls, sending form acknowledgments, confirming artist holds. The decisions that require the founder are almost always production decisions rather than judgment decisions: is this round-three contract correct, does the invoice number match the signed proposal, do the four calendars agree with each other. These should not require founder attention. They require it because the production pipeline is not wired. |
Regulating Absent |
No post-event review process, no artist relationship debrief, no client satisfaction signal collected after delivery. The firm does not systematically deepen relationships after successful events — a booking closes, the event happens, and the relationship goes dormant until the next inbound inquiry. There is no mechanism for the firm to generate repeat business from its existing client and artist relationships. Revenue is mostly reactive to incoming demand rather than cultivated from the firm’s own network. |
Primary Structural Failure Mode
The map exists. The territory is charted. The bottleneck is that executing the map is a copy-paste exercise across three rounds of near-duplicate documents, and the founder is the only person in the firm disciplined enough to run it cleanly every time. This is the actual diagnosis. It is not a delegation failure and it is not a documentation failure. The documentation is unusually good. It is a production failure.
The offer process has three rounds. Each round produces a document that is 80–95% the same as the last round, with a handful of fields that change — fee, date, scope notes, technical rider, specific terms. By the final round there is a signed contract, an invoice, event docs, and calendar entries across artist, client, firm, and venue calendars. Seven artifacts per deal. All hand-produced, round by round, from templates that are not wired to each other or to a single source of truth.
The founder runs this cleanly because she has the full picture in her head and catches her own errors. Staff run it slowly and nervously, because the cost of a wrong number in round two surfaces as a contractual issue in round three — and the risk of that error is asymmetric enough that staff default to routing every document back to the founder for review. The result is that the founder is not just the relationship manager. She is the production line.
The calendar layer compounds this. Artist calendar, client calendar, internal firm calendar, venue hold windows. A booking that moves requires four calendar edits. A booking that lands requires all four to agree. None of them update each other. The founder is the sync engine.
The business is approaching a structural vulnerability: if the founder became unavailable for 30 days, the firm could continue to accept inquiries — but could not produce the documents to close them cleanly. Staff could hold the pipeline. They could not advance it.
Where the Margin Is Leaking
Deal throughput is capped by document production, not by demand or judgment. Every deal consumes founder hours at the production stage that could, if the pipeline were wired, be consumed at zero marginal cost. The hours spent on mechanical copy-paste work are hours not spent on artist development, client cultivation, or category expansion. The leak is in the opportunity cost of founder time applied to work that does not require founder judgment.
Commission rates are inconsistent across similar deals because there is no documented pricing structure built into the templates. The founder prices each engagement by feel — accurate on average, uneven across the portfolio. Some repeat clients pay 15% commission; others in identical categories pay 12%. Some artist categories carry 18%; others with comparable demand carry 15%. The inconsistency is not strategic — it is the output of deal-by-deal improvisation at the moment of proposal generation. A documented commission structure built into the round-one template would stabilize margin without requiring a single rate increase.
Existing relationships are underworked as revenue sources. A client who booked a corporate act 18 months ago is not being contacted about their next event. An artist who performed successfully for three clients is not being actively presented to a fourth. The firm is leaving repeat revenue in relationships it has already paid to establish. This is a signaling and regulating problem that compounds with the production problem: there is no bandwidth to cultivate repeat business because the bandwidth is consumed producing documents for new business.
The Automation Decision: Where the Seam Goes
This is the section most operating reports skip. The operating problem at Meridian has a category of answer — automation — but the category is wide and the wrong choice inside the category creates new structural problems.
Deterministic automation — merge fields, pre-wired templates, a single source of truth for each field, calendar sync via API — handles the 90% path cleanly. A deal that fits the mold (standard artist, standard event type, standard terms) should produce all seven artifacts from one form submission, with the founder reviewing once at each round boundary rather than producing each document by hand. This is well-understood technology; the question is configuration, not capability.
AI rewriting — LLM-based generation for scope language, custom riders, client-specific framing — handles the 10% that doesn’t fit the mold. AI can produce a rider paragraph tailored to an unusual venue or an artist’s specific technical requirements faster than a human can, and without the deterministic template’s brittleness around edge cases.
The failure mode of each. Deterministic automation breaks silently when a deal doesn’t quite fit — it produces a document that looks correct but is subtly wrong, because the template assumed a standard case and the case wasn’t standard. AI rewriting introduces drift — small inconsistencies in numbers, dates, names, or legal phrasing that a contract cannot tolerate. Both failure modes are worse than slow hand production, which is why most firms stop short of automating.
The correct answer is a hybrid, and the judgment call is where the seam goes. For Meridian: deterministic automation owns the 90% path across all seven artifacts, with explicit human checkpoints at each round boundary. AI is restricted to a narrow set of fields — scope language, rider customization, email copy fluency — and is explicitly prohibited from touching the fields that contracts cannot tolerate drift in: fees, dates, names, signatory blocks, payment terms, cancellation language. That boundary is written into the pipeline as a rule, not a convention.