← Back
Healthtech

Mais Saúde Hub

From a generic experience to personalized health journeys that drive adoption, recurrence and revenue on the Raia and Drogasil apps.

Company
RD Saúde · Vitat
Period
Jul 2024–present
Role
Product Designer
Mais Saúde Hub

From two separate products to a health hub inside Brazil's largest pharmacy network

Vitat was born as an independent health and wellness app focused on wellness and B2C. In 2024, after a rebrand focused on primary care, it was integrated into the Raia and Drogasil apps as the Mais Saúde tab — creating a health services hub for millions of users. The promise was to connect continuous care with pharmacy convenience.

But initial data and research showed the experience was not delivering this: 18% activation, weak CTR and consistent feedback that the tab felt generic and purposeless.

"The feeling that when I answer, you're going to give me something personalized. But the result wasn't personalized. It felt like a newly launched app."— Client A, initial qualitative research

End-to-end co-leadership: from strategy to impact

I worked in co-leadership with PM and Tech Lead, responsible for all design decisions — not just the interface, but defining hypotheses, success metrics, feature prioritization and negotiating trade-offs with stakeholders.

My responsibilities covered the full cycle: continuous discovery, research synthesis, translating insights into hypotheses, prototyping, A/B testing, handoff, bug-bash and post-launch impact tracking. I was also responsible for mentoring junior designers and evolving the Vitat design system.

Four problems feeding each other

Directionless journey

Users arrived and did not know where to start. Without a clear next step, there was no habit formation or return.

Late personalization

Everything felt generic until after a lot of effort. Value was not clear in the first seconds — the critical retention moment.

Diffuse target user

Without a defined anchor segment, the roadmap became a demand dispute. Subjective prioritization, hard to justify to stakeholders.

Weak measurement

Mixed KPIs prevented proving impact and scaling what worked. Decisions relied on intuition, not data.

Three simultaneous research fronts

Three simultaneous research fronts

I structured discovery across three parallel fronts — each with specific questions, methods and outputs — to ensure hypotheses were grounded in multiple evidence sources before any design decision.

01
Quantitative — where the journey broke

Funnel analysis, abandonment maps and behavioral patterns in the app. Findings: 39% never accessed the tab, 58% did not remember it existed, only 7% completed their Profile.

02
Qualitative — why it felt generic

Interviews, NPS and usability tests to understand what built trust. Findings: 85% did not understand the benefits, 50% expected immediate personalization after filling their Profile. Profile completers had 70% CTR — vs 13% without profile.

03
Strategic — monetization and anchor segment

Stakeholder alignment to understand which segment sustains recurrence. Output: chronic user as the highest engagement profile + identification of sponsorable journeys with the pharmaceutical industry (GLP-1).

Before designing, define what we'll measure

One of the most important decisions was defining KPIs before prototyping. Each hypothesis had clear validation metrics — making design decisions more objective and conversations with PM and stakeholders more evidence-based than opinion-based.

H1: Guided journey increases activation

Measure: activation (1st click), CTR on first modules, completion of "first step". Intervention: welcome Bottom Sheet + micro-anamnesis.

H2: Personalization in a few clicks increases relevance

Measure: profile completion, CTR on personalized recommendations, engagement per module. Intervention: next step highlight + pharmacy shortcuts.

H3: Condition-based platformization increases recurrence

Measure: D7/D30 return, condition adherence, service conversion, partnership revenue. Intervention: journeys sponsored by the pharmaceutical industry.

Process decision

We used FigmaMake for testable prototypes and A/B tests before development — reducing validation cost and accelerating learning.

Three interventions, each with a hypothesis, metric and result

Three interventions, each with a hypothesis, metric and result
01
Welcome Bottom Sheet + micro-anamnesis (A/B)

Users arrived without context — they did not know what the tab was, what they could do or where to start. We designed a welcome Bottom Sheet with micro-anamnesis to collect health goals in a few clicks, generating immediate personalization. A/B validated before development. Result: +20% activation.

02
Next step highlight + integrated pharmacy shortcuts

Even with personalization available, users with a complete profile had only 13% CTR — the value was not visible. We redesigned the tab home with a dynamic next-step highlight and contextual shortcuts to pharmacy services. Result: CTR 13%→70%, +40% overall CTR, +16% engagement.

03
Condition-based platformized journeys (GLP-1 pilot)

With the anchor segment identified, we designed condition-specific journeys sponsored by the pharmaceutical industry. The GLP-1 pilot connected continuous care, medication reminders and pharmacy services in a single experience. Result: 80% follow the recommendation.

Handoff, bug-bash and continuous tracking

Handoff, bug-bash and continuous tracking

Handoff was done with detailed flow specifications, states and edge cases in Figma. I participated in the bug-bash with development before launch — ensuring the delivered experience was the designed experience. After launch, I tracked KPIs weekly and maintained short discovery cycles to identify new friction points and opportunities.

Measured impact

+20%
Activation
+40%
Overall CTR
13→70%
CTR w/ profile
+16%
Engagement
80%
Follow recommendation
M+
Users impacted

What I would do differently

I would define the anchor segment earlier. We tried to solve for all profiles at once. It was only when we identified the chronic user as the highest recurrence profile that decisions became clearer and more assertive. This should have been step zero.

I would accelerate KPI instrumentation. Before prototyping, align exactly what we will measure, who is responsible and what the success threshold is. This transforms the conversation with PM and stakeholders — from opinion to evidence.

Next case
InPacto 2026