--- # /blocks/delivery/ - stamped from block-map-canon-v0.5 (entry 4) and the # block-page template. Confidentiality: shape yes, implementation no; moments # are illustrative composites; no client names, thresholds or gated figures. title: 'The delivery block' slug: 'delivery' object: 'Each unit of promised work - matter, claim, order or mandate, from instruction to completion.' pain: 'The write-off surprises us at month end. Scope creeps in the inbox, never in the system.' description: 'Every unit of promised work run as one loop - scope creep and margin leak caught in the correspondence, before the month-end reveal.' metaTitle: 'The delivery block: scope creep and margin leak' related: - 'capacity' - 'account' order: 5 noindex: false # launched 2026-07-24 --- # The delivery block **Every unit of promised work, run as one loop** - scope creep and margin leak caught in the correspondence and the clock, before month end. --- ## The pain *"The write-off surprises us at month end. Scope creeps in the inbox, never in the system."* The work is promised in one place and tracked in another. Scope changes in an email; time and cost drift in a timesheet nobody reads until billing; the SLA clock runs where no one is watching it. Each unit of work - the matter, the claim, the order - is a small business of its own, and the signals that it is going sideways arrive routine and separate: one more request, one more slipped milestone, one more quiet week. Put together they are a write-down; apart they are noise, and the noise is only added up at month end, when it is too late to act. In legal this is the matter; in insurance, the claim; in wealth, the mandate; in distribution, the order. ## What the block is The object is each unit of promised work - one continuous picture per matter, claim, order or mandate, from instruction to completion. Everything it produces feeds one live record: the instruction and its scope, time and cost against plan, milestones, the SLA clock, the correspondence, quality flags. A model reads it permanently. Your practice, case, matter or project systems stay exactly where they are - the block reads from them, it does not replace them. ## The loop in action [MOMENT: styled quote panel] A scope-bearing request is buried in a client email - "while you're at it, could you also…" - and the hours on the matter are already drifting past plan. Neither would be noticed until billing. Together they are margin walking out of the door. The block drafts a scope-change note and the fee variance for the owner while it can still be raised: *"this request adds work beyond the mandate; here is the variance, ready to put to the client."* The write-down becomes a conversation, held in time. - *the dial: recommend* [MOMENT: styled quote panel] The catch. A deliverable is ready to send, and a quality concern raised three weeks ago in the correspondence was never closed. The block holds the send: *"this is going out with an unresolved quality flag; a review is inserted before it leaves."* Nothing embarrassing reaches the client, and the review happens because the whole picture - not just the outbox - governs the action. - *the dial: recommend, with the governance holding* [MOMENT: styled quote panel] A milestone completes on Tuesday. The block fires the billing trigger the same day ⇄ the cash loop - the work billed while it is fresh, not gathered up at month end. Lock-up shrinks not by chasing but by never letting the gap open. - *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 a delivery lead can read and a finance director 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 updates and fee changes sit behind a human gate wherever your mandate or your policy demands one. The mechanics are the immune gate described in [our framework](/ai-native-company/). ## How it lands It starts narrow: one practice group or one matter type, the block at observe against your own past outcomes. 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 matters: one delivered on plan, one that crept in the inbox until it was written down, and one whose overrun surprised you at month end. What did your own systems know about the drift, and when? 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%20delivery%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/)