Why Ancillary Programs Underperform at Medical Practices

Ancillary services can improve access, strengthen care between visits, and create new revenue streams that help independent medical practices compete with larger healthcare systems. Yet many programs never achieve their clinical, operational, or financial potential.

The problem is rarely the reimbursement opportunity alone. Underperformance usually begins with poor planning, weak leadership support, the wrong vendor or operating model, and fragmented execution.

Here are the most common reasons ancillary programs underperform and what medical practices can do differently.

1. The opportunity was never properly assessed

Practices sometimes select a program before validating patient eligibility, clinical need, reimbursement potential, workflow requirements, staffing demands, or expected financial return. Leadership becomes invested in a solution before determining whether the underlying opportunity is appropriate for the organization.

Before evaluating vendors, complete a formal opportunity assessment. This should examine the eligible patient population, clinical use case, payer mix, staffing requirements, compliance considerations, expected collections, implementation costs, and projected net contribution.

2. The initiative is treated as a side project

Clinics frequently assign an ancillary program to a lower-level team member while executives and physicians provide minimal support. The employee may be capable, but they are unlikely to have the authority to resolve cross-functional problems, secure physician participation, or hold vendors accountable.

A properly executed service line can transform patient care while creating diversified revenue streams that support the practice’s independence. It should be treated accordingly. Establish executive sponsorship, physician participation, an operational

owner, appropriate resources, and clearly defined clinical and financial objectives.

3. The wrong service line was selected

A service may be reimbursable without being clinically appropriate, financially attractive, or operationally realistic for a particular practice. Selecting a program because it has worked elsewhere does not mean it will work for a different specialty or patient population.

Compare each opportunity against the practice’s diagnoses, payer mix, patient needs, clinical priorities, staffing capacity, and reimbursement environment. The objective is not to add another program. It is to identify the service line that fits the practice.

4. Often the cheapest vendors cost you the most

Practices commonly evaluate vendors by asking how much the service costs per patient. PMPM pricing matters, but it reveals very little about the vendor’s ability to produce results.

Leadership should ask how many billable codes the vendor completes per patient per month, how it identifies and enrolls eligible patients, how consistently patients engage, and how the service improves access. The practice should also determine whether the vendor reduces administrative burden or quietly transfers work back to clinic staff.

A low PMPM fee provides little value when enrollment, engagement, billing performance, and collections remain weak. Evaluate vendors according to total value, operational impact, and net collections rather than price alone.

5. Vendor selection is driven by the sales presentation

A polished demonstration does not prove that a vendor can implement, scale, engage patients, support clinical escalations, or perform within a specific specialty.

Use a structured evaluation process. Request specialty-specific references, verifiable performance data, sample reports, workflow demonstrations, escalation protocols, implementation plans, and access to current clients. Evaluate how the vendor performs after the contract is signed, not simply how well it sells.

6. The operating model does not fit the practice

Technology-only, internally staffed, and fully managed programs each require different levels of staffing, expertise, oversight, and investment. Problems arise when a practice selects a model that does not match its operational capabilities.

Determine how much control the practice wants and how much work it can realistically absorb. Then select the operating model that aligns with its staffing capacity, patient needs, budget, clinical oversight requirements, and organizational maturity.

7. Contracts do not create accountability

Many agreements fail to define implementation timelines, enrollment expectations, performance reporting, clinical responsibilities, billing ownership, data access, or termination rights. When performance declines, the practice has little contractual leverage.

Negotiate measurable service levels before signing. The agreement should address implementation, outreach, enrollment, documentation, reporting, escalations, data ownership, billing responsibilities, corrective actions, and reasonable exit provisions.

8. No senior leader owns the program

Without executive ownership, vendor coordination weakens, staff participation declines, and performance issues remain unresolved. The program becomes everyone’s responsibility and, therefore, no one’s priority.

Assign both an executive sponsor and an operational owner. The executive should remove organizational barriers and reinforce the program’s importance. The operational lead should manage workflows, staff participation, vendor performance, reporting, and corrective actions.

9. Clinical and administrative teams are involved too late

