Get invoices paid without burning the relationship
prompt.txt
Act as a practical specialist helping me with late payment escalation ladder. My context: [the unpaid invoice amount and age; payment terms agreed; your contact there; past payment behavior; contract clauses; your cash situation].
1. Send the friendly nudge: invoice re-attached, 'just flagging' tone, at day 1 past due.
2. Send the direct ask at day 7: is there a blocker, and a specific pay-by date.
3. Send the firm notice at day 14: late fee or pause-work clause invoked per contract.
4. Write the final notice at day 30: escalation path stated plainly.
5. Add prevention: deposit, milestone billing, and autopay language for the next contract.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#freelance & clients#getting paid
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Act as a seasoned independent-consultant coach who protects the freelancer. The task is responding to out-of-scope requests mid-project. Context: [the original scope agreed, the new request verbatim, project stage, my rate].
1. Write the reply that names the request as new work warmly.
2. Price the addition with a simple change-order line.
3. Offer the trade: swap something out to keep the budget.
4. Include the sentence that protects the deadline.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Quote with confidence instead of apologizing with numbers.
Act as a seasoned independent-consultant coach who protects the freelancer. The task is preparing a project quote. Context: [the deliverables, estimated hours, my target rate, client budget signals].
1. Present price as three scoped options, not one naked number.
2. Anchor each option to an outcome, not hours.
3. Write the line that states what is excluded.
4. Add the expiry and revision-round terms in plain language.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Start every project like a professional operation.
Act as a seasoned independent-consultant coach who protects the freelancer. The task is building a client onboarding flow. Context: [my services, what I need from clients, typical timeline, tools I use].
1. List the five things I must collect before work starts.
2. Write the welcome email that sets communication rules.
3. Draft the kickoff agenda that surfaces hidden expectations.
4. Include the payment and file-handoff terms to confirm in writing.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.