MVP Definition — April 21, 2026
MomDom.
Household Operating System
8–10 Month MVP + Pilot Launch · Part-time · 10–15 hrs/week
01
Strategic Context
Why MomDom exists, what it actually is, and where the moat comes from.
MomDom is a household operating system designed for modern mothers — a relational, adaptive platform that manages health records, routines, inventory, caregiver access, and eventually AI-driven anticipation of family needs. This is not a calendar app. It is a fully architected, multi-tenant family management system with a clear path from manual data entry today to predictive AI automation in a subsequent release.
Core principle: Every manual entry by a pilot user is silently structuring the dataset that Amazon Bedrock will draw from at AI launch. The database is designed from day one to feed it cleanly — no migration required, no retrofitting. The architecture is the long game.
Core Value Propositions
Row-Level Security at the Database Layer
Caregivers, spouses, and babysitters access only what the primary account holder explicitly permits. Enforced in PostgreSQL — not in application code.
Multiplayer Household Model
Real-time caregiver synchronization without AI. If a caregiver logs a medication dose, Mom is notified instantly. Day-one value that doesn't wait for Bedrock.
Cross-Platform from One Codebase
iOS, Android, and Web delivered from a single TypeScript monorepo. API contracts, types, and validation logic are always in sync across all platforms.
Silent AI Training — Manual Phase Now
The relational schema is the training ground. Every household routine logged manually today teaches the future AI model without a single Bedrock call in MVP.
The Moat: MomDom is not building disconnected lists. It is building an adaptive behavioral loop — a household Operating System. The relational database schema, the caregiver permission model, and the behavioral data accumulated during manual use collectively create a structural barrier that no simple notes or calendar app can replicate.
02
Technical Architecture
Stack selected for suitability to this use case and scalability toward post-MVP AI features.
UI Layer
React Native (Expo)
iOS + Android. Expo Router handles navigation; EAS handles cloud-based binary compilation for both app stores. Minimal native configuration overhead.
UI Layer
React / Next.js
Web frontend. Shares component logic and TypeScript types with mobile via the monorepo
packages/shared package. Hosted on AWS Amplify.Backend
AWS Lambda + API Gateway
Stateless serverless functions for everyday reads and writes. Auto-scaling, cost-efficient at pilot scale (200–300 users).
Backend
Aurora PostgreSQL Serverless v2 + RDS Proxy
The relational data model is non-negotiable for this app's interconnected data structure. RDS Proxy manages connection pooling under concurrent load.
Backend
Amazon Cognito
User registration, login, Google/Apple SSO, and JWT token issuance. Integrates directly with API Gateway for request authorization.
Backend
AWS Fargate
Container-based processing for future high-volume AI pre-processing tasks (MVP+1). Architecture-ready in MVP, not actively running.
AI Layer (MVP+1)
Amazon Bedrock — Claude Models
Processes forwarded emails and voice transcripts into structured data. Runs inside a private VPC — no data leaves the controlled environment. Deliberately deferred to post-MVP.
AI Layer (MVP+1)
Amazon EventBridge
Powers proactive reminders and future-dated AI-generated notifications. Wired in during infrastructure setup even before AI is active.
DevOps & Infrastructure
AWS CDK (TypeScript) · GitHub Actions · npm Workspaces + Turborepo
All cloud resources defined in version-controlled code. A
cdk deploy command reproduces the entire environment deterministically. Push-to-deploy automation for cloud, web, and mobile binaries. Single repository containing cloud/, web/, mobile/, and packages/shared/ — ensuring API contract, types, and validation logic are always in sync.
devMode flag: During development, Aurora is swapped for a free-tier RDS instance and the NAT Gateway is removed. This keeps AWS account cost near $0 throughout the build phase. Production costs run on MomDom's AWS account.
03
Milestones & Deliverables
All Milestones released upon functional demonstration. No parallel work is allowed.
| # | Deliverables | Timeline |
|---|---|---|
| M0 | Architecture Validation Sprint: finalized DB schema with all RLS policies documented; confirmed tech stack decisions; resolved caregiver sharing model. Deployment of waitlist landing page with email capture. | Weeks 1–2 |
| M1a | Monorepo lives on GitHub with CI/CD pipelines; foundational AWS CDK stacks deployed (VPC, IAM, Secrets Manager). Prototype started. | Weeks 3–5 |
| M1b | Amazon RDS PostgreSQL + RDS Proxy deployed; Expo EAS configured and connected. Prototype completed. | Weeks 6–8 |
| M2a | Amazon Cognito auth fully integrated with Google/Apple SSO. | Weeks 9–11 |
| M2b | Row-Level Security (RLS) enforced and pgTAP-tested across family profiles in the DB. | Weeks 12–14 |
| M2c | Core React Native and React screens navigable; manual Calendar Events and Tasks syncing to cloud DB. | Weeks 15–16 |
| M3 | Final Architecture Document, defining AI ingestion architecture and data contract for Amazon Bedrock. | Weeks 17–28 |
| M4 | UI/UX bug resolution from internal beta; production deployment to Apple TestFlight and Google Play Closed Testing for pilot cohort (200–300 users); 30 days active monitoring, DB optimization, and critical patching. | Weeks 29–36 |
Pause Checkpoints: Either party may invoke a Checkpoint Review at the conclusion of M0, M1, or M2. A written request must be made at least 7 days before the milestone demo. If paused, all completed and accepted payments are immediately due (net-5). The engagement may resume within 180 days by mutual written agreement without renegotiation.
04
AWS Cost Staging
Projected monthly costs on the MomDom production AWS account. DevMode swaps Aurora for free-tier RDS on the Consultant's personal account during development.
M0–M1
< $10
AWS Free Tier covers nearly all infrastructure setup
M2
$15–25
RDS db.t3.micro becomes primary ongoing cost in dev
M3–M4
$40–70
Pilot-scale infrastructure supporting 200–300 users
Post-Launch
$150–250
1,000+ user production load — RDS scaling and Lambda concurrency are the primary levers
05
Risk Register
Key risks monitored across the engagement. The two existential risks anchor all architecture and testing decisions.
High
Silent data corruption across household boundaries
A caregiver reading or writing data belonging to a different family is an existential trust failure. Enforced by PostgreSQL RLS + pgTAP tests at M2b. No merge to main without passing RLS test suite.
High
Unauthorized data exposure across permission boundaries
A babysitter seeing a co-parent's full profile, or a co-parent seeing medical data they were not granted access to, breaks the core trust model. RLS is the guard — application-layer permission checks are a secondary fallback only.
High
Behavioral cold start problem
A mother must form the daily update habit before the system proves its value. The app is less useful on day one than on day 30. Only real behavioral observation (not surveys or stated intent) can validate whether this loop closes. PWA prototype validation is the primary mitigation before M1a.
Medium
Stock Option Agreement execution delay
The SOA is a hard pre-condition for M0 payment release. Engaging Clerky must happen this week. Delays here push the entire milestone payment timeline.
Medium
AWS CDK / React Native learning curve
The Consultant has acknowledged learning curves on AWS CDK and Expo/React Native. The 10-month timeline includes an honest buffer. Architecture decisions are logged in MOMDOM_DECISIONS.md so intent is preserved if a second developer onboards.
Medium
Scope creep at milestone boundaries
New feature requests surfaced during milestone review are not acceptance criteria. They require a formal written Change Request amendment (§5.9). The M0 and M1 checkpoints are the cleanest pause points if funding timing shifts.
Medium
Market ceiling without B2B or international pivot
Current ICP and pricing supports a strong lifestyle or regional SaaS business. Venture scale requires a B2B pivot (employer benefits, pediatric practices) or international expansion. Year 1 should optimize for household depth over raw user count.
Low
Apple D-U-N-S / Developer Program delay
D-U-N-S processing + Apple business entity review can take up to 3 weeks. M4 TestFlight deployment is hard-blocked until complete. Must be initiated this week. No shortcut exists.