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.
Check the nonprofit’s programme and giving workflows before the build.
Discovery examines public content, editorial ownership and the tools behind donation or assistance routes. We identify what the website can support without assuming that a public form should hold sensitive case information or replace programme systems.
A few clients we’ve worked with
What we do
Website discovery for nonprofits: Content inventory, Workflow inspection, Dependency register.
Decisions that shape the work.
Which system owns donation and programme records?
Which routine publishing tasks currently depend on one person?
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 records the website scope, approved source material and responsibilities for review.
Content inventory
List programmes, campaigns, reports and public resources with their owners.
Workflow inspection
Review giving and contact paths using documentation and synthetic examples.
Dependency register
Verify provider capabilities, access needs and unresolved operational decisions.
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.
The agreed engagement produces the following artifacts.
- 01
A content and asset inventory.
- 02
A giving and contact workflow map.
- 03
A build-requirements and dependency register.
Our process
How the work runs.
Inspect the current site
Record public pages and the systems they link to.
[ 01 ]
Trace operational handoffs
Review who receives each action and handles exceptions.
[ 02 ]
Document the scope
Assign missing information and provider questions before implementation.
[ 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 nonprofits: questions.
Do you need beneficiary case files?
The default website discovery uses approved public information and synthetic examples, not sensitive case records.
Will any donation platform support the requested design?
Its supported checkout, embedding and reporting capabilities need verification before that commitment.
Website 2.0 combines strategy, design, development and launch in one engagement.