RunPractice Gets Ruth Johnson Backing for Practice AI

RunPractice is asking independent medical practices to buy an ongoing relationship with the company supplying their technology. Alongside software for patient administration, it offers agreed marketing, website development and continuing management. For an owner who has become the person connecting every vendor, responsibility for the work is part of the purchase.

The New York health technology company identified physician Ruth Johnson as an investor in its October 16 announcement. Ruth Johnson uses RunPractice in her own clinical practice and helps inform product development. The investment amount, terms and closing date were not disclosed, making this a story about a physician's backing rather than a priced financing round.

Co-founder and CEO Leo Suleyman and co-founder and CTO Jamal Ali lead the company, whose current team page lists Ruth Johnson as Medical Director. RunPractice is building for independent practices in wellness, aesthetics and direct care, where the patient relationship continues through booking, preparation, documentation and follow-up. Bringing those activities into a connected service gives the investor's daily experience a practical place in the product conversation.

What Ruth Johnson's backing brings to RunPractice

Ruth Johnson founded Genesis Health NYC, a Manhattan practice that brings together internal, functional and integrative medicine. RunPractice says it originally built its system for the team at Genesis Health NYC. That history connects the business to the ordinary work of keeping appointments, information and patient communication moving through a small organization.

The relationship also gives the company several ways to hear the same operational problem. Ruth Johnson is an investor, a practicing user and the Medical Director identified on RunPractice's current team page. A difficulty encountered during the working day can therefore enter a clinical-workflow discussion with someone who has experienced the setting firsthand. That is a useful feedback arrangement for software sold to other physicians.

It also requires careful reading of the investment announcement. The company identifies Ruth Johnson as an investor but supplies no allocation of proceeds, ownership percentage or financing instrument. The announcement dates this public disclosure; it does not establish when funds changed hands. The reported involvement is specific enough to explain without attaching a valuation or a round label the company has not provided.

What practice owners are buying

RunPractice's current pricing separates the software from the managed relationship. Essentials is listed at $99 per month for patient-facing functions such as online booking, a portal, payments and telehealth. The $399 monthly Platform plan adds the RunPractice EHR, its AI workforce and additional practice tools. E-prescribing is described as an optional add-on.

Full-Service has custom pricing and adds agreed marketing, website development and ongoing management. RunPractice says the engagement's scope, timelines and costs are settled before work begins. A practice owner buying the platform should therefore distinguish the subscription's capabilities from the services included in a separately scoped engagement.

The commercial implication reaches beyond the subscription price. A medical practice can have several individually useful applications and still leave its staff responsible for connecting the patient journey. Someone has to reconcile a booking with the right calendar, get information to the practitioner and make sure a follow-up reaches the right person. A managed supplier takes on a different obligation when it agrees to help configure and operate that collection of work.

Compatibility remains part of the buying decision. RunPractice says it can work with supported existing EHRs, with compatibility confirmed before implementation. That qualification matters to a practice whose records, staff habits and patient communications already live in another system. The transition has to fit the practice that will use it.

DevCuration's coverage of Confido Health's CareOS financing follows administrative AI across multi-site healthcare practices. RunPractice's offer places the independent practice owner at the center of the purchasing decision, including the choice to buy ongoing help with the work surrounding the software. Both settings make the movement of information between tasks commercially important, even when the organization buying the service looks different.

Where the AI hands work back to the practice

RunPractice describes AI support across reception, visit preparation, documentation, follow-up and recall. Its AI Receptionist uses approved information for patient questions and appointment coordination, while clinical, sensitive or unresolved requests are routed to staff. The product's usefulness depends partly on whether that transfer carries enough context for the person taking over.

The same distinction runs through documentation. In a company article about its AI scribe, RunPractice describes consent before recording, a structured draft and practitioner review before a note enters the record. Those steps place the clinician inside the workflow instead of treating a generated note as a finished medical record. A practice evaluating the service needs to understand each approval point as clearly as the automation itself.

RunPractice's security page describes encryption, controlled access, practice-level data separation and activity logging. It also says patient identity is verified before patient-specific information is shared or appointments are changed. These are the company's descriptions of its controls, rather than independent findings about security effectiveness. They identify concrete questions for implementation: who can see the information, what the agent can do and where a human approval is required.

The work that travels beyond the first practice

Building inside Genesis Health NYC gives RunPractice a starting environment with known people and familiar routines. Serving another practice introduces a different schedule, a different division of staff responsibilities and different patient expectations. Even a shared software platform has to account for those differences when a team begins using it.

RunPractice describes its implementation approach as guided setup and training. Its broader service model includes agreeing on responsibilities and continuing to review the work. That combination puts implementation capacity inside the growth story: each additional practice brings work for the supplier as well as a potential subscription.

The October announcement does not disclose revenue, independently measured labor savings or a financing-backed hiring plan. Those omissions keep the investment from supporting a numerical growth forecast. The disclosed relationship supports a narrower and more interesting observation: the physician helping shape the workflows has to return to a practice where patient messages and follow-ups continue to arrive.

For Leo Suleyman and Jamal Ali, taking that experience into additional practices means learning which decisions can become standard and which need local configuration. Ruth Johnson's involvement brings one physician's working context into that process. The next practice will bring its own staff, its own records and its own way of deciding when an unanswered patient question needs a person.