Opportunity cost in one line

Saying no

If your target day rate is £450 and a "small favour" costs two days, you did not earn goodwill worth £900 unless it truly does.

When no is the professional answer

  • Scope unclear after two clarifications
  • Red flags present — client red flags
  • Timeline requires heroics that destroy other clients
  • Budget only works at your floor rate forever
  • Work conflicts with ethics or skill honesty

Scripts (short)

Soft no

I can't take this on for that timeline, but I could start from [date] at [rate], or introduce you to someone else.

Hard no

Thanks — I'm not the right fit. Wishing you a smooth project.

No to scope creep

Happy to include that as a change order: [price], [timeline impact]. Want me to issue it?

Fear that blocks no

  • "They'll never come back" — good.
  • "I need every pound" — then raise rates and cut costs; desperation pricing digs holes.
  • "I'll disappoint them" — disappointing your future self is worse.

Yes, but

Sometimes yes with constraints is correct:

  • Higher rush rate
  • Reduced scope
  • Prepaid block
  • Clear kill criteria

That is negotiation — negotiation — not people-pleasing.

Practice

Decline one low-quality request this month on purpose. Note what happens. Usually: nothing bad, more oxygen.

The maths of one bad yes

Opportunity cost is easier to feel when you put numbers on it. Take a composite example: a freelance developer whose target rate is £450 a day, with a realistic 150 billable days a year.

A prospect offers a three-week project at £300 a day. It looks like £4,500 of income. But it also:

  • Fills 15 of the year's 150 billable days at a third below target. At the target rate those days are worth £6,750, so the yes "costs" £2,250 against the plan.
  • Sets an anchor. If the client returns, they'll expect £300. Raising a rate on an existing client is harder than starting at the right one — see raising rates.
  • Blocks better work. If a £450-a-day enquiry arrives in week two, you can't take it.

None of that means every low offer should be refused. A lower rate can be right for a new niche, a portfolio piece you need, or a quiet month when the alternative is nothing. The point is to decide with the numbers visible, not in the relief of being asked.

A decision rule you can write down

Before replying to any offer below your floor, answer three questions:

  1. Is my calendar for the next six weeks less than half booked?
  2. Does this work give me something I can't get elsewhere (a sector, a case study, a referral source)?
  3. Can I cap it, with a fixed end date and a written scope?

If the answer to all three is yes, a limited yes can make sense. If not, use one of the scripts above. Your pricing page should hold the floor figure, so you're not working it out in the moment, and client red flags covers the signs that a "yes" will cost more than the rate suggests.

Related

Why saying no is a skill

Every yes spends capacity. A weak yes creates a strong future resentment. Clean nos protect delivery quality and reputation.

Scripts

Misaligned budget: “I cannot deliver that outcome in that budget without cutting quality. Here is a smaller scope that fits, or I can introduce someone else.”

Misaligned ethics / red flags: “I am going to pass on this one. Wishing you a good search.”

Full calendar: “I can start after DATE, or we can book a paid discovery later. I will not half-start and stall.”

After the no

Log it. Sometimes the same buyer returns with a real budget. Leave the door open without free consulting — client red flags, capacity.

🐺 Back to Jackals