From health answers to buying decisions
Discovering and validating a new business vertical inside an existing AI product (without changing what made it work).
Product Snapshot
This case study documents the discovery of an unserved commercial behavior pattern inside an existing AI product, and the three-week experiment that validated it as a B2B revenue channel. The insight came from a product designer analyzing conversation data, not from a growth meeting or a revenue target.
In three weeks, 427 product and service-related questions surfaced inside Julieta's conversations. 70% received a specific suggestion. 6 in 10 parents clicked through to a brand or provider. 4 in 6 confirmed a purchase. Average ticket: $650 MXN. Zero complaints about the commercial layer. The trust that made the health product work transferred directly to the purchase recommendation.
Context
AI parenting assistant · existing live product
Julieta already supported high-trust parent conversations.
Problem
Unserved commercial intent inside trusted conversations
Parents asked where to buy, but the product had no commerce layer.
Solution
Structured product/service data layer for Julieta
Specific suggestions inside relevant conversations only.
Role
Product discovery + experiment design + cross-functional lead
Conversation data analysis, hypothesis framing, pilot design, and measurement.
Team
Founders · Marketing · Engineering
A one-week pilot approved and scaled into a three-week validation.
Outcome
Validated B2B channel · $650 MXN avg ticket · 4/6 confirmed purchase
Commercial signal validated without changing core health behavior.
Scope
Behavior analysis · Growth design · Commerce layer · B2B model
From product discovery to commercial model validation.
Context
Parents came for health guidance. They stayed for everything else.
bbconmigo was built to support parents of babies 0–12 months through high-anxiety, low-bandwidth moments. The core product (an AI assistant named Julieta) was designed around three behavior states: reassurance, uncertainty, and escalation.
It worked. Parents returned. Retention held at 60% next-day during the freemium trial. But something beyond the original design was happening in the conversation data. Parents who came in scared and left calmer began returning with a different kind of question. Not "is this fever dangerous?" but "which formula has better nutrients for my baby?" and "where can I find a hearing screening clinic near me?"
Julieta had become their source of truth for daily parenting decisions. Not just emergencies. Everything.
The Real Problem
Julieta knew the baby. She didn't know where to send the parent.
When parents asked about products and services: formula brands, pediatric specialists, hearing labs, mosquito repellents safe for infants. Julieta responded with generic, ambiguous answers.
Not because the AI wasn't capable. Because it had never been given the right information source. Julieta's knowledge base was built for clinical guidance. There was no structured data for brands, services, or local providers. So when a parent asked "where can I find a hearing screening for my baby in the city?" the response was vague, non-specific, and in a product built entirely on the trust of its precision, that ambiguity had a cost.
| Evidence | What it meant | Product decision |
|---|---|---|
| Parents asked product and service questions inside a health conversation | Intent was present but infrastructure wasn't | Build a structured product/service data layer for Julieta |
| Julieta's generic answers on commercial queries didn't satisfy parents | Ambiguity breaks trust at the point of practical need | Give the agent specific, curated data to answer with precision |
| Parents already trusted Julieta for health decisions | Trust was transferable to purchase decisions in the right context | Validate whether trusted suggestions drive conversion |
| Suggestions only appeared when the parent asked | No intrusion = no trust erosion | Keep commercial suggestions inside the conversational context only |
Hypothesis
What if the agent that parents trusted for health could also tell them exactly where to buy?
The hypothesis emerged from a product designer analyzing conversation behavior data, not from a growth meeting or a revenue target.
The pattern was clear: parents were generating commercial intent inside a trusted conversation. Julieta had context no ad platform has. She knew the baby's age, feeding situation, sleep patterns, and health history.
If given the right data source, could she convert that context into a precise, helpful suggestion that parents would act on?
“If Julieta is given structured data about products and services relevant to each query, parents will click through to learn more, visit the provider, and complete a purchase. Because the suggestion comes from an agent they already trust at the moment they already need it.”
The hypothesis was presented to founders, marketing, and engineering. A one-week pilot was approved. Scope: 30 users. Filtered for product and service specific intent. Zero changes to the core health guidance behavior.
The Experiment
One week to test. Three weeks to validate. Zero intrusive placements.
The pilot ran for one week. 30 users. 45 questions filtered specifically for product and service intent. Products and services were introduced into Julieta's knowledge base for a defined set of categories: personal care, infant formula, pediatric specialists, and clinical labs.
When a parent's question matched an available category, Julieta responded with a specific suggestion (a named product, a brand, a specialist, or a location) presented as a card inside the conversation, with a UTM-tracked link to the provider's page.
Nothing appeared unless the parent asked. No push. No banner. No interruption. The pilot signal was strong enough to move to a three-week scaled experiment.
| # | Question pattern | Category |
|---|---|---|
| 1 | Which formula is better: nutrients, digestion, reflux? | Infant nutrition |
| 2 | Traditional crib vs. co-sleeping, which is safer? | Baby gear |
| 3 | Attachment toy recommendation: safe materials, no allergies. | Baby products |
| 4 | Best price on infant mosquito repellent (6–12 months). | Baby care |
| 5 | Unisex diapers vs. gender-specific, which and where to buy cheaper? | Baby care |
| 6 | Baby needs hearing screening, where in the city? | Clinical services |
| 7 | Find a new pediatrician: mine moved, too far now. | Medical services |
| Variable | Decision | Rationale |
|---|---|---|
| Product introduction order | Scaled by most frequent question type | Start where intent was highest |
| Suggestion format | Conversational card with UTM-tracked link | Non-intrusive, contextual, dismissible |
| Conversion tracking | UTM clicks + direct user follow-up question | Double-validate with confirmed purchase |
| User validation method | Re-engagement: "Did you buy?" Yes / No / Why not | No assumption of conversion from click alone |
| Commercial model explored | CPC + monthly brand subscription in parallel | Two revenue mechanics tested simultaneously |
Experiment Flow
01
Parent asks product/service question
Intent appears inside chat
02
Category match
Formula, baby care, specialist, lab
03
Suggestion card appears
Only when relevant
04
UTM click tracked
Provider or brand page
05
Follow-up confirms purchase
Yes / No / Why not
Results
70% suggestion rate. 6 in 10 clicked. 4 in 6 confirmed a purchase. $650 MXN average ticket.
| Metric | Meaning | Decision generated |
|---|---|---|
| 427 product/service questions in 3 weeks | Commercial intent was already in the product unserved | The channel existed before the infrastructure did |
| 70% response rate with specific suggestions | Structured data transformed vague answers into actionable guidance | Expand product and service directory as a priority |
| 6 in 10 clicked through | Parents acted on Julieta's suggestions at a high rate | Trust from health interactions transferred to commercial ones |
| 4 in 6 confirmed purchase | Conversion wasn't click inflation parents bought | The agent's context made suggestions feel personally relevant |
| $650 MXN avg ticket | Mid-range purchase value across a mixed product/service set | Revenue potential scales with directory depth and brand diversity |
| 0 complaints about suggestions | No trust erosion from commercial layer | Context-only suggestions preserve the product's core value |
Design Decisions
The hardest decision was what not to build.
The easiest version of this feature was a recommendation widget that appeared after every health question. We didn't build that.
The second easiest version was a dedicated Shop tab inside the product. We didn't build that either.
The decision that defined this feature: the commercial layer would only exist inside the conversational context that created the need. A parent asking about formula sees a formula suggestion. A parent asking about fever management sees nothing commercial. That constraint wasn't a technical limitation. It was a product principle.
Suggestions appear only inside relevant conversations
Persistent recommendations or dedicated commerce section
Trust is contextual. Serving outside context erodes it.
Lower total impressions. Higher relevance per impression.
Click-through rate reflects genuine intent, not exposure.
Card format with UTM link + follow-up purchase confirmation
Conversion assumed from click data alone
Parents could click and not buy. Validation required actual behavior.
More friction to validate. Higher confidence in the data.
Metrics reflect real purchases, not optimistic proxies.
Scaled introduction by most frequent question type
Full directory launch from day one
Start where intent was highest and signal was clearest.
Slower initial revenue surface. Cleaner hypothesis validation.
Each category validated independently before expanding.
CPC model + subscription exploration in parallel
Single monetization mechanic from the start
Two mechanics generate different brand relationships and data.
More complexity to track in early stage.
Data will determine which model brands prefer at scale.
How the System Changed
Julieta didn't become a sales agent. She became a better guide.
The product's core behavior didn't change. Reassurance, uncertainty, and escalation remained the three states that governed every health-related conversation.
What changed was the knowledge base the agent could draw from. A structured directory of products, brands, pediatric specialists, and clinical labs was introduced as a new data layer. Separate from the clinical RAG, invoked only when the query matched a commercial category.
The agent's role expanded without shifting. She went from being a guide through health uncertainty to being a guide through daily parenting decisions which, for a parent of a 0–12 month baby, include an enormous number of purchase decisions made under uncertainty, at speed, with limited time to research.
The trust that formed in the first interaction didn't just retain users. It created a context where parents adopted Julieta as a reference point for decisions they would have previously made through Google, WhatsApp groups, or guessing.
Query classification
Context decides which knowledge layer answers
Clinical RAG
Health guidance
Reassurance, uncertainty, escalation
Commerce directory
Products, services, and providers
Specific suggestions only when relevant
| Before | After |
|---|---|
| Julieta answers health questions only | Julieta answers health + product/service questions |
| Generic, ambiguous responses to commercial queries | Specific, curated suggestions with direct provider links |
| One RAG data source: clinical knowledge | Two RAG layers: clinical + product/service directory |
| Revenue model: B2C subscription only | B2C subscription + B2B CPC + subscription exploration |
| User value: health guidance in uncertain moments | Trusted guide for daily parenting decisions |
Impact
A behavior pattern in conversation data became a validated B2B revenue channel in three weeks.
The experiment didn't just validate a hypothesis. It opened a business vertical that didn't exist before a product designer looked at what parents were actually asking.
Brands, pediatric specialists, and clinical labs are now in commercial conversations with bbconmigo. A consolidated directory is being built to live permanently inside the product ecosystem. The channel is real, the conversion is confirmed, and the trust that makes it work was already there it just needed the right infrastructure to act on it.
| Outcome | Signal | Next step |
|---|---|---|
| 4/6 confirmed purchase rate from suggestions | Parents act on Julieta's commercial guidance | Expand directory across all 7 question categories |
| 0 trust erosion from commercial layer | Context-only suggestions preserve core product value | Maintain strict context-only rule as directory scales |
| Active commercial conversations with brands, labs, specialists | B2B vertical is commercially viable | Define CPC pricing and subscription tier for brands |
| Consolidated product/service directory in development | Infrastructure for scale is underway | Prioritize categories with highest question frequency |
| New revenue stream validated without changing core product | Growth happened inside the existing trust relationship | Document as repeatable model for future product verticals |
Commerce funnel
01
427
Product and service questions
02
70%
Received a suggestion
03
6/10
Clicked through
04
4/6
Confirmed a purchase
Average ticket
$650 MXN
Reflection
Three things that are true about growth inside AI products after building this.
The first lesson: the most valuable growth signal isn't in the analytics dashboard. It's in what users are already asking that the product can't answer yet.
The second lesson: trust transfers, but only when the new capability doesn't break the context that created the trust. Julieta could carry commercial weight because the suggestion felt like guidance, not an ad. That distinction was a design decision, not an accident.
The third lesson: a product designer looking at conversation data is doing product strategy. The channel existed before the infrastructure. Identifying it required reading behavior, not reading metrics.
What I'd Validate Next
The questions that matter after the first validation.
- Does purchase intent increase as the directory grows and suggestions become more locally specific?
- Does a parent who converts once trust Julieta's commercial suggestions more in future sessions?
- At what suggestion frequency does the commercial layer begin to affect the perceived identity of the product?
- Which model do brands prefer at scale: CPC per click or flat monthly subscription with unlimited placements?
- Can the query classification layer be trained to surface commercial categories proactively within safe conversational boundaries?
- What's the LTV delta between a parent who only uses health guidance vs. one who also engages with product suggestions?