A client interview is a two-way fit check: understand the problem, explain your process, and identify risks before work starts.
Avoid
- Promising a price or deadline before understanding the brief
- Talking only about yourself
- Giving unlimited revisions or vague deliverables
- Speaking negatively about old clients
- Failing to summarise decisions in writing
Ask what outcome matters, who approves work, what assets exist, what deadline is fixed, and how feedback will be collected. Send a written summary of scope, assumptions, and next steps after the call.
Prepare a short interview sheet
Before the call, write the client’s stated goal, the likely deliverables, three questions, and one relevant sample. During the conversation, listen for hidden constraints: missing assets, several decision-makers, a fixed launch date, an existing tool, or a result that cannot be measured. Ask permission before recording any call and respect the client’s privacy.
Discuss scope without sounding difficult
Use neutral language: “That change would add a new deliverable, so I would quote it separately,” or “To meet Friday’s deadline, I would need the final copy by Tuesday.” Specificity is more professional than agreeing immediately and hoping the details work out later.
End with written next steps
Send a short recap with the objective, deliverables, exclusions, deadline, feedback owner, payment milestone, and the information still needed. If the client cannot describe who approves the work or keeps changing the goal, pause before committing. A good interview protects you from a bad-fit project as much as it helps you win a suitable one.
Never pay a recruiter or client to receive work, install unknown software, or share passwords. Verify the person and company through independent channels before sending confidential information.
Use the interview to qualify the project
Ask who the audience is, what result matters, what already exists, who approves the work, what deadline is fixed, and what feedback process will be used. Listen for contradictions—for example, a very short deadline with no assets or several people who can change the brief. These signals do not automatically mean “no,” but they should affect scope, price, and milestones.
Explain your process in plain language
Describe the first deliverable, what you need from the client, how you handle feedback, and when you will communicate progress. Avoid claiming certainty about sales, rankings, or other outcomes you cannot control. If you need to research an answer, say so and follow up rather than guessing during the call.
Close with written terms
Send a recap with scope, exclusions, deadline, payment points, revision limits, and the next action. Do not start from a verbal promise alone. Verify unfamiliar companies and never pay for access to a job or install unknown software at a client’s request.
Prepare evidence before the call
Bring one relevant sample, a short description of your process, and three questions. Know which parts of the brief are clear and which are assumptions. This allows you to discuss the project rather than improvising a promise. Do not show confidential work, record a call without permission, or share a client’s private information as proof.
Listen for project health
A healthy brief has an outcome, audience, decision-maker, assets, deadline, and feedback path. If any of these are unclear, ask how the gap will be resolved. Several people giving uncoordinated feedback, a deadline before the required assets exist, or a demand for unlimited changes should affect the milestones and price. These are not automatic reasons to reject a project, but ignoring them creates avoidable risk.
End the interview with a written recap
Summarise the objective, deliverables, exclusions, schedule, payment points, number of revisions, and next action. Ask the client to correct anything inaccurate before work begins. Written clarity protects both parties when a friendly conversation is remembered differently a week later.
Never pay to receive a job, install unknown software, provide a password or OTP, or accept suspicious payment instructions. Verify unfamiliar companies through an independent channel.
Prepare evidence, not a memorised speech
Prepare two short examples that explain the problem, your role, the steps you took, and the result or next test. If the example is practice work, say so. Review the client’s brief and identify one useful question before the call. This preparation helps you answer clearly without pretending to have experience you do not have.
Clarify the working relationship
Ask who approves the work, how feedback is shared, which files are supplied, what the first milestone contains, and how changes are handled. Confirm the deadline and communication window in writing after the call. Avoid agreeing immediately to an undefined scope just to appear enthusiastic. A professional interview is also your chance to identify missing information, unrealistic expectations, or unsafe payment requests.
Close the interview carefully
End by repeating the agreed problem, first deliverable, open question, and next decision. Send a short written recap and wait for confirmation before starting unpaid work. If the client refuses to define scope, asks for credentials, or pressures you to bypass the platform’s payment process, treat that as a risk signal. A respectful interview should leave both sides clearer than when it began.
