About Duet

Duet is proving that nurse-practitioner-led care isn't just more accessible, it's better. We help NPs build and scale independent practices in communities too often overlooked by the health system: rural towns, immigrant populations, LGBTQ+ patients, and more. Backed by AI-driven tools that give independent NPs the backing of a much bigger system, our network of 100+ practices covering 400,000 annual visits has driven a 30% increase in preventative visits and a 35% drop in hospitalizations, the clearest sign yet that localized NP-led care means better outcomes.

We're a well-funded, early-stage company led by seasoned entrepreneurs and nurse practitioners, and backed by investors including Lerer Hippeau and Kairos.

Why Duet, Why Now

Independent primary care is disappearing, swallowed by hospital systems and private equity roll-ups, often pulling out of the communities that need it most. But 31 states now support autonomous NP practice, and the results back up what we've long believed. We built the first value-based care contracts for NPs with major payors, taking on real financial risk for outcomes. In our anchor market in New Hampshire, our network outperformed the state on total cost of care by 19%, proof that a solo NP in an underserved area can outperform a system ten times their size and get rewarded for it.

About the Role

Today NPs come to Duet to launch their clinics for its community of owners, special vendor deals, enhanced payor contracts, and advisor guidance.

Your job is to productize this experience. You'll sit close enough to the work to understand it in detail: sitting in on practice onboarding, watching how practice advisors actually spend a Tuesday, working with credentialing and billing. From there you’ll lead building the systems, workflows, and products that make the next launch faster and more delightful.

This is a 0-to-1 role in the real sense: how does a new practice acquire its first hundred patients, and which of those channels can be managed at scale? What does a launching practice actually need to see and do each week, and how much of that can our product guide them vs an advisor? You'll form opinions on these, design experiments to test them, and work with engineers to build what survives contact with reality.

The measure of your success is that the Launcher experience becomes a repeatable system that takes driven NPs and helps them fill up their practices.

What You'll Do

• Live inside the launch process. Shadow the practice advisors, join practice calls, sit with credentialing, billing, and EHR onboarding. Build a first-hand map of where a launch can stall, what gets repeated, and which pain is loudest for the NP versus most expensive for us.

• Own the launch product roadmap. Turn what you learn into a prioritized set of bets across internal tooling, practice-facing product, and automation. Write the specs, make the tradeoffs, and defend the sequencing.

• Solve patient acquisition as a product problem. Design and run experiments on how launching practices fill a schedule — paid channels, directory and marketplace presence, referral mechanics, local demand generation. Start scrappy and manual, measure honestly, and productize the channels that work into something we can run across a cohort rather than one practice at a time.

• Build the practice-facing experience. Shape what a launching practice sees, does, and gets nudged toward in our product during their first ninety days, so the product carries more of the relationship over time.

• Test community and cohort models. Explore whether launching NPs get more from each other than from us — cohort programming, peer content, shared playbooks — and build the ones that show signal.

• Work directly with engineers. Partner with a small team to scope, ship, and iterate. Prototype yourself where it's faster. Be technical enough to be useful in a design discussion and honest about tradeoffs.

• Hand off cleanly. Get each piece of the Launcher experience to the point where it's documented, instrumented, and stable enough to transition to our core product team, then go find the next bottleneck.

KPIs You'll Own

• Time to launch: days from signed agreement to first patient seen

• Milestone cycle time: days spent in each launch stage, and the variance across practices

• Patient acquisition cost and payback by channel

• Share of launch steps that are automated or self-serve rather than human-mediated

• NP-reported experience of the launch process

What You Bring

• 5+ years in product management, ideally including 0-to-1 work where the problem space was undefined and you were the one who defined it. Founding PM, new-product, or internal-platform experience is all relevant.

• Experience in an operationally complex domain — healthcare, fintech, logistics, marketplaces, or another environment where software has to accommodate messy real-world processes and regulated constraints.

• A track record of turning manual operations into product. You've watched a team do something by hand, understood why, and shipped the thing that stopped them from having to. You can point to specific examples and the before-and-after numbers.

• Real experimentation discipline. You think in hypotheses, know how to design a test that can actually fail, and can tell a real signal from a flattering one in a small sample.

• Technical depth to work with engineers as a peer. You can reason about integrations, data models, and APIs, evaluate a build-versus-buy call, and prototype when prototyping is faster than speccing.

• Growth instincts. You've been close enough to acquisition — paid channels, funnels, CAC, conversion — to run a channel test yourself rather than hand it to someone else.

Nice to Have

• Experience with EHR, practice management, revenue cycle, or credentialing systems

• Background in provider enablement, practice management, or small-business enablement platforms

• Experience with local or multi-location patient or customer acquisition

• Time spent in an operations role before moving into product

Who Will Thrive Here

• You want to build the system, not run it. You'll be tempted to just fix the launch yourself; the job is to make the fix unnecessary next time.

• You prefer to be measured on business outcomes rather than shipped features.

• You’d rather run three scrappy experiments this month than write one perfect PRD.

Location & Compensation

This role is hybrid 3x/week in office, out of NYC.

The salary range for this role is $175-200k base salary + equity.