Get concise advice on choosing the right CMS, understanding migration costs, and avoiding expensive implementation mistakes before they become roadmap problems.
Most B2B website projects start by asking the wrong question. "How do we make the website look better?" is a reasonable starting point, but for companies selling complex, high-value, or configurable products, a more useful question is: "How should the website support the way we actually sell?"
That question changes the scope of the project entirely. A website does not have to be a passive brochure. For the right business, it can become part of the sales process, part of the qualification system, and part of internal operations — and that is where the real value lives.
The brochure problem
When I first get into a discovery call with a B2B client, I usually see the same pattern. The website has had a redesign or two. The pages look clean enough. The copy has been polished. But the sales team still answers the same questions every week, leads still arrive without context, and the marketing team still dreads editing anything on the site.
The redesign fixed the surface. The system underneath did not change.
A basic redesign usually delivers cleaner design, better copy, faster pages, improved mobile experience, easier editing, and stronger calls to action. All of that matters. If the current website looks outdated or performs badly, those foundations need fixing. But if that is the entire scope, the result is still a brochure — a prettier, faster, more professional one, but still mostly passive.
For some businesses, a brochure website works fine. If the offer is simple, the buying journey is short, and the customer already knows what they need, passive is acceptable.
Many B2B companies do not sell that way.
Complex products need more from the website
The more complex the product, the more work the website needs to do. This is especially true for companies selling manufacturing products, technical equipment, industrial systems, construction products, custom-built goods, high-ticket B2B services, configurable products, or anything sold through fairs, showrooms, distributors, or sales teams.
In those businesses, the buyer rarely lands on the website and converts. They need to understand the product first. They need to compare options, know whether the product fits their situation, understand the process, the limitations, the pricing logic, the technical requirements, the timelines, and what happens after they make an inquiry.
And often, the company already has useful content: PDFs, videos, brochures, specifications, case studies, internal documents. It just is not structured in a way that helps the customer or the sales team. That gap — between the content that exists and the way it reaches buyers — is where a serious website project should focus.
The website is not responsible for every step of the sales process. The goal is to identify where digital tools create the most leverage, and build there first.
Start with the sales process, not the sitemap
Before talking about pages, design, or technology, I want to understand how the company sells.
Where do leads come from? Google, referrals, events, fairs, distributors, outbound, or existing relationships? What happens after first contact — does the buyer need a demo, a consultation, a site visit, a quote, a technical review, or an internal approval process?
Where do prospects hesitate? What does the sales team explain again and again? What does a qualified lead look like, and what information would help the sales team before the first call?
These questions matter more than the sitemap at the beginning of the project. The sitemap comes later, after understanding the business system the website belongs to.
A useful exercise before any redesign: ask three people on the sales team to list the five questions they answer most often. Those answers become the core content brief for the new site.
A website can guide the buyer through a complex decision
A good website for a complex product does not just list information — it helps the buyer make sense of it.
That might mean clearer product pages. It might mean comparison tables. It might mean use-case-based navigation instead of product-category navigation alone. It might mean a guided questionnaire that helps visitors understand which product or service fits their situation. It might mean explaining trade-offs: when one option makes sense, when another is better, and when the buyer should talk to sales directly.
The goal is not to replace the salesperson. The goal is to make the buyer more informed before they speak to the salesperson, so the first conversation starts from a better place — for everyone.
A website can qualify leads
Not every inquiry has the same value. For many B2B companies, the sales team does not need more leads — they need better leads.
A website can help with that. Instead of a generic contact form with name, email, and message, the inquiry flow can collect useful context: what the buyer is looking for, intended use case, company type, timeline, approximate budget range, location, required features, current supplier or system, and level of urgency.
This does not need to be complicated. Even a better-structured form can dramatically improve the quality of the first sales conversation. The sales team can understand the lead before replying. The buyer feels the process is more tailored. Routing and follow-up become more intelligent.
You do not need a full lead scoring system to improve qualification. Start with three to five additional fields on the existing contact form — just the ones the sales team would want to know before picking up the phone.
A website can support the sales team directly
This is where most redesigns miss the biggest opportunity.
If a company sells through salespeople, fairs, showrooms, or demos, the website should not only serve anonymous visitors. It can also support the people doing the selling. For example, a website or connected digital tool could help the sales team quickly show the right product video, compare models or service packages, walk through options on an iPad, demonstrate a configurator on a large screen, capture a prospect's preferences during an event, send a tailored follow-up after a conversation, or access technical documents without digging through folders.
None of that is visible from the outside. But it creates real business value.
If the sales team repeats the same explanation every week, the website can help package that explanation. If prospects struggle to visualize options, the website can make those options tangible. If fair or showroom conversations generate interest but follow-up is inconsistent, the website can help capture and structure that interest.
That is sales enablement, not just web design.
When a configurator makes sense — and when it does not
When companies sell customizable products, the idea of a configurator often comes up early. Sometimes it is the right call. Sometimes it is not.
A configurator can be useful when it solves a real problem: helping customers visualize options, helping sales teams present variations, qualifying leads based on selected preferences, preparing quote requests, or creating a stronger showroom or fair experience.
A configurator built without a clear business problem to solve usually becomes an expensive distraction. Scope creep on configurator projects is common precisely because the goal was never defined.
The question that matters is not "can we build a configurator?" — the right question is "what role would a configurator play in the sales process?" Is it for inspiration? Serious quoting? Internal sales presentations? Lead qualification? Trade fairs? Each answer leads to a different scope. A lightweight visual tool is very different from a full pricing and production configurator, and the cost difference is significant.
Features should not be proposed blindly. They should come from understanding the buyer journey and the sales process first.
The CMS matters because operations matter
For many companies, the website is painful not because the public pages are bad — it is because the internal editing experience is bad. Marketing teams cannot update content without involving developers. Images need manual resizing. Product information gets duplicated across pages. Landing pages are difficult to create. The content model does not match how the business thinks about its products.
A good CMS should reflect the company's real content structure. If products have specifications, variants, downloads, use cases, media galleries, related case studies, and sales documents, that structure should exist in the system. Editors should not have to copy and paste the same information across multiple pages.
This is one reason I use Payload CMS for most bespoke builds. The content model can be shaped around the business — not the other way around. Editors get an interface that matches how they actually think about their products.
The website should be designed around how the team actually works. If it is not, the site gets stale within months of launch because nobody wants to touch it.
The best redesigns start with diagnosis
A serious website project should not begin with a list of pages. It should begin with diagnosis.
Before talking about design and technology, I want to understand how the company gets leads, how buyers make decisions, what the sales team explains repeatedly, what content already exists, where the current website creates friction, what internal processes are manual or duplicated, what a qualified inquiry should contain, and what the website should make easier for both customers and the team.
Only then does it make sense to define the structure, CMS, integrations, content model, and technical architecture.
This is also why two websites with the same number of pages can have completely different business value. One is a collection of static pages. The other is a business system that supports sales, marketing, content, and operations. They may look similar from the outside. They are built from entirely different premises.
Questions worth asking before your next redesign
If you are planning a website redesign, these are the questions that actually shape the project:
What role should the website play in our sales process?
Where do our best leads come from?
What happens after someone discovers us?
What questions do prospects ask again and again?
What does the sales team need to explain manually?
What information would make an inquiry more qualified?
What do buyers struggle to compare or visualize?
What content do we already have that is underused?
What internal workflows could the website simplify?
What would make the website genuinely useful six months after launch?
These questions lead to a much better project — and they prevent the common pattern of spending a serious budget on a website that looks better but does not perform much better.
The goal is not more features
This point matters. Turning every website into a large platform is not the goal. Not every company needs a configurator, AI integration, a custom dashboard, CRM integration, or complex automation.
The goal is to understand where digital tools create the most leverage for that specific business. Sometimes the right answer is a focused website with a better CMS. Sometimes it is a guided product finder. Sometimes it is a sales presentation tool. Sometimes it is a better inquiry flow. Sometimes it is a content system that saves the marketing team hours every week.
A good project adds structure where the business is currently relying on manual work, scattered content, or repeated explanations. A good project does not add complexity for its own sake.
A phased approach often works well here: fix the foundation first, then identify which higher-value sales tools to build in phase two, once the team has seen how buyers actually use the new site.
A website should earn its place in the business
For complex B2B businesses, the website can go well beyond creating a first impression. It can guide buyers through a difficult decision. It can qualify leads before the first call. It can support sales conversations in the room. It can organize content that currently lives in folders and inboxes. It can reduce the internal friction that slows down follow-up.
That is the difference between a website that exists and a website that works.
If your current website feels disconnected from your sales process, your content, or your internal workflows, another visual redesign alone probably will not close that gap. The better starting point is to understand how the website should support the business behind it.
That is where the real work begins.
FAQ
How do I know if my website is already doing enough?
A simple test: ask your sales team whether the website helps them before, during, or after a sales conversation. If the answer is "not really," there is likely a gap worth addressing.
Does this approach only apply to large companies?
No. Even small B2B businesses benefit from a website that prepares buyers and qualifies inquiries. The scope of the solution changes — a small business might only need a better inquiry form — but the underlying thinking applies regardless of company size.
How much does a sales-process-aligned website cost compared to a standard redesign?
It depends on which tools make sense for the business. A better CMS structure and improved inquiry flow adds relatively little to a project budget. A full configurator or sales enablement tool adds significant scope. That is why diagnosis comes before pricing.
What is the first step if we want to go in this direction?
Map the buyer journey before touching the website. Document where leads come from, what they need to understand before making contact, and what the sales team repeats most often. That map becomes the brief.
We already have a new website — is it too late?
Not at all. The sales-process layer can be added incrementally. Start with the inquiry flow, then improve content structure, then add higher-value tools if the business case is there.
If you found this useful and are working through a B2B website project, feel free to leave a comment below or get in touch directly. I write practical guides on building with Payload CMS, Next.js, and headless architectures — subscribe if that is relevant to what you are building.
