Information architecture
The page map your product actually needs, not the one the template came with. Which pages exist, what each one is for, how they link.

Norml designs and ships the website your product company is judged by — the architecture, the design system in Figma, and the build. For teams raising a round, launching, or replacing a site that no longer matches the product.
A few clients we’ve worked with










It has to explain a product that changes every sprint.
It has to survive investors running due diligence and procurement checking whether you look like a real company.
The template was picked before the product had a shape.
Pages were added one at a time, by whoever had the deadline.
The copy still describes the version that shipped eighteen months ago.
Six things, in the order we do them. Every engagement starts with an agreed page list and the material already available; Norml can take the complete scope or work alongside 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 is for, how they link.
What the product does, said in the words your buyer uses. Written against the real 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.
Product demos, feature reveals, pricing comparisons that work without a sales call.
Next.js with Sanity, or WordPress. Editable by your team, not dependent on us.
The exact page count depends on the product. A typical SaaS 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.
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 — what the current site does and doesn’t do.
[ 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 ]