Selected work / Seed Health

From working demo to integrated member experience

I built a personalization and learn-to-earn journey that moved from a working demo through a measured pilot into Seed’s broader member product.

AI Consultant · August 2024 – March 2025

Botanical study with green leaves, pale diagram marks, and visible roots.

The arc

A demo built to become a journey.

The outcome was more than an AI assistant. It was a connected product experience for members.

01 / Demo

Working product flow

Onboarding, product-fit questions, personalized results, learning modules, learn-to-earn, and Agent Flora existed together in the initial demo.

02 / Pilot

Measured engagement

A six-week pilot reached 40 weekly active users and showed a 24-point increase in module completion.

03 / Integration

Broader member experience

The personalization and learn-to-earn journey became part of Seed’s wider member product. Agent Flora’s later status is unknown.

Member journey

From first question to the next useful step.

The flow linked what a member shared to relevant education and product guidance.

01Onboarding

Give the experience enough context to begin.

02Product-fit quiz

Capture structured answers and open-ended needs.

03Personalized results

Turn responses into tailored guidance.

04Learning modules

Connect recommendations with education and progress.

05Learn-to-earn

Reward continued learning inside the member experience.

Related AI systems

Two users. Two different jobs.

Both systems depended on trustworthy source retrieval, but they served different workflows.

Member-facing · demo

Agent Flora

A retrieval-backed assistant inside the working member demo, connected to the broader quiz and module journey. Its status after the demo is not something I can verify.

Flask · OpenAI embeddings · Pinecone · grounded response generation

Internal content workflow

Article Generator

An internal Streamlit tool that retrieved indexed source material before drafting content for human review. The workflow included document preparation, chunking, indexing, and citation-focused evaluation.

Streamlit · LangChain · Pinecone · reviewed drafting

Internal article generator

From source material to a reviewable first draft.

This was a separate internal tool with its own workflow and measured outcomes, not an extra screen in the member demo.

The bottleneck was getting from a scattered research and content library to a draft a subject-matter expert could evaluate. I built a Streamlit workflow that made the source trail visible before publication decisions.

  1. 01 / Prepare
    Make sources usable

    Clean and segment internal content, SciCare Q&A, and relevant PubMed research for retrieval rather than handing a model one large document.

  2. 02 / Retrieve
    Find the evidence first

    Index source chunks with embeddings and retrieve material relevant to the draft brief. This made grounding an explicit input to generation.

  3. 03 / Draft
    Generate an editable starting point

    Use the retrieved context to assemble a first draft with citations that a human editor could inspect and revise.

  4. 04 / Review
    Keep the expert in the loop

    Route the output to subject-matter review. The workflow supported editorial judgment rather than treating a generated article as publishable by default.

The measured first-draft time reached 2.5 minutes; citation coverage increased from 72% to 88%. Those figures describe this internal drafting workflow, separate from the member pilot.

Measured outcomes

Results without collapsing the stories.

The pilot measured member engagement. The internal tool had its own drafting and citation outcomes.

Member experience · six-week pilot
40

weekly active users

+24pp

module-completion increase

Internal article generator
2.5 min

time to first draft

72% → 88%

citation coverage

Engineering decisions

Grounded AI is a product system.

The member demo combined session-backed onboarding, questionnaire state, recommendation logic, module progression, and retrieval-backed answers. In the internal tool, preparing documents for retrieval and preserving the review step were as important as the generation call itself.

The production code path after integration is proprietary. This case study focuses on the experience I built, the pilot we measured, and the product direction you can accurately trace from that work.

Next project

QuietDesk

A quieter Mac desktop, built around one precise interaction.

Explore the case study →

Build note

When a demo becomes a workflow

The product lesson behind the Seed experience.

Read the note →