Architecture Overview
Design Philosophy
Section titled “Design Philosophy”SeedTrust Portal is built around three principles that shape every screen:
Event-Driven UI
Section titled “Event-Driven UI”The surrogacy journey has defined milestones — contract signed, medical clearance, confirmed pregnant, heartbeat confirmed, birth. The interface dynamically adapts based on which milestones have been reached:
| Milestone | What Unlocks |
|---|---|
| Contract Signed | Journey timeline becomes visible |
| Medical Clearance | Transfer scheduling available |
| Confirmed Pregnant | Maternity allowances, monthly compensation |
| Heartbeat Confirmed | Increased payment tier |
| Birth | Final payments, closing procedures |
This means a gestational carrier won’t see “Maternity Clothing Allowance” until the journey reaches the “Confirmed Pregnant” milestone. The UI never shows irrelevant options.
Gamified Productivity
Section titled “Gamified Productivity”Internal staff process high volumes of conversations and disbursement requests. Rather than treating this as a static queue, the portal emphasizes:
- Progress counters — “5 of 12 handled today” visible in the queue header
- Auto-advance — completing a conversation automatically navigates to the next one
- Continue Working — a single button to resume the queue without decision fatigue
Two-Portal Architecture
Section titled “Two-Portal Architecture”The application serves two fundamentally different user groups from a single codebase:
External Portal (client-facing)
- Transparency-focused — clients see where their money is and what’s happening
- Mobile-first for gestational carriers — large touch targets, camera-first uploads
- View-heavy for intended parents — balances, timelines, status
Admin Portal (staff-facing)
- Productivity-focused — optimized for throughput and queue clearing
- Data-heavy — team dashboards, response time indicators, bulk actions
- Keyboard-navigable — power users can triage without a mouse
Communication Flow
Section titled “Communication Flow”Messages flow through two stages:
Incoming Email → Triage Queue → Assignment → Communications Inbox → Reply/Complete- Triage — new emails land in a shared queue. A triage admin assigns each conversation to a team, person, and case.
- Communications — assigned conversations appear in the team member’s “My Inbox.” They reply, add notes, and mark conversations complete.
This two-stage flow ensures every conversation gets properly categorized before anyone responds, preventing duplicate replies and misrouted messages.