Launch is not the finish line
Many nonprofit sites look finished on day one and become fragile by week three. The usual failure mode is simple: the agency built pages, the client clapped, and nobody practiced the ordinary work of publishing, correcting copy, uploading files, or recovering from a broken plugin.
If your team cannot make a routine change without calling a developer, you did not buy a website. You rented temporary attention.
Start with ownership, not themes
Before choosing a CMS or design direction, answer three questions in writing:
- Who publishes weekly content? Name a person, not a committee.
- What changes must they make without help? Pages, posts, forms, events, donation blurbs.
- What is allowed to stay locked? Brand tokens, redirects, security settings, billing.
Those answers decide the CMS shape more than any feature matrix. A powerful stack that only your vendor understands is worse than a plain CMS your coordinator can use.
The handoff package that actually works
We treat handoff as a deliverable, not an email attachment. A useful package includes:
- Owner publishing guide — short, screenshot-backed steps for the weekly tasks
- Access inventory — who has what login, where MFA lives, and how to rotate access
- Content model map — what each content type is for, and what fields matter
- Recovery notes — backups, staging, and the first three things to check when something breaks
- Support boundary — what the client owns vs what still needs engineering help
If a document cannot help someone complete a task alone, rewrite it.
Practice one real update before you leave
Do not hand over a PDF and disappear. Sit with the owner and complete one real publish cycle: draft, review, schedule or publish, confirm on the live site, and undo/redo if needed.
That single rehearsal surfaces missing permissions, confusing labels, and documentation gaps faster than any checklist review.
What good looks like 90 days later
- Content updates happen without Slack panic
- Donation or contact paths still work after seasonal campaigns
- Someone on the client team can explain how backups and DNS are handled
- The next contractor can orient from the same handoff pack
That is the standard. Pretty pages are table stakes. Operable ownership is the product.