A typical high-level workflow with me looks like:

1

Align on what we're solving for

We start by you and your team talking me through what you're working on. Sometimes that's a specific problem — a broken process, a regulatory constraint, a client relationship that isn't working the way it should. Sometimes it's an idea or opportunity you're trying to validate or build toward. Either way, that shapes the engagement, not the other way around.

2

Getting started

I start with a kickoff call with the team I'll be partnering with. We talk through where things stand, where they are stuck, and what's already been tried vs not. From there I ask for documents, access to the right stakeholders, and whatever feedback or metrics already exist. This helps me get a clear view and align your problems to solve with current state.

3

The day-to-day

What that looks like week to week depends on the engagement, but the substance stays the same: I'm in the details with your team, unblocking decisions and keeping momentum toward what we aligned on at the start. Some clients get dedicated embedded days, some are more async support, some are a standing meeting cadence, or a mix of all three. It's scoped to the size of the engagement and what the team needs, not a fixed template.

4

Wrapping up

When an engagement ends, I put together a summary: what I set out to do, what got delivered, and my recommendations for what comes next.

Not sure where to start?

Tell me what you're working on, whether that's an idea you’re trying to build toward, or problems your teams are facing. Think of this the same way you would in an intro call. This is an AI-assisted tool I built to map what you've described to the engagement type that's likely the best fit.

The work we do together may evolve from there, but this can give you a starting point for framing the relationship and how long it might run.

How I can help you
What are you working on?
Not sure what you need? Tell me what's going on, and I'll point you to the engagement model that fits.
A brief sentence description is all that's needed
About your organization
What kind of organization are you?
This helps me understand the context before we talk.
Clinical research / CRO
Trials, RWD, clinical ops
Pharma / life sciences
Drug development, regulatory, R&D
Biotech
Early-stage, platform, therapeutics
Health SaaS / digital health
Software, platforms, apps
Care delivery & providers
Health systems, practices, pharmacies, clinics
CDMO / life sciences services
Manufacturing, lab, outsourced services
Medtech / devices
Medical devices, diagnostics, wearables
Other
Organization not listed above
How big is your team?
Rough headcount is fine.
Startup
Under 50 people
Growth stage
50-200 people
Mid-market
200-1,000 people
Enterprise
1,000+ people

Prefer to just talk it through?

Working with me

  • "You gave me practical tools I could bring to our teams to start driving immediate change... and how to apply them in the reality of day-to-day work"

    —Product Director, Former Growth Stage Startup Advisory Client

  • "In just a short period of time you've helped us add clarity and conviction to our product plans. Helping us create a common language between our product and engineering teams has been incredible."

    —CEO, Former Advisory & Product Leader Client

  • "She is likely one of the most in-depth product leaders for healthcare / pharmacy product design in the game. She is smart, practical and realistic – not a trifecta we see often in the healthcare product space.."

    —Corporate Counsel, Fortune 500 Healthcare Company

  • "It's hard to create the right mix of clinical and product talent, and you are one such talent."

    —Director of Product, Fortune 500 Healthcare company

  • "Your dedication to making things simple for patients that should be simple will be a legacy you will leave behind."

    —Director of Operations, Fortune 500 Healthcare Company