When a foundation needs SitecoreAI for its website, and when it does not

23 October 2026
Arcsen

A foundation’s website carries more than its size suggests. It tells the stories that move donors, starts every online donation, signs up volunteers, and publishes reports for funders and the public, in Arabic and English and often in the languages of programmes abroad. When the work spans several programmes and countries, enterprise platforms start to appear in proposals.

Some foundations need one. Many do not, and an enterprise platform without the team to run it serves a nonprofit worse than a simple site run well. This guide sets out what SitecoreAI (formerly XM Cloud) adds, when a simpler CMS is the better choice, and a decision table you can take to your board.

What an enterprise platform adds

SitecoreAI is a SaaS, hybrid headless platform: Sitecore hosts, maintains and updates it, editors build pages in Page builder, and content is delivered through Experience Edge, a GraphQL service on a CDN. For a large nonprofit, five things matter.

Many sites on one platform. Programme, country and campaign sites can share one environment, one set of components and one set of brand rules. Experience Edge allows up to 1,000 sites per environment.
Languages with review. A site can have as many languages as you want, and AI translation creates language versions of a page and its data sources, guided by a brand kit. With Keep workflow state cleared, each translation starts in the initial state and waits for review.
Governance. Workflows and access rights decide who may edit and approve what. Language Write controls whether a user can edit a given language version, so each country team edits its own language.
Data and AI. Sitecore says SitecoreAI customers receive baseline entitlements for CDP, Personalize, Search and DAM, with features rolling out in phases. Our guide to Agentic Studio explains the AI side.
Fewer upgrade projects. Sitecore updates the platform itself, so a small IT team does not plan platform upgrades, although the front-end application still has its own.

When a simpler website is the better choice

The front end of a SitecoreAI site is an application you build and run. Sitecore’s Content SDK provides a starter Next.js application, and the site is hosted on Vercel, Netlify or another provider. That means developers, a release process and a hosting bill every year, on top of the licence. A simpler hosted CMS is usually the better choice when:

you run a single site in Arabic and English, with a few editors;
your hand-offs are a donate button and a volunteer form;
nobody on staff or at a retained partner can maintain a headless front end;
the budget covers the build and little after it.

Choosing simple is a sound decision for a small team. Put the savings into content and fundraising, keep the content model tidy, and revisit the platform when the number of sites, languages or hand-offs grows.

Donation and volunteer hand-offs

The website starts a donation, a payment provider takes it, and the CRM records it. SitecoreAI Forms sends data to third-party applications through webhooks without capturing user data, so a form is a hand-off by design. The receiving endpoint must be public HTTPS on port 443 or 8443, with TLS 1.2 or 1.3, and test submissions arrive flagged as tests. Sitecore’s page does not describe retries, so the receiving service should store each payload before it calls the CRM.

Send codes. Pass the campaign, fund, programme and language with every hand-off, so a gift from the Arabic Ramadan appeal reaches the right fund and the right thank-you.
Keep card details off the website. Link to or embed the payment provider’s page, and carry the codes across.
Route volunteers. Send sign-ups to the CRM with programme, location and language, so the volunteer team works from one list.
Keep portals in the CRM. Signed-in areas for volunteers, grantees or donors usually belong on a CRM portal such as Experience Cloud, with the website linking to them.

Stories, consent and accessibility

Stories carry people’s faces and words, often those of beneficiaries and children. Treat consent as a rights record on every photo and video. In Sitecore Content Hub, digital rights management restricts an asset once a rights profile is linked to it, with conditions for territory, media and period, and a public link to a restricted asset returns a 404 error. When consent ends, replace the asset on live pages, then restrict it.

Video belongs on a video platform, with captions in each language. In SitecoreAI’s modern Media Library, images get metadata and alt text on upload for editors to check, in a phased rollout, while video, audio and PDFs are skipped. AI translation includes image alt text, so every language gets alt text to review. Sitecore also notes that, depending on your contract, bandwidth and storage limits can apply, so check them before a media-heavy campaign.

Accessibility is decided in the front-end code and the content. Test against the Web Content Accessibility Guidelines in each language, with screen readers in Arabic as well as English, and build right to left properly, as our guide to Arabic-first Sitecore explains.

A fair decision table

Score your organization row by row. The right-hand column describes the work an enterprise platform is built for.

Factor	A simpler CMS is usually enough	SitecoreAI earns its place
Sites	A single site, perhaps with campaign pages	Several programme, country or event sites sharing components and brand rules
Languages	Arabic and English, written by one team	Several languages, local editors, and AI translation under review
Editors and approval	A few editors and one approver	Many editors in several countries, with approval by role and language
Hand-offs	A donate button and a volunteer form	Donations, volunteers, newsletters and grant applications flowing to a CRM with codes
Personalization	The same page for everyone	Content by country, campaign or returning visitor, with tests
Media	Photos and embedded video	A managed library with consent and rights records
Team	No developers once the site is built	A product owner and a development team or partner for the front end
Budget	The build is the main cost	Licence, hosting and front-end support funded for several years

If most of your answers sit in the middle column, put the money into content and fundraising. If most sit on the right, an enterprise platform earns its cost in governance and reuse, provided the team is funded too.

Ask for the whole bill. Licence, hosting, front-end development, support and content work over several years belong in the same comparison, for SitecoreAI and for the simpler option. Compare like with like before you compare platforms.

Where to start

Count your sites, languages, editors and approvers, and the systems the website must hand off to.
Map each hand-off, from donation and volunteer sign-up to newsletter and grant application, with the codes each one carries.
Audit your current site for accessibility and consent records, in every language.
Price each option over several years, including the team that runs it.
Already on Sitecore? Read our Middle East guide to XM Cloud and SitecoreAI, and use our Sitecore RFP checklist when you go to market.

Weighing a new website? See our nonprofit work, start with the free Sitecore Health Check if you run Sitecore today, and talk to our nonprofit team or send us your RFP. Our Sitecore practice works in Arabic and English.

Frequently asked questions

Does a nonprofit need an enterprise CMS like SitecoreAI?

Only when the website’s job is large: several sites or countries, several languages, many editors with approvals, and hand-offs to donation, volunteer and CRM systems. A single site in Arabic and English, run by a small team, is usually better served by a simpler CMS.

Can SitecoreAI take donations?

It hands them off. SitecoreAI Forms sends data to third-party applications through webhooks without capturing user data, so the payment runs on your payment provider’s page and the record lands in your CRM.

Can one SitecoreAI environment run several country sites?

Yes. Experience Edge allows up to 1,000 sites per environment, so programme and country sites can share one environment, one set of components and one set of brand rules.

Who maintains a SitecoreAI website?

Sitecore hosts, maintains and updates the platform. You or a partner build and maintain the front-end application and its hosting, which is why a nonprofit without developers should think twice.

Does SitecoreAI help with accessibility?

It helps with alt text: the modern Media Library suggests alt text on upload, in a phased rollout, and AI translation includes alt text fields. Accessibility itself comes from the front-end code and the content, so test against the Web Content Accessibility Guidelines in every language.