Case study / Employer outcome

Dialysis Network Growth

Referral architecture and operating cadence in a complex ESRD/CKD market.

Return to verified work

Dialysis referral network growth engine

Evidence register

What this case can support.

Evidence class
Employer outcome
Claim boundary
Public-safe aggregate outcomes only. Facility, patient, payer, and referral-source records are excluded from the site.
Source basis
  • Executive resume
  • Multi-facility operating record
  • Aggregate referral performance

Case architecture

Ecosystem thesis

Dialysis growth was not a referral-volume problem. It was a complex-care ecosystem problem involving nephrologists, hospitals, payers, intake, transportation, facility readiness, ESRD economics, and patient handoffs.

System path

  1. 01Referral source
  2. 02Intake redesign
  3. 03Payer coordination
  4. 04Facility cadence
  5. 05Treatment start

Executive decision brief

CEO question

What system did this work make more launchable, fundable, or scalable?

Operating answer

In complex care categories, growth happens when referral, intake, payer logic, and field relationships are engineered as one system.

Proof to inspect

Annualized referral revenue, multi-site cadence, cycle-time compression, acceptance quality, and faster intake-to-treatment matter because they show a full handoff system improving, not one isolated sales outcome.

Ecosystem context

The outcome only makes sense inside the system around it.

CKD and ESRD growth depends on the moments between clinical recognition and treatment start. A patient can be clinically appropriate and still stall because admissions, payer coordination, documentation, transportation, facility capacity, or provider communication breaks.

The operating opportunity was to redesign the referral architecture so relationships, intake, payer logic, facility cadence, and treatment start behaved like one system. This mattered because large dialysis organizations compete not only on scale, but on reliability, access, and referral confidence.

For healthtech founders, this case is a reminder that complex-care GTM often lives inside the handoff. The company that understands the workflow friction can build a better commercial wedge than the company that only understands the market size.

Outcome record

The proof signals attached to the case.

growthReferral engine

Referral revenue

Annualized revenue delivered.

operationsMulti-site cadence

Facilities

New York ESRD/CKD facility network.

operationsCycle compression

Cycle time

Referral cycle-time compression.

growthAcceptance quality

Acceptance lift

Acceptance rate improvement.

operationsIntake speed

Treatment speed

Intake-to-treatment reduction.

Interoperability map

How the layers connect.

The case is designed as an operating ecosystem: signal, economics, workflow, proof, and expansion are connected rather than treated as separate workstreams.

01

Referral Source

Who trusts the network enough to route patients?

Relationship management was tied to conversion quality, not just contact count.

02

Intake

Can the patient move from referral to acceptance faster?

Admissions flow, documentation, payer coordination, and facility handoffs were compressed.

03

Facility Cadence

Can operations keep the promise?

Facility-level rhythm made cycle time, acceptance, and treatment start visible and governable.

04

Economics

Does the motion create durable value?

Revenue, payer context, and throughput improvements were connected to the operating cadence.

Operating record

The work, the sequence, and the strategic read.

The record separates the conditions, operating moves, interpretation, and repeatable lessons so the result can be evaluated without flattening the work into a headline.

Challenge

Referral friction, admissions delays, payer coordination, and large dialysis organization competition slowed conversion across a multi-site network.

Approach

Redesigned nephrology referral architecture, intake coordination, relationship management, payer dashboards, and facility-level operating cadence.

Founder takeaway

In complex care categories, growth happens when referral, intake, payer logic, and field relationships are engineered as one system.

Strategic read

The high-level insight is that provider growth in complex care is a reliability game. Referrers shift behavior when the receiving system consistently lowers friction, communicates clearly, starts care faster, and proves that the handoff will not fail.

Proof interpretation

Annualized referral revenue, multi-site cadence, cycle-time compression, acceptance quality, and faster intake-to-treatment matter because they show a full handoff system improving, not one isolated sales outcome.

Operator moves

  • Built physician partnership coverage around referral conversion, not just relationship count.
  • Compressed intake and treatment handoffs through facility-level cadence discipline.
  • Translated kidney-model policy changes into payer strategy and local operating actions.
  • Aligned dashboards to ESRD PPS, APG economics, and payer-facing conversations.

Expansion path

  1. 01

    Map the before-and-after referral flow with cycle-time owners.

  2. 02

    Segment referral sources by trust, volume, fit, and conversion friction.

  3. 03

    Build intake governance around speed, acceptance, and payer readiness.

  4. 04

    Use facility cadence as an executive growth instrument.

  5. 05

    Turn throughput proof into stronger payer and provider conversations.

What I would do again

  • Make the before/after referral flow visible to operators and executives.
  • Translate policy shifts into account-level talking points.
  • Use operating cadence as a growth lever, not an internal admin routine.

What this proves

Azis can improve revenue by fixing the handoff architecture between providers, payers, facilities, and patients.

Evidence objects

Proof artifacts

Start a serious conversation

Build the wedge. Prove the motion. Scale what repeats.

For Series A/B teams that need sales, partnerships, implementation, payer logic, and revenue intelligence to become one operating system.

Contact Azis Download Resume