How to answer a client effectively

TL;DR

Summary

Answering a client means structuring your response in 4 steps: describing the context (rephrase to prove understanding), presenting the approach (broad then detailed), showing examples (prove with concrete evidence), and displaying the pricing (reassure through transparency).

Goals

• Show the client you’ve understood their problem before talking solution
• Structure your proposal so it’s readable, credible, and convincing
• Handle objections and follow up professionally

Introduction

Definition

Responding to a client is a daily event in a professional’s life. Whether you’re a freelancer, a salesperson, or part of a team, this step matters a lot for working with other people.

What sets a good response apart from a bad one is rarely technical expertise. It’s the ability to show that you’ve understood the problem. A client who feels understood is a client who trusts you. And trust is the prerequisite for any collaboration.

The 4 main steps:

• Describing the context
• Presenting the approach (broad then precise)
• Demonstrating with examples
• Displaying the pricing

The 2 main types of engagement

There are broadly 2 types of engagement:

• If you’re on a time-and-materials basis, you have a means commitment and you’ll bill the time spent working (often called daily rate, the cost per day of your involvement)
• If you’re on a fixed-price basis, you have a results commitment and you’ll bill a single price regardless of the time you spend

The 4 steps of responding to a client

1. Describing the context

In one word, REPHRASE!

The challenge: let the client check that you’ve understood them. In 4 key points, describe their situation. First, briefly describe your client’s business. Then, use the CAR template: CONTEXT / ACTIONS / RESULTS.

1. Quick description of the company (sector, business, size, or any indicator that helps grasp the company)
2. Description of the starting situation in a very factual way
3. Description of actions already taken
4. Description of current results

To this, add the goals of the engagement to wrap up the context phase.

Rephrasing is a direct application of active listening: it proves you’ve listened, understood, and synthesized. It’s also a chance to clear up any misunderstandings before committing to an approach.

Example 1: a request from a dental practice

Slide 1: “An appointment management solution was rolled out and isn’t working for you.”

• The MARCAND practice has specialized in dental prosthetics since 2012. The company has 5 employees in 2019.
• In January 2019, you decided to digitize your practice by installing a new appointment management tool.
• You trained the 2 assistants on this new tool with PowerPoint materials you provided.
• Despite these materials, many booking issues are coming up: double appointments, “surprise gaps” in the agenda.

Slide 2: “You want to understand where the problems come from so you can identify a more effective solution.”

• We propose to interview team members and patients before delivering a list of recommendations. This will let us efficiently identify a solution and adapt the way training messages are highlighted.
• Engagement goals:
  • Study a range of appointment booking solutions
  • Roll out an appointment booking solution suited to your usage
  • Train your users on the tool

Example 2: a request from an e-commerce site

Slide 1: “Your e-commerce site is seeing an abnormally high cart abandonment rate.”

• The NATUREO brand has been selling organic cosmetics online since 2020. The company makes 800,000 euros in annual revenue with a team of 8 people.
• In 2025, you launched a redesign of your e-commerce site on Shopify to modernize your image and improve the shopping experience.
• Since the launch, your team has observed a cart abandonment rate of 78%, 15 points above the industry average.
• Despite email recovery campaigns and adding free shipping, the rate hasn’t dropped significantly.

Slide 2: “You want to identify the barriers to purchase to reduce the abandonment rate and increase your conversion rate.”

• We propose to run user testing on the current checkout flow, combined with an analysis of analytics data, to precisely identify friction points.
• Engagement goals:
  • Identify the causes of cart abandonment (UX, trust, performance, price)
  • Propose concrete and prioritized recommendations
  • Prototype and test the most promising solutions
  • Support the rollout of the improvements

In both cases, the structure is identical: describe the situation (facts), show you’ve understood the problem, then state the goals. The client recognizes themselves in your description.

2. Presenting the approach

Present your approach in 2 steps:

• The broad approach
• The more precise approach

First, explain your approach broadly with the main elements of each step.

For example (dental practice)

• EXPLORATION: Interviews with the assistants and 5 patients
• ANALYSIS: Experience map, benchmark of existing solutions
• WORKSHOPS: Ideation, story mapping

For example (e-commerce site)

• AUDIT: User testing (5 participants), analytics analysis
• DIAGNOSIS: Synthesis of identified barriers, prioritization by impact
• DESIGN: Wireframes of improved flows, interactive prototype
• VALIDATION: User testing on the prototype, comparative measurement

Then, for each step, give more details about the activities you’ll run.

If you’re on a fixed-price basis, give a precise list of deliverables you’ll provide for each of your steps. A deliverable is a concrete document (PPT, PDF, DOC, source file…) that you’ll send to the client.

3. Demonstration with examples

For each step you present, add examples of deliverables you’ve already produced, summaries of past engagements, or anything else that backs up your claims.

If you don’t have any, 3 options:

• Create some on an internal project: the main thing is that you’ve already applied this approach. A fictional but well-executed project beats nothing.
• Use visuals found online: this approach is riskier because it doesn’t prove you’ve actually done the task in question. Be ready to address this in your delivery.
• Don’t include examples: I’d advise against this. It’s always more reassuring to have deliverable examples early on so you’re aligned on the upcoming output.

