Chatter Snow

Chatter Snow was growing rapidly (more donations, more gear, more community interest) but had no system to track inventory of donated gear, share what equipment was available to community members, coordinate volunteers, manage events, handle finances, or organize donations. Everything was scattered across spreadsheets and email threads, with no visibility for community members, and it didn't scale. Core issue: as an organization trying to serve the community, Chatter couldn't easily tell people "here's what we have available" or manage operations efficiently.

A nonprofit with a limited budget and a volunteer team, a growing inventory of donated ski and snowboard gear, and an active community of members who wanted to know what was available. Existing infrastructure included Zoho for some communications. Being both a board member and technical lead meant seeing the operational need and the technical constraints firsthand.

• Create a centralized inventory system
• Enable the community to see available gear without email or phone calls
• Reduce manual admin work
• Build a foundation for future growth (volunteers, events, giving, etc.)
• Keep it maintainable by volunteers — not over-engineered

• Nonprofit budget (minimal)
• Volunteer-driven — the system couldn't be complex
• Needed to launch quickly; the community was waiting
• No dedicated devops/infrastructure team
• Growing organization that needed the system to scale

As board member and director, the operational workflows, community expectations, staff pain points, budget reality, and volunteer capabilities were already well understood. Key insight: don't rebuild everything — integrate with what Chatter already uses (Zoho). Start narrow (inventory) but design for expansion.

Core philosophy: minimal, maintainable, integrated. Next.js + TypeScript power both the admin UI and the community-facing view, talking to Vercel Edge Functions that handle mutations, auth, and logic, backed by Supabase/PostgreSQL for inventory, events, volunteers, and financials — integrated with Zoho for communications and Cloudflare for CDN/DNS. Next.js + TypeScript enabled fast iteration and full-stack capability with familiar tools; Supabase + PostgreSQL suited simple relational data at low cost; the Zoho integration avoided replacing a tool Chatter already used; Vercel kept deployment and scaling simple; Cloudflare provided CDN, DNS, and DDoS protection. Deliberately not built: a custom CMS (Supabase's admin interface was good enough), extensive reporting (kept focus on core operations), a mobile app (responsive web was sufficient), and complex authentication (simple role-based access was enough).

Functional and clear, focused on usability over visual polish — volunteers needed to understand the system quickly. Key interfaces: an admin dashboard for inventory management, volunteer coordination, and event creation; a community-facing gear view showing what's available to rent or borrow; volunteer coordination for shift signup and event management; and financial tracking for donations and expenses.

The initial phase covered inventory management (the core problem), the community-facing gear view, and basic volunteer coordination. The platform then evolved to include event management, donation/financial tracking, and member communication. Rough timeline: about two weeks of discovery and planning, three to four weeks for the MVP build, two weeks of testing and iteration, and one week to launch — built with volunteer time alongside the technical lead role.

• Requirement creep — once people saw the system working, everyone wanted new features
• Designing for volunteers — complex features had to stay simple to use
• Data accuracy — getting historical inventory data into the system
• Scaling — Vercel serverless can handle growth, but database optimization matters as data grows
• Feature priority — deciding what's MVP versus what can wait

Chatter now has a centralized inventory system, and the community can see available gear without email or phone calls. Admin overhead has been reduced (specific figures TBD — pending more usage data). The platform now also handles events, volunteers, financials, and donations, and has built a foundation for future growth.

• Start narrow, design wide — focusing on inventory first made launch possible, but the architecture allowed for expansion
• Integrate, don't replace — Chatter was already using Zoho, and building on top of existing tools was faster than rebuilding everything
• Design for your actual users — volunteers have limited patience for complexity, so every feature needs to be justified
• Get hands dirty — being on the board meant understanding real problems firsthand, an edge an outside consultant wouldn't have
• (Additional lesson TBD — to be added as the project matures)