upwork-client-messenger

Upwork Client Messenger

Mid-contract messages decide whether a contract ends in a review and a referral or in silence. Method extracted from a Top Rated Plus freelancer's real client threads across long and short engagements, plus published guidance. The through-line: state facts plainly, never litigate, and let structure do the negotiating.

Inputs

1. The situation (which of the five below).
2. Thread context, pasted: what was agreed, what changed, the client's last few messages.
3. Engagement type: long-term relationship or short transactional contract. Several moves below fork on this; ask if unclear. If it isn't stated and can't be inferred, ask once and draft both closings so the user isn't blocked on your question.

Profile shortcut: if a stored profile file exists (upwork-profile.md in the working directory or ~/.claude/), read identity and rate context from it and ask only for what's missing or not stated concretely (a rate line that says "ask me" means ask).

Voice (hard, applies to all five)

Professional peer, warm and short. Contractions, plain words, no em dashes. Banned: permission-seeking and apology stacking. "Can I possibly ask if maybe" is the junior register; the working register states facts and asks one clear question. One apology maximum when apologizing is warranted, then move to the plan.

1. Delay news

Lead with the revised date in the first line; never bury it under context. Then, in order: what is already done (specifics build trust), the honest ETA with its hedge stated plainly ("aiming for Thursday, can't fully lock it yet"), and a promise to flag the moment it's ready. No over-promising to soften the moment; a slipped second deadline costs more than a conservative first one.

When the delay is the client's, zero pushback: well wishes, confirm no rush. Holding a client to a date they slipped buys nothing and spends goodwill.

2. Scope creep (the fork that matters most)

First, classify with the repeated-game rule:

• First small extra ask from a good long-term client: do it, and name it as a courtesy in the same message ("happy to include this one; it sits outside our original scope, so flagging it"). The boundary is set without a confrontation.
• Large ask, any client: always bill, framed forward: "Let me scope that properly and send you a number." Never a flat no; the counter-offer form ("I can get it to you by Friday instead, will that work?") declines the terms while accepting the relationship.
• Chronic pattern of free-work asks: stop litigating individual asks; price the pattern into the next engagement's rate.