Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
Website

Practo, Custom Booking or Third-Party Widget: A Build-vs-Buy Matrix for Clinics

A decision matrix for Indian clinics comparing marketplace booking, an embeddable widget and a custom build on fees, patient data ownership, brand control and conversion tracking.

Practo, Custom Booking or Third-Party Widget: A Build-vs-Buy Matrix for Clinics

A clinic that wants online bookings has three realistic routes. List the doctor on a marketplace platform and take bookings there. Embed a third-party booking widget on the clinic's own website. Or build a booking flow that sits on the clinic's own domain and connects to its own systems. Each route works. They differ on four things that matter more than the feature list: what you pay and how, who holds the patient data, how much of the experience you control, and whether you can see what happened between the first click and the booked appointment.

This post is for doctors, clinic owners and practice managers, and for the marketing or IT person advising them. It builds on our earlier note on setting up a Practo profile and does not repeat it. We do not publish any platform's current fee card here, because prices change and vary by plan. Instead, it gives you the matrix and the questions to ask each vendor, so you can fill in the numbers from the quotation in front of you.

Define the three options precisely

Marketplace booking. Patients find the doctor inside a listing platform, which also handles the booking. The platform brings its own audience and its own brand. The patient relationship begins on the platform's pages.

Embeddable widget. A scheduling tool, sold by a software vendor, that you place on your own site as a button, popup or iframe. The page and brand are yours; the booking form and often the patient record sit with the vendor.

Custom build. A booking flow designed and hosted as part of your own website, connected to your scheduling source (a practice management system, a calendar, or the HIS if you are a hospital). More design freedom, more build and maintenance work.

These routes are not exclusive. Many clinics run a marketplace listing for discovery and a widget or custom flow for patients who arrive through their own site, Google Business Profile or referrals.

The build-vs-buy matrix

Score each row from the real quotation, not from a brochure.

DimensionMarketplace listingEmbedded widgetCustom build
Fee modelOften subscription and or per-booking; confirm which events are billableUsually monthly per doctor or location; check booking capsBuild cost plus hosting and maintenance; no per-booking fee unless you add a payment gateway
Who the patient is, in your recordsHeld first by the platform; you may receive a contact and booking detailHeld by the vendor; export may be limitedHeld by you
Brand controlLow: platform layout and ranking rulesMedium: theme and text, within limitsHigh
Conversion trackingYou see platform reports, not your own funnelDepends on whether the widget sends events to your analyticsFull, if you instrument it
Time to launchDaysDays to weeksWeeks to months
Integration with your schedulingPlatform's own calendar or a supported integrationVaries widely; check two-way syncAs deep as you build
Multi-location or multi-doctorPer-doctor listingsPlan-dependentDesigned for your structure
Exit costLose listing and reviewsRe-create the flow; patient export may be difficultLow if you own code and data
Maintenance burdenPlatformVendorYou or your agency

Two rows deserve more detail.

Row one: data ownership is a legal as well as a commercial question

Under India's Digital Personal Data Protection Act, 2023, the entity that determines the purpose and means of processing personal data is a "Data Fiduciary" and a party that processes on its behalf is a "Data Processor" (see the definitions in the Act). Which party holds which role in a marketplace booking can differ from a widget on your own site, and the answer shapes who must give notice, who handles correction and erasure requests, and who is responsible for security.

You do not need to resolve that in an article. You do need to ask each vendor in writing:

  • Do you act as a processor for the clinic, or do you treat the patient data as your own?
  • Can you export every patient and booking record in a standard format, on request, at any time?
  • On what terms do you contact patients we sent you, or patients we received from you?
  • What happens to our data if we leave?

The DPDP Rules' consent and notice provisions come into force eighteen months after publication of the Rules in November 2025, per the Rules text. Choose tools now that can support a notice and a consent record, rather than finding out in 2027. Have your legal adviser review the vendor contract.

Row two: conversion tracking decides whether you can improve anything

