← all hypothesesPromise-Held Ledger for SaaS support directors
exhausted [TRIANGULATED] signals: 1 independent
What is this?
A pre-send gate and post-resolution ledger for the customer-facing date commitments support agents make every day ("fixed by Friday", "response within 48 hours"). It plugs into Zendesk/Intercom, watches outbound replies for commitment phrases, and the moment an agent drafts one shows the historical resolution-within-window rate by category, agent, and customer tier. After the ticket resolves, it grades the promise against the actual close timestamp. Over weeks it builds a per-agent and per-category miss-pattern ledger the support director uses for coaching, SLA forecasting, and honest external promise-setting. Built for support directors at 50-500 person SaaS who own CSAT and SLA breach numbers and hold direct budget. AE's adversarial multi-model debate and the structured constraint language with promotion/demotion lifecycle map cleanly onto graded commitments with explicit promise-state transitions; the under-24h grading loop matches ticket resolution rhythm. Truth is the Zendesk close timestamp — no rubric interpretation, only date strings and statuses leave the buyer's tenant.
Why did we consider it?
Promise-Held Ledger is the rare hypothesis where AE's reality-graded, lifecycle-aware substrate has a one-to-one mapping onto a buyer who owns the budget, feels the pain daily, and lives inside a system (Zendesk) that already emits the ground-truth signal.
What breaks?
- Workflow Sabotage: A pre-send LLM gate adds latency to the 'Send' button, directly harming Average Handle Time (AHT) and triggering agent rebellion.
- Deployment Contradiction: Zendesk/Intercom plugins are inherently multi-tenant SaaS, which violates the core AE constraint and is unviable for single-tenant solo-dev deployment.
- Native Redundancy: Zendesk Explore already handles SLA tracking and resolution timestamps without the need for expensive, token-heavy LLM interception.
What did we learn?
Killed: evidence_search_exhausted.
Evidence
Signal D — Demand proxy
{"found":true,"summary":"A Reddit thread in r/managers describes a manager who forgot a commitment to a direct report; commenters explicitly recommend 'a promise ledger' as the fix, validating organic demand for systematic commitment tracking beyond personal notes.","sources":["https://www.reddit.com/r/managers/comments/1qv6e4e/forgot_a_commitment_i_made_to_a_direct_report/"],"reason":"Result [2] is a forum discussion (Reddit r/managers) where the snippet directly names 'a promise ledger' as the solution to forgotten commitments, showing unprompted demand for the core concept. Other results ar…
Evaluation history
| When | Stage | Phase |
|---|
| 2026-05-10 00:42 | evidence_search | evidence_hunt |
| 2026-05-10 00:36 | evidence_search | evidence_hunt |
| 2026-05-10 00:24 | evidence_search | evidence_hunt |
| 2026-05-10 00:18 | evidence_search | argument |
| 2026-05-09 22:42 | evidence_search | argument |
| 2026-05-09 22:36 | evidence_search | argument |
| 2026-05-09 22:24 | evidence_search | argument |
| 2026-05-09 22:18 | evidence_search | argument |
| 2026-05-09 22:12 | audience_simulation | argument |
| 2026-05-09 22:06 | red_team_kill | argument |
| 2026-05-09 21:54 | steelman | argument |
| 2026-05-09 21:50 | genesis | argument |