KCAA · Volunteer Build Plan
A sequenced roadmap for the brand guide, volunteer program, website rebuild, financial system, social media agent, and inbox automation — ordered by dependency, leverage, and (for one phase) real-world timing.
At 2–3 hrs/week, running six projects in parallel means six projects that stall. Most of the plan below still runs one thing at a time, in the order that unlocks or de-risks the next: brand rules feed the website and social voice; the inbox is a fast, isolated win; the financial system starts as a spreadsheet before it becomes software; social publishing goes last because it's public and hardest to walk back.
The one exception is Volunteer Program (Phase 2), which jumps the queue and runs alongside the tail of the brand guide. It's time-sensitive — high school and university outreach has a real semester calendar — and it's low-hour relative to its payoff: a business student who joins to help with Phase 5's bookkeeping or a marketing student who takes over Phase 6's social posting doesn't just add hands, it gives some of this roadmap's hours back.
One-time scaffolding so every later phase has somewhere to live.
Lowest technical lift, highest leverage — everything visual downstream (site, social, forms, jerseys) inherits from this.
Runs in parallel with Phase 1 on purpose — outreach to high schools and universities is seasonal, and waiting for brand/website to finish first would miss the window.
Independent of brand/site, native to tools you already have, and removes a standing pain point fastest.
Current site (Squarespace) is already reasonably modern — this is a re-skin and mobile-first pass with the new brand, not a rebuild from zero.
Highest governance value but the biggest build — split into a spreadsheet stage you can start using in weeks, and a software stage once the categories are proven.
Last on purpose: it needs the brand voice from Phase 1 to sound right, and publishing mistakes are public and hard to undo — so it starts human-in-the-loop, not autonomous.
Gmail, Drive, Docs, Sheets, Calendar have a native Claude connector on claude.ai — Claude can read/draft email, search Drive, and edit Docs/Sheets directly in a chat. This covers Phase 2's outreach tracking, the Phase 5a spreadsheet work, and reviewing the Phase 3 inbox digest.
No official connector — Squarespace doesn't expose a content API for this. Work stays manual in the Squarespace editor; Claude's role is drafting copy, layout notes, and CSS snippets you paste in yourself.
No official connector either. Two paths: Meta's Graph API directly (requires app review to get publish permission), or a scheduler like Buffer/Later with a documented API — much less setup, and it already includes an approval queue.
Not a connector at all — this is custom software built with Claude Code directly, not something you "connect" to. Hosting choice below.
| Layer | Recommendation | Why |
|---|---|---|
| App + API | Vercel (free tier) | Zero ops, deploys straight from a git push — matches a 2–3 hr/week cadence |
| Database | Supabase (free tier, Postgres) | Built-in Google OAuth so login can be restricted to board member accounts, no separate auth system to build |
| Cost at this scale | $0–$25/month | Nonprofit transaction volume stays well inside free-tier limits for years |
| Hub & document set | Stays the top-level portal; the finance app mounts under it (e.g. a /finance route) | The Hub hosts everything, not the other way around — one address for members and board |