Business and audience discovery
Discuss the offer, buying process, business priorities, and the questions visitors need answered before contacting your team.
Website strategy before the build begins.
Norml helps B2B teams decide what their website needs to say, show, and do. We turn business goals, buyer questions, existing evidence, and technical constraints into a page structure and a practical brief for the work ahead.
Book a callA website project needs more than a list of pages.
Stakeholders need to agree which audiences and offers the website should prioritize.
Several products or services need an understandable relationship in the site structure.
Your team is deciding what to retain, rewrite, combine, or retire.
Design and development need a brief that explains the purpose of each page.
Content, integrations, and approvals need clear owners before production starts.
What our website strategy services include.
This is the planning stage for a new website or a substantial update. We review the material you already have, identify missing decisions, and document the agreed direction so the next team can work against a common brief.
Current website review
Assess the existing content, page structure, journeys, available analytics, and constraints that will influence the new site.
Messaging priorities
Identify the core explanations, supporting proof, and distinctions the website needs to communicate.
Sitemap and information architecture
Organize the approved page set, navigation groups, service relationships, and important paths through the website.
Page and content requirements
Define each page’s job, required sections, source material, main action, and dependencies for writing and design.
Delivery brief
Bring the decisions together with technical requirements, scope boundaries, responsibilities, and review criteria.
Website strategy deliverables.
The agreed scope identifies which of these deliverables your project needs.
- 01
A website brief tied to business priorities.
- 02
An audience and buyer-question summary.
- 03
An agreed sitemap and page inventory.
- 04
Messaging and proof priorities.
- 05
Page-level content and functional requirements.
- 06
A handover brief for content, design, and development.
Our process
How our website strategy process works.
Collect the inputs
Review current pages, sales material, research, analytics, and stakeholder perspectives.
[ 01 ]
Resolve priorities
Agree the audiences, offers, and visitor actions that matter most to the website.
[ 02 ]
Plan the structure
Organize pages and journeys, identifying where existing material can be reused and where new content is needed.
[ 03 ]
Define the requirements
Document the page content, functionality, evidence, and responsibilities needed to execute the plan.
[ 04 ]
Align the team
Review the brief with decision-makers and prepare the approved direction for the production team.
[ 05 ]Website strategy questions.
Can we use the strategy with another agency?
Yes. The deliverable is an organized brief for the people writing, designing, and building the website. Norml can also carry the project into production.
Does this include finished website copy?
The strategy defines messaging priorities and content requirements. Finished page copy is a separate deliverable that can be added to the engagement.
Is this useful for an existing website?
Yes. It can help organize an expansion or redesign by identifying what to retain, change, or add before implementation.
Who should participate?
A decision-maker who understands the business, the marketing owner, and relevant sales or subject-matter experts. Technical input is useful when integrations or platform constraints affect the scope.
Do you need analytics before starting?
Existing analytics and search data are useful when available. Where evidence is missing, we record the gap and distinguish assumptions that need validation.
Website 2.0 combines the planning work with content, design, development, and launch.