The challenge: reconstructing the case
Yunda coordinates a journey with two starting points: intended parents seeking services and gestational carrier candidates moving through intake and records review. Those pipelines converge through matching, agreements and clearance, then continue through IVF, pregnancy, birth and remaining follow-up obligations.
Leads, candidate records, waiting reasons and case updates were distributed across sheets and team processes. Before taking action, a coordinator needed to assemble the current situation: what changed, what is still missing, who owns the next step and what evidence is required before the case can advance.
An illustrative handoff
In the proposed operating model, a coordinator associates a consultation transcript or document with the right opportunity or application. The assistant proposes facts, dates, responsibilities and follow-up tasks with source references. An authorized employee reviews the changes.
After required evidence and approval are recorded, the outgoing team submits a handoff package. The receiving case manager accepts responsibility with visibility into unresolved tasks, history, external dependencies and open obligations.
This describes the proposed operating model, not a report of an executed customer case. Medical conclusions, legal clearance and financial verification remain with authorized people.
What the pilot has demonstrated
Project documentation records an authenticated portal MVP connected to an Azure-hosted Frappe instance using synthetic data. Its demonstrated loop includes role-specific case access, individual appointment acknowledgements, task completion and a carrier update released only after case-manager review.
The Yunda-specific assistant integration, source ingestion, transcription, AI proposals, workflow-specific private uploads and notifications still require implementation and end-to-end acceptance. The interactive prototype is not a complete production CRM.
The next proof is operational
A comparable baseline and pilot period should measure the time from a source event to a reviewed update, staff time spent assembling case status, open items discovered after a handoff, evidence coverage for AI proposals, and overdue follow-ups.
These are proposed measures, rather than achieved results. The value to validate is less repeated reconstruction of customer context and more reliable follow-through across a long-running journey.
