Sell readiness and decisions, not an impossible guarantee
The agency can promise a rehearsal, named staffing window, monitored signals, response target, decision log, and post-event report. It cannot promise zero downtime from the model provider, payment processor, internet, or unsupported custom transports. Put that distinction in the proposal before discussing price.
Define the covered event by hostname, date, timezone, six-hour live window, AI features, supported WordPress paths, and client business contact. Requests made through direct SDKs or systems the agency cannot observe are exclusions unless separately integrated and tested.
Cost the whole delivery, not just the six live hours
The example includes four hours of preparation, eight staffed hours, and three hours for the report. Eight staffed hours may represent two people overlapping during a six-hour event; document roles so the number is not mistaken for duration. Multiply each role by its loaded rate and add sales, tooling, and payment costs.
Apply the 25% uncertainty reserve to delivery labor that can genuinely vary. At a $2,500 fee, margin equals fee minus preparation, coverage, report, reserve, license allocation, and any subcontractor cost. If escalation beyond the stated window is common, it needs an hourly rate rather than being hidden in the reserve.
| Worksheet line | Example units | Cost input | Commercial rule |
|---|---|---|---|
| Preparation | 4 hours | loaded rate by role | includes rehearsal and runbook |
| Staffed coverage | 8 person-hours | loaded rate plus on-call premium | six-hour event window |
| Report | 3 hours | loaded rate | one decision log and summary |
| Uncertainty reserve | 25% of variable labor | calculated | not extra client scope |
| Fee | $2,500 example | fixed | overtime/escalation quoted separately |
Specify response in operational terms
A response target means the operator acknowledges a valid alert and starts the runbook within a stated time. It does not mean service is restored within that time. Define alert sources, acknowledgement channel, decision authority, and how the client is contacted when revenue context is needed.
List available actions in advance: hold the absolute ceiling, narrow a repeated-request rule, pause background work, roll back a configuration, or switch to a tested degraded mode. Provider failover belongs in scope only if both routes and duplicate-cost behavior were rehearsed.
Protect margin with entrance and exit gates
Require access, baseline data, campaign forecast, contact details, tested alerts, and rollback permissions by a cutoff date. If the client misses the gate, postpone, reduce coverage, or issue a change order. Last-minute evidence recovery should not consume the live-event staffing budget.
Coverage ends at the scheduled time unless an authorized extension is purchased. The report includes timeline, observed metrics, decisions, customer impact, remaining actions, and evidence gaps. Root-cause remediation and custom development are follow-on work, not unpaid closure obligations.
Review the offer after each event
Track quoted and actual hours, alerts per hour, senior escalations, client response delays, extensions, and report corrections. Calculate contribution margin per event and by client. A profitable average can still hide one client whose missing access repeatedly consumes the reserve.
The service is saleable when its promise, evidence, authority, hours, exclusions, and completion condition are all testable. Refer multi-site clients to the Agency plan page for licensing scope; keep licensing cost distinct from the labor and accountability of staffed event cover.
Use the event-cover margin worksheet from “Price a peak-day protection service without promising zero downtime” on a real first installation. Download AI Cost Circuit Breaker for free, begin in Monitoring, and move to enforcement only after the expected signals and rollback are verified.