Six decisions for Helen + Karina

"Of the five wedges, which is the right Day-1 3-week prototype with an hours-saved metric?"

The hypothesis is brand-deal triage because it has the densest workflow surface in the org — it touches every team member in sequence. But the Sessions cohort engine and the Skill foundation are both defensible Day-1 bets.

"Whose voice is the Skill anchored to, and how do we audit drift?"

Single voice across both businesses preserves your stated delegation philosophy and keeps governance simple. Splitting Sessions out as a sub-voice would honor the Lane / postpartum emotional anchor as a distinct register.

"Which surfaces does the team already run, and which need installation as a prerequisite?"

Multi-select. This is the desktop / CLI prerequisite gate from the corpus — we need this baseline before any prototype begins. Web Claude alone cannot install Skills or connect to Notion.

"How are Briana and Pia split today? We have been holding this as an open hypothesis since 5/11."

Whichever it is shapes how the brand-deal triage assigns briefs — and where the Sessions content engine routes drafts in Phase 2.

"Where does scheduled content actually post from today?"

We will keep this layer pluggable in any recommendation. The corpus has a founder-concentration finding on one scheduler (Blotato, three of six videos, recorded by the founder). We do not lead with it.

"What hours-saved or output-quality metric do we measure against?"

The recommended metric — hours per brand-deal pitch — directly aligns with your "wildly efficient" framing and is measurable in three weeks against a current baseline.