Free · no email required
Three replies for “can you just also…”
Copy, replace the [brackets], send. The pattern in all of them: acknowledge, classify, price or path, ask for the go-ahead. Never apologize for the price. Never argue about scope; point at the document.
1 · The “can you just also” mid-project
When: the project is underway and a new deliverable appears in a sentence that starts with “oh, and.”
Hi [Name], Happy to add [the pricing page / a second email template / the Spanish version]. That's outside the scope we agreed in the proposal, so here's what it looks like as an addition: • Work: [one-line description] • Cost: [$X] (fixed) / [Y hours at $Z/hr] • Timeline: adds [N days] to the current delivery date, so [new date] Reply “approved” and I'll fold it in. If you'd rather keep to the original scope and timeline, that's completely fine too. Just let me know. [Your name]
Chat version: Can do. That's an addition to the agreed scope: [$X], adds [N days] (new delivery [date]). Want me to go ahead? A quick “yes” here is enough.
Next: do not start until you have the yes in writing.
2 · Feedback round #4 when the contract said 2
When: you've done the agreed revisions and a new round arrives with no acknowledgement that it's extra.
Hi [Name], Got the notes, thanks. Quick flag before I start: we're now past the [two] revision rounds included in the proposal (rounds 1 and 2 were [dates]). Additional rounds are [$X per round / billed at $Y/hr, usually about $Z for a round this size]. Two options: 1. I apply this round as a paid revision: [$X], turned around by [date]. 2. We do a 20-minute call to lock in all remaining changes at once, so this is the last round rather than one of several. I'd recommend option 2. It usually saves everyone money. Which works? [Your name]
Chat version: Thanks! Heads-up: this is round [4], proposal included [2]. Extra rounds are [$X]. Happy to do it, or let's do a quick call to bundle everything remaining into one final round. Your call.
Next: whichever they choose, write “Round 4, paid revision, approved [date]” in your log. Round 5 will come.
3 · The urgent Friday 5pm request
When: “Need this live by Monday morning.” It's Friday evening. It's not in scope, or it is but wasn't due.
Hi [Name], I can make Monday work. Weekend turnaround is outside normal hours, so it's billed at my rush rate: [1.5x / 2x], which for this comes to [$X]. If you approve by [7pm tonight], you'll have it by [Sunday 6pm / Monday 8am]. If Monday can slip to [Wednesday], it's [$Y] at the standard rate. Reply with “rush” or “standard” and I'll get moving. [Your name]
Chat version: Can do Monday. Weekend work is at rush rate ([1.5x]) = [$X], approve by [7pm] and it's yours by [Monday 8am]. Or [$Y] standard rate for [Wednesday]. “Rush” or “standard”?
Next: roughly half the time the urgency evaporates once it has a price. That is the point. The other half, you get paid properly for a weekend.
The other eleven
The full kit has 14 scripts (including “I assumed this was included,” the client's brother-in-law with opinions, source-file requests, the equity-instead-of-fees pitch, ignored change orders, and pausing work until it's signed), a one-page change order template, a pricing framework, six proposal clauses, and a printable cheat sheet.
One-time payment. Instant download. 14-day refund if it isn't useful.