← All Case Studies
Chief of Chaos

Jul 14, 2026 · 3 minute read

150 new customers a month. Three systems talking to each other. Zero cannibalizing paid search.

How Chief of Chaos built a precision affiliate program for Skin Laundry that added real, treated customers every month without touching a single channel it was not supposed to.

The front desk of a Skin Laundry clinic

The results

  • ~150

    New treated customers every month

  • 0

    Paid search partners used

  • 10

    Partner categories activated

  • 3

    Systems unified for accurate attribution on every commission

Most affiliate programs operate on a simple logic: drive traffic, track the click, pay on the sale. Skin Laundry’s program could not work that way.

Skin Laundry is a leading medical aesthetics brand offering clinically backed laser facial treatments at premium clinics across the United States. Commissions could only be earned after a customer completed their first in-clinic treatment, not at the point of booking, not on interest, only on a completed visit. That meant tracking had to span three separate systems: booking, clinic attendance, and Impact. All of them had to talk to each other accurately, every time.

On top of that, paid search partners were off the table entirely. The program had to grow without cannibalizing existing acquisition channels. Every new customer had to be genuinely incremental.

Chief of Chaos, the managed services arm of the XPFlow family, built the program and managed the attribution infrastructure to run it.

The problem is not always strategy. Sometimes it is the plumbing.

Skin Laundry did not have a partner strategy problem. They had a tracking problem that made the right strategy impossible to execute without solving it first.

If you cannot reliably attribute a commission to a completed in-clinic treatment, you cannot pay partners accurately. If you cannot pay partners accurately, you cannot recruit the kind of premium partners worth having. The whole program depends on getting the attribution layer right before anything else matters.

Chief of Chaos coordinated tracking across all three systems, booking, clinic completion, and Impact, building the reconciliation layer that made accurate, treatment-based attribution possible. That infrastructure became the foundation everything else was built on.

Selective by design

With the attribution problem solved, the recruitment strategy was deliberately narrow. Not every partner category fits a high-consideration, premium medical aesthetics brand. Chief of Chaos focused on the ones that do: vetted editorial publishers, listicle and review sites driving high-intent readers, subscription and membership platforms, and credit card reward partners reaching qualified, premium audiences.

  • Vetted editorial publishers
  • Listicle and review sites
  • Subscription and membership platforms
  • Credit card reward partners
  • Creators

The standout partnership was Capital One, a strategic relationship that put Skin Laundry in front of exactly the kind of customer the brand is built for.

Chief of Chaos also built a creator network through a different model: complimentary treatments exchanged for authentic, honest content. Not scripted endorsements. Real experiences from real customers who happened to have audiences. The result was genuine creator advocacy that drove strong engagement and sentiment without manufactured enthusiasm.

The results

Approximately 150 new treated customers every month. Zero paid search partners used. Ten partner categories activated. Three systems unified for accurate attribution on every commission.

And not a single cannibalized channel. Every customer was incremental.

The attribution layer is what XPFlow builds in software

There is a line in the Skin Laundry case study worth reading closely:

“Three systems unified so every commission traced to a completed treatment: booking, clinic, and Impact reconciled into one truth. That reconciliation layer is what XPFlow now builds in software.”

The human operators at Chief of Chaos built and managed that reconciliation layer by hand. Precise, disciplined, and accountable to a tracking standard that most programs never have to worry about. It worked. And it proved the thesis that XPFlow is now building into the platform infrastructure every program in the family runs on.

That is the relationship between Chief of Chaos and XPFlow in its clearest form. Human expertise that proves the model. Software that scales it.

If your program has constraints most tools cannot handle

Complex attribution requirements, channel protection rules, high-consideration categories where partner selectivity matters more than partner volume: this is exactly the kind of program Chief of Chaos was built to run.