About

Built for how nutrition is actually practised, wherever that is.

PlanRhythm is practice management software for dietitians and nutritionists across the United States, Canada, Gulf, United Kingdom and Europe, Australia and New Zealand. This is why it exists, the product rules we set before writing code, and what is still unfinished.

Why this exists

Look for software to run a nutrition practice and you find two kinds. The first was built around one market's clinical and billing model — almost always a clinic in the United States. It expects an insurance code you do not use, weighs everything in grams and ounces, has never heard of a katori, and offers your halal, Jain or kosher client a diet list she is not on. The second is a general-purpose CRM that treats a diet plan as a task and a consultation as a calendar event.

So everyone outside that one market ends up where the tools do work — the same three, in Dubai, Chennai, Manchester and Melbourne. A spreadsheet of client names and phone numbers. Word files and PDFs for plans. WhatsApp for the rest. That stack is not a mistake — it is fast, free and already on the phone. It just stops holding somewhere around thirty clients, when you can no longer remember which version of the plan you sent to whom, and yesterday's lunch photo is four forwards up the scroll.

We are building the missing piece: one place for the plans, the check-ins, the notes and the money — in the measures your clients already use, with the conversation left on WhatsApp where they already are.

What we believe

Three things we decided before writing any code.

These are not values on a wall. Each one closed off features we could otherwise have shipped.

1. The record should not shame anyone

Most tracking apps grade the person using them. An adherence percentage, a streak counter, a calendar of red days. It looks like rigour. What it produces is a client who has a bad week, watches the number fall, and stops logging so it stops falling. Then she stops opening the app. Then she stops replying to you. The data goes dark at exactly the point you needed it most.

So PlanRhythm has no score, no grade, no streak and no red day, anywhere, for anyone. A daily check-in has five honest outcomes: followed the plan, adapted it, ate something different, couldn't do it, skipped. And a day with nothing on it is simply not recorded — never counted as failure.

This is the more rigorous choice, not the softer one. Adapted it — had bread instead of rice because she was eating at her mother's is clinical information you can work with. 62% is not. Retention follows the same logic: a client who is not being marked keeps telling you the truth, and a client who keeps telling you the truth stays in the programme long enough for it to work.

2. Software drafts, the dietitian decides

Nothing clinical happens in PlanRhythm without you. The software lays out a week in a grid, carries a template forward, keeps every version of a plan, and puts a flagged intake answer in a review queue. Then it stops and waits. You publish the plan. You decide what the flag means. Your name is on the advice, so the last step is always yours.

That rules out things we could easily have built. No automatic calorie target pushed to a client. No message sent on your behalf. No warning fired at a client because an answer looked unusual — the questionnaire raises it to you, in your queue, and you choose what to do with it.

The plain test we apply: if we cannot explain to you why the software put something in front of you, it does not ship.

3. Your data is yours

PlanRhythm runs on Microsoft Azure. At onboarding your practice picks the region its data lives in — Central India, UAE North, West Europe, East US, Canada Central or Australia East — and it stays there. It is encrypted in transit and at rest, and it does not move between regions. When a client, a hospital or a regulator asks where the records sit, the answer is one region name.

Consent is recorded per client, written around GDPR and UK GDPR, DPDP, PDPL, PIPEDA, the Australian Privacy Principles and US state privacy law, and there is an audit trail of who accessed what. Staff accounts see only the clients assigned to them — not because your team is untrustworthy, but because that is what handling health data properly looks like.

Yours also means yours to take back. A self-serve export button is not built yet — it is in the list further down this page, and we are not going to describe it as though you can press it today. Until it exists, ask us and your client list, plans, notes and check-ins come out in a readable format, including on the day you decide to leave. Making the exit difficult is a way to keep customers who want to go, and we would rather keep the ones who want to stay.

Who it is for

Solo up to about twenty practitioners.

The solo practitioner

You are the dietitian, the front desk and the accounts department. The win is the hour a week you get back from rebuilding plans and hunting for what you sent in March.

The small practice

A few of you, sharing clients and covering for each other. Add every practitioner and assistant who needs access — you are billed per client, never per seat. Owner and staff roles, staff seeing only their own clients, and one record of every plan and note instead of three laptops.

The clinic

A nutrition department inside a larger practice, up to roughly twenty practitioners. Past that we are not the right tool yet, and we would tell you so on the call.

Where we are

What we are building next.

PlanRhythm is early. We have no customer logos, testimonials or awards to show you, and we are not going to invent any on a healthcare site. Here is what is genuinely not finished, so you can judge whether it matters to your practice.

Being built

WhatsApp plan delivery

Today a published plan appears in your client's app and she gets a link. Pushing the day into WhatsApp itself is not built yet. If your clients will not install anything, wait for this one.

Being built

Appointment booking

You can write consultation notes against a client, with a lock and a revision trail. A booking page with your slots and automatic reminders does not exist yet. For now you schedule the way you do today.

Being built

Printable kitchen sheet

A one-page version of the week to print for the fridge or hand to whoever cooks. The person who cooks is often not the person in the consultation, which is why we want it. It is on the list, not in the product.

Planned

Arabic and right-to-left

The app ships in English, Hindi and Tamil today. Arabic with a right-to-left layout is the next language we take on, and European languages after that. If you need to work in Arabic now, we are not ready for you.

Planned

Export you run yourself

Ask us and your client list, plans, notes and check-ins come out in a readable format. A button you press yourself, at midnight, without asking anyone, is not built. If pulling your own data out unassisted matters to you, wait for this one.

When one of these ships we will say so here. Until then, assume anything not on the product page is not built.

Tell us what your practice actually does

We are building this in the open with working dietitians, and the useful conversations have all started with someone describing their week rather than us describing our software. If you have a view on any of the above — including where you think we are wrong — we would like to hear it.

Or write to [email protected]. A person reads it.

WhatsApp