For practitioners building inside someone else's infrastructure and deciding what needs to remain theirs.
Not sure this is your stage? Holistic practices develop differently as they grow. If this guide does not fully match your current situation, the full stage guide library is available at holisticpracticemanagement.com/stages
Holistic practices evolve through recognizable operational stages.
Stage 1 - New Practice
Stage 2A - Small Practice
→ Stage 2B - Practice Within a Practice
Stage 3 - Busy Practice, No Front Desk
Stage 4 - Busy Practice with Front Desk Staff
Stage 5 - Multi-Provider Clinic
You are practicing inside someone else's infrastructure: renting a room, joining a group practice, or working under a shared administrative umbrella.
On the surface, the operational burden feels lighter. The phone is covered. The front desk exists. The EMR is already chosen.
What is less visible is what you do and do not own.
The arrangement can work well, sometimes very well. A host practice that understands your modality, refers actively, and has a front desk that represents your work accurately is genuine infrastructure, not just borrowed convenience.
But it is worth being clear about what is and is not portable. The phone number belongs to the clinic. The EMR records live in someone else's system. If the arrangement changes, you leave with your skills, your relationships, and whatever you thought to build independently along the way.
How much that matters depends on one question: where are your patients coming from?
If most of your patients come through the host practice (through their marketing, their referrals, their reputation) then in a practical sense you are operating as part of that ecosystem. In that situation, using the shared infrastructure usually makes sense.
If you are generating a meaningful part of your own patient base, through your own marketing, talks, referrals, or reputation, then you are building something that needs to be portable, regardless of how long you plan to stay or how well the current arrangement is working.
Most practitioners in this stage have not asked themselves this question directly. The answer changes what the priorities are.
Not every shared arrangement has these problems. But these are the patterns worth noticing.
A shared front desk serving multiple modalities is answering for the clinic as a whole. If they do not know your fees, your intake process, your clinical focus, or how to represent what you actually do, new patient calls may be handled generically. Some host practices train for this. Many do not.
The EMR belongs to the host. If the arrangement changes, access to those records is governed by the host's policies, not yours. The recall list, the patient history, the intake data: none of it is automatically portable, even in arrangements that feel stable and collaborative.
Patients who reach you through the clinic number do not necessarily have a way to find you if the arrangement changes. There is no clean way to bring that contact history with you.
Host practices change ownership, close, restructure, or shift their model. Even good arrangements end. Practitioners who have built their patient base entirely inside someone else's infrastructure often discover, at the moment of transition, that the infrastructure was doing more work than they realized.
The goal is not to duplicate the host's infrastructure or work around it. It is to own the layer that makes your practice portable, without friction to the existing arrangement.
A practice with its own infrastructure can move. A practice without it cannot.
The right investments here pay for themselves not just in bookings and referrals, but in your ability to move if the arrangement changes.
Worth naming: practitioners in shared arrangements often discover the portability gap at the moment of transition, when it is no longer easy to fix.
If the host front desk represents your practice well, that coverage may be entirely adequate for day-to-day operations. The question is still whether the number is yours.
The right setup, particularly if you are generating your own patient base, is a dedicated VoIP business number that forwards to the existing front desk. From the host's perspective, nothing changes. From yours, the number belongs to you. If the arrangement ends, it comes with you, forwards to a new location or service, and your patients never need to be notified of a change.
The same logic applies to texting and automated communication. If patient reminders, follow-up messages, and recall sequences are running through the host's system, those communication relationships belong to the host. Own your texting infrastructure for the same reason you own your number. The configuration cost is low. The portability value is real.
If the existing front desk is not representing your practice well, a separate reception layer may be necessary. HPM provides dedicated numbers and can manage overflow or specific call types without disrupting the existing arrangement. Business texting configuration is available as an add-on service.
Your Google Business Profile is an ownership question, not just a marketing question.
Patients increasingly discover practices through maps and local search. Reviews, visibility, and location data are attached to whoever claimed the profile. In a shared practice arrangement, that is often the host.
If the host's profile is where your patients find you and leave reviews about your work, that visibility belongs to the host's infrastructure. When the arrangement ends, so does the discoverability asset you helped build.
Claiming and maintaining your own Google Business Profile, even while practicing inside someone else's clinic, is the same category of decision as owning your own phone number. It is infrastructure portability, not marketing sophistication.
The question here is not whether the website looks good. It is whose website it is.
If patients find you through the host's site, on a page the host controls, then the web presence that represents your work is not yours. The reviews, the search ranking, the booking flow, the content, all of it stays with the host when the arrangement ends.
A practitioner generating any meaningful part of their own patient base needs a web presence they own: a site, or at minimum a profile, that describes their work in their words, ranks under their name, and can move with them. It does not have to be elaborate. It has to belong to you.
The same logic that applies to your phone number and your Google profile applies here. A web presence you own, connected to a relationship system you own, means the patients who find you are yours to keep in touch with, regardless of what happens to the arrangement.
HPM helps practitioners in shared arrangements establish an independent patient-facing presence, including a website and the connection to a relationship system, without disrupting the host relationship.
The EMR is probably the host's choice and not changeable. The right question is not which one to use but whether your clinical records are exportable and whether you have independent access to your own patient data.
Most practitioners assume this is fine until they need to leave. Worth confirming before that moment arrives.
This is the most important system at this stage, and the one most practitioners here do not have.
It sits before the EMR in the patient relationship: everyone who has ever expressed interest, asked a question, attended a talk, or was referred but never booked. That layer belongs entirely to you because it was never part of the host's infrastructure in the first place.
A CRM (contact and relationship system that tracks everyone who has ever expressed interest in the practice, not just current patients) can be implemented without disrupting the existing arrangement. It does not touch the EMR. It does not change how the shared front desk operates. It simply ensures that the patient relationships you have built have a home that belongs to you.
Even in well-aligned arrangements where the host refers actively and the front desk represents your practice well, a CRM layer costs little and risks nothing. A single salvaged relationship or referral covers the cost.
Configuration is where most implementations fail. Holistic Practice Management offers configuration support for practices setting up a CRM at this stage, along with a three-month free trial.
Get instant access to:
✓ Stage 2B: Practice Within a Practice Guide (PDF)
✓ Holistic Practice Operations Guide 2026 Edition
---
Everything you need to evaluate your phone setup, discoverability, patient relationships, and communication infrastructure - and understand which parts of your practice are truly portable if the arrangement changes.
Treating the arrangement as the infrastructure.
The host practice provides operational convenience, and sometimes genuine operational support. It does not provide a portable practice. Practitioners who have been in a shared arrangement for several years sometimes discover, when the arrangement ends, that they are effectively starting over: no owned phone number, no independent patient records, no CRM, no Google presence that belongs to them.
The time to build the portable layer is before it is needed, when there is no urgency and no friction to the existing arrangement.
The arrangement is asking a new question when:
you are generating a meaningful part of your own patient base independently
the host front desk is not representing your practice specifically or well
the arrangement has changed, or feels less stable than it did
you are beginning to think about what a practice of your own would look like
a patient has asked how to reach you directly, outside the clinic
Some practitioners stay in shared arrangements permanently, by choice. If the host generates most of the patient flow, the arrangement is stable, and the front desk represents your practice well, the shared infrastructure may be exactly right.
The operational goal in that case is simpler: make sure the front desk knows your practice well enough to represent it accurately, and that new patient calls are handled in a way that fits your clinical culture.
Even then, a CRM layer costs little and risks nothing. The patient relationships it protects are yours regardless of the arrangement.
The work here is not to build a parallel operation. It is to own the layer that makes your practice yours regardless of the arrangement.
You can piece this together from separate vendors: a number from one, a CRM from another, a standalone website. Each is portable on its own, but they arrive disconnected, and connecting them, then keeping them connected, is work that lands on you, on top of a full clinical schedule inside someone else's practice. A number that does not feed a CRM, and a website that does not either, is three portable assets that still do not function as a system.
HPM provides the portable layer already integrated: your own number, a CRM configured for clinical practice, a web presence you own, and the connections between them, set up so they work as one system from the start. Everything it builds belongs to you, not the host, and it can step in for overflow or coverage without touching the host's setup.
Facebook
LinkedIn
X
Mail