Full-service restaurant slow-season budget pitch scripts - asking the owner for marketing money, with the house's own numbers pre-answering "what if it loses money" and "we tried that already" before they are spoken

You are a pitch coach for the marketing planner of a full-service restaurant. Write a set of Slow-Season Budget Pitch Scripts for presenting to the owner or partners in person. Organize into the five segments below; for each, give "what to say" (speakable lines with placeholders) and "what this segment does" (one sentence, so the user can adapt it with understanding).

Pitch context: the post-holiday slow season (or the house's known traffic trough); the planner is requesting a budget for one traffic campaign.

Five segments:

1. Open on the baseline: start with the house's own numbers - last slow season's weekly tables and sales (placeholders). No "industry slowdown" narratives. Purpose: anchor the conversation in this restaurant's reality, not the industry's story
2. The proposal, capped: present one concrete campaign (placeholder), and the framing must include the budget cap and the worst-case floor ("if this entire budget is spent and not one new table comes in, the maximum loss is X - that is the bottom line of this experiment"). Purpose: turn "afraid of losing money" from an emotion into a bounded number
3. Pre-answer one - "what if it loses money": concede that discounting costs money, then show the arithmetic - the margin per incremental table and how many tables it takes to break even (placeholders from the house's average check and margin basis). Purpose: the owner does not fear spending; they fear spending without a floor
4. Pre-answer two - "the last one didn't work": do not defend the previous campaign - dissect it. Which layer failed (no follow-through on the floor / rules too complicated / wrong window / baseline already declining), and which one thing this campaign changes (placeholder). Purpose: convert "last time didn't work" from a veto into this campaign's design rationale
5. Close on a pilot: request only a small two-week trial plus one go/no-go metric, stated as a hard number ("if incremental tables during the trial reach [N], we extend"). Purpose: shrink the decision - the owner is approving a two-week experiment, not a campaign

Constraints:
- No predictive promises anywhere in the scripts ("we expect to bring in X tables") - only the capped worst-case loss and the break-even table count; forecasts are how pitches lose credibility
- No industry data, industry conversion rates, or competitor cases - this restaurant's numbers only
- No "build brand influence" or "own the customer mindset" goals that cannot be verified
- Each segment's script stays within what can be spoken in a minute - this pitch is talked, not read aloud

Why it is written this way

The structure of these scripts converts a pitch from persuasion into arithmetic. The two standard objections - fear of losing money, and the memory of the last flop - are both computable: for the fear, compute the worst-case cap so risk becomes a finite number; for the last flop, dissect it into layers so the failure lands on a specific, changeable decision. Once both objections have numbers to answer them, they stop being standing vetoes.

The worst-case cap is the load-bearing move. Most pitches die not because the owner believes the campaign will fail, but because the cost of failure cannot be stated: budget burned, nothing gained, loss open-ended. Opening with "the maximum loss is X, that is the floor" shifts the owner's question from "do I trust you" to "is that floor worth betting on" - a far easier decision to make.

"Last time didn't work" gets dissected rather than defended because defending always loses: the last campaign did fail, and arguing invites the owner to conclude campaigns never work. Breaking it into layers (no floor execution, convoluted rules, the wrong window) demonstrates you understand the failure better than the owner does - and this campaign changes exactly that layer. The past turns from baggage into the design rationale for the present.

Closing on a two-week pilot with one stated metric minimizes the weight of saying yes. And forcing the metric to be a hard number makes the planner decide in advance what success means: a vague "if it goes well we continue" sends the debrief back into old habits, while "extend if incremental tables reach [N]" lets the experiment carry its own verdict. The ban on forecasts and industry stats exists because slow-season pitches love leaning on industry stories - and the only numbers an owner actually trust are the house's own.

Variables