Most businesses lose customers not because their offer is weak, but because they’re solving for the wrong thing. They build websites, campaigns, and sales pitches around what they assume customers want, instead of the situation the customer is actually trying to resolve. David S. Duncan’s book The Secret Lives of Customers makes this point clearly: customers act based on what they’re trying to fix in the moment, not on some fixed list of preferences a business has projected onto them.
I’ve spent years working across design, web development, digital marketing, and data analytics, and I’ve watched this gap show up in nearly every client relationship I’ve had. The businesses that grow predictably are the ones that stop guessing at what customers value and start paying attention to the real decision context. The ones that stall are usually still building for an assumed customer instead of the one actually in front of them.
To make this practical, I use a framework I call CLEAR: Context, Language, Evidence, Action, Reassurance. It’s not something I invented in the abstract. It came out of patterns I kept seeing across real client work, and it maps directly onto the lessons in Duncan’s book.
Context: Read the Situation Before You Respond to the Request
Every customer interaction happens inside a specific moment, not in a vacuum. Urgency, prior experience, budget pressure, and risk tolerance all shape how a person evaluates what you’re offering. Two people can look at the exact same proposal and respond in completely different ways, not because the offer changed, but because their situation did.
This shows up constantly in how I work with new clients versus long-term ones. A new client is almost always more cautious than a returning one. Often they’ve been burned before, whether that’s a vendor who disappeared mid-project, missed deadlines, or work that didn’t match what was promised. So a new client tends to want to test the waters before fully committing to a larger engagement.
What eases that caution, in my experience, is being their single point of contact throughout the relationship. There’s no runaround, no hierarchy of people to work through, just direct access to the person doing the work. Over time, that consistency builds trust, and the same client who once hesitated becomes a long-term relationship where commitment is no longer a question. It also becomes an advantage for the client themselves. Once they see the value of ongoing support, they can plan and budget for it annually instead of treating every project as a one-off decision.
The takeaway here is simple: don’t treat every client interaction the same way. A cautious, new relationship needs a different approach than an established one, and reading that context correctly is the first step to getting the rest of the engagement right.
Language: Reframe the Offer Around the Outcome, Not the Deliverable
A common pattern I see with new clients is that they come to me with a fixed idea of what they want, usually a description of a deliverable rather than an outcome. Someone wants “a new website” or “a logo refresh” without stepping back to consider the bigger picture of what that deliverable is actually supposed to do for their business.
A website isn’t an online brochure. It’s a lead generator. It’s a salesperson working around the clock. It’s a customer service touchpoint, a message board, a front desk for a business that may not have a physical location open at all hours. It’s a living, breathing entity that needs ongoing care and attention to stay relevant and useful. When a client only sees it as a static deliverable, they undervalue what it should be doing for them, and that undervaluation shows up in how much they’re willing to invest and how they measure success afterward.
My job in that first conversation is to shift the framing. Instead of talking about design choices or page count, I talk about what the client is actually trying to accomplish, more qualified leads, fewer manual customer service questions, a clearer sales process. Once a client understands their site as a functional extension of their business rather than a static asset, the entire project conversation changes. Priorities shift toward what will actually move the business forward, and the value of the investment becomes obvious rather than something I have to argue for.
This is the same principle Duncan describes when he talks about customers buying progress, not products. Nobody wants a website. They want what a good website does for them. The businesses that lead with outcome-focused language see stronger engagement and clearer positioning, because they’re speaking to what the customer actually came to solve.
Evidence: Data Only Becomes Useful Once You Understand the Why
Analytics show you what happened. They rarely tell you why it happened, and that distinction matters more than most businesses treat it. A number on a dashboard is a symptom. The cause is almost always somewhere else, usually in a conversation you haven’t had yet.
I worked with a client whose campaign data looked strong on paper. Traffic was healthy, the ads were performing, people were clicking through at a reasonable rate. But conversions were flat, and no amount of staring at the analytics explained why. The data told us something was wrong. It didn’t tell us what.
It wasn’t until I sat down with the client and talked through what their sales team was actually hearing from prospects that the disconnect became clear. The landing page wasn’t answering the real concerns their buyers had. The copy was speaking to features and specifications, while the people landing on the page needed reassurance about something else entirely, timeline, reliability, what happens after they sign up. Once we rewrote the language and communication on that page to match what buyers were actually asking about, conversions improved. The fix wasn’t a design change. It only surfaced by combining the data with a direct conversation.
That’s the fundamental lesson in working with data: numbers point you toward a problem, but they rarely explain the cause on their own. Root cause analysis, connecting the pattern in the data to the real behaviour behind it, is what turns a dashboard from a reporting tool into an actual decision-making asset. Businesses that treat analytics as the whole picture end up optimizing the wrong thing. Businesses that use data as a starting point for investigation get to the actual fix faster.
Action: Narrow the Decision Before You Present It
Customers delay when the next step feels unclear, risky, or simply too big to evaluate. This is one of the most common reasons a deal stalls, not because the client doesn’t want to move forward, but because the path forward hasn’t been made simple enough for them to act on.
I saw this play out clearly while working alongside another designer presenting creative concepts to a client. When you hand a client too many options at once, whether that’s five logo directions or ten campaign concepts, you don’t make the decision easier. You make it harder. The client isn’t equipped to evaluate that many directions against each other, so instead of choosing, they freeze. That’s analysis paralysis, and it’s a completely predictable outcome of presenting too much at once.
The fix is narrowing the field before the client ever sees it. Start with a wide set, ten ideas, and cut it down through your own judgement, first to five, then to two finalists. From there, present your single recommended choice, along with a clear explanation of why you chose it over the alternative. That structure does two things. It shows the client your thinking rather than just your output, and it gives them something concrete to react to, agree with, or redirect, instead of an open field of undifferentiated options.
This principle extends far beyond creative concepts. Any time a client is stuck on a decision, whether it’s a service package, a strategy direction, or a technical approach, the fix is rarely more information. It’s a narrower, clearer recommendation. When customers understand exactly what happens next and why it matters now, they move forward. When the field is too wide, they stall, and that stalled decision is often the single biggest barrier to growth in a client relationship.
Reassurance: Address the Trust Concern Directly, Don’t Wait for It to Surface
Logic gets a proposal considered. It rarely gets a proposal signed. What actually moves a hesitant client forward is confidence, specifically, confidence that this project won’t repeat a bad experience they’ve already had.
I’ve worked with new clients who had every reason on paper to move forward, the scope made sense, the pricing was fair, the timeline was reasonable, but they still hesitated. In nearly every case, that hesitation traced back to a previous vendor relationship that went wrong. Communication broke down, or the finished work didn’t match what was promised, or they simply felt like an afterthought once the contract was signed. Whatever the specific history, the underlying concern is the same: what’s stopping this from happening again?
The way I address that isn’t through more reassurance in general terms. It’s specific. I ask directly what went wrong before, and I build the answer into the project scope itself, in writing, before the engagement starts. When a client sees their exact concern named and addressed as part of the plan, the uncertainty around the relationship drops substantially. That peace of mind carries through the full length of the project, not just the sales conversation.
This is the piece most businesses skip. They treat trust-building as something that happens through tone, warmth in an email, a friendly call, general reassurance that everything will be fine. But specific trust concerns need specific answers. A client who’s been burned by poor communication doesn’t need to hear that you’re a good communicator. They need to see exactly how communication will work differently this time, built into the scope where they can refer back to it.
Strategic Takeaway
The five lessons in The Secret Lives of Customers all point to the same underlying discipline, and it’s the same discipline I try to bring to every client relationship. Understand the real situation a customer is in before you respond to what they’re asking for. Speak to the outcome they actually want, not the deliverable you’re producing. Back your recommendations with evidence that explains the why, not just the what. Narrow every decision down to a clear, single recommended path. And address trust concerns directly instead of hoping general reassurance will be enough.
That’s the CLEAR framework: Context, Language, Evidence, Action, Reassurance. I didn’t pull it from a book, it came out of patterns I kept seeing across real client work, and it’s become the lens I use to evaluate whether a client relationship, a campaign, or a piece of messaging is actually built around how customers make decisions, or just around what a business assumes they want.
If you’re looking at your own marketing, sales process, or customer experience and something isn’t converting the way it should, this is exactly the kind of gap I help businesses find and fix. You can reach out through my website contact form or connect with me on LinkedIn. It starts with a simple conversation about how your current approach is performing and where the opportunity is to improve.
