← Home
HIFP · v4 Canonical Kit

Build + Engineering Plan v4

Draft for trio review · brandonstauber@gmail.com

HIFP — Build + Engineering Plan v4

Supersedes. HIFP-timeline-compression-cut-sheet-v0.1 (2026-09-04) + HIFP-hustle-plan-v0.1 (2026-09-07). Both remain as historical decision-record; this is the current canonical plan. Date. 2026-09-12 Author. Brandon (lead pusher; trio decisions land jointly). Status. Draft for trio review. Gate on trio thumbs-up: SAFE-sizing formal ratification (see HIFP-decision-log-2026-09-11 §1). Companion. HIFP-session-notes-2026-09-11-checkin · HIFP-decision-log-2026-09-11 · HIFP-open-questions-2026-09-11 · HIFP-POV-v4 · HIFP-investment-memo-v4 · HIFP-gtm-tier-strategy-v0.1 · HIFP-poc-hosting-runbook-v1.

Executive Frame (SCQ)

Situation. Since the 2026-09-04 v0.1 cut sheet, four things have materially changed the build picture: (1) POC is live at hifp-poc.pages.dev with User + Practice + Employer persona surfaces + dual-concierge positioning + Plan-Delta enrichment shipped; (2) 4-lane GTM structure ratified 2026-09-11 (T1 Employer · T2a Concierge active-direct · T2b Partner-channel D2C · T3 Employer-overflow); (3) SAFE sizing directionally adopted at $2.5M target / $2.0M floor / $15M cap post-money, funding a 3-engineer founding bench + advisor board; (4) MVP scope locked as concept-proof + T2a chain-1 pilot + one clinical-import path proven end-to-end on test data — with multi-chain HIPAA-hosted production + banking-tier security locked as the Series-A milestone.

Complication. v0.1's 16-week compressed MVP was built against 2-3 engineers, no ratified GTM, and no clarified Series-A boundary. The plan holds structurally — 16 weeks against the compressed MVP is still the right shape — but the load distribution changes materially with a 3rd engineer, the employer-persona surface as a first-class MVP deliverable (not deferred), and the sharpened chain-1 pilot dependency.

Question. What is the revised 16-week build that (a) honors the locked MVP scope, (b) ladders cleanly into the Series-A milestone without over-promising, (c) staffs the ratified 4-lane GTM properly at MVP, and (d) uses the SAFE bump on team + advisors + HIPAA infrastructure, not scope expansion?

Answer. Same 16-week window, redistributed across a 3-engineer bench (Brandon + 2 founding engineers hired within 4-6 weeks of SAFE close), with three explicit shifts from v0.1: (1) employer benefits-admin surface stays in MVP as a demoable persona (already shipped in POC; production-hardening slots into Weeks 13-14); (2) one clinical-import path proven end-to-end on test data becomes the load-bearing engineering milestone — chain-1 SMART-on-FHIR against Apple Health Kit / CCDA / Quest-Labcorp import; (3) HIPAA infrastructure lands from Day 1, not deferred — the $500K-1M SAFE bump specifically funds this so the MVP-to-Series-A jump is a scale story, not a rebuild story. Everything else deferred to H1 (weeks 17-36) or Series-A (post-SAFE-conversion) per the sharpened cut list below.

§0 · What changed since v0.1 — the delta

