Stakeholders agree once
Sessions surface competing priorities while they are still cheap to reconcile, not after a design has been drawn to one of them.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

Discovery examines the current site, publishing responsibilities and appointment systems. Norml records the dependencies that affect a dental website build so the scope describes work the team can actually deliver.
A few clients we’ve worked with




















Website discovery for dental practices: website inventory, system review, scope and acceptance.
Which pages and files need to move into the new site?
What appointment-provider capabilities can the website actually use?
A project can be ready for discovery before it is ready for design. Finding the unresolved questions early is what keeps the build from pausing.
Sessions surface competing priorities while they are still cheap to reconcile, not after a design has been drawn to one of them.
Technical constraints and the systems the website has to live with are identified before they become a mid-build surprise.
A brief naming the decisions and open questions lets design, content and development be quoted against something real.
The agreed scope names the website work, source material and people responsible for review.
List treatment pages, locations, clinician profiles, files and existing URLs that need a decision.
Identify the appointment provider, supported website handoff and account owners without accessing patient records.
Define what will be built, who supplies content and how the practice will review the result.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
The engagement includes the following artifacts for the agreed scope.
A current-site and content inventory.
A system dependency and account ownership record.
A build scope with acceptance checks and open decisions.
Explore the wider scope behind the website.
Define the audience, message, page structure, and requirements before the website moves into production.
Write the pages that explain your offer, answer buyer questions, and support your claims with evidence.
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 public pages and the editing setup using the agreed access.
[ 01 ]Confirm provider capabilities and reception requirements before promising an integration.
[ 02 ]Assign unresolved questions and define the conditions for starting design and development.
[ 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