Choose charity website developers by checking how they plan the build and what happens after launch.

A charity website often serves people seeking help alongside supporters and staff. That mix makes the brief harder than a standard brochure site, even when the finished website looks simple.

The right developer will ask about those competing needs before discussing colours or page layouts. This guide gives you practical questions for meetings and a way to compare the answers in writing.

KC Web Design's website design service for nonprofit organisations explains its approach. You can also check the work in its live website portfolio against the inclusions on the website design pricing page.

What should charity website developers ask before quoting?

Good charity website developers start with visitor tasks and internal responsibilities. They need to know who uses the site, what each group must do and who can approve decisions. A crisis service needs a different path from a grant-making foundation.

Find out how discovery will separate people seeking support from people offering money or time, then ask who turns the discussion into an approved page plan.

A useful first workshop should produce clear answers to questions such as:

  • Which two visitor tasks matter most on the homepage?
  • What information must remain easy to find during a campaign or emergency?
  • Who approves service information, fundraising claims and privacy wording?
  • Which pages will staff need to update without developer help?

In our review of Australian nonprofit website examples, Big Group Hug separates giving money, donating goods and volunteering. Lord Mayor's Charitable Trust gives grant applicants and donors different routes. Use that idea as a test during discovery.

Does the developer understand charity website constraints?

A developer's charity experience should change the questions asked at the start. Client logos alone do not explain how the team handled multiple audiences or sensitive enquiries. Pick one similar project and have the developer walk through its decisions, including what staff could manage after launch.

The developer should also ask how donation forms, volunteer applications and service enquiries collect personal information. The Australian Information Commissioner says not-for-profits may have Privacy Act obligations and should collect only what they need, store it securely and delete it when no longer required.

Ask the developer to explain these charity-specific decisions in plain language:

  1. How will the site separate support, donation and volunteering pathways?
  2. Where will donation and enquiry data go after a form is submitted?
  3. How will expired appeals and old program information be found and removed?
  4. What can staff change safely, and what still needs technical help?

Read the OAIC privacy guidance for not-for-profits before the scoping meeting. It explains what to check when a form collects supporter or service-user information.

What evidence should a developer show?

A portfolio screenshot proves very little. Open two or three live websites on your phone and complete a real task on each one. Find an eligibility requirement, a service contact or the donation form without getting lost.

Ask what part of the site the developer built and whether the live version still reflects that work. Be wary of donation claims that do not separate website changes from a fundraising appeal or extra advertising. You need something concrete to compare.

Run the same short test on every provider in your shortlist:

  • Open a live client site on a narrow mobile screen.
  • Complete one task that matters to that organisation.
  • Check whether labels explain what happens after a click.
  • Ask the developer to identify one compromise made during the project.
  • Request a reference from a client whose staff still maintain the site.

Click through the finished sites rather than stopping at mock-ups. Test a form and find out who maintains the site now.

How should you compare developer quotes?

Read what each quote leaves out before you compare totals. Two quotes can cover the same number of pages but very different work. One may include copywriting and migration while the other expects your team to supply finished text and move old resources.

Each developer should list exactly what will be supplied in plain language. The quote should name its assumptions and revision limits, including when a change becomes billable. Published inclusions are useful because they show what a stated price actually covers.

Put each quote beside this scope list and mark every item included, excluded or unclear:

  • Discovery workshops and a written page plan
  • Copywriting, editing and migration of existing resources
  • Donation, volunteer and service enquiry form setup
  • Accessibility testing and fixes before launch
  • Redirects from old page addresses and analytics setup
  • Staff training, launch support and a written warranty period

If the budget does not cover the whole list, ask which features can wait and what a later phase would require. Put that answer in the scope rather than relying on a verbal promise.

Who owns the website and its accounts?

Your charity should know what it owns, what it licenses and what it can take elsewhere. Get that answer in writing before work starts. The agreement should cover the domain, website files, content, analytics, donation tools and project accounts.

