Your donation page converts. The charity's website is where supporters give up.

By the We.Inc editorial team · Updated · Editorial policy

Fundraising platforms spend years tuning the giving form. Then a supporter arrives from a search, lands on a charity homepage that has not been touched since the last director left, and never finds the donate button. This page is for the platform deciding whether to offer its nonprofit customers a website too, under the platform's own name.

TL;DR

Where supporters are lost

Trace a typical small-charity donor journey and the losses are rarely on your form:

  1. A supporter hears about the charity and searches for it.
  2. The first result is the charity's own site, slow on a phone, with last year's event still on the homepage.
  3. The donate button is in the footer, or links to a dead campaign.
  4. The supporter leaves. Your platform never sees them.

Your product could not fix step 2 or 3, because the website belonged to someone else, usually a volunteer. A white-label site builder lets you fix it without becoming a web agency.

Who this is for, and who it is not

This page is for software companies: donation tools, peer-to-peer and event fundraising platforms, membership and donor-management systems with many small nonprofit customers. If you are a federation of charities giving sites to your own chapters, our nonprofit federations page is the better read.

What the nonprofit gets

Client dashboard on the brand host with a prompt box and the client's website

*The client home under a demo brand. A charity would see your name and its own site.*

Visual editor with a heading selected and controls for font, size and colour

*The visual editor. A volunteer can change a heading or a colour without touching code.*

Keep the money where it already works

Do not move giving into the website builder. Your platform already handles the parts a website builder should not: payment processing, recurring gifts, gift aid or tax receipts, and donor records. In the US, for example, the IRS requires a written acknowledgment for any single contribution of $250 or more, naming the organisation, the amount, and whether any goods or services were given in return. That belongs in a system built for receipts.

So the website's job is narrow and important: make the donate button impossible to miss and send supporters to your page in one click. In practice:

Site elementWhat it should doWhere the giving happens
Header donate buttonOn every page, one click to the current appealYour giving page
Campaign pageStory, photos, progress in words, a single call to giveYour giving page or embed
Event pageDate, place, what to bring, register linkYour event registration
"Ways to give" pageMonthly giving, in memory, workplace givingYour forms for each
Thank-you pageWhat the gift does nextShown after your form returns the supporter

If you want your giving widget inside the page rather than a link, every site is real code. Bring your widget to the demo and we will check how it fits before you promise it to customers.

Controls for volunteer editors

Charity websites are often edited by whoever has time. That is fine until a volunteer deletes the donate page the night before an appeal. Set your brand-wide defaults, then adjust per charity:

Brand-wide defaults for what clients can do, including publishing and Publishing needs my approval

*Brand-wide defaults. Each charity inherits these unless you change them for that one.*

Charities can also invite their own people. On your side, your staff get fixed roles (designer, support, billing) so your support team can look at a charity's site without touching billing.

Telling charities what their site did

Boards ask whether the website is worth the effort. We.Inc can send each charity a monthly email under your brand with visitors, top pages and the change on the previous month. Switch it on when you are ready; it is off by default.

Analytics screen with the monthly client report setting

*Analytics and the monthly report setting on the brand side.*

Commercial shapes that work

We are demo-only and do not publish our own pricing; your price to charities is yours. Common shapes:

Plans for your clients screen where the brand sets its own prices and connects Stripe

*Where you set your own plans for clients. Stripe is not connected in this demo.*

A 60-day rollout for your first cohort

Start small so you learn what charities actually do with a site before you promise it to every customer.

DaysStepWhat you learn
1-7Choose 20 customers: some with no site, some with a site nobody can editWhich group takes it up
1-7Pick four or five templates that suit charities: appeal-led, event-led, service-ledWhich starting points get used
8-21Run a one-hour onboarding call per charity; publish a first version on the callHow long a real launch takes
22-45Leave approval on; review each first publish, then switch approval offWhich mistakes volunteers make
46-60Compare visits to your giving pages from these sites against beforeWhether the site moved giving

Write down what your support team was asked. Those questions become your help pages, which appear under your brand on the client side.

Exit, because charities ask

Trustees increasingly ask "what if we leave?" The honest answer is short: with the code switch on, a charity can download its site or push it to GitHub and host it anywhere. Your giving pages stay where they are. See code export.

When to say no

If most of your customers are large nonprofits with digital teams and their own content system, they will not want a second site builder. If your customers mainly run one-off crowdfunding pages, the campaign page you already have is probably enough. The fit is many small and mid-sized organisations that need a real site and have nobody to run it.

Sources

Last checked 2026-10-25. Not legal or tax advice; rules differ by country.

Book a demo to walk a charity's journey from search to your giving page.

Book a demo. Pricing is tailored to your volume and setup, and you get your exact price on the call. 0% transaction fee.

Frequently asked questions

Does the website builder process donations?

We recommend keeping donations, receipts and donor records in your fundraising platform and sending supporters there from the site. The site is the front door.

Can a charity keep its existing web address?

Yes, if you allow it. The own-domain switch lets a charity connect a domain it already owns.

Can we stop a volunteer publishing a broken page?

Yes. Turn off publishing for that charity, or switch on "Publishing needs my approval" so changes wait for your single-step approval.

Can charities leave with their site?

With the code switch on, a charity can download its site code or push it to GitHub and host it elsewhere.

Keep reading

More in White Label

We.Inc is an AI-powered website builder you can resell under your own brand. Launch a branded client dashboard, bill on Stripe Connect, and deliver AI-generated websites in minutes. White-label pricing is tailored to your volume and setup: book a 30-minute demo for a quote.

Product

Who It's For

Features

Resources

Company

View Sitemap