Skip to content
dentalstackstudio

What's next

What we're thinking about, before we build it.

Two areas of Indian dental practice that nobody has solved well — the ones that come up on the third call with a clinic, after we've already talked about appointments and payments. Neither is a product yet, and we don't know which one becomes one first. But they might, with your input.

Two areas

Where the next conversations are.

  1. 01 New patients
    Sketching

    Turning leads into appointments.

    The patient who messaged you on WhatsApp at 9 PM and never heard back.

    What we're seeing

    Three out of four new-patient leads die between the front desk's phone and the patient's reply. Most clinic websites push leads into a contact form that nobody opens, or a WhatsApp inbox that nobody triages. The gap between interest and a booked chair is where new-patient revenue lives — and where it leaks.

    What we're considering

    A small layer that watches the WhatsApp inbox tied to a Clinic Websites site, flags new-patient threads, and gives the front desk a one-tap way to send a slot. Not an SMS blast. Not a CRM. Just the move that turns a message into a booking.

    Where we are

    Sketching. Looking for two or three clinics with high-traffic locations and an inbox that's overflowing — if that's you, we'd love to talk.

    Have a strong opinion on this one?

    Tell us about it
  2. 02 Chains
    Prototyping

    Multi-clinic operations.

    When you have three clinics under one brand and three different versions of the truth.

    What we're seeing

    The third clinic is where the seams show. Chair occupancy lives in a spreadsheet at clinic A, collections in a different spreadsheet at clinic B, and recall in the principal's head at clinic C. The owner spends Sundays merging numbers that shouldn't have to be merged.

    What we're considering

    A layer above DentalOS that gives chain owners one dashboard across every clinic — chair occupancy, collections, recall, performance — without exporting and merging CSVs. DentalOS already supports multi-clinic at the database level; this is the front-end that makes it useful.

    Where we are

    Prototyping. The data model exists. The dashboard doesn't, yet — but it's the one thing on this page that's closest to being a real screen.

    Have a strong opinion on this one?

    Tell us about it

The honest part

Why we're not selling these yet.

We don't ship to a calendar. Each of these areas is real — we hear them every week — but until we've talked to enough clinics and prototyped something that actually saves a Tuesday morning, we're not going to put a price tag on it. No pre-orders, no waitlist tier, no "Founders' rate".

The fastest way for any of these to become real is for you to tell us what you're seeing. What's hardest. What would change your week if we built it. The areas on this page are loose enough that the next clinic we talk to could reshape any of them — or point us at something we haven't thought of.

"I'd rather build something we'd be proud to charge for than something we ship just because the roadmap said so. The clinics we work with deserve better than that."
Mukesh Murugan, Founder, dentalstackstudio

Tell us what you'd build

What would you build, if you were us?

We read every email. If your clinic has a problem nobody's solved well — even if it's not on this page — we want to hear about it. A short paragraph is plenty.

Email Mukesh

mukesh@dentalstackstudio.com · usually replies within a day

dentalstackstudio · Trivandrum, India · 8°N