Area v0.1 assumption (2026-09-04) v4 reality (2026-09-12) Impact
POC state POC exists, not deployed POC live at hifp-poc.pages.dev behind Cloudflare Access; User + Practice + Employer surfaces shipped 2026-09-12 Week 15 deploy milestone effectively done; POC quality is now Ledger §3.51-tracked, not the-thing-we're-building
GTM structure 3-tier framing under discussion 4-lane ratified 2026-09-11 (T1 Employer · T2a Concierge active-direct · T2b Partner-channel D2C · T3 Employer-overflow) Engineering surfaces map cleanly to 4 lanes now (see §9); no more speculative revenue-lane discussion
SAFE sizing $1.5-2M target $2.5M target / $2.0M floor / $15M cap directionally adopted +$500K-1M funds team + advisors + HIPAA, NOT scope expansion (Brandon Message 1 ratified by Sindhu DM)
MVP scope statement "credible demonstrable narrative-plus-real-data" Concept-proof + T2a chain-1 pilot + one clinical-import path proven end-to-end on test data Sharper — chain-1 dependency now load-bearing, not fallback-able
Series-A milestone not explicitly stated Multi-chain HIPAA-hosted production + banking-tier security Clean ladder; anything HIPAA-graduate-scale defers to Series-A explicitly
Team assumption 2-3 engineers 3-engineer founding bench (Brandon + 2 founding engineers) Distributes clinical-import + financial-import workstreams in parallel
Advisor board not scoped Legal + financial + actuarial via SAFE proceeds (advisors-via-SAFE posture, 2026-09-12) Closes moats "defensible-in-court" gap without hiring; three-mind pressure test lands as advisor-board scoping
Dual-concierge positioning not surfaced "Financial concierge married to a medicine concierge" shipped in POC landing 2026-09-12 Serves T2a lane; changes v4 positioning line permanently
Plan-Delta signal set biomarker + wearable + self-report + EHR Extended with credit score + financial background + employment status + HENRY-segment markers (Fatima Friday check-in) Financial-signal engineering scope expands slightly; UI already in POC
Employer persona deferred to Series-A per Red Team T2 Shipped in POC as /employer (2026-09-12) — first-class MVP demo Red Team T2 cut item recovered; production hardening is now Weeks 13-14, not H2
Karen briefing pre-SAFE-immediate In flight — Sindhu texted 2026-09-11 Legal gate on schedule; NDA scaffolding sequenced normally
Fatima full-time gate asymmetric commitments named 4-week transition possible only after July 1 2027 (Friday clarification) 16-week clock still valid; Fatima high-availability assumption holds through July 2027

§1 · MVP scope statement — locked

MVP = concept-proof + T2a chain-1 pilot + one clinical-import path proven end-to-end on test data.
Series-A milestone = multi-chain HIPAA-hosted production + banking-tier security.

Three concrete implications this locks:

1. Chain-1 is load-bearing at MVP, not a fallback. If chain-1 doesn't sign, MVP doesn't ship as spec'd — b.well individual-access is a category-preservation mechanism, not a chain-1 substitute for the pilot narrative. Fatima chain-1 conversations must run in parallel with the build, with a hard sequencing decision at Week 8. 2. "One clinical-import path proven end-to-end on test data" means the pipe is real. Not a screenshot; not a mock. Live CCDA + Apple Health Kit + Quest / Labcorp import running against a de-identified test cohort, with data-scope + underwriting-firewall + delete-forever architecture demonstrable to an investor. 3. HIPAA infrastructure lands Day 1, on test data. AWS BAA in force, HITRUST-adjacent posture established, Epic sandbox access provisioned — all before production real-user traffic. This is what the SAFE bump funds.

§2 · What's already done (POC state as of 2026-09-12)

POC live at hifp-poc.pages.dev behind Cloudflare Access. Ledger §3.49-3.51 tracks the deployment; runbook at HIFP-poc-hosting-runbook-v1.

User-persona surface (D2C, T2b lane demo):

Practice-persona surface (T2a lane demo): /practice

Employer-persona surface (T1 lane demo): /employer — NEW 2026-09-12

Demo scaffolding:

What this means for engineering: the 16-week MVP starts from a running Next 14 codebase with 3 personas already scaffolded. Weeks 1-2 are architecture-alignment + founding-eng onboard, not a from-scratch build. Weeks 5-13 are the production-graduation of what's already in the POC skeleton.

§3 · What stays in MVP (revised from v0.1 §1)

Feature is IN if it satisfies all three of: (a) demonstrably necessary to the HIFP thesis walk, (b) unblocks a chain-1 pilot demonstration, (c) achievable by the 3-engineer bench in 16 weeks.

3.2 · One clinical-import path proven end-to-end on test data (LOAD-BEARING)

3.3 · One wearable + one financial import

3.4 · Plan view + one Plan-Delta scenario

3.5 · Question-asking AI assistant (canned + guarded)

3.6 · Share-view (advisor-preview)

3.7 · Trust surface

3.8 · Employer benefits-admin surface (NEW to MVP scope)

3.9 · Practice-persona surface (elevated to first-class MVP)

