Audience decisions
Identify the questions different buyers need answered before they contact the team.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

A website brief needs to establish what buyers should understand before it specifies how pages will look. We map your offers, audiences, supporting evidence, and enquiry needs into a proposed structure that can guide later design and development.
A few clients we’ve worked with










Agree the website’s audiences, page roles, evidence and delivery priorities before design begins.
We do not have an office in Clearwater, and the map is honest about it: the pin is our Florida office in Fort Myers, about 130 miles north-west of our Fort Myers office. The distance changes how easy it is to meet, not how the work runs.
Different offers share an overly broad description
Proof is disconnected from the claims it supports
New pages are commissioned without a defined role
The planning work can produce an offer map, page briefs, a content responsibility list, and a proposed enquiry and measurement approach. We identify reusable page types and record technical questions for verification. Your team reviews the facts and service boundaries. This scope supplies decisions and a build brief; it does not implement the resulting website.
Identify the questions different buyers need answered before they contact the team.
Give each service and product a defined place without duplicating the same proposition.
Map available cases, people and supporting materials to the claims they can substantiate.
Record page priorities, content responsibilities, dependencies and acceptance criteria.
The approved scope determines the final deliverables:
An audience and buyer-question map.
A proposed sitemap with the role of each page.
A content and proof inventory with named gaps.
A prioritized brief for design, copy and development.
Our process
Review the offer, sales questions, existing site and available research with the team.
[ 01 ]Connect audiences and decisions to pages, evidence and contact paths.
[ 02 ]Separate launch requirements from later work and record dependencies.
[ 03 ]Agree the page scope and responsibilities so design and development can proceed with a shared reference.
[ 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