B2B website design and redesign, planned around how buyers compare their options
We design and redesign websites for B2B companies whose buyers read carefully before they get in touch: consultancies and other service firms, agencies and software companies. We agree the page structure first, then the visual direction on a few key pages. The rest of the site follows as templates and components for desktop, tablet and phone, and either our team builds it or your developers work from the design file.
Norml designs and redesigns websites for B2B companies. The scope can include the sitemap, copy, art direction, page templates, a component library and responsive designs. We then build the site ourselves, or hand the approved design to your developers and check their build against it.
What a B2B website design or redesign involves
A project can cover a whole site, a homepage or one product page, and uses only the parts below that it needs. Structure comes before visual design, so every layout is drawn for the actual page list and copy.
Sitemap and audience pathsWe review the current site and the content you plan to add, then propose the sitemap and navigation. Buyers comparing vendors get one route; existing customers looking for instructions or a support form get another, and every page has one job and one next step.
01
Art direction on key pagesType, colour, spacing, photography and the style of icons and diagrams are worked out on the homepage and one inner template, using your brand files and any references you share.
02
Templates for pages you keep publishingService pages, case studies, articles, resources and customer stories each get one template, designed around your longest real example. A long page list becomes a small set of page types with a clear heading order, and new entries use them without new design work.
03
Responsive designs and a component libraryEvery template is designed for desktop, tablet and phone. Navigation, footer, buttons, cards and form fields sit in one Figma library with their hover, error and empty states, so a page added later matches the rest of the site.
04
Proof and enquiry pathsCase studies, client logos, reviews and figures taken from your own records appear beside the claims they support. Enquiry, quote and demo forms ask for the details your sales team needs to qualify a request.
05
Handoff to your developersIf your developers build the site, they receive the Figma file with named components, colour and type tokens, spacing rules, interaction and motion notes, exported assets and a short written guide. We agree component names with them early, so the file matches how they write code.
06
Build by our teamIf we build the site, each page is made of the approved components, and your team changes text and images in editing fields without a developer. Images are sized for their layouts, and page speed is checked before launch.
07
Design review of the built pagesWhoever builds the site, we compare the built pages with the approved designs at phone, tablet and desktop widths and list each difference with the fix it needs before launch.
Shows a site for an engineering studio after more than one earlier marketing-site attempt: an identity extended past a logo and flat colours, a template for each named client engagement, and posts and job listings its team publishes without a developer.
Shows a website treated as a credibility problem for a software company in a conservative industry: workshops that gave its teams shared product language, a modular brand system, and product pages and lead funnels for carriers, agencies and solo agents.
Shows structure settled before visual design for a genomics software platform entering the US market: a site architecture of more than 50 potential pages, messaging developed with its marketing team, and wireframes for the five pages it needed first.
Shows how we apply a brand made by another agency: a nutrition platform's brand book became a web design system with a component library and spacing rules, and the site was replaced one part at a time, with traffic and tracking checked after each release.
Access to the current siteEditor access to the current site's CMS and read access to its analytics and search accounts, shared by invitation, so we can see what exists and which pages bring in visitors. A new site skips this.
01
Brand files and contentLogo files, colours, fonts and any brand guidelines, plus the copy, photography and product screenshots you already have. If copy is still being written, name the person who owns it.
02
Proof you can publishCase studies, client names and logos you have permission to show, reviews, and any figures from your own records that a page may quote.
03
References for the directionSites you admire or a rough concept of the look you want, with a note on what you like in each.
04
Your developers' setupIf your team builds the site: the framework or CMS they use, any naming conventions for components, and one developer who goes through the handoff with us.
05
One approverOne person who approves the structure, the direction and each round of designs, and gathers your team's comments in the design file.
06
How a design or redesign project runs
[Review and structure]
We review the current site, its content and analytics, then agree the sitemap, the page types and the job of each page with you.
Step 01
[Approved direction]
The homepage and one inner template, or the first sections of a one-page site, are designed first. Once you approve them, the remaining pages follow that direction.
Step 02
[Full page set]
Every other template is then designed at desktop, tablet and phone widths with the component library. Comments stay in the design file and are resolved there.
Step 03
[Build or handoff]
Our team builds the site from the approved components, or your developers receive the file and the written guide and walk through both with us before they start.
Step 04
[Check and launch]
Forms, redirects, page titles and search settings are tested on the finished site by the team that built it, and the differences found in the design review are fixed before launch.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Yes. We keep the logo, colours and fonts and extend them into what a website needs: a type scale, spacing rules, components and an imagery style. If the brand itself needs new work, such as a new logo or name, that is a separate branding project agreed before design starts.
Which tools can our developers build the design in?
Usually the tool they already use. The handoff describes layouts, components, tokens and behaviour rather than code for one platform. If they build on a CMS, we list the fields each template needs so they can set it up to match.
Which platform should the new site use?
We recommend one once the structure and design are agreed, based on how your team will edit pages and what the site must connect to. If your current platform still fits, the site can stay on it. If it is leaving a hosted site builder, every page, image and form on the live site is listed and carried over, and each changed address is redirected.
Can we start with the homepage or a single product page?
Yes. A homepage or a one-page product site can be the first phase. Its type, colours and buttons are still set up as a component library, so later pages extend it instead of starting over.
Can you work from a rough concept or a generated mock-up?
Yes, as a reference rather than a layout to copy. We note what the concept gets right, such as its tone or a visual idea, then design one section in that direction with accurate product details. Interface mockups can use fictional data where real customer records can't be shown.
Do you write the copy?
Copy can be part of the scope or come from your team. Either way, the copy for each page is agreed before visual design, so layouts fit the real text. Where the structure needs it, we suggest changes to headlines and calls to action.
Can the site include a return or quote calculator?
Yes, when the calculation can be written down. Your team supplies the inputs, the formula and its assumptions, and approves a set of worked examples. We design the calculator into the page and, if we build it, run every example through it before launch. Results appear as estimates with your disclaimer, and a form can send the inputs to your sales team with the enquiry.
What happens to our existing pages and their addresses?
Before the sitemap is final, we go through your current pages with you and decide which to keep, rewrite, merge or drop. Kept content moves into the new design, every address that changes is redirected at launch, and each template has its own fields for page titles and descriptions.
Can you work with a team in another time zone?
Yes. Most of the work runs in writing: comments in the design file, a written update after each stage and a live review when a decision needs discussion.
What falls outside a B2B website project?
Product and dashboard interface design and ongoing SEO or content production are separate scopes with their own discovery. Approving the claims, figures and any calculator formula that appear on the site stays with your team.
See more of our website work
Each case study explains the problem we started with and the work that followed.