Where This Idea Came From

I co-lead The Ampersand Cohort a paid, application-based community for people with serious careers in both business and the arts. There are three of us on the leadership team, plus my EA, who helps out when she can. None of us does this full time.That means the community's institutional memory was everywhere and nowhere. It lived in:

• two years of email threads
• a dozen Google Docs and Sheets
• meeting notes, Fathom recaps and calendar invites
• the Circle community itself
• and, mostly, my head

When my co-leads needed something, they had to ask me. When I sat down with Claude to work on the community, I had to re-explain it every time. Some decisions were made in a meeting and never written down. Some to-dos lived in one inbox and nowhere else.So I asked Claude a simple question: can you create one Fulcra file with everything related to my work with the Cohort?

‍

Steps to Solve

• Gathered everything first. Had Claude search my Gmail, Google Drive and calendar for the Cohort under all three of its names. That came to 200+ email threads, the running Huddle notes doc, the membership CRM, event budgets, a NASA partnership proposal, newsletter drafts, and years of planning docs.
• Caught a false match right away. My email signature mentions the Cohort, so "Ampersand" matched almost every email I've sent. Claude switched to subject-line and sender searches to cut out the noise.
• Wrote a single master file in Fulcra (/The Cohort/the-cohort-master-file.md): what the community is, who's who, pricing, programming, past events and lessons, upcoming events, strategy, branding, partnerships, open to-dos, and links to every source file.
• Kept a password out. The Huddle notes doc had a login stored in plain text. Claude didn't copy it into the file and flagged it so I could delete it from the doc.
• Corrected context as we went. I told Claude:
  • that a contractor's invoice was already paid, and that payment details don't belong in shared community files
  • that Slack is only for my other job
  • who is actually on the leadership team, and what my EA's role is
• Each time, Claude updated the file, its own memory, and every downstream task.
• Stored the logo. Fulcra's file store takes text, not images, so Claude converted our current logo PNG into an SVG (vector) file. It rendered the SVG back to confirm it matched the original, then saved it in a brand/ folder marked "temporary" (we're mid-rebrand).
• Set up two scheduled tasks:
  • a Monday Circle snapshot that saves what changed in the community to Fulcra
  • a weekly "community growth advisor" that reads the snapshot, the master file, recent email and the latest Huddle notes, then writes a report with specific next moves, owners and ready-to-use copy
• Used the folder for a real decision. A launch coach was pitching a $3,747 pre-launch program. Claude weighed it against our budget and saw that one program would cost and instead, it built our January enrollment plan from what was already in the folder: application answers, event feedback and our own meeting notes.
• Shared it. Shared the folder read-only with my co-leads, using their Fulcra user ID. Fulcra shares are one-way, so for real collaboration she'll share a folder back and my agent will pick up her updates.

‍

Solution

• One folder is the source of truth. /The Cohort/ in Fulcra holds:
  • the master file
  • dated Circle snapshots
  • meeting recaps
  • the enrollment plan
  • a brand folder
  • the weekly growth advisor reports
• Links, not copies, for other tools. The master file points back to Google Drive, Circle and the podcast instead of duplicating them, so the originals stay where people already work.
• Agents do the upkeep. A snapshot runs every week and the master file updates itself when events or members change. Nobody has to remember to maintain it.
• Read-only sharing for collaborators. Co-leads get the full picture without being able to accidentally overwrite it. Their input comes back through their own shared folders.
• Agents read and draft; humans decide and send. The advisor never posts or emails anyone. It writes a report, and we pick what to act on.

‍

Result

My co-leads and I now have one place to look, and it stays current. When I open a new session with Claude, it already knows:

• who's on the team
• what we decided last week
• which ritual slipped
• which event still has the wrong location

When my co-lead has a question at 10pm, she doesn't have to wait for me to answer.What surprised me most wasn't the summary. It was how much the process uncovered. Pulling everything into one place exposed small inconsistencies that no single email or doc would have shown. Having an agent reread the community every week turned "we should check on that" into a list with owners.This setup would work for any small, volunteer-led group: a nonprofit board, a creative collective, an alumni network. The pattern is the same: gather everything once, keep one source of truth that agents maintain, share it read-only, and let the agents handle the reading so the humans can do the actual work.

‍