Regarding Her · The Seven Phases

The plan, phase by phase

The full engagement runs in seven phases over about ten months, from the signed scope of work. Here's each one, what happens in it, and its sign-off milestone.

Where we are: Phase 1 (Milestone 1) is complete and the scope was signed off on the Sep 14 call. We're now in Phase 2, designing the future-state ecosystem.

Done complete Now in progress Ahead upcoming Aug 2026 → May 31, 2027 · $120,000

The seven phases

Foundation + Visioning

through ~Sep 4, 2026Done

Document the current state and get clear on where RH wants to go. Firefly builds the current-state map while the team joins focused visioning sessions.

M1Current-state map confirmed + Wants & Needs list approved.

New Functional Ecosystem Design

Sep 4 → Oct 2, 2026Now

Design the future-state ecosystem: a functional blueprint covering data architecture, tool categories, integrations, and the site updates needed. No tool names yet, just what needs to exist and how it connects.

M2Future-state ecosystem map confirmed.

Solutions Testing + Data Prototype

Oct 2 → Nov 20, 2026Ahead

Test tools against the ecosystem map, starting with what RH already uses. The main goal is a working data prototype. Implementation sequencing is confirmed at the close of this phase.

M3Solutions testing complete + implementation scope confirmed.

Technical Specifications + Build Plan

Nov 23 → Dec 9, 2026Ahead

Finalize the full technical specifications and confirm the build plan. Scope is set based on available time and budget.

M4Technical specifications complete + build plan approved.

Build

Dec 10, 2026 → Mar 31, 2027Ahead

Build the system. The data solution goes first; the site lift and the map and directory improvements follow. RH team touchpoints are minimal during this phase, with internal QA before handoff.

M5Internal QA complete: system ready for RH team testing.

RH Team Testing + Launch

April 2027 · exact dates TBDAhead

The RH team takes over for end-to-end testing, with Firefly's testing materials prepared in advance. Revisions and training follow. The launch date is set by RH.

M6System live (exact date set by RH).

Post-Launch Support

April → May 2027 · exact dates TBDAhead

Firefly monitors and supports the live system, resolves issues, finishes training and documentation, sets the post-launch roadmap for the next funding cycle, and closes the scope of work.

M7Project sign-off + SOW close.

What we build first

Inside the Build phase, these are the smallest, highest-leverage pieces, sequenced so value shows up early.

Central data hub / CRM Members, donors + board contacts, one source of truth
Join form + Circle onboarding Tally form auto-routes tiers; Circle members created on join
Member map & directory Syncs from the member data, no double upload
Donor & partner CRM Follow-up triggers, dedupe, a board-facing view
Comms + SMS broadcast Targeted sends from the hub
Ticketing + online giving One integrated events + donations flow
Claude quick wins + training Calendar/Drive fixes; team enablement

The full detail sits in the current-state map, the future-state map, the Wants & Needs ranking, and the grant alignment. See also the board Q&A.