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.
Resolve the content and system questions behind the healthcare brief.
Before a build, we inspect what the public site depends on: product information, reviewer availability, content ownership and supported integrations. Discovery turns these dependencies into requirements the delivery team can test.
A few clients we’ve worked with
What we do
Website discovery for healthcare teams: existing-site inventory, system boundaries, delivery requirements.
Decisions that shape the scope.
Which public-site functions depend on an external platform?
What content or access is missing from the brief?
What discovery settles before design starts.
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.
Dependencies appear early
Technical constraints and the systems the website has to live with are identified before they become a mid-build surprise.
The next stage can be scoped
A brief naming the decisions and open questions lets design, content and development be quoted against something real.
Website discovery: scope.
These work areas are scoped against the organisation’s existing site, approved information and available technical access.
Existing-site inventory
List pages, assets, languages and owners. Record where current product information lives and which sources are approved for reuse.
System boundaries
Document the distinction between public marketing, authenticated applications and patient-facing systems. Check supported integration routes before promising shared data flows.
Delivery requirements
Define page types, acceptance checks and access needs. Assign unresolved questions to the relevant content or technical owner.
Selected healthcare and life-science website projects
All case studies
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“I was impressed by Norml Studio's good communication and efficiency.”
“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.”
What you receive.
The brief identifies which outputs are required and who reviews them.
- 01
A content and dependency inventory.
- 02
A public-site system-boundary map.
- 03
Requirements, acceptance criteria and an open-question register.
Our process
How the work runs.
Inspect the current site
Inventory content, integrations and the people responsible for them.
[ 01 ]
Investigate dependencies
Check documentation and identify requirements that need a feasibility decision.
[ 02 ]
Document requirements
Hand over testable scope and the open questions with their owners.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“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 startedWebsite discovery for healthcare: questions.
Can discovery include patient records?
The website discovery can use synthetic examples and system documentation. Access to sensitive records is outside the default public-site scope.
Does discovery commit us to a platform?
No. It documents constraints and findings so a platform decision can be made with those inputs.
Website 2.0 combines strategy, design, development and launch in one engagement.