part six · client relationship strategy
Client Relationship Strategy
Trust building, cadence, renewal, expansion — the strategic frame for how the chain meets the people who pay for it.
The relationship is the layer above the work. It is what makes the work fundable, repeatable, and renewable. The strategic relationship is set in this volume; the operational relationship runs in Volume V Part 7. Both volumes describe the same relationship from different altitudes.
The relationship is an asset
It is real, valuable, and depreciating. A client relationship that is not invested in for two quarters is worth less, even if the work has shipped on time. Trust does not hold on inertia.
The corpus treats the relationship as a portfolio item. It is reviewed quarterly, the way an initiative is reviewed quarterly. The questions are different but the discipline is the same.
The four states of a client relationship
| State | Signal | What the chain does |
|---|---|---|
| Establishing | First 90 days | Cadence is set, SLA is signed, weekly update begins, first prediction is checked together |
| Operating | Cycles are running, predictions are checked, retention is steady | Maintain cadence, surface patterns, hold the trio's attention |
| Expanding | Client raises a new problem space; trust has been earned | Move to Initiative discovery, write an initiative brief, run Volume II |
| Renewing or ending | Contract approaches term | Quarterly portfolio review with the client; explicit decision on what continues, what changes, what stops |
The state is named, not implied. We are establishing and we are renewing are different conversations and need different artifacts.
Cadence as strategy
Cadence is not administrative. It is what makes the relationship legible. A client who knows when they will hear from the team has fewer reasons to ask, and the asks they do raise are the ones that need attention.
The corpus default cadence:
- Weekly written update — Friday, before 4pm, ~200 words, three sections (shipped / in progress / blocked).
- Bi-weekly sync — 45 minutes, fixed agenda (signal readings, scope decisions, CS patterns).
- Quarterly portfolio review — 90 minutes, three artifacts (SLA, VRI, root-cause patterns).
The cadence is held even when there is nothing to say. Nothing changed this week is a useful update. Silence is anxiety.
Trust building
Trust is built by repetition of small, kept commitments. The corpus's pattern is to make every commitment small enough to keep, and to keep all of them.
- We will run the check on this date — and the check runs on that date, even if the result is uncomfortable.
- We will tell you the prediction outcome by Tuesday — and the email lands on Tuesday.
- We will surface the support patterns each month — and the patterns are surfaced.
Trust is not built by occasionally-heroic effort. Heroic effort is what the chain produces when the regular effort isn't running. A client whose team relies on heroism does not trust the chain — they trust the people, which is more fragile.
Renewal and expansion
The corpus pattern: renewal is the easiest sale; expansion is the second easiest. Both depend on trust having been built in the operating phase. Both are anchored to artifacts the client has been reading.
- Renewal — anchored to the SLA review and the VRI trend. Here is what we said we would do, here is what we did, here is what comes next at the same shape.
- Expansion — anchored to the pattern in CS-to-bug pipeline (Volume V Part 7) or to a new initiative the client has surfaced. We have been seeing this in the support pipeline for six weeks. We believe it is initiative-shaped. Here is the brief we would write.
Neither is a sales conversation. Both are chain conversations. The chain that produces good artifacts produces its own pipeline.
When to walk away
The corpus is opinionated here. A client relationship that cannot accommodate Discovery, will not pay for prediction, and frames witnessed assumptions as scope creep is one where the chain will produce rework as its main output. The right response is to say so plainly and to walk away, ideally before the contract is signed.
Walking away is a strategic act. It is documented as a portfolio decision and joins the corpus the same way a kill decision does. Future engagements with similar shape inherit the learning.