The Nonprofit Web Developer Vetting Checklist: Questions to Ask Before You Hire

Most nonprofits hire the first web developer or agency that returns a quote. Two years later, they’re stuck with a website no one can update, support that ignores emails, and no idea what they actually own. By then, you’ve already spent the budget, and the damage is done. The fix? Ask the right questions upfront. This checklist is designed for executive directors, nonprofit board members, and development staff who aren’t tech experts but know better than to trust a sales pitch alone.

If you’re evaluating web design for Charlotte nonprofits, this template will save you thousands in regret and wasted cycles. The questions below are the ones that actually matter. Print them out, hand them to vendors, and listen to how they answer, not just what they say.

Why Nonprofits Get This Wrong

Nonprofits operate on tight budgets and usually don’t have dedicated IT staff. When the website goes down, there’s no internal person to call. That’s why the agency’s support model matters more than their design portfolio. A beautiful site that you can’t update, or for which nobody answers the phone, is an expensive decoration.

Four Eyes has worked with Charlotte nonprofits since 1998, including organizations like Roof Above, Dilworth Church, and Camp North End. Over 28 years, we’ve learned that nonprofits don’t need cutting-edge features. They need reliability, people who answer emails, and systems they can actually use. The difference between a successful nonprofit site and a failed one often isn’t the design. It’s whether the person or agency supporting it actually shows up.

When you’re evaluating a developer or agency, you’re not just evaluating their coding skills. You’re betting that they’ll answer your phone calls in years two and three. You’re trusting them with your donor relationships, your volunteer management, and your credibility. That deserves more than a portfolio and a handshake.

How Roof Above Learned This the Hard Way

Roof Above is a Charlotte nonprofit that connects individuals and families with stable, safe housing. They’re doing critical work in Uptown and South End Charlotte, and they needed a website that didn’t require a web developer on staff just to update a program description.

When they came to Four Eyes three years ago, their previous site was built by a freelancer who’d essentially disappeared. No support. No documentation. No one knew what platform it was built on or how to add a new staff member’s bio. The nonprofit had paid for the site five years earlier, and they were still paying a different developer to answer simple questions because the original builder was unreachable.

We rebuilt it on WordPress using a modern, maintainable platform. We provided training on how to make updates themselves. We documented everything. We committed to answering the phone. Three years later, they have a site that works, they can manage most of it themselves, and when they need help, we’re here. You can read more about how we rebuilt Roof Above’s nonprofit website in their case study.

That’s not fancy. But for a nonprofit, that’s everything.

Common Mistakes Nonprofits Make When Hiring

1. Picking based on price alone. The cheapest quote often comes from someone who will disappear fastest. You’re not saving money on a $3,000 site if you end up paying $500 a month for someone else to support it.
2. Hiring a family member’s friend who “knows computers.” Personal connections don’t replace professional support, documentation, and insurance. When something goes wrong, there’s no recourse.
3. Not asking about support upfront. Every nonprofit thinks support will be free or cheap. It usually isn’t, and when you don’t define it upfront, you get silence instead.
4. Assuming the cheapest platform is the best. A template builder (Wix, Squarespace) seems cheap. But nonprofits often outgrow them, can’t integrate specific tools, and end up rebuilding.
5. Not getting a contract. A handshake or an email exchange isn’t protection. You need a document that spells out what you’re getting, what it costs, and what happens if something goes wrong.
6. Focusing only on design. A beautiful website means nothing if donors can’t give or volunteers can’t sign up. Function matters more than aesthetics.

How to Measure If You Made the Right Choice

Six months in, your website choice was either right or a regret. Here’s what to check:

• Does your team actually use it? If staff are avoiding the site because it’s too complicated, you made a mistake. A good nonprofit site should be intuitive enough that your marketing coordinator can update it in 15 minutes.
• Are people calling you because they found information on the site? Use Google Analytics to track which pages get traffic and which are ghost towns. If nobody’s reading it, something’s wrong.
• Can you reach your developer when you need to? Email them a test question. Is the response time measured in hours or weeks? First test of a support relationship is responsiveness.
• Do you understand what you’re paying for? Pull your receipts. Do the monthly bills match the original quote? Are there surprise charges? If yes, you hired someone who wasn’t transparent upfront.
• Are donors finding you online? If nonprofit-specific traffic (searches for your mission, your programs, donation pages) isn’t increasing, the site isn’t working as a fundraising tool.

The Long Game: Why Experience Matters

Four Eyes has been building websites for Charlotte nonprofits, contractors, churches, and local businesses since 1998. That’s 28 years in one city. We’ve worked with organizations in South End, Uptown, NoDa, Dilworth, and neighborhoods across the greater Charlotte area. We’ve built sites for Roof Above, Dilworth Church, Camp North End, and organizations like Charity Navigator, Charlotte Is Creative, and Pasadena Arts Alliance.

