A hospital does not buy from a person. It buys from a process. One department head can want your product badly and still be unable to sign anything, and the people who can stop the deal are in departments you will not meet until month three. If you understand that process before you start, the long timeline stops being a surprise and becomes a plan.
This guide is for a small company selling a non-clinical product or service to a hospital or health system: scheduling, patient communications, facilities, workflow software, staffing support. Clinical products and devices face an extra layer of review that we only touch on. Compliance rules vary and change, and this is general information, not legal advice.
A hospital is a stack of committees
There is no single buyer. There is a department that feels a problem, and then a series of people who each have a veto. The department head cannot spend outside her budget or her authority. Procurement, IT security, compliance and legal each check something different, and each is trained to find reasons to say no, because a bad vendor is their problem for years. A yes from one does not move the deal; it only gets you to the next one.
Clinical and non-clinical buyers
Anything that touches patient care, such as a supply, a device or a clinical software tool, usually goes to a value analysis committee, a group of clinicians, supply chain and finance staff who ask whether the product is better or cheaper than what the hospital already uses. Non-clinical purchases, such as facilities services, patient reminders, scheduling or back-office tools, tend to skip that committee and are decided by the department director with procurement. Know which one you are. A non-clinical product with a small price is the easiest first sale into a hospital.
The chain, in the order each one says yes or no
- The department sponsor, such as the director of patient access, facilities or outpatient operations. She has the problem and the budget line. Without her, nothing starts.
- Procurement or supply chain. They check whether the category is already covered by a contract, whether the price is competitive and whether the purchase needs a formal bid.
- IT security. They send a security questionnaire and want to know where data goes, who can see it, and how you protect it.
- Compliance and privacy. They check vendor credentialing, conflict-of-interest rules and whether you will handle protected health information (PHI). If you will, you need a business associate agreement.
- Legal and finance. Contract terms, insurance, liability limits, payment terms.
Each step asks for a document. Have these ready before you start: a W-9, a certificate of insurance, a completed security questionnaire (even if you fill it in a generic version first), references from other organizations, a one-page product description, a price quote, and a statement that your company and staff are not on federal exclusion lists. Many hospitals also ask vendors to register with a vendor credentialing service and keep immunizations or background checks current for any staff who visit on site.
Group purchasing organizations
Most hospitals buy a large share of their supplies through group purchasing organizations, which negotiate contracts for members. For categories a GPO covers, buying off-contract is harder for the hospital to justify, and your product may need to be on the contract before procurement will move. For services and software that a GPO does not cover, procurement has more room to buy directly. Ask your sponsor early: "Is this category on a contract?" It saves months.
Why timelines run in months
Each stage runs on a committee's calendar, not yours. A value analysis committee may meet monthly. Security reviews queue. A legal review of a contract may sit for weeks. A rough expectation is several months from a first meeting to a signed contract for something small, and a year or longer for anything that touches clinical workflow or patient data. The cost of this is cash flow: price your own runway accordingly, and check how long sales cycles run before you count on a hospital in your first year.
A pilot a department sponsor can approve
The way through is a small pilot that stays under the sponsor's own approval limit and avoids PHI where you can. Take an illustrative example. A company sells appointment reminder texts to outpatient clinics. It proposes a 90-day pilot at one clinic with 1,200 appointments a month, measuring the no-show rate before and after. The sponsor is the clinic's practice manager. The pilot is small enough to fit within her budget, so it does not go to a committee. Reminder texts require prior consent from patients, so the pilot uses only patients who've already agreed to text messages. If the no-show rate drops from, say, 14 percent to 11 percent, that is 36 fewer missed visits a month, a number a finance director understands.
The pilot also builds the reference list that the later security and legal reviews ask for. See how a pilot becomes a paid contract for the structure.
What to do this month
Pick one department with a visible problem. Find the sponsor by name: a job post, a conference talk, a hospital newsletter, a department web page. How to find decision makers at a company and how to get meetings with decision makers give the methods. Write to her about the problem, not the product, and offer the pilot. When you hear "we already have a vendor," do not argue; see how to handle that objection.
Hospital outreach takes patience and a long list of named people at many departments and systems. Rocketship can find those department leaders by name, email them from your own Gmail, and keep following up across the months it takes; see how the AI workers run it. A retail buyer is a much faster, single-decision-maker version of the same sale, and how to sell to retailers shows the contrast.
Rocketship finds the buyers, emails them from your own Gmail, follows up, and books the meeting on its own. Plans that get you customers start at $24.99 a month (Launch), and both Launch and Frontier start with a 7-day free trial, card required.
