Supreet Gupta, Co-founder and Chief Product Officer, Dmand AI

Supreet Gupta

Co-founder and Chief Product Officer, Dmand AI

Supreet Gupta is the co-founder and Chief Product Officer of Dmand AI. He leads the product and the healthcare data behind it, and most of his work comes back to one question: how US healthcare is really organized, from the health system at the top down to the clinic where a physician sees patients, and how teams selling into it can find the right person at the right site. He writes Selling Into Healthcare, a newsletter about how hospitals and health systems buy, and the guides and comparisons on this site.

Writes about
Selling to hospitalsProspecting and outboundMarket data explainedComparisons
Newsletter
Selling Into Healthcare
On this site
17 articles, reviews and data pages

Start with these

Two reviews to read first if a data contract is up for renewal.

  • Comparison

    Definitive Healthcare Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    What Definitive Healthcare does, what it costs, where it stops for outbound teams, and the alternative built for selling into US healthcare.

    21 min read

  • Comparison

    ZoomInfo Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    ZoomInfo pricing: median contract $33,500 a year (Vendr). See its healthcare data gaps and the best ZoomInfo alternative for HCP and hospital data.

    15 min read

Everything Supreet has written

Type

17 articles

Newest first

  • Prospecting and outboundPlaybook

    Healthcare cold email templates for hospital executives, by role

    Cold email templates for the hospital CIO, CNO, CFO, CMIO and VP of supply chain, with what each role cares about, how to write the first line, when to follow up and the rules that apply.

    8 min read

  • Prospecting and outboundGuide

    Hospitals using Epic: how many there are, and how to build a list of hospitals by EHR

    What share of US hospitals run Epic, Oracle Health and MEDITECH, why the numbers differ by source, and how a Health IT team builds its own list by EHR, state and bed size.

    7 min read

  • Prospecting and outboundGuide

    How to find a doctor's email address: a guide for sales and recruiting teams

    The NPI Registry tells you who a doctor is and where they say they practice, but not their email. Here is how to get from an NPI to a verified work email and direct line, and the rules for using them.

    7 min read

  • Selling to hospitalsGuide

    Selling to hospitals: how hospitals buy, and who signs, by purchase type

    Capital equipment, IT software, supplies and staffing each take a different path through a hospital. Here is who evaluates, who approves and who can block each one.

    11 min read

  • Comparison

    Definitive Healthcare Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    What Definitive Healthcare does, what it costs, where it stops for outbound teams, and the alternative built for selling into US healthcare.

    21 min read

  • Comparison

    ZoomInfo Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    ZoomInfo pricing: median contract $33,500 a year (Vendr). See its healthcare data gaps and the best ZoomInfo alternative for HCP and hospital data.

    15 min read

  • Comparison

    Apollo.io Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    Apollo.io pricing starts at $49 per user a month and Vendr's median deal is $19,000 a year. See its healthcare data gaps and the alternative.

    21 min read

  • Comparison

    Definitive Healthcare Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    What Definitive Healthcare does, what it costs, where it stops for outbound teams, and the alternative built for selling into US healthcare.

    21 min read

  • Comparison

    ZoomInfo Review, Pricing and Alternatives for Healthcare Sales Teams (2026)

    ZoomInfo pricing: median contract $33,500 a year (Vendr). See its healthcare data gaps and the best ZoomInfo alternative for HCP and hospital data.

    15 min read

  • Newsletter

    The healthcare sales map was wrong. So we drew a new one.

    Why most databases file healthcare people under the wrong site, what an org forest looks like, and the map we built instead. Issue 1 of Selling Into Healthcare.

    6 min read

Editorial standards

How Supreet researches and writes

The rules every page on this blog follows, so you can check any claim.

  1. Every number has a source and a date

    Counts say what was counted, the universe and the month.

  2. Competitor facts come from public records

    Their own site, SEC filings, Vendr, G2 or TrustRadius. Never from memory.

  3. Our data is labeled as ours

    Figures from the Dmand AI database say so, with the date of the count.

  4. Updated means something changed

    The date moves only when the facts or the advice on the page change.

  5. No invented people

    No made-up quotes, customers or reviewers. Product examples use labeled sample data.

  6. No review scores

    We do not reprint review scores or review text. We link to the source instead.

Newsletter · Free, on SubstackIssue 1 ·

Selling Into Healthcare

In every issue

  1. 01How healthcare buys
  2. 02Data notes
  3. 03Build notes
  4. 04Field notes from real outbound to providers

Latest issue

Selling into US healthcare

Check the accounts you sell to in Dmand AI

Open any US health system, see every site of care under it, and find the people who work at each one.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)