--- # /blocks/cash/ - imported from the company-brain draft # (blocks-cash.md v1, 2026-07-15), stamped from block-page-template.md. # Status honesty: mapped - pattern worked out, NOT delivered and NOT yet # specified to build; the weakest of the three tags, stated plainly. title: 'The cash block' slug: 'cash' object: 'The money owed - quote, bill, collect, dispute, resolve.' pain: 'Profitable on paper, tight every quarter. We do the work, then chase the money for ninety days.' description: 'The money owed run as one loop - quote, bill, collect, dispute, resolve - with collection tone set by the whole relationship, not the ledger alone.' metaTitle: 'The cash block: quote to collection, one loop' related: - 'subscription' - 'account' order: 2 noindex: false # launched 2026-07-24 --- # The cash block **The money owed, run as one loop** - quote to resolution, with collection tone set by the whole relationship, not the ledger alone. --- ## The pain *"Profitable on paper, tight every quarter. We do the work, then chase the money for ninety days."* The money owed is one continuous thing - quote, bill, collect, dispute, resolve - but no one function owns that journey. Sales sets the terms, delivery finishes the work, finance raises the bill, service fields the dispute; the invoice ages while each holds its own slice. The milestone that completed on Tuesday isn't billed until month-end. The dispute that's really a service fault sits in the collections queue, souring a good relationship. The discount that broke the pricing floor was agreed in an inbox. In legal and professional services this is lock-up and WIP; in insurance, broker balances and premium credit; in distribution, trade credit; in wealth, fee billing. ## What the block is The object is the money owed - one continuous picture per account, from quote to resolution. Everything the position produces feeds one live record: quotes and terms, milestones and WIP, invoices and their ageing, payment behaviour, promises made in email threads, disputes and what sits behind them. A model reads it permanently. Your billing, ledger and matter systems stay exactly where they are - the block reads from them, it does not replace them. ## The loop in action [MOMENT: styled quote panel] The milestone completes on Tuesday; the draft bill exists on Tuesday. WIP that ages past its threshold surfaces with an interim bill proposed, not a month later at the partners' meeting. *"This work is finished and unbilled; here is the draft."* Days of lock-up disappear not by chasing harder but by never letting the gap open. - *the dial: draft* [MOMENT: styled quote panel] The catch. An invoice hits sixty days and the chase is queued - and the block holds it. Behind the non-payment sits an unresolved service fault ⇄ the delivery loop: the complaint stalled three weeks ago. Collection pauses, the fault routes to its owner, and the chase that would have burned the relationship never sends. The cash arrives because the problem was fixed, not because the letter was firmer. - *the dial: recommend, with the governance doing the holding* [MOMENT: styled quote panel] A quote goes out with a discount beyond the agreed authority. The block quarantines it pending approval - not to slow the deal, but because the cheapest moment to protect margin is before the promise is made. The same read flags payment behaviour deteriorating across an account and summarises the exposure, so the credit-terms conversation happens before the write-off, not after. - *the dial: recommend* 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 a finance director can read and an auditor 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. Anything a customer receives - a chase, a bill, a correction - sits behind a human gate for as long as your policy says it should. The mechanics are the immune gate described in [our framework](/ai-native-company/). ## How it lands It starts narrow: one segment of the ledger - one office, one practice group, one ageing band - the block at observe against your own past outcomes. What did the record know about the invoices that went bad, and when? Nothing is replaced, nothing is migrated - the first signals flow from the billing and matter 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 invoices: one that paid late for a reason you never learned, one dispute that turned out to be your own service fault, and one write-off that surprised you. 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%20cash%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/)