Buyer and page map
Decide which audiences need distinct routes and what each page must help them judge.

A manufacturer may need to show specifications and project evidence; a financial technology team may need to explain a product to buyers and partners. These are examples of different page decisions, not claims about Norml’s local clients. We design the navigation, page types and responsive components around the company’s own buyers. Our Florida office is in Fort Myers.
A few clients we’ve worked with










Design the route from offer to evidence to enquiry before choosing page layouts.
We do not have an office in Jacksonville, and the map is honest about it: the pin is our Florida office in Fort Myers, about 300 miles north of our Fort Myers office. The distance changes how easy it is to meet, not how the work runs.
Products, services and industries compete for the same place in the navigation.
The homepage carries details that belong on specialist pages, while those pages say too little.
Proof appears as a logo strip far from the offer it supports.
Mobile pages preserve desktop order even when a buyer needs a different reading path.
We first map the audience, offer and available proof. The design work turns that map into page roles, wireframes, responsive layouts and a reusable Figma system. Development is a separate scope unless the engagement includes it.
Decide which audiences need distinct routes and what each page must help them judge.
Organize products, services, sectors and case studies so a visitor can find the relevant path.
Design the approved page types with real copy, data tables, forms and content length at desktop and mobile widths.
Define reusable headings, content blocks, cards, filters and states that remain coherent as the site grows.
Provide assets, specifications and review notes so the built pages match the approved designs.
The design handoff is defined by the page inventory and the team that will build it.
An approved sitemap and purpose for each page type.
Wireframes for the buyer paths that matter most.
Responsive Figma designs tested with representative content.
A reusable component library and interaction states.
Developer notes and browser design QA when build is in scope.
Each scope has its own work and deliverables. Start with the one that matches your site’s next decision.
Our process
Review the offer, buyer questions and evidence the business can publish.
[ 01 ]Agree navigation, page roles and the next action for each route.
[ 02 ]Test wireframes and the visual system against real copy and representative data.
[ 03 ]Document states and responsive rules, then review the built pages where development is included.
[ 04 ]
“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.”
Max TymoshynFounder & Architect
Get started