Production-ready clinic platform that connects your public website to the people who answer enquiries.
Website content, patient enquiries, doctors, and records in one admin. Ready to customize in 3–4 weeks.
- Time to customize
- 3–4 weeks
- Modules
- 7 modules
- Built with
- Next.js · NestJS · PostgreSQL · Prisma
Overview
What this foundation
solves.
Most clinic software treats the website and the clinic as two different problems. The website is built by an agency and frozen the day it launches. The enquiry form emails a shared inbox. Nobody owns a request, two people call the same patient, and changing the services list means raising a ticket with whoever built the site.
This foundation makes the website part of the system. Homepage copy, the services catalog, doctor profiles, testimonials, and the statistics strip are edited by your admin from the same panel that manages patient enquiries. An enquiry arrives with the service the patient asked about, gets assigned to a doctor, and moves through New, Viewed, and Completed - so at any moment you can see what came in today and who has not been called back.
It fits multi-location clinics, specialty practices, and telehealth providers: organizations where more than one person handles enquiries, and where the marketing site changes more than once a year.
Built for
- Multi-location clinics
- Specialty practices
- Telehealth providers
Industries
Time to customize
3–4 weeks
From kickoff to production, including your customization and data migration.
Key Capabilities
What it does
out of the box.
Every capability below is running today. Customization changes how they behave for you - it does not build them.
Website Content Management
Hero, about page, services, testimonials, footer, and the statistics strip edited from the admin. Counts refresh from the database - no developer required.
Patient Enquiry Requests
Every website enquiry lands as a record with the patient, mobile number, service requested, and message. Nothing gets lost in a shared inbox.
Query Management & Filters
Filter enquiries by status, assigned doctor, service category, patient gender, age bracket, and date range. Bulk select and act on what matters today.
Doctor Management
Doctor profiles, specializations, and availability. Profiles publish straight to the public website; assignment routes enquiries to the right clinician.
Patient Records
Patient details, contact history, and the enquiries and consultations attached to each person over time.
Service Catalog
Services with descriptions, perks, and booking numbers. One edit updates the public site and the categories used to classify enquiries.
Doctor & Admin Portals
Separate logins with separate views. Admins see everything; doctors see the patients and enquiries assigned to them.
Dashboard
Enquiry volume, status breakdown, and doctor workload for the current period on one screen.
Screenshots
Real screens,
running today.
Captures from the working system, not mockups. Click any screen to enlarge it.
Modules
Everything included
on day one.
Modules are independent. Remove what you do not need and the timeline gets shorter.
Technical Foundation
The stack
underneath.
Boring, proven, and fully yours. You get the complete source code at handover.
Frontend
Next.js
Public site and admin panel
Backend
NestJS
Modular REST services
Database
PostgreSQL
Relational, transactional
ORM
Prisma
Typed schema and migrations
Deployment
Docker
Reproducible builds
Hosting
AWS or self-hosted
Cloud or on-premise
Built-In Features
The engineering
already done.
The work a from-scratch build spends its first two months on. Here it is finished.
Customization
A foundation,
not a product.
Every deployment is customized. Nobody receives the same system twice.
Appointment booking
Slot-based booking with doctor availability, confirmations, and reminders on top of the enquiry flow.
WhatsApp & SMS
Automatic acknowledgements to patients and new-enquiry alerts to the assigned doctor.
Payment gateway
Consultation fees and package payments collected online through Razorpay, Stripe, or a local gateway.
Lab & pharmacy modules
Test orders, report uploads, and prescription records connected to the patient file.
Existing EMR integration
Push and pull patient records from the clinical system you already run.
Multi-branch routing
Enquiries routed by branch and specialization, with per-branch reporting for management.
This is what clients ask for most often - it is not a menu. If the change you need is not listed, it is still in scope. We fix the specification and the price before development starts.
Delivery Process
From kickoff
to production.
Foundation setup
Deployment, branding, your services and doctor profiles loaded, admin and doctor accounts created.
Business customization
Website content mapped to your copy, enquiry workflow and assignment rules configured, integrations built.
Testing
Your front desk runs real enquiries end to end. Content editing tested by the people who will do it daily.
Deployment
DNS cutover, production launch, staff training, and 30 days of live operations run together.
Questions
Clinic Management,
answered.
Yes - that is the point of the content module. Homepage copy, services, doctor profiles, testimonials, and the statistics strip are all edited from the admin panel by your staff. No deployment, no developer.
Yes. Branches share one deployment with separate doctor lists, enquiry queues, and reporting. Staff see their own branch; management sees everything.
Patient records sit in your own PostgreSQL database with role-based access, so doctors only see the patients assigned to them, and you can host it on your own infrastructure. If you have a specific regulatory requirement, raise it during discovery and we scope those controls into the build.
Yes, if it exposes an API or a documented export. The common pattern is keeping clinical records in the existing EMR while this system owns the website, enquiries, and front-desk workflow.
Yes. Booking is a customization on top of the enquiry and doctor-availability model that already exists. It can go into the initial build or be added after launch.
Yes. If you only need the website plus enquiries, patient records and doctor portals are switched off. A smaller scope means a shorter timeline.
Next step
Ready to customize this foundation?
Tell us how your team works today. We will show you the Clinic Management build running, map it against your workflow, and give you a fixed scope and timeline before any development starts.
Other foundations