Practice software for solo therapists

Priced for one practice, not one seat

Rs 1,250 a month for the whole practice, with 15% off for annual prepay. Not per seat, because a solo practice has one person in it and paying per seat for a seat count of one is a pricing model borrowed from a different kind of buyer.

There is no commission on your session fees. Client payments settle into your own linked payment account rather than passing through us, which is also why we never hold your clients’ money.

What you get, without an org chart

• Scheduling and a calendar that understands leave, session length, and how far ahead people may book.
• Client records with clinical notes and risk assessments, encrypted at the field level.
• Invoicing in rupees, with receipts and documents in your own practice’s style rather than a generic template.
• Payments through your own gateway, or the manual flow if you take UPI and bank transfers directly, including the client-confirms-then-you-confirm path.
• A client portal, so people can book, reschedule and see their own sessions without messaging you.
• Teletherapy links generated with the session.

A public booking page you control

A page a prospective client can reach without an account, at your own link, carrying your practice’s colour. You decide whether it offers direct booking, a waitlist, both, or nothing at all, and it shows real availability from your actual calendar.

The controls on it are deliberately conservative, and one of them is worth knowing about before you turn it on. You are not publicly bookable until you have actively confirmed real working hours: default hours will not silently expose you. You can narrow the window strangers see to something tighter than your working day. And if you take on clients in acute crisis, that is an explicit setting that actually gates the booking rather than only showing a badge.

You are the Data Fiduciary, so the tools are yours

As a solo practice there is nobody to share that with: no compliance officer, no legal team, no colleague whose job it is. Most of it is about your own conduct rather than your software, the notice you give, the consent you record, the retention period you decide on and can justify, what you disclose in supervision, how you handle your devices and email. None of that is something software can do for you. What it can do is make each of those actions possible, recorded, and provable afterwards, which is the difference between having made a defensible decision and being able to show that you did.

Consent, recorded rather than assumed

Consent is captured as a record with its own version and timestamp, not as a checkbox whose state is the only trace it ever happened. The version of the notice a client agreed to is kept alongside their agreement, because the burden of proving that notice was given and consent obtained sits with you, and proof has to outlive the moment. Separate purposes are recorded separately, so a client agreeing to treatment is not thereby treated as having agreed to anything else.

Data-rights and erasure requests as a workflow

A request from a client is a tracked item with a state, not an email you have to remember to action. You can assemble the record that answers it, review that document before deciding what to release, and record the decision and your reasoning. Erasure is executed rather than approximated: real deletion of stored objects, with a tombstone so the fact of the erasure survives the data itself.

What must be retained and why is your decision, because it depends on clinical, professional and limitation context the software cannot see. The reasoning behind a schedule you can defend is set out in how long to keep client records in India.

Retention, encryption and the paperwork

• Retention periods you set, with floors enforced in code so a period cannot be set to something indefensible by accident.
• Legal holds that suspend the clock on a specific record while a complaint or claim is live.
• Opt-in automatic deletion, off by default, with a warning before the deadline rather than a silent disappearance.
• Field-level encryption of clinical data rather than reliance on disk encryption alone, with key rotation, and a log of every access and change.
• Records of processing and an incident register, generated from what the system actually holds rather than written from memory in a hurry.

A person under eighteen is a child under the Act, which is older than many people expect, and processing their data carries additional requirements. There is an exemption for health services provided to a child, but its edges are genuinely unclear for practitioners without a statutory registration. Take your own position on that with a lawyer; what the software does is make the consent and guardian records explicit rather than implicit.

What we will not tell you: that using this makes you compliant, that any particular retention period is legally required for a therapist in India (no Indian law sets one), or that we hold a security certification we have not obtained. Where the law is unsettled, our guides say so rather than manufacturing certainty.

Supervision, on both sides

Solo does not mean alone, and supervision is usually run outside whatever software a practice uses: a calendar invite, a spreadsheet of hours, and an invoice written by hand at the end of the month. Here it has its own records, its own money, and its own visibility rules.

The two sides are treated differently, deliberately, because they are different things:

• Supervision you receiveis an expense. You see what you owe and what you have paid, and not your supervisor’s wider financial picture.
• Supervision you deliver is income. You see the sessions, the fees, and what has settled, because it is your own revenue, and it is billed and settled like any other service rather than folded into session revenue where it would distort your reporting.

You can be on both sides at once, supervising two people while being supervised by a third, and each relationship resolves its own visibility independently. A supervisee can be another practitioner on the platform or an external contact who is not. Sessions are recorded as they happen, with dates, attendance for group supervision and fee status, so an hours record is a by-product of doing the work rather than something you reconstruct from memory when a training programme asks for it. Ending an engagement closes it rather than deleting it, so the settled fees and the audit trail survive.

One thing worth knowing before you agree a fee, because it surprises people: supervision is a professional service supplied to another professional, which puts it in a different tax position from therapy delivered to a client, and a supervisee whose own income is exempt generally cannot recover the tax charged on it. We set that out in clinical supervision in India.

The money questions you will actually hit

Whether GST applies to your fees, how long you must keep records, and what happens if you take on an associate are the three that come up most, and the honest answers are less obvious than most sources suggest. We researched them properly rather than repeating what circulates:

• GST on therapy and counselling in India
• How long to keep client records in India
• Going from a solo practice to a group

If you grow

Taking on a second therapist changes the shape of the practice rather than just its size, and the software follows: a roster, per-therapist payouts on commission or fixed salary with effective-dated rates and TDS, role-scoped record access so one therapist does not open another’s caseload, and supervision you deliver as income. All of it is described on software for multi-therapist practices.