Leadership may approve a program without understanding how it will affect physicians, nurses, medical assistants, front-desk staff, billing teams, compliance, or IT.

Include representatives from these functions during vendor evaluation and workflow design. Early involvement reveals practical obstacles before they become expensive implementation problems and creates stronger internal support for the program.

10. The workflow was never properly designed

A signed contract is not an operating model. Without a defined workflow, patient identification, enrollment, consent, documentation, escalation, billing, and communication occur inconsistently.

Map every step from patient identification through collections. Assign an owner, required documentation, system of record, and expected turnaround time to each stage. The program should fit into the practice’s existing operations rather than depend on informal workarounds.

11. Implementation adds work instead of reducing it

Some practices discover after launch that their staff must manually identify patients, transfer information, explain the program, duplicate documentation, or resolve issues the vendor was expected to manage. Document the practice’s responsibilities before signing an agreement. Automate data exchange where possible and require the vendor to demonstrate exactly which tasks it will assume, reduce, or eliminate. Administrative burden should be measured as carefully as revenue.

12. I hate to tell you, your patient population isn’t unique

Practices often make assumptions about how their patients will respond to an outside care-management team. One of the most common is that patients will not communicate with a vendor because they do not already have an established relationship.

The quality of the partner matters, but clinic participation matters just as much. Introduce the partner as an extension of the practice, reinforce that relationship through physicians and staff, and ensure both organizations operate as one team.

Rather than relying on assumptions, begin with a defined patient cohort and measure reach rates, engagement, retention, and patient feedback.

13. Geography is used to justify untested assumptions

Rural practices sometimes assume their patients will not use text messaging as readily as patients in urban markets. My experience working with ancillary-care organizations has shown that rural patients can be highly active through text and, in some programs, have texted more frequently than urban patients.

SMS also requires limited bandwidth, making it practical in areas with inconsistent cellular data coverage. Practices should test calls, SMS, portal messages, email, and caregiver outreach, then allow actual response data to determine the engagement strategy.

14. Patient eligibility is overestimated

Vendor pro formas are frequently based on the total addressable population rather than patients who are eligible, clinically appropriate, reachable, willing to enroll, and likely to remain engaged. Aggressive projections can create unrealistic expectations before the program begins.

Be critical of vendor-provided pro formas. Build a conservative model using verified eligibility, realistic enrollment, code attainment, retention, collection rates, vendor expenses, and internal costs.

The practice and vendor should also identify the patient populations best suited for the initial enrollment phase. Starting too broadly can create billing inconsistencies, enroll patients who are poorly matched to the service, and make it harder to establish a reliable operating model.

15. Patient enrollment is treated as an administrative task

Patients are sometimes contacted without a clear explanation of why the service matters, how it supports their care, who will communicate with them, or how the new team is connected to their physician.

Enrollment should be a patient-education process. Explain the clinical benefit, the relationship to the practice, expected communication, potential cost-sharing, and how the program complements existing care. Patients are more likely to participate when they understand the value rather than simply the name of the service.

16. Physicians and staff do not actively support enrollment

Programs struggle when patients first hear about them from an unfamiliar third party. Even a capable vendor will have difficulty overcoming a weak or confusing introduction.

Give physicians and staff simple talking points, clear referral triggers, and visibility into program outcomes. A trusted member of the clinic should introduce or endorse the service before vendor outreach begins.

17. The vendor cannot consistently engage patients

Low contact rates, repetitive communication, limited follow-up, language barriers, oversized care-manager panels, and inadequate caregiver involvement reduce participation. Conversations can also become stale when outreach focuses on completing time rather than addressing relevant patient needs.

Establish expectations for care-manager panel size, outreach frequency, communication methods, language support, caregiver involvement, and the quality of patient interactions. Monitor reach rates, meaningful conversations, retention, and engagement by care manager rather than looking only at aggregate minutes.

18. Clinical escalation pathways are unclear

Medication concerns, changes in condition, abnormal readings, and other clinical findings may not reach the appropriate person quickly. This limits the program’s clinical value and can introduce unnecessary risk.