A booking route that cannot tell you where patients dropped off is a black box. For each route, check what you can measure.

  • Marketplace: typically you can see views, bookings and sometimes patient source within the platform's own reports. You will not see how a patient got from your Google Ads click to the platform page, unless the platform allows tagging.
  • Widget in an iframe: the widget runs on another domain. Unless the vendor sends events or you configure cross-domain measurement, your GA4 sessions break at the widget and a booking looks like direct traffic. GA4 cross-domain measurement works by listing the domains and passing the client and session IDs in a _gl URL parameter, as described in Google's cross-domain measurement help. It does not work across an iframe unless the widget cooperates, so ask the vendor what it does.
  • Custom build: you can send named events at each step. A usable set is booking_started, slot_selected, details_submitted, otp_verified and booking_confirmed, each with doctor, location and source parameters. Our conversion tracking page covers how those events map to ad platforms.

A simple test before you sign: ask the vendor to book a test appointment from your campaign link and show you, in your own analytics, where the booking appears. If they cannot, your cost per booking will be a guess.

Want this applied to your practice? Get a free website audit.

Book my free audit

Decision rules by type of clinic

These are starting rules, not guarantees. Change them with your own numbers.

Single doctor, low volume, no website investment. A marketplace listing plus a Google Business Profile booking link is probably enough. Add a widget later if bookings from your own site grow. Make sure your booking link and details are consistent across profiles.

Single-specialty clinic with its own website and marketing spend. An embedded widget is often the right middle path, provided it passes the tracking test and data export questions. If the vendor fails either, move to a custom flow before you scale ad spend.

Multi-doctor or multi-location group. A custom build, or a widget with a deep scheduling integration, because the real cost is manual rescheduling and mismatched rosters. The appointment scheduling page describes what the build involves.

Clinic that already has a practice management system. Start by asking whether it has a booking module or an API. A booking flow that reads from the system you already use avoids a second calendar.

Procedure-led or high-ticket practice. Booking is only the first step. A consultation request with a call back may convert better than a self-serve slot picker, and a lead capture form with a human follow-up may beat a widget. Test, do not assume.

Hypothetical worked example

Consider a three-doctor dermatology clinic in Jaipur with its own website and a modest Google Ads budget. It has a marketplace listing that brings in new patients, and a phone line that reception answers until evening. Its owner wants bookings after hours.

Using the matrix: marketplace booking already exists and stays as a discovery channel. The widget option passes the data export test but fails the tracking test, because the vendor cannot send booking events to the clinic's analytics. The custom flow passes both but costs more up front. The clinic chooses a lightweight custom flow for its own site, wired to the calendar the doctors already use, and keeps the marketplace listing. It sends the five events above to GA4, and after two months it can compare the cost per confirmed appointment from its own site with the cost per booking on the marketplace. The clinic, its numbers and the decision are all invented to show the reasoning; yours will differ, and a different clinic could reasonably pick the widget.

The point of the example is the order of operations: tracking and data ownership were tested before design preferences, and the marketplace was not dropped just because a custom flow existed.

Compare cost without inventing numbers

Do a 12-month total cost of ownership with your own figures.

  1. Subscription or build cost, per year.
  2. Per-booking or per-lead fees, multiplied by your expected bookings. Use your own booking history, not the vendor's illustrative figure.
  3. Integration cost, one-off.
  4. Staff time for rescheduling, reconciling and answering patients, in hours per week.
  5. Cost of lost bookings from a slower or clumsier flow, estimated from your funnel once you can measure it.

Then compute cost per confirmed appointment for each route. If a route cannot give you the inputs, treat that as a risk and price it in.

Checklist before you decide

  • Fee card in writing, including what counts as a billable event.
  • Data export tested with a sample file.
  • Written statement of the vendor's role over patient data, reviewed by your legal adviser.
  • Test booking visible in your own analytics.
  • Two-way sync with your calendar or system confirmed, not just promised.
  • Cancellation and reschedule flow tested from the patient side.
  • Exit plan: how you leave, and what you keep.
  • Clinical and advertising wording on the booking page reviewed by the doctor, in line with NMC rules.

For a wider walkthrough of picking and wiring a system, see our guide to setting up an appointment booking system.

Filed underappointment booking software clinic IndiaPracto vs own booking systemclinic booking widgetbuild vs buy appointment bookingonline appointment booking for doctors

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 13 pages

WhatsApp AI Chatbot for Hospitals (14-Day Deploy)

The 14-day WhatsApp booking-bot implementation playbook.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free website audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to practo custom booking or third party widget a build vs buy.

Explore client work →