payment_plan_proposal_email
Write emails to propose or confirm payment installments for projects when a client cannot pay the full fee upfront. Supports initiating a plan, responding to requests, or negotiating terms.
Instructions
Write the email proposing or confirming payment installments for a project. For when a client can't pay the full fee upfront, or when you want to proactively offer a payment plan to remove a barrier to closing the deal. Three routes: propose_plan (default — you initiate a structured installment proposal: milestone-based or monthly splits; works for high-value projects where budget is not the issue but cash flow is), respond_to_request (client has already asked for installments and you're confirming what you can offer — tone is helpful and collaborative, not reluctant), negotiate_back (client wants different terms than you proposed — e.g. smaller upfront, more splits — and you're counter-proposing or finding a middle ground while protecting your interests). Distinct from deposit_request_email (collecting an agreed deposit that's already been discussed), budget_negotiation_email (negotiating the total fee, not the payment structure), and payment_reminder_email (chasing a payment already due). Does not count against your monthly draft limit. Required: client_name, total_amount (total project fee — e.g. '$4,500', '£3,000'). Optional: project_name, plan_description (your proposed structure — e.g. '50% upfront, 50% on delivery', '30% to start, 30% at midpoint, 40% on completion', '$500/month over 3 months'), installment_count (number of payments — e.g. '2', '3', 'monthly for 4 months'), client_plan (for negotiate_back route — the terms the client asked for), route ('propose_plan' | 'respond_to_request' | 'negotiate_back' — default propose_plan), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client first name | |
| total_amount | Yes | Total project fee — e.g. '$4,500', '£3,000', '$12,000'. Required. | |
| project_name | No | Optional: name of the project — e.g. 'the Westbrook website', 'your brand identity', 'the app build'. | |
| plan_description | No | Optional: the payment structure you're proposing — e.g. '50% upfront, 50% on delivery', '30% to start, 30% at midpoint, 40% on completion', '$1,500/month over 3 months'. If omitted, a standard 50/50 split is implied. | |
| installment_count | No | Optional: number of payments — e.g. '2', '3', '4 monthly payments'. Helps make the email concrete if plan_description is not provided. | |
| client_plan | No | For negotiate_back route: the payment structure the client asked for — e.g. '20% upfront and the rest on delivery', 'monthly over 6 months'. Used to acknowledge their ask before counter-proposing. | |
| route | No | propose_plan (default) — you initiate the payment plan offer; respond_to_request — client asked, you're confirming what you can offer; negotiate_back — client wants different terms, you're counter-proposing. | |
| your_name | No | Optional: your name for the sign-off |