3.10 · Consumer-tier billing (Stripe) — locked in MVP per Hustle Plan

3.11 · Mobile-web responsive

3.12 · Basic analytics (product-side, not consumer-facing)

3.13 · HIPAA infrastructure baseline (NEW to MVP scope)

§4 · What defers to H1 (weeks 17-36, post-MVP, post-SAFE)

§5 · What defers to Series-A (post-SAFE-conversion) — the Series-A milestone spec

Series-A milestone = multi-chain HIPAA-hosted production + banking-tier security. The following ladder cleanly:

§6 · What falls off entirely (was in v0.1 or v3 scope; not returning without new evidence)

§7 · Team + resourcing (updated for $2.5M SAFE)

7.1 · Founding team at SAFE close

7.2 · Advisor board (NEW per advisors-via-SAFE posture 2026-09-12)

Funded through SAFE proceeds; not hired. Three-mind pressure test framework (Fatima Friday proposal) implemented as advisor-board scoping:

Advisor cost budget: ~$100-200K of SAFE proceeds across advisor honoraria + equity grants over the 16-month runway (indicative; individual engagements are one-shot moats-read consultations vs. ongoing advisory-board seats).

7.3 · Sindhu review bandwidth

40-60 hours budgeted into the 16-week plan for canned-response boundary review (unchanged from v0.1 §6.4). Sindhu owes full HIFP-ethical-framework-v0.1 by 2026-09-21.

§8 · Four-lane GTM ↔ engineering surface map

GTM lane (2026-09-11 ratified) POC surface (2026-09-12 live) MVP production hardening H1 extension Series-A extension
T1 Employer (self-insured; Salesforce-shape) /employer benefits-admin dashboard Cohort reporting + BAA + underwriting-firewall enforced Benefits-committee export polish · PEO channel integration · Broker-mediated group buys (Mercer/WTW/AON/Alliant) Real-cohort scale reporting · SLAs · benefits-consultant-channel (Gallagher/Marsh/Aon) partnership formalized
T2a Concierge active-direct (MDVIP/One Medical Premium/EHG/PartnerMD) /practice cohort dashboard + chain-1 pilot SMART-on-FHIR integration proven end-to-end · practice-branded advisor briefs · dual-concierge positioning Multi-chain integration · role-aware share views (RIA/CPA/Estate Planner) Chain-network aggregation · concierge-network-of-networks pattern
T2b Partner-channel D2C (Consumer-Wellness Partnerships: biomarker/wearable/concierge-adj/telehealth) Landing + Signup + /(app) user surfaces D2C paid tier via Stripe · biomarker + wearable + b.well individual-access Loop C P0/P1 partner integrations (biomarker · Aura/Whoop wearables · GoodRx-shape) Loop C partner licensing revenue (Series-A pipeline per hustle plan Lane 3)
T3 Employer-overflow (broker-mediated · exec-perk · voluntary-benefit) Home / signup upsell paths + /employer for benefits admin Basic overflow paths · MFA · Stripe billing Voluntary-benefit channel (MetLife/Prudential VB/Unum/Colonial/Aflac) · Executive-health-perk sub-segment Broker partnerships full · SMB-through-PEO scale

Reading the table. MVP staffs all four lanes at demoable-quality; H1 promotes each lane's revenue-generating channel to production quality; Series-A scales to real cohort data + multi-chain + multi-partner. Investor conversation: "we can demo four lanes today; here's the H1 revenue-conversion plan by lane; here's the Series-A scale story."

§9 · Sequencing — the 16-week plan (revised)

Assumes Week 1 begins at SAFE-close date with founding-eng #1 onboarded within 4-6 weeks. Fatima high-availability holds through July 2027. Brandon full-time by Week 4.

