--- # /blocks/account/ - imported from the company-brain draft # (blocks-account.md v1, 2026-07-15), stamped from block-page-template.md. # Status honesty: designed - specified and ready to build, NOT delivered; # no engagement link in the footer. title: 'The account block' slug: 'account' object: 'The customer relationship, continuous from first signal to last renewal.' pain: 'We find out an account is at risk when the cancellation arrives. Growth means hiring more account managers.' description: 'The customer relationship run as one loop - weak signals joined months before the renewal, every client action governed.' metaTitle: 'The account block: retention, signal to renewal' related: - 'subscription' - 'delivery' order: 1 noindex: false # launched 2026-07-24 --- # The account block **The whole customer relationship, run as one loop** - weak signals joined months before the renewal, every client action governed. --- ## The pain *"We find out an account is at risk when the cancellation arrives. Growth means hiring more account managers."* A customer relationship is one continuous thing; the company serving it is not. Sales, service, delivery and finance each hold a slice, in their own systems, measured on their own numbers - and the full picture of any account is assembled only in meetings, handovers and the heads of a few experienced people. The early signs of trouble - a key contact leaves, usage dips, an invoice ages, a complaint stalls - land in different systems and are never put together. Each looks routine alone. Together they are decisive. The firm finds out at the renewal, about things it already knew months earlier. In wealth this is the client book; in insurance, broker and insured relationships; in legal, the client and introducer base; in distribution, the trade accounts. ## What the block is The object is the customer relationship - one continuous picture per account, from first signal to last renewal. Everything the relationship produces feeds one live record: emails, tickets, invoices and payments, usage, meeting notes, contract changes, public filings. A model reads it permanently. Your CRM, service desk and ledgers stay exactly where they are - the block reads from them, it does not replace them. ## The loop in action [MOMENT: styled quote panel] Three weak signals arrive through different doors: the sponsor who championed the deal leaves the client, usage drifts down across the quarter, and a healthy account goes quiet. None would justify a call on its own. Together they describe an account at risk, months before the renewal window opens. The block assembles the picture and routes it to the named owner - *"here is what changed, here is the history, here is the play"* - while there is still a relationship to save. Early intervention is the cheapest revenue you will ever protect. - *the dial: recommend* [MOMENT: styled quote panel] The catch. The renewal comes up and the standard uplift is queued. The block holds it - service history shows repeated SLA breaches this period, and the invoices on the account are ageing โ‡„ the cash loop. The whole picture says this customer is owed a conversation, and perhaps a credit, before they are asked for more money. The uplift waits; the relationship doesn't burn; the renewal survives. - *the dial: recommend, with the governance doing the holding* [MOMENT: styled quote panel] The departed champion resurfaces as an executive at another firm - a public filing, a press mention. The block opens a warm opportunity carrying the relationship's history โ‡„ a new account, and drafts the outreach in the owner's voice, waiting for a signature. What used to be a name lost to somebody's memory becomes pipeline. - *the dial: draft* Each output states what it saw, why it matters, what it recommends, and how confident it is - every fact linked back to its source, in an order an account owner can read and a board can examine. ## You set the dial Every capability has four positions: **observe** - it reads silently and measures its own accuracy; **recommend** - it surfaces the case and a proposed action to a named owner; **draft** - it prepares the action for a human signature; **act** - it executes within agreed bounds and logs everything. Everything starts at observe. Promotion is earned on the measured record and reversed instantly if it doesn't hold. Client-facing communication sits behind a human gate wherever your policy or your regulator demands one - permanently, if that is your policy. The mechanics are the immune gate described in [our framework](/ai-native-company/). ## How it lands It starts narrow: the top 20โ€“50 accounts by value or risk, the block at observe against your own past outcomes. Before anything goes live, a short diagnostic on a few past accounts - one lost, one saved, one that surprised you - establishes the baseline: what did the record already contain, and when did you find out? Nothing is replaced, nothing is migrated - the first signals flow from the systems you already run. From there it is a bounded engagement - blueprint, build, handover - and your team owns the result outright: the signal map, the judgement rules, the dial settings, the working loop. ## The backtest Take three past accounts: one you lost, one you saved at the last minute, and one that surprised you late. What did your own records know, and when did you find out? That is the first question the diagnostic answers. Take [the ten-minute diagnostic](https://benchmark.somai.studio), or write to [hello@somai.studio](mailto:hello@somai.studio?subject=The%20account%20block). --- Runs on [our framework](/ai-native-company/) ยท related reading: [Most AI spend never reaches the P&L](/thinking/most-ai-spend-never-reaches-the-pnl/)