revision_rounds_exceeded_email
Generate an email to inform clients when revision rounds are exceeded, with options to quote additional costs, offer an upgrade package, or close the project.
Instructions
Write the email when a client requests revisions beyond their contracted allocation — enforcing your revision policy without damaging the relationship. One of the most avoided conversations in freelancing; this email makes it easy by being matter-of-fact, not defensive. Three routes: notify_and_quote (default — inform the client their rounds are used, quote the additional cost, invite them to proceed; works when you want to keep the work and the relationship), offer_upgrade (offer a small add-on package for further revisions — works when the client is likely to need ongoing changes and a bundled approach makes sense), close_and_decline (flag that contracted revisions are complete and the project is considered signed off unless they purchase more; works when revisions are clearly not converging or the client is acting in bad faith). Distinct from revision_response_email (which handles the content of a specific revision), scope_creep_response_email (which is broader scope expansion), and change_order_email (which is a formal contract amendment). Does not count against your monthly draft limit. Required: client_name, project_name. Optional: revisions_included (how many rounds were in the contract — e.g. '2 rounds', '3 rounds of revisions'; default is 'the included'), revisions_used (how many have been used — helps make the email concrete), additional_rate (your rate for extra revision work — e.g. '$85/hr', '$150 per round'; makes the quote concrete), route ('notify_and_quote' | 'offer_upgrade' | 'close_and_decline' — default notify_and_quote), package_name (for offer_upgrade route — name of the add-on, e.g. 'Revision Pack', 'Polish Pass'), package_price (for offer_upgrade route — e.g. '$200', '2 hours at $85'), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | First name or full name of the client | |
| project_name | Yes | The project name — e.g. 'the Westbrook website', 'your brand refresh', 'the app design'. Used throughout the email. | |
| revisions_included | No | Optional: how many rounds were contracted — e.g. '2 rounds', '3 rounds of revisions', 'two feedback rounds'. Default is a vague reference to 'the included revisions'. | |
| revisions_used | No | Optional: how many rounds have been used — e.g. 'two', 'three'. Helps make the email concrete rather than abstract. | |
| additional_rate | No | Optional: your rate for extra revision work — e.g. '$85/hr', '$150 per round', '$200 per additional feedback round'. Makes the quote concrete. | |
| route | No | notify_and_quote (default): inform the client, quote additional cost, invite them to proceed. offer_upgrade: propose a small add-on package for further revisions. close_and_decline: mark the revision stage as complete, project considered signed off unless they purchase more. | |
| package_name | No | For offer_upgrade route: name of the add-on revision package — e.g. 'Revision Pack', 'Polish Pass', 'Extended Refinement'. | |
| package_price | No | For offer_upgrade route: price of the add-on — e.g. '$200', '2 additional hours at $85', '$150 flat'. | |
| your_name | No | Optional: your name for the sign-off |