HIFP — Open Questions: Friday 2026-09-11 Check-in

Date. 2026-09-11 (Friday) Purpose. The list of things not yet resolved after the check-in — for trio deliberation before v4-kit propagation. Written to make the decisions legible, not to force answers. Companion. HIFP-session-notes-2026-09-11-checkin (narrative) · HIFP-decision-log-2026-09-11 (what's closed). Status. Draft for Sindhu + Fatima review.

Framing. These are joint-deliberation inputs. Where a working position exists, it's marked "directionally adopted" and can be vetoed. Where the answer is genuinely open, options are presented without a recommendation Brandon has already locked in.

§1 · SAFE sizing — $2.5M target / $2.0M floor / $15M cap post-money

Working position (directionally adopted, veto reserved through Monday 2026-09-14): Bump from prior $2.0M target / $1.5M floor / $15M cap → $2.5M target / $2.0M floor / $15M cap post-money.

Why this shape, and why now. Sindhu's Friday concern was concrete: "is it a true MVP … or maybe it is an idea" — will $2M actually fund the proof-of-integration that turns "sketch" into "investable data platform"? Bumping the target by $500K without moving the cap or floor keeps the SAFE→Series-A story clean while making room for:

1. Third founding engineer — the delta between one HIPAA-fluent build lead and a two-engineer bench with parallel workstreams (clinical import + financial import). Sindhu's "$2M may not be enough for actual data-integration proof" becomes false if we can staff two integration paths at once. 2. HIPAA infrastructure setup — AWS BAA + HITRUST-adjacent posture from day one, not "after Series A." Sindhu's escape-hatch ("we can do anything with test data … but then I think our product environment has to come with all the safety guards") is exactly the risk: a test-data MVP that can't graduate. $500K buys the real thing. 3. Epic sandbox access + one clinical export path proven end-to-end — CCDA export → Apple Health Kit or direct → HIFP synthesis on test data with the pipe HIPAA-grade. Sindhu explicitly named this: "connect to an Epic … just to prove that you can do it." 4. Buffer for the "one thing that goes wrong" — because in a 4-month MVP compressed from 12 months, the buffer isn't optional.

What the bump does NOT change.

• Runway math holds — Fatima to 2027-07-01, $250K/founder floor, insurance built in. $500K delta lands ~90 days of runway to the founding-eng bench, not the founders.
• Cap unchanged — $15M post signals discipline. We are not asking for more dilution.
• Series-A story unchanged — still $7–9M Series A on the far side of MVP-with-integration-proof-live.
• Fallback preserved — organic-to-A remains the documented fallback per HIFP-safe-vs-organic-decision-matrix-v0.1 §4.

Two alternatives Sindhu raised in-meeting, kept live for trio deliberation.

• Alt A · Y Combinator / build-money round. Sindhu: "like a Y Combinator or something or, you know, like there's a lot of options on this." Trade: potentially larger check, more program value, more dilution and a batch cadence that doesn't match the July-1-2027 timeline.
• Alt B · MVP-as-idea, integration proof deferred. Sindhu: "the model might be a little bit different where we go ask for the money to build it." Trade: keeps $2M range, but changes the pitch from "we can prove data integration end-to-end" to "here's the design; fund us to build it." This is a different investor conversation — earlier-stage narrative, higher perceived execution risk.

Deliberation question (joint): Do we adopt $2.5M/$2.0M/$15M as the working position for v4-kit propagation, or do we want to re-open the sizing question with Alt A or Alt B considered on their own merits?

What Brandon is asking for from Sindhu + Fatima:

• Thumbs-up (silence-is-assent through Monday 2026-09-14 5pm PT) — propagation runs, we hold veto for one weekend cycle.
• OR: raise the question again with specific concerns, and we make a joint call before propagation.

Non-negotiable: whichever way this goes, it's a trio decision, not a Brandon unilateral. Framing this as "directionally adopted" means propagation isn't blocked by ambiguity but the door is open through Monday.

§2 · Moats section — how "defensible in court" gets built

Working position: rewrite POV v4 §7 to Sindhu's standard, structured around Fatima's three-mind pressure test framework.

What's being asked. Sindhu named the standard cleanly: "almost like defensible in court type of thing where I feel that strongly about this being the way." Not just "we have moats" — moats that survive adversarial reading by someone whose job is to break the argument.

Fatima's proposed framework. Three-mind pressure test: 1. Financial mind — does the unit-economics moat survive a wealth-management-industry read? (Ties to §3 wealth-mgmt gap.) 2. Actuarial mind — does the risk-modeling moat survive an insurance-adjacent read? (Ties to Fatima's actuary placeholder.) 3. Legal mind — does the consent-model + IP-strategy moat survive a general-counsel read? (Ties to Karen briefing.)

