An Excel spreadsheet that tracked assignments but drove nothing.

The Community Arts Foundation ran six volunteer administrators across eight platforms — TikTok, Instagram, Twitter, Blue Sky, Weibo, Red Book, YouTube, and WeChat. A spreadsheet tracked who owned which channel, but it didn't drive execution: content got created and posted reactively, and each continuous stream of events received a single post instead of a real campaign.

A software question masking a strategy problem

Philip assumed the fix was a scheduling tool, but the real constraint was coordinating six volunteers — software alone doesn't solve a communication and planning-visibility gap.

Analytics that contradicted intuition

Reels generated 26,000 reaches to non-followers while stories barely registered, and the audience engaged most heavily at 6-9am Pacific — data Philip had seen but couldn't yet translate into strategy.

An unresolved frequency question

Limited volunteer bandwidth meant "post more" wasn't a viable answer, but there was no framework connecting posting frequency to actual content quality and capacity.

Genuine eight-platform complexity

Each platform served a real, distinct audience — Chinese-language communities on Weibo and Red Book, younger viewers on TikTok — making the coordination challenge legitimate, not just poor planning.

Google Workspace over new software, and analytics over intuition.

Rather than prescribing a scheduling tool, I mapped the real ecosystem (Content Studio, Hootsuite, Buffer, Feedhype), diagnosed that CAF's actual constraint was volunteer coordination rather than scheduling, and redesigned the planning system around Google Calendar and Tasks — infrastructure the team already knew.

Google Workspace as the planning nucleus

Google Calendar became the hub for pre-event, day-of, and post-event content plans; Google Tasks auto-assigned work to the responsible volunteer — a zero-training-curve system using tools CAF already checked daily.

Reels-first analytics interpretation

Reels reached 26,000 people (mostly non-followers) while stories barely registered — because Instagram pushes reels to Explore pages to compete with TikTok. This directly reprioritized where volunteer effort should go.

Capacity-based posting frequency

Since platforms initially show content to only ~10% of followers before expanding based on engagement, the real question became "how often can we post good content" — not "how often can we post."

FAQ-based content framework

Turning real audience questions (How do I volunteer? What should I expect at my first event?) into content shifted social media from broadcast to service — a sustainable idea pipeline that doesn't depend on constant creative effort.

A plan Philip could implement immediately, with zero procurement cycle.

No new software required

Recognizing that existing Google Workspace tools could solve the coordination problem meant Philip could act immediately — no procurement, no training, no adoption friction.

Analytics literacy, not just answers

Philip left understanding why reels outperform stories and what his audience's engagement window means — able to keep interpreting new data independently.

A frequency framework replacing guilt with clarity

The shift from "we need to post more" to "we need to post better content as often as capacity allows" removed pressure to match unsustainable daily-posting norms.

A grateful, engaged client

"This has been really helpful looking at the analytics. You're a wealth of information," Philip said — with an open invitation to follow up as new questions arise.

Diagnose the Real Constraint Before Recommending a Tool

Philip arrived with what looked like a software question. Solving it required treating the six-person volunteer team as the actual system constraint, not an afterthought.

Optimize what you already use before adopting something new.

The strongest nonprofit systems are the ones a real, resource-constrained team can actually keep using — not the most sophisticated ones.

Tools and Platforms I Applied

Every recommendation matched CAF's real constraint: volunteer capacity, not a missing piece of software.

Google Calendar
Google Calendar & Tasks

Repurposed as the planning nucleus and volunteer assignment system — zero new tools, zero training curve for the existing team.

Instagram
Instagram Insights

Analyzed live to decode reels-vs-stories reach disparity and the 6-9am Pacific engagement window.

Notion
Notion (evaluated alternative)

Presented as a more sophisticated planning option with multi-view templating, for if Google Workspace ever became insufficient.

CS
Content Studio / Hootsuite / Buffer

Evaluated honestly against the real constraint — API-extension schedulers solve a different problem than volunteer coordination.

Certifications That Informed This Strategy

Six certifications, chosen for direct relevance to the analytics, platform-strategy, and content-framework work in this consultation.

HubSpot Social Media

Directly informed the reels-first content prioritization and the capacity-based posting frequency framework.

HubSpot Content Marketing

Shaped the FAQ-based content framework turning audience questions into a sustainable content pipeline.

HubSpot Inbound

Guided the "service, not broadcast" reframing — content answering real questions before they're even asked.

HubSpot Digital Marketing

Informed the cross-platform strategy documentation across eight distinct channels and audiences.

Meta Blueprint: Facebook and Instagram

Directly explained the reels-vs-stories reach mechanics and the algorithm's 10%-then-expand delivery model.

Canva Essentials

Supported practical, low-effort visual asset production the volunteer team could sustain independently.

Volunteer-led social media doesn't need more software — it needs a system.

If you run a nonprofit coordinating social media through volunteers, Philip's situation should feel familiar. You have passionate people willing to help, you're active across multiple platforms because different audiences live in different places, and you're not sure whether your real problem is tooling or planning.

The answer depends on your actual constraint: if volunteers can't post consistently, a scheduler helps. If nobody knows what to post or when, no scheduler fixes that — you need planning clarity first, built on infrastructure your team already trusts.

Coordinating social media across a volunteer team?

I can assess whether your real gap is tools or strategy, then build a planning system using infrastructure you already have.

Six volunteers, eight platforms, and a spreadsheet that tracked assignments but drove nothing.

Without Edd

  • A new scheduling tool gets bought to solve what's actually a volunteer-coordination problem
  • Reels data showing 26,000 non-follower reaches stays unread, with effort still going into Stories
  • "Post more" stays the default answer with no framework connecting frequency to real capacity
  • Continuous event streams keep getting a single reactive post instead of a real campaign

What Actually Happened

  • Google Calendar and Tasks — tools the team already used daily — became the real planning nucleus
  • Reels-first analytics interpretation redirected volunteer effort to what was actually reaching people
  • Posting frequency was reframed around "how much good content can we make," not an arbitrary target
  • An FAQ-based content framework turned social media into a sustainable service pipeline