Why Do I Ask for Recent Lost Deals Before a Website Redesign?

What does a lost deal have to do with a website redesign?

More than most people expect. A lost deal shows the exact point where a real buyer stopped believing you. Often that point is something the website should have handled: a missing answer, an unclear price, a weak proof point, or a competitor who explained it better. That is why I ask for recent lost deals before I plan any redesign.

Most redesign projects start with the wrong inputs. A brand workshop, a mood board, a list of competitor sites the founder admires, and an analytics export. All useful, but none of them tell you why buyers said no. A redesign built only on those inputs tends to produce a prettier version of the same problem.

So early in a project, I ask a question that sometimes surprises clients. Can I see the last handful of deals you lost, with whatever notes your team kept? It is one of the most useful things I ask for, and it shapes the whole plan.

Why do lost deals beat analytics as a starting point?

Analytics tell you what visitors did, but not why they decided against you. Lost deals carry the why. They come with notes, objections, and sometimes the competitor who won. Together they point to the specific doubts the website failed to resolve, which is far more useful than bounce rates when planning what a new site should say.

A high bounce rate on the pricing page tells me something is wrong there. A lost-deal note that says "buyer felt the product was too expensive for a team their size" tells me what is wrong. It tells me the pricing page needs to explain value for smaller teams, or show a plan that fits them, or stop implying a price that scares them off.

Analytics also miss the buyers who never filled a form. Many B2B buyers do their research quietly, then talk to sales once they have a shortlist. By the time a deal is lost, the website already did its part, well or badly. Lost deals let me look back at that hidden part of the journey through the questions buyers asked later.

I still use analytics. They help me find where people get stuck. But lost deals help me understand what they were stuck on, and that is the input a redesign plan needs most.

What exactly do I ask the client to share?

I ask for the most recent lost deals that were real opportunities, not unqualified leads. For each one, I want the deal notes, the stated loss reason, the competitor if known, and any emails or call notes the team is comfortable sharing. A short list of real stories beats a long export of loss reasons with no context.

I specifically ask for real opportunities. A lead who was never a fit tells me little about the website's job, except maybe that the site attracts the wrong people, which is useful in its own way. But a buyer who seriously considered the product and walked away is the richest source of insight.

Loss reason fields alone are rarely enough. "Price" and "went with competitor" appear on most loss reports, and they hide more than they reveal. The notes and emails underneath are where the specifics live. If a client tracks loss reasons in a structured way, I wrote about building a lost-deal reason report in HubSpot, and that report is a great starting point for this conversation.

I always respect what clients are comfortable sharing. Some will share full call recordings. Others will summarize. Either works. What matters is that the plan rests on real buyer decisions, not guesses about them.

What patterns do I look for in the lost deals?

I look for doubts that repeat. If several lost buyers questioned the same thing, such as security, fit for their team size, integration depth, or time to value, the website probably fails to address it. I also note which competitor keeps winning and what that competitor explains better on its own site.

Repeated doubts become content requirements. If three buyers asked whether the product works for a regulated industry, the new site needs a clear answer, probably a dedicated page or section, with proof. If buyers repeatedly misunderstood what the product does, the homepage message needs work before any visual design starts.

Competitor patterns are just as useful. When one competitor keeps winning, I study how that competitor explains the same thing. Not to copy their design, but to understand which buyer question they answer that my client does not. Sometimes the answer is a comparison page. Sometimes it is a pricing explanation. Sometimes it is simply clearer wording.

I also look for timing. Did deals stall after the demo, during procurement, or after a trial? Each stage points to a different part of the website. A stall during procurement often means missing security or compliance information. A stall after a trial often points to onboarding content rather than the marketing site at all.

How does this change what I put in the redesign plan?

It turns the plan from a list of pages into a list of buyer doubts the site must resolve. Each repeated objection gets a home: a section, a page, a proof point, or a clearer sentence. The visual design then serves those answers, instead of the answers being squeezed into a design chosen first.

In practice, the plan gets a short "doubts to resolve" list near the top. Each doubt has a target page and a type of proof. For example: buyers doubt the product fits small teams, so the pricing page shows a small-team plan and the case studies include a smaller customer. That list becomes the checklist I review every draft against.

It also changes priorities. A client might want a new animated homepage, but the lost deals say buyers cannot find integration details. I will still build a strong homepage, but the integration content moves up the list. Lost deals give me the evidence to make that case without it sounding like my personal preference.

This connects to a broader habit of mine. I wrote about why I ask clients for their worst lead first, and the principle is the same. The edges of your pipeline teach you more than the middle.

What if the client has no lost-deal notes?

Then I ask the people who were in the deals. A short talk with the founder or a sales rep about the last few losses often gives me what I need. If even that fails, the lack of notes is itself a finding, because a team that cannot explain its losses has a GTM gap.

Many small teams do not track loss reasons in any structured way. That is normal early on. The founder remembers most deals, and a thirty-minute conversation is enough to surface the patterns. I ask simple questions. Who did you lose recently? What did they say? What did you wish you could have shown them?

When there is truly nothing to go on, I suggest a light system for the future, usually a required loss reason field and a short note in the CRM when a deal closes lost. It costs reps a minute per deal and gives the next redesign, and the next quarter's marketing, real evidence to work from.

This is where my GTM engineering work and my website work overlap. The same CRM fields that help sales learn from losses also help the website improve over time. A redesign is a good moment to set them up.

Does this approach slow the project down?

Slightly at the start, and it saves time later. Reviewing lost deals usually adds a short step to discovery. In return, the plan is clearer, fewer drafts go back and forth over opinions, and the finished site answers questions buyers actually ask. It is a trade I am happy to make.

The biggest time saver is fewer debates. When a stakeholder wants to cut a section, I can point to the lost deals that needed it. When someone wants to add a feature tour nobody asked for, the evidence helps keep the page focused. Opinions still matter, but evidence settles arguments faster.

My projects are fixed-fee, usually between $1,000 and $10,000, so scope discipline matters to me as much as to the client. Starting from real buyer doubts keeps the scope tied to outcomes, which protects both sides from a redesign that drifts.

It also changes how clients think about their site after launch. Once a client sees how lost deals shaped the plan, it becomes natural to keep reviewing losses and feeding new doubts into page updates. The website stops being a one-time project and becomes part of how they learn from the market.

What should you do before your next redesign?

Pull your most recent real lost deals, read the notes, and write down every doubt that appears more than once. Note which competitor won and what they explain better. Then turn that list into the first page of your redesign brief, before any talk of colors, layouts, or animations.

If you have no notes, talk to whoever ran those deals and ask what buyers worried about. Then add a simple loss reason field to your CRM so the next redesign starts with better evidence.

I have delivered more than 100 projects for over 25 clients across six years, and the lesson I keep coming back to is that a redesign should be grounded in why buyers said no. Design matters. But design aimed at the wrong doubts is just decoration.

If you are planning a redesign and want help turning your lost deals into a plan, or setting up CRM fields that capture loss reasons going forward, reach out. Let's chat about what your lost deals are trying to tell you.