The Rate Conversation Most Contractors Handle Badly

by Eric Hanson, Backend Developer at Clean Systems Consulting

The moment a client asks "what do you charge?" is a hinge point in every contractor engagement. Most contractors fumble it in one of three predictable ways.

The Three Common Fumbles

Fumble one: Asking what the client's budget is before naming a rate. This happens because contractors are afraid of anchoring too high. But when you ask for the budget before naming your rate, the client either gives you a number that anchors the conversation at their ceiling (which is usually lower than your actual rate) or they feel like you are fishing for information and it creates a vague, uncomfortable dynamic.

Fumble two: Giving a range. "I charge between €80 and €150 depending on the project." The client hears the lower number and the conversation starts there. Ranges feel like negotiating against yourself before the negotiation has even started. State a number, not a range.

Fumble three: Apologizing for the rate. Not always literally, but the pattern is recognizable — softening the number with qualifications, explaining it unprompted, or lowering it preemptively because the silence after stating it felt long. Silence is normal. Wait through it.

Why This Moment Matters More Than It Should

The rate conversation is awkward for almost everyone, which is part of the reason it goes badly so often. But it matters disproportionately because it sets the tone for the entire working relationship.

A contractor who is confident and clear about their rate signals: I know what I am worth, I have done this before, and I expect to be treated professionally. A contractor who hedges and qualifies their rate signals the opposite — even if the rate itself is exactly right.

Clients take their cues from the contractor's confidence. A rate stated clearly and without apology is much easier for a client to say yes to than one delivered with visible anxiety.

How to Handle the Question Well

The sequence that works:

  1. State your rate directly. "My rate is €X per hour" or "my project fees typically start at €Y for this scope of work." One sentence. No preamble.

  2. Wait. Do not fill the silence. The pause belongs to the client now. Let them think.

  3. If they push back, ask what they had in mind before you adjust anything. "I understand — what range were you working with?" This gives you information without immediately conceding. Sometimes the pushback is reflexive and the client's number is actually workable. Sometimes there is a real gap and you need to decide what to do with it.

  4. If the gap is real, decide. You can negotiate (if the engagement is genuinely compelling), propose an adjusted scope (if project-based), or decline professionally (if the gap is too large). All of these are valid. The one thing that is not valid: accepting a rate that makes you resentful.

Timing Matters

The worst time to have the rate conversation is when you are deep in a discovery call and the client is excited about working together. The pressure to say yes is highest, the information you have about the scope is still incomplete, and any number you give is underinformed.

The best practice: establish rate range early, before detailed scoping. A brief note in initial outreach or an early email — "for context, my rates for this type of work start at €X" — filters out budget mismatches before anyone invests significant time. The clients who respond after seeing that number are already self-qualified.

The Language That Works

Precise and confident language, not hedge-y and vague:

  • "My rate for this type of engagement is €120 per hour." ✓

  • "I typically charge somewhere around maybe €100 to €140 depending on various things." ✗

  • "Based on the scope you've described, I'd price this project at €15,000." ✓

  • "I'm thinking maybe somewhere in the range of €10,000 to €20,000, give or take." ✗

The confident version does not sound arrogant. It sounds like someone who knows their business. That is exactly the signal a client needs at this stage of the conversation.

The rate conversation is not a negotiation — it is a reveal. How you reveal it tells the client everything about how you will handle the hard conversations that come later.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Logging Across Microservices Is Useless If You Can't Connect the Dots

Logs from individual services are only as useful as your ability to correlate them across service boundaries. Without structured logging and a consistent correlation ID strategy, your logs are evidence without context.

Read more

Why Remote Contractors Deliver Faster Than Office Teams

Remote contractors focus on results, not office presence. With fewer meetings and clearer scope, work moves faster and more efficiently.

Read more

Why Remote Contractors Who Write Well Get More Work

In remote work, you are your words. The quality of how you write determines how much you are trusted, how clearly your value comes across, and how often you get hired.

Read more

Why Tallinn's Digital-First Startups Are the Most Natural Fit for Async Remote Backend Contractors

Estonia built its entire national infrastructure on the assumption that digital-first is just how things work. Its startups carry that assumption into how they operate — and it makes async contracting a natural fit.

Read more