What problem does it solve?
Demand letters often fail because the writer skips structured pre-drafting intake, leading to weak facts, mismatched tone/marking, and missing leverage or privilege guardrails.
Core Features & Use Cases
- Structured intake capture: Collects demand type, parties, triggering event, legal/contractual basis, desired outcome, deadlines, prior outreach, and distribution details into an intake.md file for downstream drafting.
- Matter-specific posture first: Forces questions for tone, response window, marking, and signer so the draft aligns to the specific dispute instead of generic defaults.
- Strategic risk layer (optional/conditional): When the heuristic deems it material or when --full is used, gathers leverage & BATNA, downside tolerance, settlement-communication posture, privilege filters, and admission/accord-and-satisfaction risk to improve draft quality and safety.
Quick Start
Run the demand-intake flow by asking the system to collect intake for a demand letter with the title you provide, then save it for drafting.