4. Pricing

Once the approach is presented, indicate the number of days you estimate. It’s not mandatory but it’s very reassuring for the client.

Estimate effort (number of days) per major activity. Add these together to get the total effort.

To get the cost of the engagement, multiply your total effort by your daily rate (your day rate) and/or those of your colleagues. You’ll get a pre-tax amount you can propose to your client.

Example phrasings

• Time-and-materials: “We estimate a time-and-materials engagement of 20 days at a daily rate of 500 euros pre-tax, for an estimated envelope of 10,000 euros pre-tax. Payment will be made at the end of the month based on the time spent by the consultant.”
• Fixed-price: “We propose a fixed-price envelope of 8,500 euros pre-tax for this engagement. Payment will follow this schedule: 50% at the start of the engagement and 50% on delivery of the final deliverable.”

Tip: if your engagement is significant, propose a 3-step schedule (30% at kickoff, 40% mid-way, 30% on delivery). This reassures the client because they pay as you go, and it secures your cash flow.

Written proposal vs oral pitch

The 4-step method works just as well in writing as out loud, but the form changes.

The written proposal

The written proposal (often a PDF or a slide deck) has to be self-contained: the client should be able to understand it without you. It’s often this document that will circulate internally at the client’s, with people you’ve never met.

Best practices:

• One slide per idea. Never overload a slide.
• Put the important numbers big and the details small.
• Include a table of contents at the start of the document.
• End with a summary slide that recaps scope, timeline, and budget at a glance.
• Mind the layout: a well-presented document inspires trust.

The oral pitch

Out loud, you can be more concise on slides because your voice carries the content. The key is to tell a story: the client’s problem, your understanding of that problem, your approach to solving it, the proof that it works.

Best practices:

• Start by rephrasing the client’s problem in their own words. It’s the best way to grab attention.
• Never read your slides. Use them as visual support, not a teleprompter.
• Plan time for questions. The decision often plays out during the questions.
• Adapt your level of detail to your audience: a CEO wants the high-level view and the ROI, a tech lead wants method details.

To structure your oral argument, see the article on pitching.

Handling objections

Objections aren’t refusals. They’re signals of interest. A client who objects is a client who’s thinking about the feasibility of your proposal. A disinterested client doesn’t even bother to object.

”It’s too expensive”

It’s the most common objection. Several strategies:

• Break down the price. “The total budget is 15,000 euros, but spread over 3 months that’s 5,000 euros per month. For a team of 50 people, that’s 100 euros per user.” Once broken down, the price often looks more reasonable.
• Compare to the cost of inaction. “Your cart abandonment rate is costing you about 200,000 euros in revenue per year. Our engagement aims to reduce that rate by 15 points, which would represent a 40,000 euros annual gain.”
• Propose a reduced scope. “If budget is a constraint, we can start with the audit phase alone (5 days, 2,500 euros pre-tax). The results will let you decide with full information.”

Never slash your price. Cutting your rate without cutting scope sends a negative signal: either you were too expensive in the first place, or you don’t value your work.

”We don’t have time”

This objection often hides a question of priority rather than time.

• Show that not acting also takes time. “Each month that goes by with the current system, your assistants spend 2 hours a week handling scheduling errors. Over a year, that’s 12 working days lost.”
• Propose a lighter format. “We can start with a 2-day express audit that will only require 2 hours of your team’s time in total.”
• Adjust the schedule. “We can spread the engagement over a longer period to minimize the impact on your day-to-day."

"We already have a designer / an agency”

This objection is a chance to position yourself as a complement rather than a competitor.

• Value the existing work. “That’s a good thing. Our engagement focuses on the user research phase, which will feed your designer’s work with field data.”
• Propose a neutral audit. “I’d suggest an outside look at the current journey. A fresh eye can spot things the in-house team no longer sees because they’re too close.”
• Show your specialty. “Our expertise is specifically in user research and testing. We regularly work in tandem with internal design teams.”

Following up after the proposal

Sending a proposal and passively waiting for a reply is a classic mistake. Follow-up is part of the sales process.

Follow-up timing

• D+1 after sending: a short note to confirm receipt and offer yourself for questions. “Just wanted to make sure you got the proposal. Let me know if any points need clarifying.”
• D+5 to D+7: a more substantive follow-up. Share something of value (a relevant article, a case study tied to their problem) rather than just asking “So, have you decided?”
• D+14: if you still haven’t heard back, a final courteous note. “I understand priorities shift. If the project is still relevant, I’m available. Otherwise, please don’t hesitate to let me know, that’s perfectly fine.”

Best practices for follow-up

• Never be pushy. Pressure doesn’t work and damages the relationship.
• Bring value with every contact. Each message should give something to the client, not just ask for something.
• Accept refusal gracefully. A “no” today can become a “yes” in 6 months. Keep the door open.
• Ask for feedback in case of refusal. “Could you tell me what tipped the scales? It would help me improve.” The most valuable input often comes from projects you didn’t win.

Going further

• The pitch: to structure your oral argument
• Active listening: to better understand the client’s request
• Feedback: to handle client responses and keep improving
• Exploratory interviews: the same listening method, applied to user research