What do you charge? The four seconds that decide the price

Six minutes into a first call, before you have asked a single question about the work, the client says: "so what do you charge?"

The next four seconds set the ceiling on the whole engagement. Most freelancers have a rate and no answer: the number is written down somewhere and has never been said out loud, so when it is needed they improvise, and the improvised number is almost always lower than the one they wrote that morning.

This post is about that moment. Not what to charge, which is a separate calculation with its own arithmetic, but what to say and when.

One enquiry runs through the post. An operations lead at a forty-person company wants "some kind of reporting dashboard" — an illustration, not a real client; substitute your own figures. Say your floor is $95 an hour and the build is realistically 180 hours. The improvised answer at minute six is usually "around twelve thousand?", because improvisation reaches for a number you are confident of winning. Twelve thousand across 180 hours is $66.67 an hour, which is what the effective hourly rate calculator tells you at project close, four months too late.

One thing early: there is no published data on freelance close rates by pricing approach. Nobody measures it, and anyone telling you ranges close 30% better than fixed numbers is quoting a blog that made it up. What follows is mechanism, not evidence.

The same question arrives in three different rooms

Most advice treats this as one question with one answer. It is three.

Before scope is known — on a call, in a DM, two minutes into a referral introduction. The dangerous one: any number you say becomes the reference point for everything after it, every later figure gets discussed as a movement away from it, and you produced it before you knew what you were pricing.

After scope is known. You know the shape and they ask for the number. Easy, and people still ruin it by burying the figure inside a paragraph of justification.

In writing, from a stranger, with no detail. "Hi, can you send me your rates?" The answer there is neither a number nor a refusal.

Before you know the scope, answer the question they actually asked

The client asking at minute six is not asking what the invoice will say. Neither of you knows yet. They are asking whether you are in their range, so they can decide whether to keep spending time on this call.

That question deserves an answer. Refusing costs you the deal, because "it depends" alone reads as inexperience or as the setup for a large number later.

So answer the budget-fit question and skip the total. Three parts, one breath, fifteen seconds: concede that it depends, say what it depends on, name the next step that produces a real figure.

The reframe is a promise of specificity rather than a deflection. "Ten minutes of questions and I can tell you which version you're buying" means much the same as "it's hard to say without more information." One solves their problem now. The other asks them to wait.

A range helps until they only hear the bottom of it

A range answers the budget-fit question faster than anything else, which is why it is the standard advice. What the advice leaves out is that the client hears both numbers and remembers one.

The bottom becomes the new ceiling. Every conversation after it starts there and works downward, and you spend the deal explaining why your quote is higher than the figure they already gave their boss.

Two rules.

Say the top number first. "These run up to about $28,000 for the full thing; there's a narrower version nearer $16,000." Reverse the order and $16,000 becomes the price of everything they described, with $28,000 sounding like the upsell.

Attach the bottom to a smaller scope, never to a discount. $16,000 buys three dashboards with no data cleanup. It is not $28,000 with a favor applied. Once the bottom of your range is a discount rather than a different deliverable, you have told the client your prices are soft and the only question is how hard to push.

There is also a width limit. If the top is more than roughly double the bottom, that is not a range but an admission you have no idea; say so and ask for the scoping conversation instead. And if you would be miserable delivering the $16,000 build, do not name it — you have published a price for something you do not sell.

After the number, say nothing

The most expensive habit here takes six seconds. You state the price, the client does not immediately respond, and you keep talking.

What comes out in that gap is justification nobody asked for, a pre-emptive discount, or a smaller package offered before they have reacted. Each hands over a negotiation they had not yet opened.

The pause is almost always arithmetic. They are checking your figure against a spreadsheet, working out who else has to approve it, or writing it down. That takes four or five seconds, and silence on a video call feels three times its length.

What it almost never is: disgust. Even when it is a real price objection, the response is a question rather than a concession. The multi-day version, where the client goes quiet for a week and you email offering ten percent off, is worked through in the stage-by-stage guide to losing deals. The four-second version is more common, because it happens on every call.

If you cannot hold the silence, ask a question that hands them the turn. "Does that sit within what you'd set aside?" transfers the obligation to speak without moving your price.

Three scripts, annotated

Bracketed placeholders are yours to fill.

The pre-scope answer, spoken

Depends on the shape of it, and I'd rather give you a real number
than a guess.

Builds like this run up to about [$28,000] for the full version.
There's a narrower one — [three dashboards, no data cleanup] —
that lands nearer [$16,000].

