AI agent index: /llms.txtFull content index for AI agents: /llms-full.txt

Relationship managers,
at higher leverage.

Klay RM Co-Pilot — Intelligence Studio: pipeline, documents, compliance, approvals, activation

A relationship manager has a small number of clients who get the attention, and a long tail that gets a quarterly call, if that. Most of the difference between the two is analyst labour the RM doesn't have time for.

We were brought in to change the maths. An intelligence layer that does the reading, so the RM is left with the part that needs a person.

The layer reads the whole book at once — every position against the firm's house view, on a standing basis rather than on request. The quarterly review, the most labour-heavy thing an RM produces, arrives written in the firm's house style, with positions and reasoning already on the page. Before each call, a short brief on what moved and what to raise with this client.

Every output is bounded by the firm's compliance rules at generation time. Nothing leaves the system that wouldn't pass review. The compliance team approved the guardrails once; they don't approve every draft.

Klay RM Co-Pilot — New Client Onboarding inside the KlayX Co-Pilot
Klay RM Co-Pilot — Product Studio: CRA-API contract & Protobuf schema

The RM's unit of work moves from writing to approving. The long tail starts getting the conversation it should always have had.

The Co-Pilot is in production. RMs are running larger books without a degradation in the conversations clients actually have. The work continues; the next phase extends the layer beyond the RM seat into operations and product.

Some of our best projects
started with a two-line email.

Send yours