Pricing
₹99 a bed, or ₹1,499 a clinician. Whichever number you already know.
Not per encounter, not per note, not per agent invocation, not per document exchanged. A hospital pays on its bed count and a practice pays on its clinicians, because those are the two numbers a buyer can state without going to look them up — and the only ones they can predict at the start of a year.
Per bed
₹99per bed / month
Counted on sanctioned beds, not on people. Put as many clinicians, nurses, pharmacists and front-office staff in front of the record as the work needs — the price does not move, and nobody has a reason to share a login.
- Ambulatory and inpatient on one clinical record, with orders, results and discharge
- The full pharmacy subsystem: formulary, inventory, dispensing, administration and reconciliation
- Deterministic safety engines — interactions, allergies, dose ranges, controlled-substance rules
- The whole agent roster, every tier, with the sign-off machine underneath it
- Revenue cycle: charge capture, invoicing, coverage, claims, prior authorisation and denials
- Exchange, the patient portal, consent-aware messaging and video visits
- Unlimited staff accounts, role-scoped, with an immutable audit log over all of them
- Jurisdiction adapters, data residency and an export of your own record
Per clinician
₹1,499per clinician / month
For a practice with no beds to count. The same software, the same agents and the same sign-off machine — priced on the only number a clinic has, and billed on the people who actually consult rather than on everyone who logs in.
- The full ambulatory day: scheduling, encounter, chart, scribe and coding
- Prescribing with the same deterministic interaction, allergy and dose checks
- Every clinical agent, drafting into your signature rather than around it
- Invoicing, payment references, and claims if you bill an insurer
- The patient portal, consent-aware messaging and video visits
- Reception and support staff accounts are not billed — only clinicians are
- The inpatient modules are present and simply unused, at no extra cost
Above two hundred beds
Pricing on request
Past two hundred beds the questions stop being about the software. Procurement, a security review, a data agreement, single sign-on against your directory, which region the record sits in and how the migration from whatever you run now actually happens are all decided in a conversation.
- Everything in the per-bed plan, without a ceiling and across sites
- Single sign-on and directory-based provisioning
- Multi-facility tenancy, including facilities in different jurisdictions
- A written data-flow note for your own security and privacy review
- Deployment region chosen rather than defaulted, for storage and for inference
- A migration plan for the record you already hold, with an export you can verify
- A named person who has worked on the software
- Annual invoicing and a purchase-order flow
The arithmetic
A hundred-bed hospital pays ₹9,900 a month
That is under ₹1.2 lakh a year for software spanning the clinic, the ward, the pharmacy and the billing office — less than one junior administrative salary, and small enough that it does not need a board paper to approve. The comparison that actually decides it is not against another vendor, though. It is against the hours your clinicians currently spend typing the same encounter into three places, and against the claims that come back because the charge could not be traced to what was done.
Priced on beds, not on people
Add clinicians, nurses, pharmacists, coders and front-office staff without the price moving. A pricing model that makes a hospital ration logins is a pricing model that produces shared accounts, and a shared account destroys the audit trail this product is built around.
Every module on every plan
No agent, no safety engine and no exchange path is behind a higher tier. Gating the interaction checker or the sign-off machine by price would be indefensible in a product whose entire argument is that unverified output is the thing it prevents.
The agents are not metered
Invocations, drafts, notes, summaries and documents are unlimited. The cost of running the models is ours to manage — a per-draft charge would mean somebody deciding which encounters are worth documenting properly, and those decisions always go the wrong way on the busiest day.
Against the alternative
The thing being replaced is usually not a product
Most Indian hospitals are not choosing between two EMRs. They are running a billing package that was never a clinical system, a pharmacy module that does not know what the doctor prescribed, paper for the parts that matter, and a person whose actual job is retyping between them. That is the incumbent, and it does not appear on any budget line — which is exactly why it survives.
| Legosphere Health — hospital | ₹99 / bed / month | GST inclusive, billed in rupees |
|---|---|---|
| Legosphere Health — practice | ₹1,499 / clinician / month | For a clinic with no beds to count |
| A billing package plus paper | Cheap, on paper | The real incumbent — its cost is clinician hours, and nobody counts them |
| An international EMR | Quote only | Priced for a market where a clinician costs several times what one costs here |
The third row is the one that matters. A price low enough that nobody has to build a business case for it puts a real clinical record into hospitals that a per-user enterprise quote would have kept it out of — and an undocumented encounter is what we would rather prevent at scale than charge a premium to prevent occasionally.
- Prices are in rupees and inclusive of GST. An invoice with your GSTIN is issued on every payment.
- Annual billing is charged at ten months for twelve months of service, on the same per-bed or per-clinician rate.
- Beds are the beds you are sanctioned for. Staff accounts are unlimited on the per-bed plan and are never counted.
- On the per-clinician plan, a clinician is somebody who consults. Reception, billing and support staff are not billed.
- There is no free tier and no self-serve trial: this software holds patient records, and an unpaid account holding one is a liability rather than a funnel.
- Usage is not metered. Encounters, notes, agent invocations, documents and exchange are unlimited on every plan.
Questions
What people ask about the price
Mostly two: which unit applies to us, and what else will you charge for. The second answer is nothing.
Because per-user pricing in a hospital produces shared logins, and a shared login is a clinical safety problem before it is a billing one. This product attributes every signature to a named clinician and records who opened which chart — both of which are worthless if four people are behind one account. Charging on beds removes the reason to do it. It is also the number a hospital already budgets and reports against, so nobody has to go and count anything.
₹1,499 per clinician per month. A clinician is somebody who consults — reception, billing and support staff are not billed and never have been. The inpatient half of the product is still there and simply unused; you are not charged extra for it and you are not charged less for ignoring it.
If you admit patients to beds, the per-bed plan is almost always cheaper and it is the one we would put you on. A ten-bed nursing home is ₹990 a month, against ₹1,499 for a single consulting doctor on the other plan. If it is genuinely ambiguous, tell us the shape of the place and we will say which one costs you less — including when that is the one that earns us less.
No. Every agent in the roster is on every plan, and invocations are unlimited. A per-draft charge would mean someone deciding which encounters deserve proper documentation, and that decision always goes the wrong way on the day the department is busiest — which is the day it matters most.
Twelve months of service charged as ten. That is the same shape the rest of the company uses and there is no separate negotiation for it.
The card form stops and a conversation starts. At that size the deciding questions are procurement, a security review, single sign-on, which region the record sits in and how migration from your current system actually works — none of which anyone should be answering with a checkout page.
Yes. Add beds when you commission a ward and they are billed from the next cycle; drop them when you decommission one. A hospital’s capacity moves and a contract that pretends otherwise just gets renegotiated angrily.
Not for you. A rate agreed on a subscription is the rate that subscription renews at; a change to the list price applies to new subscriptions. Being the affordable option only works if signing early is rewarded rather than punished.
You take it. The record is stored in the exchange standard rather than translated into it, so an export is the actual clinical data rather than a report shaped like one — and we would rather you were able to leave than locked in, because a vendor holding a hospital’s record hostage is the reason this category is distrusted.
Get in touch
Talk to the people building it
No chatbot and no ticket queue. Tell us what your hospital or practice actually looks like — how many beds, which departments, what the doctors are doing twice, what your billing team keeps chasing — and someone who works on the software will reply.
info@legosphere.com