Case study · Sage Collective

People do the caring. The system does the rest.

Business
Online peer support
Where
Live online
See it live
sagecollective.care
sagecollective.care
The Sage Collective home page, with an aspen forest and the headline “You don’t have to carry it alone”

The job

Sage Collective brings people together in Groves: live, facilitator-led peer support circles of up to eight people, 75 minutes at a time. Its members come for connection, and their community lives on Discord.

A Grove only works if everything around it works too. Someone has to take payment, hold the seat, remind people, open the room on time, and offer a cancelled spot to the next person waiting. None of that should land on the facilitator, and none of it should get in the way of someone who is having a hard week.

What we built

Four parts, one system.

The website

A calm, hand-built public site with membership, single-seat tokens, gifted seats, a FAQ, and a blog the team can publish to without a developer.

Sage Bot

A custom Discord bot with 28 commands for members, facilitators, and admins. Members can reserve a seat, check their tokens, set their time zone, or gift a seat from inside Discord.

Business automations

Connected workflows handle onboarding, token purchases, billing renewals, lapsed memberships, and reservation confirmations.

Tracking and reporting

Tracked links and a weekly report show which posts and channels bring people in. A daily audit checks the data and flags problems to an admin channel.

What happens around a Grove

  1. Someone joins on the website through Stripe, or receives a gifted seat by email.
  2. Their account links to Discord and their seat tokens show up in their wallet.
  3. They reserve a seat with a single command, and it shows in their own time zone.
  4. Reminders go out at seven, five, and three days, the day before, one hour, and seven minutes.
  5. The Grove room opens on schedule and locks when the session is underway.
  6. If a seat opens up, the next person on the waitlist gets a message with time to claim it.

What still needs a person

Facilitators hold every Grove, and Groves are never recorded. A person also approves every public post before it goes out.

We drew that line on purpose. The system handles the logistics so the care stays human.

Built with

  • Astro
  • Keystatic
  • Node.js
  • discord.js
  • Supabase
  • Stripe
  • Make
  • Railway
Next case study Mill Creek Snow Removal

The next hire might be a website

What’s eating up your week?

Tell us what your business spends too much time on. We’ll tell you what we’d build, and you’ll hear from a person.

jason@guerrillawarfare.agency