Week Focus Milestone Notes vs. v0.1
1-2 Founding-eng #1 onboard · arch alignment · AWS BAA + HIPAA infrastructure baseline stood up · SAFE-close operational · Karen legal-gate follow-through Eng environment ready · scope-cut ratified · HIPAA infra baseline live (test data only) NEW: HIPAA infra baseline in Week 1-2, not deferred (funded by SAFE bump)
3-4 Onboarding + consent hardening from POC pattern · audit-log infrastructure · Brandon full-time · Fatima chain-1 conversations open Auditable consent working end-to-end · chain-1 pilot conversations initiated POC pattern accelerates: 2 weeks not 4
5-6 Founding-eng #2 onboard · Oura + Empower integrations · b.well individual-access as clinical fallback · Founding-eng #3 hire criterion decided Two integrations live · fallback path stood up Parallelized: 2 engineers vs. 1 in v0.1
7-8 Chain-1 SMART-on-FHIR integration if signed; else b.well individual-access hardened · Week 8 hard sequencing decision on chain-1 Chain-1 signature yes/no explicit gate; integration path or hardened fallback NEW: Explicit gate, not open-ended
9-10 Plan-view + Plan-Delta scenario (sell-home-at-70) · Plan-Delta financial-signal ingestion (credit + employment + HENRY markers) One scenario runnable with real test data · financial signals integrated NEW: Financial-signal work reflects Friday check-in
11-12 AI assistant UI + canned response library + boundary classifier stub · Sindhu review-cycle Assistant answers 40+ questions, all guarded Same as v0.1
13 Employer + Practice persona production hardening · trust surface (export + delete) Employer + Practice demoable at production quality · export + delete verified NEW: Persona hardening in scope; was Series-A in v0.1
14 Share-view · Stripe billing production · mobile-responsive polish · product analytics instrumentation Share link works · billing live · mobile flows tested · analytics firing Same as v0.1
15 Public-URL deploy to investor-shareable Cloudflare Access-scoped domain (POC pattern extended to production) · adversarial-vector prep · Karen briefing complete + NDA scaffolding operational External URL live · testing protocol ready · NDA scaffolding in place for market-signal lunches POC learnings apply
16 User testing kickoff (5-10 HNW 55+ testers per Ledger §4a) · investor conversations open under NDA First 3 user sessions recorded · first 3 investor conversations initiated NEW: Investor conversations begin at Week 16 concurrent with user testing

Slip mode (revised). If any 2-week block slips, cut candidates in priority order: (a) mobile polish → basic responsive only, (b) share-view role variants → single view, (c) canned library → 25 questions instead of 40, (d) analytics instrumentation → manual observation only, (e) employer + practice persona production hardening slips to Week 17-18 H1, (f) Plan-Delta financial-signal set → biomarker/wearable/EHR only at MVP. Do not cut consent, audit-log, trust surface, chain-1 clinical-import path, or HIPAA infrastructure baseline — those are the pitch.

§10 · Named risks — updated

10.1 · Founding-engineer hire timing (unchanged from v0.1)

16-week plan starts at eng-onboard, not SAFE-close. If eng hire takes 8 weeks post-SAFE, real timeline is 24 weeks not 16. Pre-SAFE recruiting motion required — Fatima network + specialty recruiter engaged now. NEW risk on 3rd engineer: hire criterion decision at Week 6 means we're recruiting against a moving target for the second half of the bench. Mitigation: recruit both HIPAA-fluent + data-engineering candidates in parallel; decide at Week 6 based on which workstream is lagging.

10.2 · Chain-1 partner MVP dependency (sharpened from v0.1)

Chain-1 is now load-bearing at MVP, not fallback-able. If chain-1 signs pre-MVP → integration goes into Weeks 7-8. If chain-1 signs during MVP build → integration slots into Weeks 9-13 (compresses other work). If chain-1 doesn't sign at all pre-MVP → MVP scope statement is materially unmet; b.well individual-access preserves category but not the pilot narrative. Requires Fatima chain-anchor conversations to run Weeks 1-8 with hard sequencing decision at Week 8.

Warm-intro map to close before Week 4: MDVIP · One Medical Premium · Executive Health Group · PartnerMD (Sindhu open founder-input ask; still open per HIFP-open-questions-2026-09-11 §8.3).

10.3 · WA/IL geo-gating (unchanged from v0.1)

Red Team T1 mitigation stands — MVP does not serve WA/IL residents. Reduces addressable user-testing pool by ~4%. Impact minor.

10.4 · Canned-response boundary rigor (unchanged from v0.1)

40-60 hours of Sindhu-review time inside the 16 weeks. Sindhu bandwidth aligned Friday but not explicitly time-budgeted.