Create written escalation protocols that define the triggering event, urgency level, responsible recipient, communication channel, expected response time, backup contact, and documentation requirements. Test these pathways before scaling the program.

19. The program operates separately from the clinical team

Information collected between visits is valuable only if it reaches the people responsible for the patient’s care. When vendor notes remain isolated, they are unlikely to influence care plans or clinical decisions.

Integrate care plans, patient updates, escalations, and relevant findings into the practice’s systems and clinical workflows. The care-management team should have a defined method for communicating actionable information without overwhelming physicians with unnecessary updates.

20. Billing responsibilities are fragmented

The vendor, practice, and billing company may each assume another party is validating claims, monitoring denials, resolving patient balances, and reconciling collections.

Create a written billing workflow that assigns ownership for eligibility validation, code approval, claim submission, denial management, patient responsibility, payment posting, and reconciliation. Every handoff should have a named owner.

21. Reporting lacks operational depth

High-level activity reports do not tell leadership why a program is succeeding or failing. Total enrolled patients and billed revenue provide little insight into where performance is breaking down.

Require a dashboard covering eligibility, enrollment, reach rates, engagement, code attainment, claims, denials, collections, escalations, retention, clinical activity, administrative burden, and profitability. Reporting should support decisions, not simply confirm that activity occurred.

22. Performance is not reviewed regularly

Programs rarely fail overnight. Underperformance typically develops through a series of unresolved enrollment, engagement, workflow, billing, or staffing problems.

Hold structured monthly reviews with the vendor and relevant internal stakeholders. Document performance gaps, assign corrective actions, establish deadlines, and review progress at the next meeting. Meetings should produce accountability, not simply another report.

23. The program is scaled before the model is proven

Expanding across every provider or location may appear efficient, but it magnifies unresolved problems. Poor workflows, weak documentation, and billing inconsistencies become more difficult to correct at scale.

Begin with a controlled patient cohort, provider, or location. Expand only after validating enrollment, patient experience, documentation, billing, collections, clinical escalation, and staff workload.

24. Too many disconnected vendors are involved

Separate technology, clinical-service, billing, and engagement vendors can create fragmented ownership. When something fails, each party points to another part of the process.

Map the complete vendor ecosystem and eliminate overlapping responsibilities. Integrate data wherever possible and designate one party to coordinate clinical, operational, technical, and financial performance.

25. The vendor relationship is not managed after launch

Practices sometimes assume the program will run independently once implementation is complete. That is often when performance begins to decline.

Treat vendor management as an ongoing leadership responsibility. Hold regular operating reviews, monitor contractual commitments, validate invoices, investigate performance changes, and revisit the model as the practice’s needs evolve.

26. The program is viewed only as a revenue opportunity

When financial objectives are disconnected from patient appropriateness, access, continuity, and quality, physicians and staff are less likely to support the program. Patients will also recognize when a service lacks a clear connection to their care.

Establish balanced objectives that measure clinical value, patient access, continuity, physician experience, operational efficiency, patient satisfaction, and financial performance. Revenue should support a strong care model, not define it.

The opportunity is not the operating model

Most ancillary programs do not underperform because the underlying clinical or reimbursement opportunity is weak. They underperform because the practice selected the wrong model, chose the wrong partner, failed to design the workflow, or did not establish sufficient ownership and accountability. Before adding a service line, leadership should answer four questions:

• Is this clinically appropriate for the patients we serve?
• Can it be integrated without creating unnecessary work?
• Will the model produce compliant, collectible revenue?
• Who will own its performance after implementation?

ConnectedCare Advisory Group helps medical practices answer these questions before a vendor is selected. We evaluate the clinical need, patient opportunity, reimbursement model, workflow requirements, and partner capabilities, then help leadership structure and implement a service line that can perform over time.

The goal is not to introduce another ancillary program. It is to determine whether the opportunity fits the practice and, if it does, build the operating model required to make it successful.

Build the model before you buy the program

• ConnectedCare Advisory Group evaluates the clinical need, patient opportunity,
• reimbursement model, workflow requirements, and partner capabilities — then helps leadership implement a service line that performs over time.