brief_confirmation_email
Send a written summary of project scope, deliverables, exclusions, timeline, and price to confirm understanding before starting work. Prevents scope disputes by aligning expectations upfront.
Instructions
Write a short email confirming your written understanding of a project brief before work begins. Sends a concise scope summary — what you'll deliver, what's excluded, timeline, price, and what you need from the client to start — and asks them to confirm or correct before you begin. Prevents scope disputes by creating written alignment upfront. Required: client_name, deliverables (comma-separated list of what you're delivering), total (your price or rate, e.g. '$2,400 fixed' or '$120/hr, ~20hrs'). Optional: project_name, out_of_scope (up to 3 items explicitly excluded — omit if nothing needs spelling out), timeline (overall project duration or deadline, e.g. '3 weeks' or 'delivered by July 15'), start_date, what_you_need (assets, access, or information you need from the client to start — e.g. 'brand guidelines and CMS login'), your_name. Workflow: receive brief → discovery_call_follow_up_email (recap) → brief_confirmation_email (written scope sign-off) → project_kickoff_email (start). Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client's first name or full name | |
| deliverables | Yes | Comma-separated list of what you will deliver (e.g. 'homepage redesign, 3 interior page templates, mobile-responsive CSS, one round of revisions') | |
| total | Yes | Your agreed price or rate (e.g. '$2,400 fixed fee', '$120/hr estimated 20hrs', '$3,000 split 50/50') | |
| project_name | No | Short name for the project — used in the subject line and opening (e.g. 'the website redesign', 'your brand refresh', 'the Q3 campaign'). Omit to keep the opening general. | |
| out_of_scope | No | Up to 3 items that are explicitly NOT included — spell these out when they are the likeliest source of scope creep (e.g. 'copywriting, SEO optimisation, ongoing maintenance'). Omit if nothing needs excluding. | |
| timeline | No | Overall project duration or delivery deadline (e.g. '3 weeks from start', 'delivered by 30 July', '2-week turnaround'). Omit if not yet confirmed. | |
| start_date | No | Planned start date if confirmed (e.g. 'Monday 21 July'). Omit if not yet set. | |
| what_you_need | No | Assets, access, or information you need from the client before work can begin (e.g. 'brand guidelines, CMS login, and final copy', 'existing logo files and Google Analytics access'). Omit if you have everything needed. | |
| your_name | No | Your name for the sign-off |