Design and build stop stalling
Missing decisions are identified and resolved in planning, so production is not waiting on an answer nobody owns.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

We define the ecommerce website’s priorities using the actual catalogue, order process and customer questions. The plan connects merchandising, buying decisions and operational responsibilities before the team commits to a new page list or platform.
A few clients we’ve worked with




















Website strategy for ecommerce businesses: shopping priorities, order responsibilities, release plan.
Catalogue organisation and warehouse organisation can serve different purposes.
A storefront promise needs a working fulfilment and support process behind it.
A redesign priority needs evidence beyond a preference for a new theme.
A website project needs more than a list of pages. Without the decisions written down, they get made later, by whoever happens to be in the meeting.
Missing decisions are identified and resolved in planning, so production is not waiting on an answer nobody owns.
An agreed, documented direction means the next team — yours or ours — can work against the same reference.
When the direction is written down, a late request can be measured against it instead of quietly absorbed.
Plan shopping priorities, order responsibilities and release plan as connected parts of the engagement.
Identify the product categories, customer groups and purchase decisions the store needs to support. Account for repeat purchases, considered purchases and appointment-led selling where relevant.
Map checkout, fulfilment, returns and customer-contact ownership. Record the systems and people needed to deliver what the storefront promises.
Choose the first changes using available evidence and operational dependencies. Define the content, tracking and verification needed for launch.
“What I appreciate most is that the team always communicates openly and stays honest throughout.”
“They delivered what they said they would, on time.”
“They met all our expectations by providing great strategies based on our needs.”
The agreed website strategy scope is documented in the following work products.
Audience and page-priority brief
Conversion-route and responsibility map
First-release scope with open decisions
Explore the wider scope behind the website.
Write the pages that explain your offer, answer buyer questions, and support your claims with evidence.
Resolve website requirements, stakeholder priorities, technical constraints, and scope before the build.
Organize pages, navigation, content types, and internal links around visitor needs.
Write project stories using documented work, verified outcomes, and approved source material.
Explore the scope, deliverables and process for each part of the website.
Our process
Review the real range and distinguish repeat buying, comparison and appointment-led shopping needs.
[ 01 ]Match storefront offers with fulfilment, returns and support responsibilities.
[ 02 ]Agree page and workflow changes using available evidence, content readiness and operational dependencies.
[ 03 ]No account layer between you and them. These are the Norml specialists this work runs through.

“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