Before you give a price

Find the budget before you price the work

Eight questions to ask a prospective client. Every one has a neutral business purpose and is useful even if they refuse to share their budget directly. Type the client's answers to get a rough budget tier.

Ethical discovery only. No deception, no false anchors.

How to use this tool

Ask open questions, not yes or no.
Ask about context, not money, until trust is established.
Listen for implied budget signals: team size, funding stage, prior freelancer experience.
Never misrepresent your rate floor. Price anchoring is ethical only when honest.

Use as a script in a call or email thread.

01What timeline are you working with, and what does missing it cost you?
Why this question matters: Urgency reveals priority. Priority reveals budget. A project that blocks a $500K deal is priced differently from one that could wait a quarter.
Your notes on what they said (optional, used to score a budget tier)
02Have you worked with freelance developers on similar projects before, and what went well or didn't?
Why this question matters: Reveals sophistication and rate expectations. Experienced buyers already know market rates.
Your notes on what they said (optional, used to score a budget tier)
03Have you considered an internal build or off-the-shelf tool, and why did this path make more sense?
Why this question matters: Exposes their BATNA (best alternative) and their real value calculation. The answer tells you their ceiling.
Your notes on what they said (optional, used to score a budget tier)
04Who signs off on projects of this size, and what does their approval process look like?
Why this question matters: Reveals organisational scale and budget authority. Reveals timeline-to-close.
Your notes on what they said (optional, used to score a budget tier)
05If this is successful six months from now, what specifically has changed in your business?
Why this question matters: Translates delivery into dollar value for them. Their answer lets you calibrate price to value, not cost.
Your notes on what they said (optional, used to score a budget tier)
06Who owns the system after launch, and what internal support capacity do you have for it?
Why this question matters: Reveals handover complexity and long-term relationship potential. Signals retainer appetite.
Your notes on what they said (optional, used to score a budget tier)
07What range did your team approve for this work, so I can propose the right scope?
Why this question matters: Direct and ethical. Framing proposals to budget avoids over- and under-scoping. Asked after trust is built.
Your notes on what they said (optional, used to score a budget tier)
08What have you spent on similar integration work in the past, if anything?
Why this question matters: Past spending is the strongest anchor for present spending. Asked neutrally.
Your notes on what they said (optional, used to score a budget tier)