A healthtech startup rarely wins its first customer through the person who signs. It wins through a person who works with patients or runs the clinic, who believes the product will help, and who is willing to try it. That person is the champion. A health system, a hospital group or a practice then decides whether to turn the champion's enthusiasm into a pilot, and later a contract. So the first customers of a healthtech startup are won in order: find a champion, design a small pilot, answer the privacy and security questions, and only then talk about a contract. This page covers that order and how to start the conversations.
Two kinds of first customer
| Customer | Who decides | What it takes |
|---|---|---|
| Independent practices and clinics | A physician-owner or a practice administrator | A clear benefit, a fair price, a business associate agreement |
| Health systems and hospital groups | A department lead, with IT, security, legal and finance reviewing | A champion, a pilot, security answers, patience |
The first kind can be a quick sale if the product is simple and the benefit is plain. The second takes longer, and it often begins as a pilot inside one department. How to approach the first kind is in how to sell to medical practices. This page is about getting the startup's first real use in either.
Find the champion
A champion is someone who has the problem and the standing to try a fix. Typical champions are a clinician who runs a program, a medical director, a nurse manager, an operations lead who is frustrated by a process or a physician who has already built a workaround. They are easy to find in public: they speak at conferences, they publish, they lead departments listed on a hospital's site. How to find clients from conference speaker lists shows how to use a speaker page to find people who talk about a problem you solve.
The first note to a champion should be about their problem, with a small offer: a short call to show something, or a one-page description of what you would test. Never describe patient outcomes you cannot back up. If your product makes clinical claims, the regulatory questions start earlier, and the founder should get specialist advice before anything is said in public.
Design the pilot small
A pilot is a limited, time-boxed use of the product in one unit with agreed measures. Write it down before it starts: what you will do, for how long, for how many people, what you will measure and what happens at the end. A good pilot is small enough that nobody needs to approve a large budget, and clear enough that the champion can show colleagues the result. Agree the measure with the champion: time saved, a process step removed, a rate that matters to them. Do not promise a clinical result.
The privacy and security questions
If your product creates, receives, maintains or transmits protected health information for a covered entity, you are likely a business associate, and the covered entity will need a written agreement with you. The rule is 45 CFR 164.504(e), and the Department of Health and Human Services publishes guidance on business associates. I checked summaries of the rule through a search on 2026-11-20, and HHS's own page refused my request, so read the regulation or ask a health privacy lawyer. A health system will also ask about security practices, access controls and what happens to data when the contract ends. Answer in writing, and keep the answers in one document.
Keep a short pack ready: a description of the company, a security summary, a data flow diagram that shows where patient information goes, and a sample business associate agreement. A startup that hands this over in the first meeting shows it understands the field.
Starting without a name
A hospital has no reason to trust an unknown company, so rely on a specific, relevant note to the right person, and a pilot that costs them little. For independent practices, the NPI Registry that CMS runs is a public list of providers, with specialty and location, that helps you find practices in a specialty and area, as how to sell to medical practices explains. For systems, look at the named leaders of the department that has your problem.
Subject: A small pilot for your discharge follow-up calls
Hi {{first_name}},
I am building a tool that helps a care team schedule and track follow-up calls after a patient goes home. I would like to run a four-week pilot with one unit, with agreed measures that you choose, and I will sign a business associate agreement before anything touches patient information. I can send a one-page description of the pilot. Who leads follow-up for your unit?
Ravi Menon
[Company name], [street address, city, state, ZIP]
If you would rather not get emails from me, reply "stop" and I will remove you.
The email names one small pilot, says how privacy is handled and asks who owns the problem. It never mentions a specific patient and promises no clinical result.
Count and learn
Write to 30 people who own the problem in one setting and one specialty. Count replies, calls and pilot requests, and note what the reasons for no are. Email rules still apply to a note to a clinician, and is cold email legal sets out the US ones.
The founder builds the product and the evidence. The list and the first emails can be handed off: Rocketship finds the right people by job title, industry and place, emails them from your own Gmail, follows up, answers replies and books the meeting. Plans start at $12 a month on the pricing page, and every monthly plan starts with a 7-day free trial, card required.