Which end you're at comes down to [how many source systems there
are] and [whether anyone's cleaning the data first]. Ten minutes
of questions and I can tell you which one you're buying.

Line one concedes the honest answer and disarms it in the same breath. Cut it if you have quoted this shape of work twenty times; the hedge slows the sentence down.

Top number first, and the narrow version described by what it contains rather than what it lacks. Never introduce the lower figure with "or if budget's tight."

Naming the two variables is the cheapest thing you will give away all week. It starts the scoping conversation whether or not you get the call, and teaches the client that the price follows their decisions.

"Ten minutes of questions" is a bounded ask; "let's set up a discovery session" asks for an hour and gets declined more often. If you cannot bound the top number honestly, cut both figures and keep the last two sentences.

The post-scope answer, spoken

It's [$24,500].

That covers [the five dashboards], [the two data sources we
listed], one round of changes after handover, and the training
session. It doesn't include [the ETL rewrite] — I'd scope that
separately if you want it.

I'll put it in writing this afternoon, with a valid-until date.

The number gets its own sentence with nothing in front of it. No "so I've had a think about this." Preamble is where apologies live, and a sentence that starts apologetically is hard to steer out of.

Quote the figure your arithmetic produced rather than rounding to $25,000. Whether buyers read precise numbers as more considered I cannot tell you; rounding costs $500 and buys nothing.

The exclusion line is load-bearing. Naming one thing the price does not include stops the number being quietly reattached to a larger job in six weeks.

The last line goes before they respond, and moves the deal out of memory into a document. The whole script runs fifteen seconds. Then you stop and let the silence do what it does.

The cold email with no detail in it

Subject: Re: [their subject line]

Thanks for getting in touch.

Rates on their own aren't much use without knowing what the work
is, so rather than send a list: most of what I do lands between
[$6,000] and [$30,000] a project, and I price the project rather
than the day.

If you can tell me what you're trying to have working, by when,
and who else is involved in the decision, I'll come back with a
real figure or tell you I'm not the right fit.

Keep their subject line. A fresh one starts a new thread and loses the reply.

The refusal to send a rate card is a reason, not a rule. A rate card sent cold gets filed, forwarded internally, and compared against numbers you never see.

A wide range works here in a way it does not on a call: nobody has to react in real time. Two questions, not five — cold enquiries die on effort.

Where the enquiry does arrive with real detail — a defined outcome, a date, a named budget — send the priced document instead of any of this. The proposal generator builds a branded PDF with scope, pricing and payment terms in the browser, no signup and no watermark, which beats three more emails. What belongs inside it is its own post.

Some enquiries deserve a question, not a price

Sometimes the right answer to "what do you charge" is not an answer, and the tells are consistent. No company name, or a reply-to on a free mail domain. A request for a full quote before any conversation, or a budget attached to a scope that does not exist yet. A sender collecting rates rather than buying: an agency assembling a bid, a recruiter benchmarking, a procurement inbox building a vendor file.

The response is one qualifying question rather than a figure. "What's the deadline you're working to?" or "who's the end client here?" costs a sentence and separates the real projects immediately.

The client screening post separates fraud signals from ordinary disorganization, and covers how to check that a company exists and pays. Whether a legitimate project will be profitable is a different filter, and the five questions that predict margin run before you agree to anything.

Same day, in writing, or the number drifts

A price agreed on a call and never confirmed in writing is the most reliable source of a scope argument later. Two people leave the call with the same number and two different scopes attached to it. The number survives in both memories perfectly; the conditions around it decay within a week, in the direction that favors whoever is paying.

So the written version goes out the same day with four things in it: the figure, what it buys, one explicit exclusion, and a date it expires. The quote generator handles the valid-until date alongside line items and tax, and Worklyn's contracts go out for signature from the agreed scope rather than being retyped.

Tool choice matters here. Client-management suites are priced for the whole workflow — Dubsado's Starter tier is $335 a year — and most will print any number you type without checking it against the floor you calculated. That gap is the argument on the Dubsado alternative page.

What to do before the next enquiry lands

In the next 30 minutes: say the pre-scope script out loud, ten times, until your top number comes out flat. It will feel ridiculous, and it is the only part of this that changes the call, because the improvised answer only turns up when a rehearsed one does not exist. Then write your top and narrow-scope figures where you can see them mid-call.

This month: on the next five enquiries, say what the price depends on before you say a number, and send the written version the same day on all five. At each project's close, compute the effective hourly rate and compare it against what you said in the first four seconds. That comparison is the only feedback loop this skill has.

Worklyn turns the number you agreed into a proposal, then a contract, then an invoice without retyping it, so the scope attached to the price on Tuesday is still attached in November.