The Google stack covers a lot. Until the chore rota is in three different sheets.
Most intentional communities already run on a Google account. Calendar for gatherings, Docs for minutes, Sheets for the chore rota, Groups for the listserv. For a while, that works.
What we've heard from communities past the fifteen-person mark: the Docs sprawl, the listserv goes quiet, the chore rota lives in three sheets two people maintain by hand, and nobody can find that one proposal anymore. That's the moment ARA usually starts paying off, not as a replacement for Google Workspace, but as a layer for the things Google was never built to hold.
What Google Workspace does well
Familiar, free, almost everyone already has an account.
Docs, Sheets, Calendar, Drive, and Gmail are deeply learned by most adults. New members don't need a tour to know what a shared folder is.
Pricing is forgiving. Personal Gmail is free. Workspace business plans are inexpensive per seat. For most small communities the cost is whatever the steward's Google One subscription happens to be.
Google Groups plus Gmail makes a working community listserv, the format intentional communities have actually been using for thirty years. There's no need to fight that habit.
Where it falls short
No native shape for the things a community actually does.
Chore rotation is a sheet someone maintains by hand. New members get added to the bottom and the formula breaks. The rota that should rotate doesn't.
Consent voting on a Doc is reactions and signatures. Six months later, nobody can find which version of the proposal was the one that passed.
The truck, the canning kit, the projector. Each one needs its own sheet or its own habit of texting in the group chat. There's no log of who had it last.
Activity scatters. The Doc lives in Drive, the gathering on Calendar, the discussion in the Group, the chore in Sheets. There's no single place that holds the community's life.
What ARA does instead
Built-in shapes for the work a community already does.
One Rhythm replaces the chore rota sheet. It rotates on its own, notifies the person whose turn comes up, and lets people swap inside the app.
The Council does proposals with four vote options (Consent, Stand Aside, Abstain, Block) and an archive nobody has to maintain.
The Shed holds bookable resources with a damage note thread per item.
The Library holds ratified agreements as Scrolls. A version is either ratified or it isn't. No more "wait, which Doc was the final one?"
Side by side
Feature by feature
The honest take
Most communities don't have to choose. Keep Google Workspace for long-form documents, personal email, and shared drive storage. Bring ARA in for the things Google was never designed to hold: the chore rota that resets itself, the proposal with a paper trail, the shed booking with damage notes, the digest that lands in members' inboxes without anyone writing it.
A natural starting point: import your member list, set up one Rhythm, log a few past decisions as Scrolls, and run your next proposal through the Council. Keep the Google Doc for the meeting minutes. See how Riverbend layered ARA on top of their Google stack.
See ARA without committing.
Walk through Riverbend, a fictional ecovillage running on ARA. No signup, read-only.
Seedling is free forever for up to five members. No card.
Other comparisons
See all "ARA vs..." pages