Deliberation questions:

• Is the three-mind framework the right shape, or do we want more/fewer/different minds?
• Do we treat it as advisor-board scoping (bring the three minds on formally) or pre-Series-A consultation cycle (engage each mind once for a moats read, no ongoing commitment)?
• Timing: do the three-mind conversations happen before or after v4-kit propagation? Argument for after: v4 kit becomes the read-ahead. Argument for before: don't propagate a moats section that's about to be rewritten.

Working recommendation for trio consideration: propagate v4 kit with §7 marked "rewrite in flight — three-mind pressure test framework"; schedule three-mind consultations concurrent with Karen briefing sequence; land moats §7 rewrite as v4.1 in ~3 weeks.

§3 · Wealth-management advisor — when is too early?

Sindhu asked the question directly: "when is it too early to get advisors?" Fatima parked it: "we're not gonna have the … where we'll all come up with that today, but let's just throw it in there for Brandon's consideration."

Brandon's honest read: Cathy Lanning archetype (FINS lead industry advisor at Salesforce, same-shape as Fatima's HLS role but wealth-mgmt domain) is the specific ask, not "any wealth manager." She'd be an advisor slot, not a co-founder slot.

Two paths for deliberation.

• Path A · Recruit advisor now (pre-Karen). Read: the moats-rewrite (§2) and the Plan-Delta enrichment (Fatima's neighborhood-millionaire thesis) both need wealth-mgmt input to land. Waiting means propagating v4 kit with known gaps.
• Path B · Recruit advisor after Karen briefing. Read: sequence keeps legal-gate-before-external-conversations discipline intact. NDA scaffolding needs to be in place before any advisor conversation, per prior ratification (2026-09-07 §5.3).

Deliberation question: Path B looks right on discipline grounds; is anyone objecting? If Path B holds, then the wealth-mgmt advisor conversation lands after Karen coffee → NDA in place → Cathy Lanning outreach as first-line candidate.

§4 · Advisor-candidate prioritization — 7 names, how do we sequence?

Not a decision needed today, but a shape decision worth naming. Full list in HIFP-decision-log-2026-09-11 §7.

Two ways to slice the 7:

• By investor-vs-advisor intent — Julie Yu, Tara Bishop, Frisk Cressy, James Lakes are investor-shape conversations. Romi Chopra is operator-shape. Aura contacts are partner-shape. Cathy Lanning (proposed) is pure advisor.
• By urgency — Julie Yu + Cathy Lanning highest-leverage per wealth-mgmt gap + a16z-relationship value. Romi Chopra time-boxed (Dreamforce next week). Others can wait.

Deliberation question: Do we want to run these as a batch (produce shared warm-intro-email templates + brief docs) or as one-offs as timing allows? Batch = better v4-kit reuse; one-offs = faster to first conversation.

§5 · MVP scope statement — what exactly does the SAFE fund?

Ties to §1 SAFE sizing. Sindhu's fork remains the sharpest one on the table: "is it a true MVP … or is it an idea."

Working position for v4 kit (needs trio confirmation):

MVP = concept-proof + T2a chain 1 pilot with one clinical-import path proven end-to-end on test data.

Not full multi-chain HIPAA-hosted production. Series-A capital funds the production graduation.

Why this framing works: it's honest about what $2.5M buys ("we can prove the integration works; production graduation follows Series A") and it doesn't overpromise. It also matches Sindhu's escape-hatch framing ("we can do anything with test data … product environment has to come with all the safety guards").

Deliberation question: Do we adopt this scope statement into POV v4 §1.3 + Investment Memo v4 §1.1, or does the trio want a different scope frame?

§6 · Content-add prioritization — do all 5 land in v4.0 or does some slip to v4.1?

The 5 content adds (HIFP-decision-log-2026-09-11 §5): 1. AARP + elderly-longevity positioning 2. Plan-Delta enrichment (4 markers) 3. Anthropic + AWS cost scrutiny 4. Gallagher / Marsh / Aon framing 5. Dual concierge positioning line

Working position: all 5 land in v4.0. Each is source-material-complete (Brandon has drafted answers or existing analysis for all 5). No blockers.

Deliberation question: Any of these where the trio wants a longer conversation before the content lands in a distributable artifact? Specifically:

• AARP framing — Fatima's bio phrasing is a personal question; do we need Fatima's exact preferred language before propagation?
• Anthropic/AWS cost lines — Fatima said "I agree" on the scrutiny; is that a "add specific unit-economics detail" or a "revisit the whole cost model"?

§7 · Karen briefing prep — read-ahead artifact fit

Status change confirmed: §3.24 → in flight. Sindhu texted Karen during the meeting.

Deliberation question (light): HIFP-general-counsel-briefing-v0.1 is the current read-ahead. It was written before the check-in. Does it need a refresh before the Karen coffee, or does it hold as-is for the coffee (with the briefing-call proper getting the fresh read-ahead)?

Working position: hold as-is for coffee (Sindhu leads on relationship; coffee is not a deep-dive); refresh before the briefing-call proper.

§8 · Founder-input asks — what closed on Friday, what's still open?

8.1 · P0 BLOCKER — Fatima's exact Oracle title + preferred bio phrasing

Status: STILL OPEN. Friday did not resolve this.

The 09-11 transcript surfaced Fatima's AARP involvement + longevity/quality-of-life-planning angle as a new content-add (see HIFP-session-notes-2026-09-11-checkin §5.1) — Sindhu: "your position with the AARP, like, you know, how you've been like so active in that space." That's the AARP fact-add. It is not the P0 answer.

The P0 blocker is the specific ask from HIFP-founder-inputs-2026-09-08: 1. Exact current Oracle title — for v4 team bio + Investment Memo §3 founder credentials 2. Preferred bio phrasing — for POV v4 §10.3 team page + external circulation

Both are blocked-on-direct-call, not on documents Brandon or Sindhu can produce. Blocking v4 team bios and any external circulation (Karen briefing read-ahead, advisor outreach, investor conversations).

Ask: Fatima — can we get exact title + preferred bio phrasing before Monday 2026-09-14 5pm PT? A single Slack message from Fatima closes this.

8.2 · Closed (or in flight) as of 2026-09-11

• Karen briefing timeline + engagement mode — in flight (Sindhu texted Karen live during Friday call)
• Kristen Valdes b.well framing — locked as consent + partnership dual-angle
• Four-lane GTM ratification — closed
• Delaware C-corp ratification — closed

8.3 · Still open (per HIFP-founder-inputs-2026-09-08)

Sindhu (7 open): full Ethical Framework v0.1 (due 2026-09-21) · CCO title confirmation · clinical-network warm-intro map (MDVIP · One Medical Premium · EHG · PartnerMD) · IP counsel referrals via Karen · Neko + Aura post-IPO watch · chart-modal advice-boundary sanity check · Karen briefing delivery prep coordination

Fatima (7 open — §8.1 P0 pulled out separately): Karen briefing delivery prep · employer sub-segment matrix (pursue vs list-and-park variants) · rev-share economics pressure-test (10–20% range from prior partnership experience) · named investor targets by lane (health/longevity-strategic + AI-forward generalist) · advisor intros (Michelle Feinstein + Dan Conners) · named actuary contact (§5.1) · "best financial planners" question-quality corpus contribution

Deliberation question: Any of these that Friday moved from open to closed that isn't captured above?

End of open questions v0.1. Companion: HIFP-session-notes-2026-09-11-checkin and HIFP-decision-log-2026-09-11. Trio review requested by Monday 2026-09-14 5pm PT for §1 (SAFE sizing) veto window; other items on standard cadence.