Information architecture
The page map your product actually needs, not the one the template came with. Which pages exist, what each one has to prove, and how a visitor gets from the homepage to a signup.

Norml designs and ships the website your product is judged by — the architecture, the design system in Figma, and the build. For B2B SaaS teams who need the site to explain the product, earn the demo, and survive an investor reading it line by line.
A few clients we’ve worked with










The product changes every sprint, and the website still describes the version that shipped eighteen months ago.
Visitors reach the pricing page without understanding what the product does, so they never book the demo.
The template was chosen before the product had a shape, and every new page fights it.
Investors running due diligence and procurement teams checking whether you look like a real company read the same unfinished site.
Every launch adds another SaaS landing page in its own style, because there is no system to build them from.
Seven things, in the order we do them. Web design for SaaS starts with an agreed page list and the material you already have; Norml can take the whole scope or work beside your content and development teams.
The page map your product actually needs, not the one the template came with. Which pages exist, what each one has to prove, and how a visitor gets from the homepage to a signup.
What the product does, said in the words your buyer uses. Written against the shipped product, not the roadmap.
Structure agreed before anything is styled, so design review is about design and not about what belongs on the page.
Components, states, responsive rules. The thing that keeps page ten looking like page one.
Launch, campaign, and paid-traffic pages built from the same system, so the next SaaS landing page takes days instead of a redesign. Built on the stack the site already runs — a WordPress SaaS landing page your marketer edits, or a Next.js route — including rebuilding the ones you inherited from a page builder.
Product demos, feature reveals, and pricing comparisons that do their work without a sales call.
Next.js with Sanity, or WordPress — including moving off Webflow, Squarespace, or a page builder without losing the rankings you have. Editable by your team, not dependent on us.
The exact page count depends on the product. A typical B2B SaaS website design engagement hands over the following:
A page map you can hand to anyone — every URL, its job, and what links to it.
A Figma design system with components, states, and responsive rules.
Page content written against the shipped product.
Reusable landing-page layouts for launches and campaigns.
A built site on Next.js and Sanity, or WordPress — your team edits it.
Analytics and Search Console configured on day one, not after launch.
A handoff session and the files, so nothing about the site depends on us staying.
Our process
We read the product, the analytics, and the sales calls. Not a questionnaire. You get the diagnosis — where visitors stall and what the current site fails to explain.
[ 01 ]Page map, URL structure, and what each page has to prove. A sitemap you can argue with before anything is designed.
[ 02 ]Wireframes first, then the system in Figma. Components and states, not a stack of static screens.
[ 03 ]Next.js with Sanity, or WordPress. A site your team can edit without a developer.
[ 04 ]Redirects, analytics, Search Console, speed. Launch without losing the rankings you already had.
[ 05 ]