05B ANCHORING · USD · SCRIPTS

Name the number first.

Q: Should I give a rate range or a single number?

A purposeful range — anchors high and invites fit conversation. Desired landing point at the top; single numbers only for defined scope.

Q: What do I say when a US client asks my budget expectations first?

"For what you've described, work like this runs $X-$Y — what's your range?" Anchor first, then treat their answer as information.

Q: How do I respond to "you're too expensive"?

Move scope, not rate: offer reduced scope at their number or full scope at yours. Decline below floor.

Q: Do I mention that I am cheaper than US freelancers?

Never — you are priced against their next-best option at value. Inviting a local-market comparison starts at a discount.

Whoever anchors first sets the range the negotiation lives inside. If the client names it, their budget becomes your ceiling. If you name it — grounded in outcome, stated in a range — your number becomes the reference point. Scripts below; frameworks over feelings.

Anchoring mechanics.

State firstyou or them — someone names a range

you, if ready

Formatrange, not single point

$X–$Y band

Anchor typeoutcome value > hours worked

value-tied

Floorfrom the floor-rate formula

never below

"What's your budget?"redirect, then give range

script below

"You're too expensive"scope lever, not rate cut

reduce scope

The budget question script: "It depends on scope — for what you described, projects like this run $X to $Y; tell me your range and I'll tell you honestly what fits." You anchored with market reality, kept the range wide enough to survive discovery, and turned their number into information instead of a ceiling. The pushback script: "I can hit that number by cutting [revisions/strategy/support] — or keep the scope at $Y. Which matters more?" — price moves when scope moves, never alone.

Why "from Africa" never belongs in the pricing conversation.

Rate is set by value to the buyer, not cost of living to the seller. A US client's alternative is a US freelancer at US rates, or an agency at agency rates — your comparison set is their next-best option, not your local market. Every "I'm based in Ghana so my rates are..." preamble imports a discount the client never requested. Location appears once, at scheduling logistics (two US-hour windows). Pricing is elsewhere.

Range width does real work: a narrow range ($45-50) signals a point price with wiggle room; a purposeful range ($4,000-6,500 by scope) signals tiers and invites the fit-conversation. Anchor the top of your range at where you actually want to land — the psychological midpoint of your range is what the negotiation orbits.

Hourly vs project: hourly leaks income to your own slowness and caps you at time; project pricing ties the number to the outcome and rewards systems. Lead with project/retainer quotes; fall back to hourly only when scope genuinely cannot be defined (then use the floor rate as the hourly floor). Pair with the rate formula (floor calculator) so every anchor clears your floor, and quote in USD (strategy page).

Number, then how to defend it.

The Kit's rate card gives your floor, your anchor ranges by service tier, and the pushback scripts — plus the invoice that presents the number cleanly. $19 founding, 14-day refund.

Run the free calculator Get the Kit — $19 Card · MoMo · 14-day refund

Questions.

Should I give a rate range or a single number?

A range with purpose: it anchors high, invites scope-fit conversation, and survives incomplete discovery. Put your desired landing point at the top of the range. Single numbers only when scope is fully defined.

What do I say when a US client asks my budget expectations first?

"It depends on scope — for what you've described, work like this runs $X-$Y. What's your range?" Anchor with market reality, then use their answer as information. Never answer with only a question — that reads as evasive.

How do I respond to "you're too expensive"?

Move scope, not rate: "I can hit that number by cutting [revisions/strategy/support] — or keep scope at $Y." If they cannot afford floor, the project loses money at any scope worth doing — decline gracefully. Rate cuts without scope cuts train clients to negotiate.

Do I mention that I am cheaper than US freelancers?

Never. You are priced against their next-best option at value, not against cost of living. Inviting a local-market comparison starts the negotiation at a discount you will never recover in the relationship.