Educational overview · Approx. 4 min read · illustrative, not advice
Nobody buys a business because of its software. Plenty of people lose one because the seven systems underneath it never spoke to each other.
The seven systems
A working metabolic health business runs on roughly seven things. An EHR or clinical documentation system inside the professional entity. A telehealth or visit platform. A scheduling system. A CRM and marketing automation layer for acquisition and follow-up. A payment and subscription billing system, because cash-pay programs are usually recurring. A member experience layer, which is where coaching, education, tracking and support live. And a reporting layer that tells you what is actually happening.
Commonly cited IT and EHR infrastructure costs of $10,000 to $25,000 with EHR and technology subscriptions of $500 to $2,000 per month recur across practice-management publishers, and we label them INFERENCE because the widely repeated attribution could not be traced. Use them as an order-of-magnitude planning frame, not a quote.
The line that must not blur
Clinical records belong inside the professional entity's systems, under its control, governed by its obligations. The member experience layer on the business side is a wellness product: education, coaching, adherence support, tracking, community.
Atlas builds the member experience layer as a wellness experience that does not hold clinical records and is not a clinician write-path. That is a deliberate scope decision, not a feature gap. Pulling clinical data into a consumer-facing product owned by a non-clinical entity creates obligations and control questions that page six explains you do not want.
The practical test: if a regulator asked who controls the record of a clinical encounter, the answer should be the clinical entity, without qualification.
Where builds actually fail
Not on any single system. On the seams. The five failures that recur are: a lead captured in the CRM that never reaches scheduling; a member who pays but whose program status never updates; a clinical visit that happens but is never reflected in the member's journey; a cancelled subscription that leaves access on; and a reporting layer built on numbers that three systems each define differently.
Every one of those is an integration and definitions problem rather than a software-selection problem. Which is why the useful diligence question about any build is not which tools does it use, but what happens end to end when a member signs up, pays, is declined by the clinician, and asks for a refund. Ask a seller to walk that path with you, live, in the actual systems.
What to insist on owning
Your domain, your brand assets, your member list and contact data, your ad accounts, your payment processor relationship, and an export path for everything in the CRM. If any of those sit in the seller's name, you are renting a business rather than owning one.
This is the difference between a stack built for you and a stack you are a tenant inside. Ask, in writing, what happens to each of those assets if the relationship with the seller ends tomorrow. Page fourteen makes it a formal question.
Ask Atlas to put this in writing: itemised list of accounts and assets that are created in the partner's name at build, versus any held by Atlas, so the answer can be published rather than described
Build, buy, or license
Building this stack yourself is entirely possible and it is mostly an integration project rather than a software project. The cost is time and the risk is that the seams above are exactly the part that takes longest to get right, because you only discover them under live load with real members.
Buying assembled tools individually gets you further faster but leaves the integration and the definitions to you. Licensing a build transfers the assembly, which is the whole value proposition and also the whole thing to interrogate: ask precisely which of the seven systems are delivered configured, which are delivered as accounts you must configure, and which are not included at all. A build that includes six of seven and is silent about the seventh is a schedule risk you will meet at day seventy.
- Practice-management publishers and consultancies (aggregate; no single authoritative survey) — Commonly cited IT and EHR infrastructure costs of $10,000-$25,000 and EHR/technology subscriptions of $500-$2,000 per month. Attribution to a specific industry survey could not be traced. [INFERENCE]
- Atlas Metabolic (statement of its own product scope) — The Atlas member experience layer is a wellness product that does not hold clinical records and provides no clinician write-path; clinical records remain with the separately licensed medical entity. [VERIFIED]