That longevity means something. We’ve seen what works. We’ve learned what breaks. We’ve sat through enough nonprofit board meetings to know that your web budget is real money from donors, and you can’t waste it.

When you hire an agency that’s been in business for five years, you’re taking a risk that they’ll be gone in ten. When you hire someone who’s been in Charlotte for 28 years, with client relationships spanning over a decade, you’re hiring someone who has skin in the game and a reputation to protect.

That’s not ego. That’s just how relationships work.

The Final Questions Before You Sign

Before you shake hands or click submit on that proposal, ask one more time:

1. Are you comfortable calling this person or agency in year three with a problem?
2. Did they listen to your needs, or did they push a template?
3. Do they have real nonprofit experience, not just corporate work they’re stretching?
4. Are they transparent about costs, or are there question marks in the budget?
5. Can you actually read and understand the contract, or is it written in legal jargon?

If the answer to all five is yes, you’re in good shape. If one is no, keep looking. Nonprofits can’t afford to waste money on the wrong partner.

FAQs

What’s the difference between a nonprofit web developer and a regular web developer?

The best nonprofit developers understand that nonprofits have constraints regular businesses don’t: smaller budgets, volunteer staff, limited IT support, and mission-driven priorities. A good nonprofit specialist will ask about your programs and your donors, not just your traffic numbers. They’ll recommend tools that integrate with donation platforms and volunteer management systems, not just general-purpose software. And they’ll build with the assumption that you’ll need support, not that you’ll disappear into maintenance mode.

How much should a nonprofit website cost?

A professional nonprofit website built on WordPress by a reputable Charlotte agency typically ranges from $5,000 to $20,000 depending on complexity. Ongoing monthly support usually costs $200 to $500. If someone quotes $1,000 for a website, be skeptical. If someone quotes $5,000 without explaining what’s included, ask follow-up questions. The cost should map directly to the scope of work.

Should we use a template builder like Wix or Squarespace?

Templates work for very basic sites, and they’re cheap upfront. The problem is they limit customization, they don’t integrate well with nonprofit-specific tools, and you’ll often outgrow them. If your nonprofit is tiny and your website needs are simple (just a contact form and program description), a template might work for now. But most Charlotte nonprofits eventually need to migrate to something more flexible. Better to build right the first time.

What if our current website was built by someone we can’t reach anymore?

You have a few options. You can hire someone to audit the site and build documentation. You can ask if the original domain registrar or hosting provider has backup contact info. Or you can rebuild on a modern platform with a documented, professional partner. Many nonprofits choose to rebuild because it’s cleaner and you don’t inherit the original builder’s technical debt.

How do we protect ourselves if the agency goes out of business?

Get a contract that specifies you own your domain name, content, and website files. Ask for documentation of how the site is built and how to access the hosting. Consider requiring a transition plan in the contract if the agency closes. And choose a partner with longevity, not a one-person shop with no backup. That’s why checking how long they’ve been in business matters.

What should we look for in a nonprofit web developer’s portfolio?

Look for examples of nonprofit sites that are still live and well-maintained. Check if they have real case studies, not just pretty screenshots. Call the nonprofits they list as references. Read reviews if they have any online. And remember: a beautiful corporate site doesn’t prove they can build a nonprofit site. Look for nonprofit work specifically.

Can we make updates to the site ourselves, or do we always need to call the developer?

It depends on the platform and your comfort level. WordPress sites can be set up so nonprofits can update simple things like text and images without touching code. Wix and Squarespace are even easier. Custom-built sites are harder. When you’re evaluating a developer, ask explicitly: “Can our staff make simple updates, and is there training included?” The answer tells you a lot about whether they’re building for your independence or your dependence.

What happens to our website if we stop paying for support?

A good developer will make sure you can still access your own site and content. The website doesn’t vanish or lock up. What stops is regular maintenance, updates, and their availability to help you. A bad developer will make the site disappear or become inaccessible if you stop paying, holding your content hostage. This is something to clarify upfront and get in writing.

How often should we update our nonprofit website?

At a minimum, you should review and refresh content every 90 days: add new programs, update staff, change testimonials, fix links. Add a blog post or news update at least monthly if possible. The more actively you maintain it, the better Google ranks it and the more relevant it stays for donors and volunteers. This is where training from your developer comes in handy.

Should we hire locally or can we use a developer anywhere?

Either can work, but hiring a developer local to Charlotte who understands the nonprofit landscape and can meet you in person has real advantages. They understand Charlotte neighborhoods and local organizations and can provide phone support more easily. They also have reputation stakes in the community. That said, there are good remote developers, too. The key is responsiveness and nonprofit experience, not geography. But all else being equal, local matters.