Payment Terms and Schedule Plain-Language Summary
Explain how and when the client pays.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a plain-language payment section for a proposal. Project value and phases: [PROJECT_VALUE_AND_PHASES]. Preferred payment structure (deposit, milestones, monthly): [PAYMENT_STRUCTURE]. Late payment practices I want: [LATE_PAYMENT_PRACTICE]. Cancellation and refund approach: [CANCELLATION_APPROACH]. Jurisdiction: [JURISDICTION]. This is a drafting aid, not legal advice.
Produce:
1. A payment schedule table: Milestone | Trigger | Amount | Due date or days after trigger.
2. A short explanation (80 to 120 words) in a friendly but clear tone, covering invoicing, accepted methods, due dates, and what happens if a payment is late (reminders first, a fee only if the contract allows and local law permits [VERIFY]).
3. A cancellation and refund explanation that is fair (what the client owes for work done and costs committed).
4. Variants: a deposit-only version for small jobs, a monthly retainer version, and a version with a long-lead-time purchase.
5. A summary box ("What you pay and when") with five lines.
6. Questions to ask a lawyer or accountant about the final wording.
Show the arithmetic of percentage splits. Don't add penalties or fees I have not listed.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.