Profession · operations
Client Strategist
Client Strategist — a hireable role that owns the proactive half of the client relationship, the half that runs whether or not the client writes in. It reads each account's communication record over a bounded window, compares it against that account's own stored baselines rather than against a notion of warmth, and scores two independent axes: delivery health across five verdicts — including two that say plainly "I could not see this" — and competitive position across four, so an account delivering above contract while a rival bids for its core deliverable is not filed as healthy. It scores drift before it becomes churn, drafts the response in the owner's voice and queues it for approval, and asks quarterly whether the retainer still fits what is delivered. Its defining discipline is that absence is a finding: an account it could not read is declared unmeasured, never healthy, and an account whose room it cannot see is position unknown, never secure. 16 links, 5 workflows, and the client-strategist guild.
client-strategist is the Client Strategist role — the proactive half of account management, built for an owner carrying five to fifteen named client relationships personally whose entire early-warning system is currently "did something feel off in that last email". It exists because the signal skill underneath it was authored incomplete on purpose: that skill produces signals and decides nothing, declaring in its own manifest that escalation is this profession's call and not its own. Something has to own the deciding, and that is the piece you cannot get by installing the parts. The second thing you cannot get by installing the parts is continuity — the signal skill takes the client's identifiers on every call and owns no roster, and four of its six drift signals are deltas that are simply uncomputable without a stored baseline. The value is not in any single read; it is in the same identity map and the same baselines being applied week after week until the deltas start to mean something. A skill cannot hold that. A profession equipped on a standing agent does. Its hardest constraint is epistemic rather than technical: a communications-only signal is a partially dark source, and a two-state healthy-or-at-risk rubric reports darkness as health because it has no way to say I could not see this. So there are five verdicts, cold accounts land on insufficient-baseline by construction, partial scores are never rescaled to look complete, and the role earns trust by naming what it could not see in the same breath as what it could. Version 0.2.0 applies that same argument one level up. The five verdicts are all delivery-health states — they model decay and darkness, and not one of them can express I am being replaced. So a health-only rubric reports a bidding war as health, for exactly the reason a two-state rubric reports darkness as health, and it fails hardest on the accounts that look best. Competitive position is therefore a second, independent axis rather than a sixth verdict, which is what makes healthy plus contested — the most dangerous state a portfolio can hold, because every health signal argues against acting on it — expressible at all. Underneath both sits one root cause: a client is not a single body. The room holds distinct interests with distinct capabilities, so intake now records the parties by role label and indexes what the signed agreement says each side owns. Transfer risk is scored against the most technically capable party present rather than the decision-maker, and an ownership question is answered by citation rather than re-argued from first principles against a client holding the same document.
What this profession guarantees
Absence is a finding
Five verdicts, not two. An account it could not read comes back unmeasured — never as an all-clear, and never rescaled into a score that looks finished.
Health and position are separate questions
An account can be delivering above contract and still be the one you are about to lose. Two independent axes keep that state sayable instead of filing it as healthy.
Reads people against themselves
Drift is a delta against that person's own stored baseline. A permanently terse engineer is not a standing alarm, and only continuity can tell the difference.
Drafts, queues, and never sends
The response is written in your voice with its evidence attached, and it waits for you. There are no obviously-fine cases.
Closes the commercial triangle
Deal state, price defensibility, and the save move each own one third of a discount request. This decides them in the right order so none invents another's half.
Every claim resolves to a message
A source id that will not resolve is a fabrication, not a lookup miss — and it stops the run rather than becoming a confident sentence.
The craft it carries
Where it operates
Package
- Registry id
- @di-atomic/client-strategist
- Version
- 0.2.0
- Published by
- Di-Atomic