Vod Bolina  ·  Full System
Asset 15 · Objection Handler
The Freelancer Launch System · Session 6 of 8

The "What's Your
Rate" Objection Handler

Scripted, calm responses for the moments pricing conversations get tense. Built from common patterns in this market — not from a real objection yet, since you haven't had one. Read this before your next call, not during it.

June 2026  ·  Offer & Pricing  ·  Asset 15 of 23
A note on this document: You haven't faced a real pricing objection yet — your one outreach attempt didn't reach a pricing conversation. These scripts are built from the most common objections Remote Operations Specialists in this market typically hear, not from your actual experience. Treat this as a rehearsal script, not a transcript. Once you start having real conversations, tell your coach what objections actually come up — we'll refine this with real data after that.
Before any objection comes up

3 Core Principles

01
Pause, don't panic
A pushback on price is not rejection. It's almost always a request for more justification — give it calmly.
02
Never apologize for the number
Your rate reflects 10+ years of enterprise experience. Defending it, not apologizing for it, is the job here.
03
Adjust scope, not value
If budget is real, change what's delivered — never silently discount the same scope to save the deal.
Objection 01 · Most common
"That's a bit higher than we expected."
What's actually happening: They're often not rejecting the price — they're testing whether it's negotiable, or they genuinely compared you to lower-cost VAs without understanding the difference in experience.
Copy this
Totally fair to ask. I'll be upfront — my rate reflects 10+ years inside enterprise financial operations, not general admin support. That usually means fewer revisions, faster turnaround, and someone who already understands compliance requirements without needing it explained. If budget's a real constraint, I'm happy to look at adjusting the scope to fit — what range were you working with?
Never say: "I can come down a bit" before they've told you a number — that trains them to push further.
Objection 02
"Can you do it cheaper?"
What's actually happening: A direct ask for a discount on the same scope. This is the moment to redirect to scope reduction instead of price reduction.
Copy this
I keep my rate consistent so I can stay focused on quality rather than cutting corners. What I can do is adjust what's included to fit your budget — for example, we could start with the CRM audit and fix instead of the full setup, and revisit the rest once you've seen the results. Would that work better?
Never say: "Sure, I can lower it" — always pair any flexibility with a scope change.
Objection 03
"I found someone on [platform] who charges $8/hour."
What's actually happening: They're comparing you to a general VA on price alone, without distinguishing the experience gap. This needs reframing, not defensiveness.
Copy this
That's a really different kind of role, honestly — general VA support and financial operations work solve different problems. I'm not the right fit if you're looking for low-cost general admin help. Where I come in is when the work involves things like compliance-sensitive data, CRM logic, or processes that are expensive to get wrong. If that's not the situation here, totally understand — happy to part ways with no hard feelings.
Never say: anything that disparages other freelancers — reframe the category, don't attack the competitor.
Objection 04
"Can you just throw in [extra thing] for the same price?"
What's actually happening: Scope creep, usually well-intentioned but easy to let slide. This needs a friendly but firm boundary before the project even starts.
Copy this
Happy to include that — it would just shift this into the [next tier up / add roughly X hours], so the total would adjust to [new price]. Want me to update the proposal with that included, or keep it as a follow-on once the first phase is done?
Never say: "Sure, no problem" without naming the price change — silent scope creep erodes your rate over the whole project.
Objection 05
"We need to think about it / check with the team."
What's actually happening: Often genuine, sometimes a soft no. The goal here isn't to pressure a yes — it's to get a clear timeline so the conversation doesn't quietly die.
Copy this
Of course, makes sense. Roughly when do you think you'll have an answer? I'll follow up around then — and if anything changes or questions come up before that, feel free to message me anytime.
Never say: "Just let me know" with no timeframe — always anchor a follow-up date.
Objection 06
"Do you offer a free trial / sample work first?"
What's actually happening: A trust-building request. Sometimes reasonable, sometimes a way to get free work. The line is offering proof of capability without giving away billable work.
Copy this
I don't do free trial work, but I get wanting some assurance before committing — that's fair. I can walk you through examples of similar work I've done, or we could start with the smallest package (the CRM Quick Fix) as a low-risk way to see how I work before going further. Would either of those help?
Never say: agree to unpaid "sample work" on their actual project — redirect to your smallest paid tier instead.
The Freelancer Launch System

Hold the Line.
Adjust the Scope.

Asset 15 of 23 · Session 6 of 8 · Vodner "Vod" Bolina