/ Working Plan ⋮ Capetivate × Women's Money Matters ⋮ 2026

The Hub
plan & timeline

IgorUpdated 2026-05-04 · Version 1.0

A working plan for the WMM Hub. The urgent 3‑week budgeting MVP framed inside the broader 60‑to‑90 day rebuild, with the owners, dates, and asks we need to hold.

Sam Ingrassia (Budgetsimple / BudgetKit CEO) issued a 30-day termination notice on May 1, 2026. Signups on the existing platform are already disabled. The agreement ends ~June 1. WMM has committed publicly to platform ownership; Capetivate has been WMM's technology partner since 2021 (IT, Salesforce NPSP, the marketing site, and the in-production volunteer portal at volunteer.womensmoneymatters.org), which makes a Capetivate-owned Hub a continuation of work already proven, not a new bet.

Admin-console reconnaissance on May 1 confirmed Sam's stack in full (Plaid, Array, Stripe, OpenAI / Gemini / Anthropic, Wealthbox, Slack, Filestack, TinyMCE) and resolved his "credit secret sauce" claim. He resells Array. Every integration is replaceable, and WMM owns the direct vendor relationships from here.

On May 1, with admin access still live, we walked the entire Budgetsimple admin console at dashboard.budgetsimple.com. The goal: enumerate every system, integration, and tenant artifact before access drops. The picture below is what every Hub design decision has to be calibrated against.

WMM tenant at scale

The platform underneath

"Budgetsimple" is the consumer brand. BudgetKit is the developer/API brand at api.budgetkit.com/rest. The frontend is a Vite-built React SPA on Cloudflare CDN. The backend is multi-tenant. Each partner gets its own portal builder with full content, coach roster, courses, tools, financial taxonomies, calendar, plans, reporting, and navigation scoped to that portal.

Admin endpoint surface we mapped

• manage/users
• manage/coaches
• manage/portals
• manage/courses
• manage/assessments
• manage/tools
• manage/topics
• manage/files
• manage/leases
• manage/leases/jobs
• manage/array-integrations
• manage/array-integrations-products
• manage/plaid-integrations
• manage/wealthbox
• manage/stripe
• manage/ecrypt
• manage/webhooks
• administration/integrations
• administration/ai-providers
• administration/reporting
• partners/sign-up

Confirmed integrations and what replaces each

Auth and account model

Standard SaaS lifecycle confirmed: sign-up, magic-login link, stay-signed-in, forgot-password, confirm-email, change-email, continue-onboarding, demo-link. Two registration modes ("Enable For All" vs. restricted). Privacy / ToS gating is configurable. Partner-level signup at /partners/sign-up. None of this is exotic. Neon Auth (Stack Auth: email/password, OAuth, magic links, MFA) covers all of it as part of the same Postgres provisioning step.

Open recon questions to close before access drops

1. Q1What are the 6 WMM portals and what populates each (programs, cohorts, sponsors, regions)? This dictates how we structure the multi-tenant role model.
2. Q2Which AI provider is set as Default in administration/integrations, and what AI features does WMM actually use in production (chat? content gen? assessment scoring? coaching summaries?).
3. Q3What's enabled inside /integrations/array, i.e. which Array products are turned on for WMM specifically?
4. Q4Does the leases / jobs subsystem have any active records, and if so, what does the workflow look like end-to-end?
5. Q5How many of the 50 files and 62 courses are WMM-authored vs. Budgetsimple library content? This is the dividing line for what migrates vs. what gets rebuilt vs. what gets dropped.
6. Q6What's in the Reporting and Engagement Reporting screens, i.e. which metrics does WMM actually track for funder reporting?

Pablo and Meredith retain access; Igor's access has partly dropped. The recon channel runs through them for any remaining unknowns during the handoff window.

Three milestones to hold: May 31 emergency MVP live · June 15 grant deliverable · July 20–31 Hub soft launch with first cohort.

If only four things move this week, these are the four. Everything else is either Igor's build queue or downstream of these.

Array is the longest pole on the project. Two insights about how Array actually works change the timeline math, and they let WMM start the work this week instead of waiting on a signed contract.

Phased product rollout

WMM doesn't need every Array product on day one. Commit to Phase 1 now, design the rest later. Phase order can swap based on what coaches and clients ask for first.

What WMM produces this week (in parallel with sales call)

Eight documentation items WMM owns and Array doesn't provide. Most can move through the same fintech-lawyer review pass already running for the AI privacy work.

1. D1Use-case statement. One paragraph framing the FCRA permissible-purpose argument under section 604(a)(2): coach-supported credit education for low-income women, with consent-based credit pulls used to inform coaching plans and track progress. Owner: Pat Barry with fintech lawyer.
2. D2Information security policy update. Strengthen the existing policy for FCRA-relevant items: access controls, encryption at rest and in transit, audit logging, role-based permissions. Owner: Pat Barry with Igor on technical specifics.
3. D3Data retention and destruction policy for credit data. How long is it kept, when is it deleted, who has access. Bureaus require this in writing. Owner: Pat Barry.
4. D4Employee training plan. Any coach or staff member with access to consumer credit data needs FCRA training. Document the training, who took it, when, and how often it refreshes. Owner: Bernadette.
5. D5Breach notification process. Calling out credit-data exposure scenarios specifically. Owner: Pat Barry.
6. D6Privacy policy and ToS updates. Disclose Array as the credit-data provider, end-user consent, dispute rights, opt-out path. Same pass as the Plaid privacy policy update. Owner: Pat Barry with fintech lawyer.
7. D7FCRA compliance owner designation. Doesn't have to be a full-time role. Could be Bernadette or Pat Barry. Just needs to be one named person with documented responsibility. Owner: Danielle.
8. D8Background-check policy for coaches. Some bureaus require this for anyone with credit-data access. Establish the policy before Array asks. Owner: Bernadette.

What Array provides vs. what waits for the contract

Each portal is a fully scoped sub-experience inside the WMM tenant, with its own content, navigation, and reporting. Tabs surface based on role flags; a single user can hold multiple roles.

The AI Companion sits across portals 01 and 02 as the acquisition catalyst. Free coaching pulls credit-invisible users into WMM, EPATH, ABCD, and Union Capital programs, where human-plus-AI coaching unlocks.

WMM Connect (BuddyBoss + plugin sprawl) underdelivered on adoption, performance, and operations. Pat Barry's skepticism is grounded. The Hub will not repeat those failures, but the difference must be visible in writing. These items are line-items in the new retainer scope, not assumptions.

• R1Sam delivers no usable data export.Mitigation: scenario B is fully planned. Recapture-campaign messaging ready. Both scenarios route to the same platform; only the data path differs.
• R2Plaid production access delayed beyond 2 weeks.Mitigation: soft-launch in Plaid sandbox for the first cohort with manual seed data if needed. Production goes live within 4 weeks regardless.
• R3June 15 grant deliverable missed (active-user count below 360).Mitigation: document the full effort, the platform pivot, and the recapture campaign. Funders fund effort and adaptation, not just metrics.
• R4Array accreditation runs the full 8 weeks (or longer).Mitigation: start outreach this week and run the compression play described in Section [06]. Pat Barry begins the 8 documentation items in parallel with Bernadette's sales call, so submission to bureaus happens immediately on MSA signing rather than weeks after. Build sandbox integration in parallel. Soft-launch credit features in Cohort 2 if Cohort 1 ships before accreditation completes.
• R5Igor's admin access to Sam's platform is fully revoked.Mitigation: Pablo and Meredith retain access and are the recon channel if anything else is needed during the handoff window. Capture screenshots and exports while access lasts.