A site that explains the mission fast
Who you serve, what you do about it, and proof it works, stated plainly enough that a first-time visitor understands you in one screen. Clarity is a fundraising strategy.
For nonprofits
Every dollar on the website is a dollar off the mission
Nonprofit websites are built by whoever volunteered, then frozen when they move on. Describe your organization in plain English and get a site anyone on the team can update: programs, events, volunteer signups, and a story donors can actually find.
Free with a Puter account. No code, nothing to install, works on your phone.
What organizations build here
The public face of a nonprofit runs on the same few pages everywhere. The difference is whether your team can change them without filing a ticket.
Volunteer signups that fill shifts
Real shifts with dates, slots, and a signup form, not an email address and hope. You see who is coming; volunteers see where they are needed most.
Event pages with RSVPs
Each fundraiser, drive, or open day gets its own page with the details and an RSVP count you can plan catering around. Publish it when tickets open, retire it after.
Program pages that stay current
One page per program, updated by the person who runs it, in a sentence: "move the pantry hours to Tuesday evenings". No webmaster in the loop.
Donation pages, honestly wired
The story, the impact numbers, and a clear button that links to the payment processor you already use. The builder does not touch the money; it makes the case for giving it.
Impact reports people read
The annual report as a living web page: the numbers, the stories, the photos, readable on a phone. Costs nothing to print and reaches donors who never open PDFs.
A website the whole team can hold
Describe the organization, not the layout
"We are a food bank serving two counties. We need our programs, volunteer shifts, an events page, and a donate button that goes to our existing giving page." That paragraph is the whole project scope.
The site builds itself in a live preview, and anyone on staff can review it before it goes anywhere.
Signups and RSVPs, stored without an IT person
Volunteer signups and event RSVPs save to storage under your organization's account. There is no plugin to update, no database the board treasurer worries about, and no monthly form-tool fee.
Export the lists whenever you need them for the spreadsheet the rest of the workflow lives in.
It survives the person who built it
Every nonprofit has the story: the volunteer who built the site left, and now nobody has the password. Here the site is plain files owned by the organization's account, editable by describing changes, and downloadable as a zip at any time.
Institutional memory should not live in one browser's saved logins.
Prompts for the next board meeting
Each of these opens the builder with the prompt already in the box. Swap in your own services, names, and prices before you send it.
Organization site
Mission, programs, events, and ways to help.
Show the prompt
Build a website for our food bank, Harvest Hope. Sections: a clear mission statement with one strong photo area, what we do in three programs (pantry, meal delivery, community fridge), upcoming events, how to volunteer with a signup form that saves names and emails, a donate section that links to our existing giving page, and contact details with our hours. Warm, hopeful design that is easy to read for all ages.
Volunteer shift board
Shifts with slots, signups, and a coordinator view.
Show the prompt
Build a volunteer shift signup tool for our nonprofit. As the coordinator I sign in and create shifts with a date, time, role, location, and number of slots. The public page lists upcoming shifts with open slots, and volunteers sign up with a name, email, and phone. Full shifts close automatically. I see a roster per shift, can remove a signup, and export the week as CSV. Store everything in our Puter account.
Fundraiser event page
One event, its story, and an RSVP count you can plan on.
Show the prompt
Build an event page for our annual harvest dinner fundraiser on October 3. Sections: the story of what the dinner supports, date, time, and venue with a map section, the evening's schedule, a suggested donation note linking to our existing giving page, and an RSVP form (name, email, number of guests, dietary notes) that saves responses and shows me a private total headcount. Elegant, festive design.
Impact report page
The annual report as a page donors actually read.
Show the prompt
Build an annual impact report page for our nonprofit. Sections: a headline with the year's single most important number, our mission in one line, four key statistics with short explanations, two program highlights told as brief stories with photo areas, a financial transparency section with a simple expenses breakdown I can edit, thank-yous to partners, and a closing call to volunteer or give. Clean, credible design that prints decently too.
What boards and coordinators ask
Can it take donations directly?
No, and treat that as a feature: the builder never handles your donors' payment details. Your donate button links to the processor you already trust, and the site's job is the part that actually raises the money: the story, the numbers, and the ask.
We have no technical staff, and our volunteers rotate. Who maintains this?
Whoever can write a sentence. Updates are requests in plain English ("add the winter coat drive to events"), every change is verified before it lands, and every version is kept, so an enthusiastic volunteer cannot permanently break anything.
Is free really free, or is there a catch a treasurer should know about?
Building, publishing, and hosting on a puter.site address cost nothing, with no card on file. Very heavy storage use can hit the free account's limits, which matters to almost no nonprofit website. The honest catch is only that your address ends in puter.site unless you download the files and host them on your own domain.
Where does volunteer and RSVP information live?
In storage under your organization's own Puter account, not on a public page and not in a third-party form tool's database. Publishing the site does not publish the signups. Treat contact lists with the same care you already do, and export them only to places your organization controls.
Describe your organization and what it needs
The mission statement you already have is most of the prompt.
Open the builder