Client Disengagement Risk — 2026-02-03

Overview

As of the weekly sync on 2026-02-03, Adavacare is showing clear signs of quietly disengaging from Asymmetric. Multiple indicators surfaced over the preceding weekend, and a client meeting was already scheduled for the following day (2026-02-04) where a formal disengagement may be announced.

Indicators of Disengagement

Signal	Detail
Meta access revoked	Adavacare removed Asymmetric from their Meta Business account over the weekend prior to this call.
Site migration suspected	Melissa flagged that she believes Adavacare moved their website away from Asymmetric-managed hosting.
Google Ads suspected moved	Melissa also suspects Adavacare transferred Google Ads management to another party.

Sebastian noted the situation was "not super shocking," referencing a prior comment from the client that they appreciated the new energy but wished certain work had been done sooner.

Context

Last client meeting prior to this call: January 21, 2026
Next scheduled meeting: February 4, 2026 (day after this call)
Sebastian had deliverables to send over before that meeting
Revenue risk was explicitly called out: "Last thing we need is to lose any more revenue."

Key Decisions

No immediate escalation action taken; team agreed to get a read on the situation in the February 4 meeting before drawing conclusions.
Mark to check whether Adavacare's domain is registered under Asymmetric's Cloudflare account, which would be a relevant leverage/offboarding consideration.

Action Items

[ ] Mark Hope — Check Cloudflare account for Adavacare's domain; report findings to Sebastian.
[ ] Sebastian Gant — Attend February 4 meeting with Adavacare; assess whether disengagement is confirmed and determine next steps.

^[1]
^[2]