Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design giving, participation and assistance as different tasks.
We prototype the steps visitors take to support the organisation or seek its services. Forms and confirmation messages describe what actually happened, with safe boundaries between public contact information and sensitive programme records.
A few clients we’ve worked with
What we do
UX/UI design for nonprofits: Journey definition, Interface states, Supported handoffs.
Decisions that shape the work.
What does each action confirm?
Which information belongs in a protected programme system?
What interface decisions cost when nobody makes them.
Interfaces are not decorated; they are decided. When the tasks, roles and states are never agreed, they get invented during development — one screen at a time.
Development stops guessing
An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.
The product survives its next feature
Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.
UX/UI design: scope of work.
The brief records the website scope, approved source material and responsibilities for review.
Journey definition
Separate donations, volunteering and programme enquiries according to their actual workflows.
Interface states
Design forms and navigation with errors, empty states and recoverable failures.
Supported handoffs
Specify external-provider transitions and the next responsible staff action.
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
Audience journey diagrams.
- 02
Interactive Figma prototypes.
- 03
Form-state and handoff specifications.
Our process
How the work runs.
Map real tasks
Review the actions and receiving teams behind the public site.
[ 01 ]
Prototype complete routes
Include unsuccessful and interrupted interactions.
[ 02 ]
Verify message meaning
Check confirmations against actual provider and staff behavior.
[ 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 startedUX/UI design for nonprofits: questions.
Does submitting a form guarantee access to a service?
No. The interface must describe receipt and the organisation’s actual next step without promising eligibility or availability.
Can the public form collect case histories?
Only an explicitly reviewed data workflow should handle sensitive details; the ordinary public enquiry route should remain appropriately limited.
Website 2.0 combines strategy, design, development and launch in one engagement.