Most lists of discovery call questions are built to help you understand the client. This one is built to help you fill in a proposal. Every question below changes a specific number or clause in what you send afterwards — and the last one changes two numbers that you can't renegotiate once the work is done.
The framing matters because the call is not really an interview. It's the only chance you get to price the risk before you're holding it.
The Rule: If the Answer Doesn't Change Your Proposal, Don't Spend the Call on It
"What does success look like?" is a good question that most freelancers already ask. The problem is that a call full of good questions still ends with a quote built on guesses, because none of the answers were tied to anything you write down. Below, each question is paired with the thing it decides.
1. What budget range has already been approved?
Decides: your quote, and whether this person can authorize spending.
Ask for an approved range rather than a number. The word "approved" does double work — it gets you the figure and it reveals whether the person on the call controls the money or has to take it to someone who does.
If they won't answer, offer tiers: "Projects like this usually land in one of three bands — roughly X, Y or Z depending on depth. Which is closest?" A client who won't indicate a range even against tiers is either price-shopping or hasn't got budget approved yet. Both are useful to know before you write anything. Our guide to pricing a freelance project covers turning the range into an actual figure.
2. Who signs off on deliverables?
Decides: your revision cap, and who gets named in the contract.
The answer you want is one name. The answer that predicts pain is several names without a hierarchy — "I'm the main contact, but my partner will want to look, and our ops person has opinions." That isn't a team, it's contradictory feedback arriving in series.
This doesn't mean decline. It means the contract names a single approver, and revisions beyond your cap get billed. Write the name in.
3. What has to be true for this to be finished?
Decides: your scope section, and what counts as out of scope.
Better than "what's the scope?", because it forces a description of the finish line rather than a description of the work. If the answer can't hold its shape for two minutes on a call, it won't hold for two months in production.
Write the answer down verbatim during the call and read it back. That sentence becomes the deliverables line in your scope of work, and everything not in it is a change order.
4. Who supplies what I need, and by when?
Decides: your dependency clause and your timeline protection.
This is the most commonly skipped question and the most common cause of a project going late through no fault of yours. Copy, logins, brand assets, product photos, sign-off on stage one — if any of it comes from the client, your deadline is partly their deadline.
That last sentence, said on the call and repeated in the contract, is what stops "you're late" from being a conversation you lose later.
5. Have you worked with a freelancer before?
Decides: how much of your process you have to write down.
Not a red flag on its own. What it changes is your assumptions: a first-time client doesn't know that revisions are finite, that deposits are normal, that "quick change" has a cost. None of that is bad faith. It just means every norm you'd otherwise leave implicit needs to be explicit in the agreement and explained once, plainly, before it comes up as a conflict.
6. What's your payment process, and what's the cycle?
Decides: your payment schedule and your net terms.
Ask about mechanics, not intent. Does an invoice need a PO number? Is there an accounts payable portal? Do they run payments weekly, or on the 30th? A company that pays on a fixed monthly cycle isn't being difficult, but if you invoice on the 2nd you're waiting an extra four weeks — and that's a scheduling fact you can only work around if you know it before you set the terms.
Vagueness here is the single most predictive answer on the whole call. "We'll sort that out" about money, before any work has started, is when the client is at their most cooperative. It does not improve later. Freelance payment terms explained covers what Net-15 versus Net-30 actually costs you.
7. Where is the business registered?
Decides: your maximum enforceable late fee, and your small claims ceiling.
Almost nobody asks this, and it's the question with the most durable consequences, because both numbers are fixed by the state's law and can't be renegotiated once the invoice is overdue.
Scroll sideways to see all columns
| What varies by state | Range | What it means for you |
|---|---|---|
| Late fee ceiling | 12%/yr (Louisiana) to no cap at all | The standard 1.5%/month is over the line in some states |
| Small claims ceiling | $2,500 (Kentucky) to $25,000 (Delaware, Tennessee) | Whether you can pursue an unpaid invoice yourself |
A $9,000 project is a straightforward small claims filing in Delaware, Tennessee, Texas or West Virginia. The identical project under Kentucky or New Jersey law is above the ceiling and becomes a case that realistically needs a lawyer — which usually means it isn't worth pursuing at all. That's worth knowing before you decide whether to require a 50% deposit.
Our late fee laws by state research covers the ceiling and small claims limit in 34 states, and how to negotiate a freelance contract covers what to do when the client's paperwork names a state that doesn't suit you.
8. Why now?
Decides: your leverage, and your timeline risk.
A project tied to a dated event — a launch, a funding round, a conference, a compliance deadline — behaves differently from one with no forcing function. Real urgency means the budget is likelier to be real and approvals move faster, and it justifies a rush premium. No forcing function means the project can quietly stall for a quarter, which matters if you're holding capacity for it.
9. What happens if the timeline slips?
Decides: whether you need a kill fee clause.
You're listening for whether a delay is survivable or fatal to the project. If the honest answer is that a two-week slip kills it, then cancellation is a live risk and the contract needs a kill fee — a defined percentage payable if they terminate mid-project. Our kill fee calculator works out the figure and the matching wording.
Score the Call Before You Quote
Answer as the call actually went, not as you hope it went. This suggests a deposit and payment structure proportional to the risk, plus the two state-specific numbers from question 7.
Client Qualification Scorer
Suggestions based on common freelance practice, not a credit check. State data covers the 34 states in our late fee research.
Deposit suggestions are conventional ranges, not rules. A high score is a reason to structure the deal differently, not automatically a reason to decline.
Three Things Not to Do on the Call
Don't give a number. A figure said aloud is remembered as a commitment no matter how many times you call it a ballpark, and it anchors everything afterwards. Say you'll send a written quote, and name when.
Don't fill silences. After you ask about budget, stop talking. The pause is uncomfortable for about four seconds and then it gets answered. Freelancers lose more information to nervous talking than to clients withholding it.
Don't skip the follow-up email. Send a summary the same day: what you understood the project to be, what they're providing, what happens next, and by when. It catches misunderstandings while they're still cheap, and it becomes the reference document if the scope drifts. Project kickoff email templates and the client intake form generator cover the written side.
Turn the answers into a proposal. The free client proposal generator builds scope, timeline and payment terms into a document you can send — no login.
Open Proposal Generator →Frequently Asked Questions
What questions should a freelancer ask a client before quoting?
Ask the ones whose answers change a number in your proposal rather than the ones that build rapport. The core set is: what budget range has been approved, who signs off on deliverables, what has to be true for this to be finished, what happens if the deadline slips, who supplies the inputs you depend on, have they hired a freelancer before, what is the payment process and cycle, where is the business registered, and why is this being done now. Each answer maps to a specific term: the budget answer sets your quote, the approver answer sets your revision cap, the inputs answer sets your dependency clause, and the registration answer sets your late fee ceiling and small claims limit.
How do I ask a client about their budget without losing the job?
Ask for a range that has already been approved rather than a number, and give a reason tied to their outcome: you want to know which version of the project is realistic before spending their time on a proposal for the wrong one. Phrasing it as approved budget also surfaces whether the person on the call can actually authorize spending, which is a separate and equally useful piece of information. If they refuse entirely, offer two or three pre-set tiers and ask which one is in range. A client who will not indicate a range even against tiers is usually either price-shopping or has no budget approved yet.
Why should I ask where the client's business is registered?
Because it decides two numbers you can't change later. First, the maximum late fee rate you can enforce: most states let commercial parties write in any rate, but Arkansas caps written-contract interest at 17%/year, Louisiana at 12%, and Texas sets an 18% commercial ceiling. Second, the small claims ceiling, which decides whether an unpaid invoice is something you can pursue yourself. Kentucky stops at $2,500 and New Jersey at $3,000, while Delaware and Tennessee both go to $25,000. A $9,000 project is a straightforward small claims filing in one state and a lawyer-sized problem in another.
What are the biggest red flags on a discovery call?
Three predict trouble more reliably than anything else. A request for a price before any scoping question has been answered signals that cost is the only filter being applied. An unclear approval chain, where several people will weigh in without a stated hierarchy, predicts contradictory revisions. And a client who has never hired a freelancer before is not a red flag by itself but does mean every process assumption you hold has to be written down rather than assumed. None of these require walking away. They require a larger deposit, a firmer revision cap, and a named approver in the contract.
Should I send a quote on the discovery call itself?
No, and the reason isn't negotiating posture. A number given on a call is remembered as a commitment even when you called it a ballpark, and it anchors every later conversation regardless of what you learn afterward. Say instead that you'll send a written quote within a set time, and name the time. If the client presses for a figure, give a range wide enough to be honest, tied explicitly to the unknowns you've just identified on the call, and repeat that the written version follows.
The call is where a project's terms are actually set — the contract just records them. If you leave with nine answers written down, the proposal takes twenty minutes and defends itself.