Most B2B website projects are commissioned as design projects and judged as design projects, which is why so many of them look better and sell less than what they replaced. A B2B marketing website has a narrow job: help a buying committee of four to eight people, most of whom never speak to you, work out whether you are a credible answer to their problem, and give the one person willing to make contact an easy way to do it. Everything else on the site is overhead. Briefing an agency against that job, rather than against a mood board, changes both what you get and what it costs.
The pages that actually carry the sale
In practice a B2B site earns its keep on a handful of pages and the rest is scenery. The solution or product pages, written for the problem the buyer has rather than the capability you have. The pricing page, or if you genuinely cannot publish prices, an honest page about how pricing works, what drives it and roughly what an engagement looks like, because the alternative is that the buyer assumes you are expensive and leaves. Proof: case studies with real numbers and named customers where permitted, not logos in a row. The integrations or compatibility page, which is often the highest-intent page on a software site and is usually neglected. And the contact path itself. Ask an agency in the brief which pages they expect to carry the pipeline and why, and compare that answer with your own analytics. A proposal that treats every page as equally important has not looked at your data. The same discipline separates the best B2B marketing companies from the ones selling a template with your colours on it.
Speed and structure are commercial decisions
A heavy site built on a stack that requires a developer to change a headline will slow your marketing team down for years, and that cost dwarfs the build fee. Ask what the editors can change without engineering help, and ask to try the editing interface before you sign. Performance matters too, and not as an abstraction: the Web Vitals thresholds published on Google's web.dev cover loading, interactivity and visual stability, and buying committees on corporate networks and phones feel all three. Ask for a performance target in the contract with a measurement method, since agencies that agree to one build differently from the start. Structure is the third piece. A site organised around your internal departments will confuse an outsider, and URL and navigation decisions made at build time are expensive to unwind later. Insist that redirects from the old site are planned before launch rather than discovered afterwards, because losing accumulated visibility at go-live is the most common and most avoidable rebuild failure.
Forms, gates and the cost of friction
Every field you add costs you enquiries, and most B2B forms ask for information nobody uses. Look at your own CRM and count how many of the fields on your current form are actually read before the first call. Gating is the same argument at a larger scale. Putting a whitepaper behind a form generates contact records, but many of them are people who wanted the document and will never buy, and counting them as leads corrupts every number downstream. A defensible pattern is to publish the substance openly, so it can rank and be cited, and reserve the form for things a buyer only requests when they are serious: a quote, a demo, a technical consultation. Then define what a qualified lead means in one sentence that sales would defend, and report on that rather than on total submissions. Most of the disagreement between B2B marketing and B2B sales is a definitional problem wearing a performance costume.
Briefing the project so it can be priced honestly
Write down the page inventory, the number of templates, who writes the copy, who supplies photography, which systems the site must integrate with, and the launch date. Those five items explain most of the variance between quotes, and content is the item that derails timelines more than any other. Decide explicitly whether you or the agency writes, and if it is you, staff it before the project starts. Ask for the build to be quoted separately from any ongoing retainer so you can judge each on its own merits, and ask what happens after launch: who fixes what, for how long, and at what rate. Finally, agree ownership of the code, the design files, the content and the analytics properties in writing. Buyers who leave that until the relationship ends discover the answer at the worst possible time.
Questions people ask about b2b marketing website
How much should a B2B website cost?
The spread is enormous because the scope is. The variables that matter are the number of unique templates, who writes the content, and what has to integrate with the site. Fix those in the brief and quotes become comparable; leave them open and every proposal will price a different project.
Should we publish pricing?
If you can, yes, since it filters out poor-fit enquiries and buyers increasingly expect it. If your pricing genuinely varies, publish the model instead: what drives cost, a typical range, and what an engagement includes. Silence is read as expensive, not as flexible.
How do we avoid losing search visibility at launch?
Plan the URL mapping and redirects before build, not after. Keep the pages that earn traffic, redirect anything that moves, and check the new site is crawlable before go-live. This single item causes more post-launch panic than everything else combined.
Should content be gated?
Gate what a serious buyer requests, such as a quote or a demo, and publish the rest openly so it can rank and be referenced. Counting document downloads as leads inflates your reporting and trains the sales team to ignore marketing's numbers.