We set it up with you
Not a portal, and not a checklist you work through alone. You go through your first patients with the people who built it.
Your first Monday · Getting started
The whole setup is a 6-character code.
You generate a code, your patient enters it once, and they appear on your dashboard. That is the entire implementation.
Your patient grants the accessTheir first week starts the same day
Pairing
Start to finish, in one sitting.
Each step in full, from generating the code to the first meals arriving on your dashboard.
- You give the patient a 6-character code.Generate it from Groups & codes in your dashboard. Share it with your patient however you like.
- They enter it once, in the app.The app explains what you will see and asks for consent.
- They appear on your dashboard.Meals, weight, and weekly reviews land on their patient page as they log, plus a Monday summary email.
Then what
That is the end of your setup. There is no step four. The patient page starts filling in from their first log and keeps filling in without anything further from you.
Consent is theirs, and so is ending it.
What your patient agrees to at pairing, and what stays out of your view whatever happens afterwards, is set out in full on the security page.
How access actually worksWhat it takes
What you need, and what you'll never be asked for.
Adopting a new tool usually means configuration, training and a rollout plan. Pairing a patient needs none of it.
What you need
- A browser. The dashboard runs in it.
- A code: one per patient, or one for a whole group.
- A patient willing to use the app on their own phone.
What you'll never be asked for
- A configuration pass, a template, or a settings decision before you begin.
- Your practice's IT, at any point.
- A migration out of whatever you keep your notes in now.
- A training session for your staff.
- A rollout plan, a pilot structure, or a named implementation contact.
Pairing is a code and a tap. Everything after it happens on its own.
If you get stuck
Where to write when something isn't working.
There is no phone line and no account manager. You write, and someone who works on Lemonmint reads it.
support@mylemonmint.com
A code that will not take, a patient who paired but is not showing, access for another clinician in your practice, or a group for a cohort you are running. Usually answered within one business day.
Working together
You are set up by the people who built it.
There is no implementation team between you and the product. Setup, questions and the roadmap all run through the people who build Lemonmint.
One inbox, no ticket numbers
You write to someone who already knows your practice, rather than to a queue that hands you a reference and a tier.
Your cases shape what gets built
The roadmap is still open. What you tell us about your first month is what we are working on by your third.
What switching feels like
Week one, month one, year one.
Nothing needs bedding in, so the first year is measured in what accumulates rather than in what improves.
It is already running
Your patient enters a 6-character code and nothing else is configured. From their first logged meal, Nora is answering. By your next session the days in between are recorded rather than recalled.
Four weeks, already written
Four Monday reviews exist, and the patient page carries thirty days of meals, weight and nutrition. The session stops opening with what happened and opens with something you can both see.
Fifty-two weeks on one page
A patient who paired a year ago has every week of that year written down, in order, on a single page. None of it was reconstructed afterwards. Each week was written the Monday it ended.
What accumulates is the record. What it means for the patient in front of you stays your call.
Partner with us
Give your patients a team between visits.
Tell us about your practice in one short form.
Set up by the team that builds Lemonmint. Replies within two business days.