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.
Turn the SaaS website brief into buildable requirements.
Discovery checks the current website, product boundaries, content workflow and acquisition tools. The output is a requirement set that exposes missing inputs before design or development depends on them.
A few clients we’ve worked with
What we do
Website discovery for SaaS companies: website and product boundaries, content inventory, tool and tracking review.
Questions to resolve for website discovery.
A build estimate depends on verified content, access and integration requirements.
Unanswered system questions need owners before development relies on them.
Marketing, documentation and application routes may have different teams and release processes.
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.
What website discovery includes.
The scope below applies to the agreed SaaS website or product workflow. We confirm the source material and responsible owners before work begins.
Website and product boundaries
Map marketing pages, documentation, authentication and application routes. Identify shared navigation and the teams responsible for each surface.
Content inventory
Review feature pages, pricing information, screenshots and campaign variants. Record outdated material and missing product approvals.
Tool and tracking review
Check the CMS, CRM, scheduling tools and signup handoff. Document supported integrations and completion signals.
Selected website projects across our wider practice
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.”
Website discovery deliverables.
The handoff records the product and release boundaries agreed for this work.
- 01
Current content and system inventory
- 02
Build requirements and dependency register
- 03
Open-question log with responsible owners
Our process
How we approach website discovery.
Review the inputs
Inspect the current website and the systems named in the brief.
[ 01 ]
Develop and check
Verify the required content, interfaces and review steps with their owners.
[ 02 ]
Verify and hand over
Separate confirmed requirements and unanswered questions in the build handoff.
[ 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 SaaS companies: questions.
Can discovery be limited to the marketing website?
Yes. The application is reviewed only where website behaviour depends on it, such as a signup link or authenticated redirect.
What do you need from the product team?
A product walkthrough, current feature and plan information, and an owner who can confirm the behaviour described in the requirements.
Discuss the website discovery scope, source material and dependencies for your SaaS website.