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
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.
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, or write to hello@somai.studio.
Runs on our framework · related reading: Most AI spend never reaches the P&L