Keep account access shared because staff and suppliers change. Ownership plus a documented handover lets another qualified provider take over, although an outdated or proprietary system may still limit what can be moved.

Ask for an account register that records:

  1. The service name and what it controls
  2. The charity-owned email address attached to the account
  3. Who has administrator access
  4. How access will be handed over when staff or suppliers change

The finished project should include that register, current credentials through a secure handover method and a plain-language exit process. "We look after everything" is not an ownership plan.

How should accessibility, privacy and payments be scoped?

Set the accessibility and privacy requirements in the brief. The developer should name the accessibility standard and explain the testing. The W3C organises WCAG 2 around four principles with testable criteria at three levels.

An overlay or toolbar does not show that the underlying pages have been tested. The team should check keyboard use, headings, form labels and errors, along with colour contrast and zoom. Each form field also needs a purpose and a known storage location.

Put these items in the project sign-off list:

  • Named WCAG target and a record of manual testing
  • Form labels, errors and confirmation messages tested with a keyboard
  • A list of personal information collected by each form
  • Donation receipts, failed-payment messages and notification emails tested
  • Third-party services and ongoing fees documented

The W3C overview of WCAG 2 is a better reference than an agency badge. It helps your team ask what was tested and what level the developer is promising.

Which charity website developer red flags matter?

Several red flags should stop the shortlist process. Walk away from a provider that will not name the platform or confirm ownership. Treat guaranteed fundraising results with equal caution because donations also depend on the cause and campaign.

Another warning is a process built around one big reveal. If several people approve the project, schedule reviews before development is complete. Check the page plan first, then sample content and a working visitor path.

Pause the shortlist if a developer:

  • Quotes without asking about audiences, approvals or current content
  • Shows screenshots but will not share live work or client references
  • Treats an accessibility plugin as the complete accessibility plan
  • Leaves content, migration or post-launch support undefined
  • Requires accounts to remain under the developer's email address
  • Cannot explain how your charity could move to another provider

The developer should say when a legal, privacy or fundraising question needs advice outside their role. An instant yes to every request is not useful.

Frequently asked questions

Shortlisting charity website developers gets easier when every provider answers the same practical questions. Write down what each provider includes and the evidence offered for it.

Record the answers after each meeting so staff and board members can compare them. Use this short list:

  • Relevant charity work and a live client reference
  • Scope exclusions and change costs
  • Accessibility testing and privacy responsibilities
  • Ownership, handover and support after launch

Read the details under those headings before discussing the proposal presentation.

What should I ask a charity website developer before hiring them?

Ask who the site must serve, how discovery works, what the quote excludes, how accessibility will be tested, where form data goes, who owns every account and what happens after launch. Request live examples and a client reference.

Does a developer need charity experience?

Relevant charity work helps, but the label alone tells you little. A developer should explain how a previous project handled different users and internal approvals, especially where enquiries contained sensitive information.

How do I compare quotes from charity website developers?

Create one list of required work and apply it to every quote. Note missing costs or vague wording before comparing the total.

Should a charity website meet WCAG 2.2 AA?

Ask the developer to recommend a target based on your users and obligations, then state it in the scope. Your organisation may choose WCAG 2.2 AA, but the contract should still explain how the website will be tested.

Who should own the website after launch?

The charity should control its domain, content, analytics and main service accounts. The contract should explain ownership of design and code, plus how files and access will be handed to another provider.

Can a developer improve our current site instead of rebuilding it?

Ask for an audit before accepting a rebuild. The audit should check whether the platform still receives security updates, whether the layout can be changed and whether forms can be repaired without replacing the whole site.

Before you sign the contract

Sign only when your team can understand and test what the proposal promises. The scope should say how each important visitor action will be built, who approves the work and how the website will be handed over.

KC Web Design's website design service includes copywriting and has no lock-in contract. If a quote leaves you unsure about the scope, book a short website project discussion and bring it with you.

  • Your current website address
  • The two visitor actions that matter most
  • Any quote items that remain unclear
  • A question about repair versus rebuilding

Resolve any open questions about scope or ownership before signing.