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 dependencies behind a biotech website brief.
Before a build, we inventory public content, pipeline records, publication sources and the people who maintain them. Discovery identifies what the site can support now and which integrations, approvals or missing assets need a decision before implementation.
A few clients we’ve worked with
What we do
Website discovery for biotech companies: content inventory, system boundaries, build requirements.
Decisions for the biotech website.
Where are programme and publication records maintained?
Which approval or system dependency could prevent a page from shipping?
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 of work.
The brief identifies the public information, website functions and review responsibilities included in the engagement.
Content inventory
List existing pages, scientific figures, documents and language variants with their owners.
System boundaries
Separate public publishing from research systems, partner workspaces and restricted repositories.
Build requirements
Record supported interfaces, editing tasks and testable acceptance criteria for the proposed site.
Selected work in genomics, pharma and science communication
All case studies
What clients say.
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.”
What you receive.
These deliverables are prepared for the agreed website scope.
- 01
A content and asset inventory.
- 02
A dependency and access-ownership map.
- 03
Requirements with an open-decision register.
Our process
How the work runs.
Inspect the current website
Review public pages and the agreed editing environment.
[ 01 ]
Trace dependencies
Identify the sources and reviewers behind changing programme information.
[ 02 ]
Document the build scope
Translate findings into requirements and assign outstanding decisions.
[ 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 biotech companies: questions.
Do you need confidential research data for discovery?
Usually not. Public website planning can use approved summaries, system documentation and synthetic examples.
Does discovery choose the CMS automatically?
No. It records requirements that inform the choice, including editorial controls and the structure of the content.
Website 2.0 combines strategy, design, development and launch in one engagement.