Answers to the board

Yes, absolutely. The pieces sync together well and the data underneath is solid. One expectation to set: "everything syncs" all at once isn't how this is scoped. We'll connect the ecosystem piece by piece, in the order set by the scope, so each part is stable before the next. The end state is a well-synced system; the path there is incremental by design. And against today's fragile, manual setup, each connection we make is a real upgrade.

Yes. If anything there are several viable options for each need. We only finished discovery. The ecosystem gets designed in Phase 2, then tools are tested against that design in Phase 3, which is where the final choices land. "TBD" reflects where we are in the sequence. Every open category already has real, proven candidates with known pricing.

Yes, comfortably. The hub foundation is built for far more than thousands of records, and the member-facing tools already run at that scale for other organizations. Thousands of members is well within range. If data volume grows further, we scale up a tier rather than rebuild.

Yes. A database-driven map that auto-syncs from the member database and embeds in the Squarespace site, so members appear on the website map without manual entry. It replaces today's manual store-locator approach. The map and directory improvements are built in Phase 5.

Leah and Chae have already met and walked through the exact process, which feeds the design in Phase 2 and the tool testing in Phase 3. There are several ways to do this, all big upgrades on the current manual process. They save real time and hold up reliably. Phase 3 confirms which tools fit best, weighing reliability and cost alongside what each tool can do.

In two stages. A simpler version is possible sooner, using Claude or similar AI tools to pull and summarize the data you already have. A fuller, automated impact-reporting layer is a later goal, once the hub and clean member data are in place. It's a time-allowing item in the plan, and it depends on capturing member and event data consistently, which ties directly to questions 8 and 9.

Education and the resource library are out of this scope. Both would be a separate effort. If they become a priority, we can scope them into a later phase or the next funding cycle, once we know what each should cover.

The AI chatbot item will utilize Claude connecting to the systems to query the data. The hub will be set up to support AI querying from the start, so the team can ask questions of the data directly rather than relying on a separate chatbot.

Yes, starting at intake. Members' stats and demographics are captured when they onboard and stored in the member database as structured fields, which is what makes the information searchable and filterable. Keeping it current afterward would be up to the Regarding Her team, and can be done with another Tally form that also feeds the data hub. We can explore other ways to gather updates over time, though how far we automate that depends on what fits the agreed scope.

This is a stretch for the current scope. Tracking event participation on member profiles and the impact dashboard are "time-allowing" items in the plan, not core commitments, so fully automating how members report event stats may or may not fall within scope. What we can do regardless: share clear ideas and best practices for collecting the data (a simple form that feeds the member and event records), so you're set up to use it either way. It connects directly to impact reporting in question 6.