To qualify a new client before writing a proposal, ask three questions: what must change, who decides, and when. The answers tell you whether to propose, clarify or decline, and they stop you spending a free evening pricing a project that nobody can approve. This guide gives you the three questions, a worked example with a vague ordering-page request, and scripts for the clarify and decline replies. If you want software to hold the answers, the trial checklist lists what to test.
The method is not a statistic. We did not survey freelancers or measure win rates; it is a simple order of operations that you can adapt to your own work.
What qualifying a client is (and is not)
Qualification is a check, before you quote, of the work, your ability to deliver it and the decision process for this particular project. It is not a score of whether someone is a good or bad client, and it is not an interrogation. You do not need a perfect brief. You need enough information to choose an action.
A useful test: if an answer would change what you do next, ask for it before you price detailed work. If it would not, leave it for the kickoff. The longer list of questions belongs in your intake form at kickoff.
The three questions
1. What must change?
Replace the named service with the problem. Compare two fictional inquiries. One says “new website, please”. The other says customers cannot place pickup orders because the order form keeps timing out. The second gives you something concrete to investigate.
A named service is not a scope. “A website” could mean five pages, a booking flow or a complete rebuild, and those are different commitments. Ask what already works, too. Keep the existing pages if they are adequate, identify what needs replacing, and leave unrelated improvements out of the first proposal unless you agree them.
2. Who decides?
Your contact may be gathering information while someone else approves the budget and the scope. Ask the practical version: who reviews the proposal, who can approve it, and what happens if they request changes? Do not infer authority from an email signature or a job title.
3. When?
Separate the desired launch date from the decision date. The launch date is when they want the work; the decision date is when someone can say yes. Allow time for feedback and content from their side, and check your real capacity before promising their preferred deadline.
Budget can be a follow-up. Ask about the working range, explain what affects price, and check that the scope fits before you build an estimate.
| Question | What a good answer sounds like | A red flag |
|---|---|---|
| What must change? | A problem, an outcome and what to keep | Only a service name |
| Who decides? | A named approver and a review path | “I will check with someone” with no name |
| When? | A decision date and a launch date, both plausible | A launch date with no approval date |
Keep assumptions visible
Mark missing answers as missing. Separate confirmed facts from assumptions, and update the record after every conversation. A blank is better than an invented answer, because an invented answer quietly becomes a promise in your proposal.
Four ambiguities to watch for:
- A target date is not an agreed deadline.
- An inquiry is not approved scope.
- A contact name is not proof of authority to approve the work.
- Enthusiasm is not budget.
Worked example: one inquiry, three outcomes
A fictional bakery owner, Priya, sends a request through a public form. She wants online pickup ordering live by December 1 for the holiday rush. The message says her business partner “may need to sign off”.
- What must change: customers cannot order ahead, so a working pickup-order path is the outcome to discuss.
- Who decides: unclear. The partner may approve, but nobody is named.
- When: December 1 is the target launch. No decision date.
The outcome is clear but the approver is missing, so the next action is to clarify before you draft anything. Record that decision in a note so it survives: “Confirm who signs off before drafting a proposal.”
Now change the facts. The launch is next Tuesday and the partner is travelling until Thursday. Urgency does not remove that dependency, even when the inquiry sounds enthusiastic. A Tuesday launch needs approval earlier than Thursday. If that cannot happen, discuss another date. If neither works, decline this version of the project.
Clarify: a short email to copy
Hi Priya, thanks for the details on pickup ordering. Before I put numbers together, two quick things: who signs off on the scope and budget, and when can they look at it? Is December 1 firm or a target? Once I know, I will send you options.
Refer to their request, ask the question that changes your next action, and say what you will do once they answer. Review the draft before you send it.
Decline: a short email to copy
Hi Priya, thank you for thinking of me. A launch next Tuesday is sooner than I can deliver with a sign-off step in the middle, and I would rather say so now than promise something I cannot support. If the date moves, I would be glad to look again.
A decline can be useful: name the constraint, offer an alternative if appropriate, and leave out any promise your capacity cannot support.
Propose: when the answers arrive
Before you prepare the offer, repeat the agreed outcome, confirm the decision process and check the dates together. These answers become inputs to the proposal; how to write a business proposal takes it from there, and how to write a scope of work covers the in-and-out list.
The three outcomes at a glance
| Outcome | Choose it when | Next action |
|---|---|---|
| Propose | The outcome is clear, a decision path exists, dates are credible and you can deliver | Write the proposal using the confirmed answers |
| Clarify | A missing answer changes what you would offer | Send a short question and wait |
| Decline | A known constraint (date, capacity, scope) makes the project unsuitable | Name the constraint, offer an alternative if it fits |
Revisit the decision when answers change
Qualification is not a one-time gate. Confirm the approver. Check the new deadline. Neither automatically solves a separate scope or capacity problem, so check those too. Return to the original inquiry and ask whether the next step is still the right one.
Doing this in Workspace369
Our #1 pick is Workspace369. Per its pricing and feature pages (read October 22, 2026), the pieces fit like this:
- Capture. A configured public intake form captures the context a visitor supplies. You choose the fields, for example the outcome, the approver and the target date. Intake forms and Requests are on every plan.
- Review. The request shows the contact and their message together. A missing approver stands out when the form asks for one.
- Record. Add an internal note with your next action, for example “ask who approves before drafting a proposal”. The note keeps your decision with the request. It does not send a reply, assign a task or qualify the client automatically; the qualification is yours.
- Then propose. When the fit is right, the proposal, deposit and contract tools are on every plan, from Cadet at $29 a month billed monthly for one seat ($23.25 a month billed yearly, $278.99 a year). Cadet through Commander start with a 14-day free trial; a card is required to start.
Limits: Cadet has one seat, and the tool does not score or decide for you. The client portal needs no account but verifies the client’s email with a code; public proposal and invoice links need neither. See the Workspace369 pricing page and the client portal page.
Next step: put the three questions on your intake form
Add “what must change”, “who approves” and “when” to your intake form, then use the answers to pick propose, clarify or decline. The client onboarding process guide shows what to do once a client says yes, and you can try the form and notes in the Workspace369 trial (14 days, card required).
Frequently asked questions
What does it mean to qualify a client?
It means checking, before you write a proposal, that you understand the work, can deliver it and know how the decision will be made. It is not a score of the person; it is a check of this specific project.
What questions should I ask a new client before a proposal?
Three: what must change, who approves the scope and budget, and when they can decide and when the work must be ready. Add a question about budget range if the scope depends on it.
Should I ask about budget up front?
You can ask for a working range as a follow-up, explaining what affects price. Use it to check that the scope fits before you build an estimate rather than as a gate on the first message.
What if the contact says someone else decides?
Ask who, and how the proposal will reach them. Do not draft the full proposal until you know the approver and the review path, because their changes can reshape the scope.
When should I decline a project?
When a known constraint makes it unsuitable, such as a deadline you cannot meet or a scope outside your work. Name the constraint, offer an alternative if one exists and avoid promises your capacity cannot support.
Can software qualify clients for me?
It can capture answers and keep your notes with the request, but the decision is human. Workspace369’s notes do not send replies, assign tasks or qualify a client automatically.
