project_maintenance_proposal_email
Propose a post-project maintenance retainer or support agreement to clients using three routes: standard, priority_support, or light_touch. Upsell clients who trust you after delivery.
Instructions
Write the email proposing a maintenance retainer or support agreement after delivering a project. One of the easiest upsells freelancers miss — once the work is live, clients are most open to someone they trust keeping it running. Three routes: standard (regular monthly check-in, defined hours for updates and fixes — most common), priority_support (faster response SLA, reserved hours — for clients who can't afford downtime), or light_touch (a small bank of hours, no monthly commitment — for low-maintenance projects or budget-conscious clients who still want access to you). Distinct from retainer_proposal (which opens an ongoing relationship from scratch) and service_package_email (a general menu of services). Does not count against your monthly draft limit. Required: client_name, project_name. Optional: monthly_hours (hours included per month — e.g. '4 hours'), monthly_rate (proposed monthly fee — e.g. '$350/month'), route ('standard' | 'priority_support' | 'light_touch' — default standard), response_time (SLA for priority_support — e.g. '4 business hours', 'same business day'), what_is_covered (brief summary of what's included — e.g. 'plugin updates, performance monitoring, minor copy edits'), go_live_date (when the project goes live — grounds the timing of the ask), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | First name or full name of the client | |
| project_name | Yes | The project just delivered — e.g. 'the Westbrook website', 'your new booking system', 'the brand refresh'. Used throughout the email. | |
| monthly_hours | No | Optional: hours included per month — e.g. '4 hours', '2 hours'. Omit to keep the email non-specific on hours. | |
| monthly_rate | No | Optional: proposed monthly fee — e.g. '$350/month', '£250/month'. Omit to keep pricing out of the first email (useful if you want to discuss before quoting). | |
| route | No | standard (default): regular monthly check-in, defined hours for updates and fixes, stability monitoring. priority_support: faster response SLA, reserved capacity, named contact — for clients where downtime has real cost. light_touch: a small bank of hours, no monthly commitment — for low-maintenance projects or budget-conscious clients. | |
| response_time | No | Optional (most useful for priority_support): the response SLA you're committing to — e.g. '4 business hours', 'same business day', 'within 2 hours during business hours'. | |
| what_is_covered | No | Optional: brief summary of what maintenance includes — e.g. 'plugin and dependency updates, uptime monitoring, minor copy edits, one design tweak per month'. Makes the offer concrete without needing a full proposal. | |
| go_live_date | No | Optional: when the project is going live or was delivered — e.g. 'next Monday', 'June 30', 'this week'. Grounds the timing of the ask. | |
| your_name | No | Optional: your name for the sign-off |