What drives the cost of a veteran nonprofit website redesign

When your officers ask what a website redesign will cost, they need more than a starting price. They need to know what is included, what the organization must supply, and what it will cost to keep the site running.

The short answer: a veteran nonprofit website redesign budget depends on the public website, existing content, member or officer tools, integrations, accessibility work, training, and ongoing care. Compare proposals using the same scope and budgeting period. Separate one-time project costs from recurring charges and optional work.

This guide does not offer an invented industry price range. Instead, use the blank worksheet below to build an estimate your treasurer, Paymaster, or project sponsor can explain to leadership.

Define what you are buying before asking for a number

Describe the outcome in a few practical sentences. For example: people can find meetings and programs; an approved volunteer can update events; and the next officer team can take over without searching for accounts.

Then separate three possible parts of the project:

• Public website: mission, programs, membership information, events, contact routes, and any approved giving or registration links.
• Member resources: information or documents restricted to the appropriate members.
• Officer workspace: agreed internal tasks, reporting, records, and access rules.

You may need only the first part now. A member portal or Digital HQ should have its own requirements and costs, rather than arriving as an undefined bundle. Review the Geek Heros Digital HQ overview if your team is deciding which work belongs behind a login.

Keep existing useful tools in the discussion. Linking to a payment page, embedding an outside tool, and building an authorized data connection require different amounts of work. Ask the provider to name the approach instead of simply pricing "integration."

Six cost drivers to make visible

1. Content preparation and migration

Count more than pages. List newsletters, photos, downloadable forms, event records, and content stored outside the current website. Identify what is ready to move, what needs rewriting, and what your organization no longer wants to publish.

A proposal should say who performs the inventory, editing, data entry, image preparation, and final review. If volunteers supply approved content, specify the format and due dates. Volunteer work still requires time and a named owner even when no outside invoice is involved.

If URLs change, include mapping, redirect implementation, and link testing in the scope. Google recommends planning and monitoring site moves, and warns of possible ranking fluctuations. These tasks support a managed transition; they are not a guarantee that search performance will stay unchanged. Google's site-move guidance

2. Templates, features, and editing workflows

A site with a few reusable page layouts differs from one with custom directories, searchable records, multiple approval steps, and special forms. Ask which features are standard, configured, custom-built, or provided by another service.

Describe the editing jobs, not just the desired screens. If two officers must review a notice before publication, include that workflow. If a volunteer only needs to change meeting details, avoid paying for a complicated system they will not maintain.

3. Private access and data handling

Restricted resources add decisions about accounts, permissions, invitations, recovery, and removal of access. Existing records may need cleaning and review before import.

List the information needed for each task and who may see it. Avoid collecting sensitive material simply because a form can accept uploads. Your team should approve the data-handling requirements and decide what should remain in an existing authorized system.

Ask the provider to price the agreed workflows and tests. Do not assume that a public website quote includes a complete membership database or a connection to a national system.

4. Accessibility evaluation and remediation

Ask what the project includes for accessible templates, content preparation, forms, documents, evaluation, and corrections. If you have a large document library, identify whether the proposal covers all files, selected files, or only new content.

W3C recommends evaluating accessibility during development and explains that tools alone cannot determine whether a site meets accessibility standards. Budget for the appropriate human evaluation and follow-up work, not just a scan. W3C accessibility evaluation overview

Agree on the target and review responsibilities with qualified help where needed. A line item or a passing automated score is not a legal compliance guarantee.

5. Training and the officer handoff

Specify who receives training, what tasks it covers, whether instructions are included, and how future volunteers get help. Ask whether a recorded demonstration, written guide, follow-up session, or later refresher is included or separately charged.

Plan for organization-controlled accounts, approved role changes, and a documented recovery process. The officer who knows the history can help explain what matters while the next volunteer learns the actual workflow.

6. Hosting, software, and ongoing support

Recurring expenses may include domain registration, hosting, software subscriptions, maintenance, support, and connected services. Ask for billing frequency, renewal conditions, included usage, and any limits that trigger additional charges.

Clarify the difference between maintaining the system and creating new content. A care plan might cover updates and support but not writing a monthly newsletter or adding a new program. Your proposal should say which work belongs to whom.

Use this blank website budget worksheet

Request the same breakdown from every provider. Fill in only approved quotes or verified charges. Use not included, included in another line, or not yet priced where appropriate; an empty cell should not be read as zero.

For a first-year comparison, add the one-time project charges to all recurring charges payable during the same defined 12-month period, then add approved options and applicable fees. Do not count a recurring charge twice if it is already included in the project price.

Record the date range, currency, billing start dates, and any assumptions. If one proposal includes the first year of hosting and another does not, normalize that difference before comparing totals. Ask about later renewals separately so the lowest launch price does not hide a larger ongoing commitment.

Choose a reserve based on identified uncertainties and your approval process, rather than an unexplained percentage. If migration volume is unknown, the useful next step may be an inventory, not a guessed budget.

Reduce scope without creating a handoff problem

A phased plan can help when the full wish list exceeds the available budget. Consider launching clear public information and a manageable editing process first, then adding well-defined member or officer workflows later.

Potential tradeoffs include reusing an appropriate layout, supplying approved copy, reducing custom features, and retaining an existing service that works. Have the provider explain the consequence of each choice.

Do not quietly remove access controls, necessary testing, backups, or the agreed accessibility work to make the total look smaller. Discuss a smaller deliverable that can be operated responsibly. Also identify what future additions would require rework; a "phase two" label does not make later development free.

Ask these questions before the budget vote

1. What precisely is included in the fixed price or estimate?
2. Which content, approvals, and access must our organization provide?
3. What assumptions could change the price, and who approves changes?
4. Which charges recur, when do they start, and can they increase at renewal?
5. Which third-party fees are paid directly by us?
6. What tests and handoff items must be complete before acceptance?
7. What support and training are included after launch?
8. What can we export, and what would it cost to move to another provider?

Bring unanswered items to the provider before comparing totals. A clear exclusion is easier to plan around than a vague promise.

Frequently asked questions

Can you give us a standard price for a veteran nonprofit redesign?

A useful price needs a defined scope. Share your current site, content volume, required workflows, existing tools, and expected support. Ask for an itemized estimate with assumptions instead of treating an unrelated organization's project price as your budget.

Can volunteers lower the project cost?

They can take responsibility for agreed work such as collecting photos, preparing approved copy, or checking meeting information. Confirm whether that changes the quote and what support they need. Assign owners and deadlines so the project does not depend on unplanned volunteer hours.

Should a redesign and a member portal be quoted together?

Ask for a common plan with separate deliverables and prices. That makes it easier to see dependencies and decide whether both are needed at launch. A portal should be justified by specific users, permissions, and tasks.

Turn the worksheet into a scoped conversation

Bring your current site, completed worksheet entries, and a must-have/later list. Review Geek Heros websites for veteran organizations, then request a free Website & Digital HQ Assessment.

The assessment request starts an email follow-up to arrange a conversation. It is not an instant quote, booking, or purchase commitment. Your organization's actual scope and service agreement determine the project and ongoing costs.