--- # /blocks/third-party/ - stamped from block-map-canon-v0.5 (entry 8) and the # block-page template. Confidentiality: shape yes, implementation no; moments # are illustrative composites; no client names, thresholds or gated figures. title: 'The third-party block' slug: 'third-party' object: 'Each supplier, introducer or outsourcer - from onboarding through performance to exit.' pain: 'We discovered the dependency the day it broke.' description: 'Every supplier and dependency run as one loop - distress sensed from filings and performance together, the exit plan ready before the failure.' metaTitle: 'The third-party block: supplier distress sensed early' related: - 'resilience' - 'financial-crime' order: 9 noindex: false # launched 2026-07-24 --- # The third-party block **Every supplier and dependency, run as one loop** - distress sensed from filings and performance together, the exit plan ready before the failure. --- ## The pain *"We discovered the dependency the day it broke."* The firm's suppliers are onboarded once and then watched by calendar, if at all. The signs that one is in trouble - an SLA drifting over consecutive periods, late accounts or a new charge in its filings, an incident, a concentration that has crept past what is safe - arrive in procurement, in ops, in finance, and are never joined. So a supplier's distress is read off a single late delivery, and the concentration risk is understood the day the dependency fails, when the exit that should have been ready is started from scratch. In wealth and insurance this is the outsourcing register and resilience rules; in distribution, the supplier and logistics base; in legal, counsel and experts. ## What the block is The object is each supplier, introducer or outsourcer - one continuous picture per relationship, from onboarding through performance to exit. Everything it produces feeds one live record: onboarding and due diligence, SLA performance, public filings, incidents, renewals and concentration. A model reads it permanently. Your procurement, contract and register 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 catch. A supplier's SLA has drifted three periods running, and its latest filings show accounts filed late and a new charge over its assets. Either alone is a shrug; together they are distress. The block reads them as one picture and readies the response before the failure: *"this supplier is deteriorating on performance and on its balance sheet; the exit plan is checked and ready to run."* The dependency you would have discovered the day it broke is handled while there is still a choice. - *the dial: recommend* [MOMENT: styled quote panel] A concentration threshold is crossed - too much of one critical function resting on a single supplier. The block surfaces it with diversification options drafted, not as an abstract risk-register line but as a decision ready to take: *"you are now concentrated here; here are the alternatives and the switching cost."* - *the dial: recommend* [MOMENT: styled quote panel] An incident is logged at a supplier ⇄ the resilience loop. The block maps the blast radius across the services that depend on it and demands remediation with the dependency picture attached - the question "what else does this touch?" answered in minutes, not assembled in a war room. - *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 procurement or resilience lead 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. Supplier exits and renegotiations stay behind a human gate - 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: your most concentrated dependencies - the suppliers you could least afford to lose - 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 suppliers: one that failed with warning you did not read, one that failed without any, and one you were too concentrated on to replace when you needed to. What did your own record 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%20third-party%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/)