Draft a firm, factual letter of demand or dispute response — chronology, the ask, the deadline, and the tone that works if a court ever reads it.
Draft a {{letter_type}} (letter of demand / response to a dispute). The facts: {{facts}} (who, what was agreed, what happened, dates, amounts, evidence I hold, what I want).
Structure: factual chronology (dates, documents, no adjectives — write it knowing a magistrate might read it), the basis of the claim (agreement + breach + consequence, plainly), the specific demand (amount/action + payment details), the deadline (14 days is standard) and the stated next step if unmet (small claims tribunal / VCAT-equivalent / collections — matched to my amount and state), and 'without prejudice' guidance (when that label helps vs hurts — and note this letter usually should NOT carry it). Tone: firm, boring, zero threats beyond stated process. End with what I should NOT put in writing, and the settlement-worth-taking number to decide before sending.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekSummarise a contract clause and flag what to watch.
Draft a clear internal policy from a few requirements.
You received a demand letter or legal threat: the don't-panic triage, what to preserve and not say,...
Review a contract before signing: the clauses that bite SMBs — liability, termination, auto-renewal,...
Draft the skeleton terms and conditions for your service — coverage of scope, payment, cancellation,...
Map what personal data you actually collect and why — the groundwork that makes your privacy policy...