Making the Call

Your team disagrees about what customers value. Use it.

Summarize with AI

Are you the only person in your company who thinks the website is a problem?

That's common. In my experience, the person pushing for a website project is usually the owner, or whoever lays out the company's strategy, and other people can see it as a distraction. Once the project gets going, the disagreement that comes up usually isn't about the overall strategy. It's about what customers value most. That disagreement isn't an obstacle to the website. It's one of the most useful things you can put into it, and collecting it is also how the website stops being only your project.

Why does it fall to the owner?

Because you're often the only one who can see it. Most people in the company see one piece of the business. The person running sales is thinking about this quarter's pipeline. The person running the floor is thinking about the schedule. Each of them has a department, and a good reason to think what their department does is the most important thing to pay attention to right now.

The website touches all of those departments and belongs to none of them. So from inside any one of them it can look like somebody else's project, competing for the same hours. From where you sit, it looks like the opposite. You might be the only one who sees that this isn't one department's problem anymore. It's a website problem.

That isn't anyone being difficult. Each of them is doing the job they were hired to do, and the website isn't in any of those jobs.

The argument is usually about customers, not direction

When more than one person from the same company gets involved, the disagreement I see usually isn't about the overall strategy. Even where people roughly agree on direction, it shows up a level down, in a sentence like "Hey, our customers would really value this more." The owner has one answer. The person who meets customers, in sales or estimating, can have a different one.

A version of this I've seen: the president of an established company says customers value its reputation as an established company. The outside sales rep or the estimator says buyers care about two other things. How fast a quote comes back, and knowing the company can do the specific work that matters to them.

Put that in a contract CNC machine shop, and each view writes a different homepage. The president's version opens with something like "Three generations of trusted precision machining."

The sales rep's version opens with something like "CNC machining for production parts in aluminum, steel and titanium. AS9100 certified. Send a drawing and get a quote back within two business days." (Use your real turnaround. If the team can't agree on what it is, that's worth knowing too.)

Both are true. The first says how the company sees itself. The second answers what the buyer came to check. A purchasing agent with a drawing to place usually isn't weighing reputation in the abstract. They're checking whether you do this process in this material, whether you hold the certification their quality team requires, and how long they'll wait for a number.

Both views are real, and they're looking at different things. The owner tends to see the company over years: what it's known for, which relationships carried it, where it's headed. The person in sales or estimating hears buyers before they've decided: what they ask about first, what makes them hesitate, what they mention when they pick you.

That makes the field's view closer to the buyer than yours, but it's still filtered. A salesperson remembers the questions from their own deals, and it's easy to put a loss down to price and a win down to the relationship. Treat what they tell you as a closer view of the customer, not as proof of what customers think.

Why the homepage forces the question

A homepage gets one first line, so it settles this disagreement whether anyone chose to or not. It's the same pressure behind the decision under every website project, one level down: even once you know which customers you want, there's still what those customers check when they're choosing between you and another company offering a similar service. That's why it's one of the first things a B2B website redesign has to settle.

Who should be involved in a website redesign, and what do you ask them?

The useful part isn't the questions. It's answering the same ones separately and comparing. Start with the person closest to customers, whether that's sales, an estimator or someone in the field. They're someone to consult, not a second decider. Ask them on their own, not in a meeting with you in the room:

  • What do new customers ask first?
  • What do they need to hear before they'll send a drawing or ask for a quote?
  • When we win against another company, what do they say tipped it?
  • When we lose, or a quote goes quiet, what do you think happened?
  • What do we talk about that customers don't seem to care about?

Then write your own answers to the same questions before you read theirs. If you haven't yet settled which work and which customers you want more of, start with the decision linked above, because these answers sit underneath it.

Put the two sets side by side. Where they match, you've probably found a strong candidate for your first line. Where they don't, you've found the actual decision. It's still yours to make. But it's a different decision when the field's answers are in front of you and not just your own.

Both sets are still views from inside the company, so check them against what buyers actually wrote. Pull the last 10 to 20 quote requests or inbound emails and note what each one asks about first. That's a record rather than a memory. The most direct version is asking two or three recent customers, or prospects who went with someone else, the same questions.

Often the two answers don't really conflict once they're on paper. In the machine shop, reputation and fast quotes aren't competing for the first line. Reputation is what a buyer tends to conclude after the page has answered their questions, not something a page can announce. So the top of the page says plainly what you make and in what, the certifications that qualify you for the work, and how fast a quote comes back. The three generations and the long-standing customers go underneath, as the reason to believe it. Where those certifications sit matters as much as whether they're listed, which I've covered in the thing that rules you out.

And if the field's first questions have nothing on the site behind them, that's the start of a content audit too. If the hesitation is time, a handful of questions to one colleague is a small ask next to writing the whole site yourself, which is the version a lot of owners remember from the last project.

What do the other departments get back?

This is also how the website tends to stop looking like a distraction to the rest of the company. When the estimator finds the question they answer most often already answered on the homepage, it's less likely to read as only the owner's project. It's partly theirs, because it's their answer.

Sales isn't the only department with a view worth collecting. Someone in operations might have insight into "Hey, we really need to be focusing on these companies more because it's more beneficial to our bottom line." That belongs next to the field's answers, because it's about which customers the homepage should be speaking to first.

None of that happens if the website is something one person pushed through on their own. It's far more likely when the people who saw it as a distraction find their own answer on the page.

Common questions

Who should be involved in a website redesign?

Two groups, for two different jobs. Consulted: whoever talks to customers most, usually someone in sales, estimating or the field, and anyone in operations who knows which customers are worth more. Deciding: still one or two people, usually whoever decides what work the company takes. Collecting the field's answers before the decision keeps the site from reflecting only one view of the customer, without turning the decision into a committee.

Who should own the website internally?

One person with the authority to settle disagreements about what it says. In many established companies that ends up being the owner or whoever sets strategy, because they're often the only one who sees the website as a company-wide issue rather than one department's. Day-to-day edits can sit elsewhere, but the decision about what the site says first needs an owner who can choose.

What if sales and leadership disagree about what to put on the website?

Write both views down separately, then compare them. Where they agree, that's likely your lead message. Where they don't, it's a decision for whoever sets strategy, made with the field's answers in front of them. Often the disagreement is two halves of one answer: leadership describes what the company is known for, and sales describes what a buyer checks first, like what you make, which certifications you hold and how fast a quote comes back. The second usually goes at the top, and the first becomes the proof underneath.

Should we ask customers instead of our sales team?

If you can, ask both. Your sales team hears buyers before they've decided, which puts them closer to the customer than you are, but their view is filtered through their own deals. Asking two or three recent customers, or prospects who chose someone else, the same questions is the most direct version, and your recent quote requests show what buyers asked without anyone's memory in between. Where the customers and the team agree, you can lead with it more confidently.

How to redesign an existing website?

Roughly in this order: settle which work and customers you want more of, collect what the people who meet customers say buyers check first and compare it with your own answers, test both against recent quote requests, then decide the page structure, and only then the design. The comparison is the step that's easy to skip, and without it the site gets written from one view of the customer.

Why don't other departments care about the website?

Usually because it isn't in any of their jobs. Sales is focused on the pipeline and operations on getting the work out, and the website touches both while belonging to neither. From inside a department it can look like a distraction. That tends to change once the site carries their own answers, like the question a salesperson gets asked most often.

Website redesign vs refresh
Share

Let's build something together.

A 30-minute call. We'll listen, dig into the details, and tell you honestly whether we're the right partner, or point you to someone who is.

Book Intro Call ↗