The ones that actually get asked.
Answered the way we would answer them on a call, including where the answer is “we don’t know yet” or “not yet, and here is why we chose that.”
The product
Does this replace my staff?
No, and a practice that needs headcount removed is not our customer. It does not remove work from anyone’s day; it removes guesswork from one decision. The four weeks you currently reconstruct by asking about (doses, tolerability, protein, weight) are on the page before the visit instead of being assembled inside it.
What does a patient actually do?
They enter the one-time code you hand them and choose what your clinic may see. From then on the plan you recorded sits inside the Jeni app they already use: the medication, the day it falls on, and your instruction underneath it. Day to day they mark the dose when they take it, log meals from a photograph rather than a form, and say how the meals sat: taps, not paragraphs. Nothing is asked of them that they were not already doing in the app.
What lands on my desk?
One short list, ranked by what needs a read: a correction the patient filed against the plan on file, a follow-up past its date, a pattern in the record, each with how long it has waited. Everyone quiet is one collapsed line, which is most of a panel. Open a name and you get the interval history: the plan on file, what happened, what changed, what is still open, with doses, symptoms and weight on one axis. It is a page you read before a visit, not a feed and not something that pages you.
Clinical
Who is liable if something is missed?
Clinical responsibility stays with the treating clinician, where it already sits. Nobody at Jeni answers a clinical question; every clinical decision routes to your clinician against a protocol your clinician signed. We provide administrative and communication support under your direction and no clinical services. That is a product constraint, not a policy we could change.
Is it a medical device?
No. It records the plan your clinician authored and organizes what the patient entered. It does not diagnose, does not recommend a dose, does not make a clinical determination, and states the timing of a symptom without ever stating its cause. The site carries a development-stage notice for the same reason: a limitation is cheaper to read here than to discover later.
Will this improve my retention?
We do not know yet, and anyone who tells you they do is ahead of the evidence. No randomized trial shows that between-visit support raises long-term GLP-1 persistence. What is documented is that about one in seven patients who stop cite side effects they could not tolerate, and that those discontinuations happen early, which is the kind of thing a record of the interval is built to surface. The first thing we would measure with a clinic is day-ninety retention against that clinic’s own prior cohort. We have not measured it anywhere, because no clinic is running on Jeni.
What if my clinician disagrees with the plan on file?
They amend it, and the change is recorded with the date it took effect and nothing is quietly edited afterwards. This question is answerable at all because there are only two things a patient can receive from you through Jeni: the medication plan and the protocol, both versioned and both carrying the name of whoever recorded them. It is always possible to say which version a given patient was running. There is no message that could have gone out that you did not write, because there is no channel that could have sent one.
Operations
Does it work with our EHR?
No, and not soon. Enrollment is a code you hand a patient, so nothing has to be migrated or integrated to begin. We are deliberate about this: bi-directional integration with every record system is the fastest way for a young company to become an integrations consultancy. What we do want to know is which fields you would actually want written back, and to whom. We have no answer to that yet. If integration is a hard requirement for you today, we are not ready for you.
How long does it take to go live?
For the first clinics, longer than it should. We operate the loop by hand before automating any part of it, so that what gets built is ranked by what actually took the time. Hours to take a clinic live is the number we report internally beside revenue, and it has to fall below four by the twentieth customer or this is a services business wearing software’s clothes.
What if my patients don't engage?
It is the right question and it is the one that decides whether this works. Enrollment conversion is the first thing we measure in a pilot, before anything about retention. If invited patients do not activate, the problem is ours and no amount of clinical logic downstream fixes it.
Is this texting my patients? What about consent?
No. There is no messaging of any kind, and no channel from your clinic to a patient. The only thing that crosses is the plan you recorded, and the patient reads it inside their own app when they open it. Consent runs the other way: the patient enters your code, grants access from a stated date forward, sees an audit row every time you read their record, and can end the connection from their phone without asking anyone. We will not tell you your own obligations; your counsel confirms the consent language, and we supply the enrollment record and the access log for them to read.
Commercial
What does it cost?
We are not publishing a price while the product is being shaped with its first clinics, because a number set before the work is understood is a number one of us would have to walk back. We will talk terms directly, and we do not run free pilots: they select for clinics with nothing at stake and answer the only question a pilot exists to answer with a shrug.
Who owns the protocol and the data?
You own both. The protocol your clinician wrote stays yours and is not resold as a template. Your data is exportable in full at any time and deleted on request when we stop working together, subject to the retention periods your state imposes on the practice.
Are you HIPAA compliant?
No vendor is, because no such certification exists: HHS endorses no private HIPAA certification program. And we are further back than that: Jeni is pre-pilot, no real patient record has been in it, and the business associate agreement, counsel’s review and the infrastructure to hold real data are on a list that is not finished. None of that starts after a pilot has quietly been running for a month. What exists today is described, control by control, on the security page rather than displaying a badge.
The company
What stage are you at?
Early, and specifically so. The consumer product that produced the insight has paying subscribers; the clinic platform is being built with its first practices rather than sold ahead of them. We are assembling a founding team around clinical, engineering and go-to-market. If that is too early for your practice, it probably is. The fit section on the clinics page says who this is not for.
How are you different from the other companies doing this?
Two ways that are structural rather than featural. The protocol is authored and signed by your clinician and stays yours. We are the runtime, never the author, which is the opposite of a neutral layer that sits between you and your patient. And we publish what the evidence does not support alongside what it does. Any product description that fits in a paragraph is reproducible in a quarter; what is not reproducible is a record of what happened to patients on version four of a protocol across a number of clinics.
What happens to my patients if you shut down?
It is the right question to ask a company this early, the risk is real, and you should price it rather than be talked out of it. What we can do is make sure nothing of yours is trapped. Your record exports in full at any time: enrollments, the plans and protocol versions each patient ran, and the access log. Nothing was migrated in, so there is nothing to migrate back, and the protocol is a document you own.
Ask us something that isn’t here.
If the answer you need is missing, write to us. The questions clinics ask are how this page gets better.