10.5 · Fatima July-1-gate (NEW / clarified)

Fatima 4-week transition to full-time is possible only after July 1 2027. If SAFE closes pre-July (targeting Q4 2026 - Q1 2027), Fatima high-availability part-time carries through the entire 16-week MVP window. Named consequence: Fatima's contributions (chain-1 conversations, actuary intros, advisor-board formation, three-mind pressure test coordination) happen at part-time cadence not full-time. Not a blocker; a scheduling reality.

10.6 · Advisor-board formation timing (NEW)

Three-mind pressure test framework requires legal (Karen) + financial (Cathy Lanning archetype) + actuarial (Fatima contact) advisors engaged by Week 8 for moats-strengthening to land before v4.1 propagation. Karen in flight; Cathy Lanning outreach post-NDA; actuary contact status unclear. Risk: if moats-strengthening slips past Week 12, investor conversations at Week 16 land with unresolved defensibility question.

10.7 · HIPAA infrastructure hire dependency (NEW)

Founding-eng #1 must be HIPAA-fluent. Hiring bar is higher than v0.1's assumption. Named consequence: hire lead time may extend from 4-6 weeks to 6-8 weeks. Mitigation: engage recruiter now; Fatima HLS network for referrals; consider founding-eng #1 as contractor-to-hire if lead time slips.

10.8 · POC-to-production graduation risk (NEW)

POC is Next 14 + Cloudflare Pages + Cloudflare Access (mock auth + localStorage). Production requires real auth (Auth0 or similar), real database (Postgres + BAA), real infrastructure (AWS HIPAA-eligible). Weeks 1-2 include this graduation. Risk: if POC patterns don't translate cleanly, Weeks 3-4 slip. Mitigation: keep POC surfaces as reference implementation, not starting codebase — production is a rebuild-with-POC-as-spec, not a lift-and-shift.

§11 · Recommendation

Adopt the 16-week v4 build plan as defined above, with the following named commitments (revised from v0.1 §7):

1. Scope cut is written down and ratified — §3 IN list is MVP; §4 list is H1; §5 list is Series-A; §6 list is closed. No mid-flight additions without a formal ledger row. 2. Founding-eng #1 hire begins pre-SAFE with HIPAA-fluent bar — Fatima network + recruiter engaged in next 2 weeks so the eng seat is filled within 4-6 weeks of SAFE close. 3. Founding-eng #2 hires by Week 5-6; #3 by Week 6-8 — hire criterion for #3 decided Week 6 based on lagging workstream. 4. Chain-1 conversations run Weeks 1-8 with hard sequencing decision at Week 8 (integrate now, defer to H1, or accept b.well-only clinical category with named narrative cost). 5. HIPAA infrastructure baseline (AWS BAA + HITRUST-adjacent + Epic sandbox) lands Weeks 1-2, funded by SAFE bump. 6. Advisor-board formation (legal + financial + actuarial) completes by Week 8 so moats-strengthening lands before v4.1 propagation. 7. Sindhu review bandwidth of 40-60 hours budgeted into the 16-week plan. 8. Brandon full-time by Week 4; Fatima high-availability part-time through July 2027. 9. Employer + Practice persona surfaces production-harden in Weeks 13-14 (elevated from v0.1's Series-A deferral).

If any of these nine commitments cannot be made at SAFE-close, the 16-week clock is not the real plan — 20-24 weeks is the honest number. Better to name that at SAFE close than discover it at Week 10.

Series-A pitch story enabled by this plan: "We proved end-to-end clinical data ingestion on chain-1 in the SAFE window, with HIPAA infrastructure in place and an advisor-board pressure-tested moats section. Here's the same architecture scaling to multi-chain + banking-tier + full production real-user data — that's what Series-A funds."

End of v4. Companion decision-record: HIFP-safe-vs-organic-decision-matrix-v0.1 · HIFP-founder-contingency-analysis-v0.1 · HIFP-timeline-runway. Superseded prior versions: HIFP-timeline-compression-cut-sheet-v0.1 · HIFP-hustle-plan-v0.1 — both retained as historical decision-record.

HIFP · Post-check-in package · 2026-09-11 · brandonstauber@gmail.com