My growth-led founder stack: one operator, a run club, 40 agent skills

I run GRYT solo (a Pittsburgh run club turning into an event-production company) while advising a music-tech startup, so the stack has one job: let one person do the work of a small team without the output looking like it. Here is what actually carries weight, by layer.

Source of truth: Notion
Members, attendance, partner pipeline, content calendar. Every agent reads from here and writes back here. The change that mattered most was not a tool, it was counting confirmed check-ins instead of RSVPs. Honest numbers upstream, and everything downstream gets smarter.

Product: Lovable + Supabase
The Saturday Crew app (RSVP, waivers, confirmed check-ins, runner library, soundtrack, small shop) was built in Lovable on Supabase. It replaced a Google Form, a group chat and a spreadsheet. Lovable is great until you need a real data model, then Supabase and the repo matter more than the prompt box.

Playbooks as code: Claude Code + GitHub
Everything I learned running Saturdays became SKILL.md files: newcomer welcome, buddy system, drifter save, bring-a-friend, event run of show, creator partner programs. 40 skills across three public repos, installable as Claude Code plugins. 2,600 GitHub contributions in the last year, and a lot of them are Markdown, not code. Writing a playbook as a skill forced a level of specificity a Notion doc never did.

Agent layer: Perplexity Computer
Research, drafting, and the browser work I do not want to do by hand. It runs my skills, reads Notion and Slack, and ships drafts into an approval queue. It built most of my AI Lounge profile this morning while I read the feed. Approval stays with me. Nothing goes to a human without my click.

Distribution: Instagram, Beehiiv, Strava, GitHub
Instagram for the Saturday story, a Beehiiv newsletter (Doing Hard Things Together), a Strava club for the people who want the data, and GitHub as the surprise channel. The skill repos bring in organizers and builders I would never reach with a Reel.

Glue: Slack + n8n
Slack is the approval queue. n8n moves things between systems when a webhook is cheaper than a prompt.

What I would tell a founder starting this today: pick your source of truth first and be strict about what counts as a real number. Every tool above got more useful the day the data underneath it stopped lying.

What is in your stack that you would not give up?