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 data and approval requirements before building.
A financial website may depend on several data owners, audience definitions and publishing approvals. We inspect these dependencies and turn the brief into requirements that design and engineering can assess.
A few clients we’ve worked with
What we do
Website discovery for fintech companies: public data inventory, publishing workflow review, integration requirements.
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.
Public data fields and private account information need clearly separated boundaries.
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 financial website or platform workflow. We confirm the source material and responsible owners before work begins.
Public data inventory
List data sources, permitted fields, update frequency and ownership. Record what must remain inside authenticated systems.
Publishing workflow review
Identify the people who approve product descriptions, disclosures and figures. Check the CMS against the required review stages.
Integration requirements
Document enquiry routing, existing platform boundaries and third-party interfaces. Mark unavailable access or undocumented behaviour as open work.
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“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“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.”
“Norml Studio's professionalism and responsiveness were impressive.”
Website discovery deliverables.
The handoff records the financial product and publication 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 fintech companies: questions.
Do you need access to customer financial records?
Discovery should use documentation, schemas and safe sample data wherever possible. Any access to sensitive systems must be separately defined and authorised.
What if a provider has no usable API?
We record the limitation and evaluate supported alternatives. The scope will not assume an integration that has not been verified.
Discuss the website discovery scope, source material and dependencies for your financial website.