Risk is measured to the basis point. The judgement pricing that risk is measured by whether someone looks tired.
Sloane Labs is the human performance layer for financial institutions. It reads cognitive readiness across deal teams, desks and risk functions, forecasts where judgement quality will fall short of the calendar, and acts before it shows up in a mispriced decision.
The expensive failure is not a mistake anyone reports. It is a decision made a grade below the team's ceiling.
Every market and credit exposure in the institution is quantified continuously. The cognitive state of the people setting those exposures is assessed by observation, in a business where a single narrowed judgement outweighs the entire cost of instrumenting the floor.
The deal calendar is not smooth. Diligence weeks, closings, quarter end and results cycles create predictable spikes that arrive on a known date. Load can therefore be forecast rather than discovered, and cover can be moved before the spike rather than after it.
Four places capacity turns into outcome
The desk
Execution quality and adherence to limits both degrade with sleep debt long before anyone reports feeling tired.
The deal team
Fatigue makes diligence narrower rather than slower.
The risk function
Second line challenge is cognitively expensive and socially costly.
The junior pipeline
Two years of training walks out at the point where the investment starts returning.
A deal cycle, read the way you read an exposure
Team readiness across a live process, with the forward projection that lets you rotate cover, move a milestone or protect a weekend before the trough arrives rather than after the close.
Select an operating state to redraw the forecast.
Steady mandate load, no live process. Recovery clears week to week and readiness holds inside the tolerance band.
No intervention. The Monday brief confirms capacity is available for an additional mandate.
What we read, and what each signal decides
A signal earns its place only if it changes an operational decision. Anything that does not is telemetry for its own sake.
What is actually running, not what is on a roadmap
Morning readiness brief
A single page before the morning meeting. Cohort readiness, what changed overnight, the two teams to watch, and one recommended action.
Cohort readiness by team
Coverage, execution, markets and risk reported as separate cohorts with trend lines across the year. No cohort renders below five people.
Forward risk alerts
When a team is forecast to cross a readiness threshold inside 72 hours, the alert fires with contributing factors and stated confidence.
Staffing simulation
Model a process before you commit the team. Add cover, move a milestone or change the split and see the projected readiness effect through to close.
Individual agent, opt in only
Bankers who opt in get their own coach: recovery targets through a process, travel and sleep guidance, answers grounded strictly in their own data. Nothing is visible to management.
Conduct evidence record
An aggregated, anonymised record of how working hours and load were managed. Defensible with the board, the regulator and staff representatives.
Reading human capacity only works if the boundary is unambiguous
Trust is the adoption constraint. These are commitments, written into the agreement, not preferences.
Never a performance management tool
Explicitly excluded from ranking, bonus, promotion and disciplinary process. That exclusion is contractual and enforced in the data model.
Opt in, always
No one is enrolled by default. Participation is individual, explicit and revocable at any time, with data deleted on withdrawal.
Five person minimum cohort
Aggregate views suppress any group smaller than five. Leadership sees cohorts, never a named individual's physiology.
Metadata, never content
Calendar and messaging integrations read timing, density and participant counts. Titles, bodies and message content are masked at ingestion and never stored.
Separated from selection
Contractually and architecturally excluded from selection, appraisal and disciplinary processes. That separation is written into the agreement.
UK GDPR and DPIA ready
Lawful basis, retention schedule, data subject rights and a pre drafted DPIA template supplied for your DPO before the first device is connected.
Every exposure is priced to the basis point. The judgement setting it is priced by instinct.
An eight week pilot with a defined exit
We take a small number of design partners per sector. A partner shapes the roadmap directly, gets preferential terms, and keeps the right to walk away at week eight with no obligation.
Scope and governance
Agree cohorts, success measures and the data boundary. DPIA reviewed and signed. Integrations connected in a sandbox with a small internal group.
Baseline
Volunteers connect wearables and calendars. Individual baselines establish across a normal cycle and a peak one. No alerting yet, observation only.
Live briefing
Morning readiness briefs start reaching leadership. Forecast alerts switch on. Calibration against what the organisation already believes about its own load.
Readout and decision
Joint review of accuracy, adoption and the decisions the signal changed. Written readout, roadmap input, and a clear go or no go.
What we need from you
- One executive sponsor with authority over how work is scheduled
- Twenty to fifty volunteers across two or three cohorts
- Calendar and messaging integration approved by IT and the DPO
- Two review sessions across the eight weeks
What you get
- Full platform access for the pilot cohorts, configured to your operating calendar
- Direct roadmap influence on capability specific to your sector
- A written readout of accuracy, adoption and decisions changed
- Preferential terms and first refusal on the sector in your market
The questions we get asked first
Is this a wellbeing programme?
No. It is a decision quality system. Wellbeing programmes ask people how they feel and offer resources. Sloane measures capacity against the deal calendar and changes decisions: staffing, milestone timing, coverage and redistribution.
Does it read our deal or client data?
Never. Calendar and messaging integrations read timing, density and participant counts only. Titles, bodies, attachments and client identifiers are masked at ingestion and never stored.
Could this be used in performance reviews?
Architecturally, no. Individual physiology is never exposed to management; leadership sees cohorts of five or more. Use in ranking, compensation or disciplinary process is contractually prohibited.
How does it help with working hours commitments?
It produces the aggregated evidence record most institutions currently lack: how load was distributed, where it spiked, what was done about it, and whether the intervention worked.
What does integration require from technology?
OAuth connections for calendar and messaging, and individual device authorisation for wearables. No endpoint agents, no network changes, no access to trading, banking or client systems.
How do we know the signal is real?
Every score is deterministic and reproducible from versioned features, every forecast carries stated confidence, and the pilot readout compares prediction against what the desk observed.
Price the human variable the way you price everything else
A thirty minute conversation covering the architecture, the data boundary and what an eight week pilot would look like inside your institution.