Context
eSigns is 3Dthinks' non-invasive hormone-monitoring platform, starting with cortisol: a saliva-based alternative to blood testing that gives users real-time insight into stress, energy, and recovery patterns. I joined while the product was still pre-launch, working directly with the CMO and CTO.
The Communication Problem
The core challenge wasn't visual design, it was translation. eSigns needed to explain real clinical science (cortisol's diurnal rhythm, salivary vs. blood measurement, why patterns matter more than single readings) to a general consumer audience, without becoming either too technical to trust or too simplified to be credible. My early drafts leaned too technical. Through feedback from the team and our clinical advisor, I learned to lead with what the user needed to understand first, then layer in the science underneath.
Competitive & Content Research
I benchmarked direct competitors (Eli, cortiSense) and adjacent health-tracking apps (Whoop, Oura, Apple Health, StressWatch) to understand how other products structured similar education and data-presentation challenges, specifically how they explained diurnal rhythms, structured onboarding, and visualized trend data over single readings.
What I Wrote & Why
I owned content and information architecture across the Home page, "The Science," and "About Us," translating dense clinical material into copy that stayed accurate but approachable. One concrete example, a tone shift I made deliberately:
"Your cortisol appears lower than expected."
"Your cortisol pattern appears lower than your typical range."
That's a small wording change with a specific purpose: moving the product's voice from sounding like a diagnosis to sounding like pattern recognition, which matched how the science actually works (cortisol isn't "good" or "bad," it's about rhythm and timing) and kept the product from overstating what it could tell someone.
I also proposed a full UX restructuring based on competitive research, including turning the AI assistant's chat-bubble interface into structured insight cards, reframing the dashboard around "patterns over time" language instead of isolated numbers, and adding a personalization layer so the app could tailor insights based on whether someone was using it for mental health, athletic performance, or general wellness.
Shipped Outcome
This content shipped to the live product. esigns.health now reflects the structure and language I wrote, including the Home, Science, and About Us pages almost verbatim from my drafts.
A Moment Worth Naming
At Mobile World Congress, I represented 3Dthinks independently, speaking with CEOs and investors about eSigns' vision, and adjusting my explanation in real time depending on how technical the question was. My CEO chose me, over himself, for an on-camera interview representing the company, a moment that mattered to me as a real signal of trust, not just a resume line.
Reflection
The hardest part of this role wasn't the writing itself, it was designing for a product that didn't fully exist yet. I had to make real structural decisions (what to say now vs. what to hold back until the product was closer to launch) without a finished thing to react to. That taught me to design around a product's intended behavior, not just its current state, a skill I didn't have language for before this internship.