How to Choose a Web Designer for Your Nonprofit (Without Getting Burned)
The Stakes Are Higher Than You Think
When a for-profit business launches a bad website, they lose some revenue and move on. When a nonprofit launches a bad website, it can stall fundraising, confuse volunteers, and undermine years of community trust.
Your budget is limited. Your board is watching. And the wrong web designer can leave you with a site you can't update, can't afford to fix, and can't take with you if you need to leave. Choosing carefully isn't being picky. It's being responsible with donor dollars.
Red Flags That Should Stop You Cold
Not every web designer who says they work with nonprofits actually understands what that means. Watch for these warning signs before you sign anything.
No Portfolio or Outdated Work
If a designer can't show you recent, live websites they've built, walk away. Screenshots of old projects that are no longer online tell you nothing about their current skills or the durability of their work.
Look at their portfolio sites on your phone. Try navigating them. If their own showcase sites are slow, clunky, or broken on mobile, imagine what they'll build for you.
Zero Mention of Accessibility
If accessibility doesn't appear anywhere on their website, their proposals, or in your conversations, they're not thinking about it. That's a problem for any organization, but especially for nonprofits that serve diverse communities.
Web accessibility isn't a bonus feature. It's a legal consideration under the ADA, and it's a moral one for organizations that claim to serve everyone. A designer who doesn't bring it up unprompted probably doesn't build for it.
Vague or "It Depends" Pricing
Every project has variables, but a professional designer should be able to give you a clear range based on your needs. If every answer is "it depends" with no follow-up specifics, you're likely to end up with surprise invoices.
Ask for a written scope of work before you commit. If they resist putting numbers on paper, they're either disorganized or deliberately keeping things fuzzy. Neither is good for your nonprofit.
Proprietary Platforms You Can't Leave
Some designers build on proprietary systems where they control the hosting, the code, and your ability to move. If you stop paying them, your website disappears. If you want to switch agencies, you start from scratch.
This is one of the most expensive mistakes nonprofits make. You invest thousands in a website, then discover you don't actually own any of it. Always ask: "If we part ways, what do we keep?"
No Post-Launch Support Plan
A website isn't finished the day it launches. Content needs updating. Analytics need reviewing. Security needs monitoring. Questions will come up.
If a designer's proposal ends at launch with no mention of what happens next, you'll be on your own the moment something breaks. Or worse, you'll be paying emergency rates for help that should have been planned for.
Green Flags That Build Confidence
Great nonprofit web designers share certain qualities. Here's what to look for.
Transparent, Written Pricing
The best designers publish their pricing or provide detailed proposals that break down exactly what's included. You can see line items. You understand what costs extra. There are no hidden fees waiting to appear mid-project.
Transparent pricing respects your budget process. It lets you present clear numbers to your board. It builds trust from the very first conversation.
Accessibility Compliance Built In
Look for designers who mention WCAG standards by name. They should be able to tell you what conformance level they build to (WCAG 2.1 AA is the current standard for most organizations) and how they test for it.
Even better, ask them to show you accessibility scores on sites they've already built. Tools like Google Lighthouse and WAVE generate accessibility reports that are hard to fake. If their existing sites score well, yours likely will too.
CMS Training Included
Your team needs to update the website after launch. A good designer includes training on whatever content management system they use, whether that's WordPress, Sanity, or something else.
Training should cover the specific tasks your team will actually do: publishing blog posts, updating event information, adding staff photos, changing service times. Generic "here's the dashboard" walkthroughs aren't enough.
Performance Scores They're Proud Of
Ask to see Google Lighthouse scores for sites they've built. Performance, accessibility, SEO, and best practices each get a score out of 100. Designers who build fast, well-structured sites will happily share these numbers.
If they don't know what Lighthouse is or can't produce scores, that tells you something about their priorities and their process.
You Own Everything
The right designer makes ownership clear from day one. You own the code. You own the design. You own the content. You own the domain. You control the hosting account.
If the relationship ends, you walk away with everything you paid for. No hostage situations. No rebuilding from zero. This should be in writing, ideally in the contract.
Questions to Ask Before You Sign
Print this list. Bring it to every introductory call. The answers will tell you everything you need to know.
"What accessibility standard do you build to?"
The answer should be specific: "WCAG 2.1 AA" or "WCAG 2.2 AA." If they say "we make it accessible" without naming a standard, they're winging it. Accessibility without a defined standard is just guessing.
"What's included in the price, and what costs extra?"
Get this in writing. Common surprises include: stock photography, copywriting, additional pages beyond the original scope, third-party integrations, SSL certificates, and ongoing hosting. A thorough proposal lists all of these clearly.
"Who owns the website when it's done?"
You want to hear: "You own everything. The code, the design files, the content, the domain registration, and the hosting account are all yours." Anything less than full ownership is a red flag.
"What happens after launch?"
Good answers include details about a support period, content update training, a maintenance plan (with pricing), and a clear process for requesting changes. Great answers include analytics review sessions to help you understand how the site is performing.
"Can I see performance and accessibility scores for sites you've built?"
This is the question that separates confident builders from the rest. Designers who prioritize performance and accessibility will pull up scores eagerly. Those who don't will change the subject.
"What platform do you build on, and why?"
Listen for reasoning, not just a name. "We use WordPress because it's popular" is a weaker answer than "We chose this platform because it gives our nonprofit clients better performance and lower ongoing costs." The why matters more than the what.
Understanding Price Ranges
Web design pricing varies wildly, and nonprofits often don't know what's reasonable. Here's a realistic breakdown by project type.
DIY and Template Sites: $0 to $500
Platforms like Squarespace, Wix, or a free WordPress theme with minimal customization. You're doing the work yourself, making design choices within the constraints of a template, and handling your own content.
This works for brand-new organizations that need something online quickly. The tradeoff is generic design, limited accessibility, and the ongoing subscription cost of the platform ($12 to $40 per month adds up over time).
Custom Design on Existing Platforms: $1,500 to $3,500
A professional designer creates a custom look for your organization using an established platform. You get a unique design, some accessibility attention, and basic CMS training.
This is a good fit for small nonprofits that need a polished online presence but don't require complex features. At this range, expect 3 to 7 pages, a contact form, and basic SEO setup.
Full Custom Build: $3,500 to $6,500+
Custom design, custom development, accessibility compliance, CMS training, performance optimization, and a post-launch support plan. You get a site built specifically for your organization's needs, not a template with your logo swapped in.
This range makes sense for organizations where the website is central to their mission: accepting donations, registering volunteers, communicating with members, or serving as a public resource. The investment pays back through better conversions, lower maintenance costs, and a longer useful lifespan.
When to Spend More
Some projects genuinely need larger budgets. If you need e-commerce, membership portals, complex integrations with existing systems, or multilingual support, expect costs above the ranges listed. Get multiple proposals and compare scope, not just price.
How to Evaluate Proposals
When you have two or three proposals in front of you, here's how to compare them honestly.
Look past the total price. A $2,000 proposal that doesn't include accessibility, training, or post-launch support will cost you more than a $4,000 proposal that includes everything. Compare what you're actually getting.
Check the timeline. Rushed timelines (under 4 weeks for a full site) often mean corners are being cut. Extremely long timelines (6+ months) might mean you're not a priority. A realistic custom build takes 6 to 12 weeks for most organizational websites.
Read the contract carefully. Look for ownership clauses, revision limits, payment schedules, and cancellation terms. If there's no contract, that's the biggest red flag of all.
Talk to their past clients. Ask for references from other nonprofits they've worked with. When you call those references, ask: "Would you hire them again?" That single question reveals more than any portfolio ever could.
The Most Important Thing
If you take one idea away from all of this, let it be ownership.
You should own your code. You should own your design files. You should own your content. You should own your domain name. You should control your hosting account.
Everything else can be fixed, rebuilt, or improved over time. But if you don't own your website, you don't really have one. You're renting someone else's property, and they can change the terms whenever they want.
A good nonprofit web designer builds something that belongs to you completely. When the project is done, you could walk away and take everything with you. That's not just a nice policy. It's the only ethical way to work with mission-driven organizations spending donor funds.
Your website is too important to leave in someone else's hands. Own it. Protect it. And choose a designer who wouldn't have it any other way.
