Operations intelligence · UK Amazon DSPs

The intelligence layer for Amazon DSPs.

NEXUS·DSP reads every Amazon file the moment it lands. The week's decisions come back: drivers to coach, metrics to improve, messages already written in contractor-safe language.

Request access See how it reads

ComplianceCyber Essentials certified

DataUK residency · GDPR aligned

Trial14 days, no card

Weekly Service Overview · Station · XYZ1 Week 16 · 2026

Driver 047 ★ EliteA3JK9X8P2LMNQ1

99.91

100.00

97.2

Driver 012 SLA+B7RT8N4K1XQMW2

99.64

340

99.21

99.48

420

89.4

Driver 021 SLAC9LV5M6P3BXKT8

99.18

710

98.44

98.22

1 620

82.1

Driver 034 SLA-D4WR7T9Q5HPZJ6

98.62

1 104

94.32

97.11

3 106

68.9

Driver 019 SLA-E2MC3F8L0VNRK4

98.11

1 248

97.20

93.05

2 410

61.2

Driver 029 CRITF8ZP1N6R2DBXJ9

96.08

2 180

88.14

84.22

5 620

43.5

Driver 034Week 16 · 2026

Service data for this week:

DSC rising for 3 weeks · 1,104 DPMO this week.
POD at 94.3% of required captures.
Tier SLA-, 6.1pts below the SLA band.

Reference sheet attached for self-review

Pattern read · Driver 034

3 weeks of DSC rising. DCR holding. Coaching signal, not noise.

The read

Intelligence across files, not just within them.

Every Amazon file makes sense on its own. The full picture lives in how they connect.

A driver's completion rate drops. Their customer feedback doesn't move. Those two facts read one way on the scorecard and another way together. The full story only appears when you read them alongside the POD file, the concession log, and the contact records for the same week. NEXUS·DSP is built to do exactly that: every file against every other file, every week, with the intelligence handed back ready to act on.

Pattern

Driver 034 · DSC rising, DCR holding · 3 weeks running

Cluster

Concession pattern concentrates on 6 drivers across 4 weeks

Evidence

DCR defence pack · GPS, scan sequence, contact log

Draft

6 driver conversations · contractor-safe, ready to send

Capabilities

Six capability areas. One intelligence layer.

Every Amazon file connects to the others. NEXUS·DSP reads across them and delivers six readings of the week: diagnosis, patterns, action.

Every metric drop has a reading underneath.

Cross-references the scan distance from the pin, the contact attempts, the POD audit state, and the delivery method for every concession in the file.
Flags the same pattern recurring across drivers or weeks — photo skipped, contact not attempted, scan outside the geofence — before it shows up as a scorecard hit.
A score change stops being a number and starts being a list of specific reasons to look at.

Every metric drop has a reading underneath.

Cross-references the scan distance from the pin, the contact attempts, the POD audit state, and the delivery method for every concession in the file.
Flags the same pattern recurring across drivers or weeks — photo skipped, contact not attempted, scan outside the geofence — before it shows up as a scorecard hit.
A score change stops being a number and starts being a list of specific reasons to look at.

Stop reacting to the scorecard. Start reading ahead of it.

Automatically segments your driver pool into Elite, Solid, Developing, or At Risk based on how each driver's week actually looks, not just the tier they landed in.
Tracks week-on-week momentum, so you see exactly who is improving and who is slipping before it shows on the scorecard.
One driver, one screen, the whole week already read.

The pattern a single week can't show.

Measure each driver against their own historical baseline and their station peers, so the number arrives with context.
The driver who repeats, the driver who drifts, the problem that keeps reappearing.
Every pattern comes with the week-by-week detail that built it — so the team reads the story, not just the summary.

Yesterday's slip, today's fix.

Compresses every daily file Amazon sends into a single read, the morning after.
Keeps every metric visible between weekly scorecards, so no dip goes unseen.
Catches daily compliance drops before they drag down the weekly tier.

Generic feedback doesn't change behaviour. Context does.

Every coaching message arrives already written, specific to the driver's week — not a template pulled from a drawer.
The message names what happened, where it happened, and what the delivery record actually showed.
Your team spends the conversation coaching, not building the case for coaching.

Every message, contractor-safe by construction.

Strips imperatives and second-person commands from every draft before it leaves.
Rewrites directive feedback into neutral statements of what the delivery record showed.
Contractor-safe language enforced across UK, EU, and US jurisdictions.

The evidence

Three weeks. Three patterns. One read.

Every weekly file, every daily file, every week of history, cross-referenced into a single read. These are three real patterns NEXUS·DSP caught that a single scorecard couldn't.

Driver pattern

Driver DR-412

W14 → W16 · 2026

POD score · 3 weeks

The read

Three consecutive weeks. POD score dropping. Contact log clean, geo distance within range. The pattern is the photo.

POD audit fails

9 of 14 deliveries flagged unattended-no-photo

Triangulation flag

PHOTO_SKIPPER (severity: HIGH)

History

First flagged W14 — no prior PHOTO_SKIPPER events

Momentum

Declining across 3 consecutive weeks

Contact compliance

100% — call log clean

Geo

All scans within geofence

Driver-origin. Coaching draft queued, photo-capture specific.

Failure-type pattern

Station-wide · 6-week window

W11 → W16 · 2026

Concession types · station-level

UNATTENDED-NO-PHOTO47%

LOCKER-DECLINED18%

OTHER15%

CUSTOMER-UNAVAILABLE14%

DAMAGED-ON-ARRIVAL6%

The read

Nearly half the station's concessions share one failure mode. The pattern points to a procedural gap, and responds to station-wide remediation, not individual coaching.

Concession total

89 station-wide, W11–W16

Top failure mode

Unattended-no-photo (47% of all concessions)

Driver spread

Affects most drivers at the station

Pattern consistency

Same top-3 failure mix every week for 6 weeks

Station-wide pattern. Photo-capture procedural refresh recommended before individual coaching.

Cross-file anomaly

Station DSA1

W15 · 2026

File correlation · 5 sources

The read

Two files clean. Three diverge. The daily concession records and the DWC report don't support the scorecard aggregate, a gap that predates W15.

Concession count (DSC)

47 this week · station-level

DWC violations

23 flagged, 11 auto-exempt

Scorecard tier

Fair (historical: Fair → Fair → Fair)

Delta from daily signal

-12.4% vs expected

Raw files divergent. Station-level DSC review suggested before tier interpretation.

The gain

What happens when the reading catches up.

Twelve weeks of the same station. Same vans, same roads, same drivers. Only the reading changes — and the tier bands follow.

The Gain · composite station · twelve weeks Illustrative

25+ hrs/week Back in the operator's week

24 of 48 Drivers in the top two tiers

Fantastic+ Station band · from Great

Illustrative composite · station-level band movement varies with fleet size, route mix, and driver continuity.

Pricing

Three tiers. Monthly. No contract.

Fourteen-day trial on any tier, no card. Prices in pounds sterling, exclusive of VAT where applicable. All tiers include the IR35-safe language engine — it is not an add-on.

Pro

The foundation

£99/ month

1 station · up to 2 users

The full weekly scorecard, read Wednesday morning
Every driver scored on the 8-metric model
Daily compliance reading (RTS, CC, POD, false-scan)
Contractor-safe language across every driver message
Fourteen-day scorecard history
Automatic dispute drafts for code-eligible concessions
Postcode pattern analysis
Multi-station command view

Start Pro trial

A name. A standard. A real conversation.

Every message NEXUS·DSP drafts for a driver is written in observational, non-directive language. No "you". No "next time". No instruction. Every string passes through an IR35 filter before it renders — because the alternative is employment-tribunal exposure, and the data doesn't need the adjective to carry the weight.

DSP drivers are self-employed contractors. Every message that reads like supervision — "You should…", "Next time, make sure…", "Walk to the front door before scanning" — is evidence in an employment-status tribunal. Written warnings. Performance reviews. Mandatory training. Each is employer-employee vocabulary a tribunal looks for. A reclassification finding makes the operator retrospectively liable for PAYE, NI, holiday pay, and sick pay. Multiply by every driver on the roster and the exposure is existential.

NEXUS·DSP rewrites every driver-facing message into observational audit language before it leaves the platform.

The old way

Manager's message · Week 16

Hi [Driver], We need to discuss your performance. Your POD is at 94% and you should be hitting 98. Next time, make sure you photograph every delivery before walking back to the van. Consider this a written warning — 3 customer complaints this week. You need to work on your customer service. Please complete the POD training module before your next shift. Team meeting Friday 8am — attendance required. Thanks, [Manager]

⚠ Employment-status risk
Written warning · Performance review · Training mandate

NEXUS·DSP

Driver 034 · Week 16 · NEXUS·DSP draft
Generated 2026-W16 · service-spec referenced

Hi Driver 034,

SLA-aligned metrics:

No metrics within SLA threshold this period.

Observations against the service specification:

POD compliance recorded at 94.32%. The service specification requires 98.5% of captures to meet platform verification standards.
DCR recorded at 98.34%. The service specification requires 99.2% delivery completion for SLA alignment.
Tier: SLA- (6.1pts below the SLA band).

Reference sheet attached for self-review.
Relevant Learning Centre topics available in NEXUS → Learning Centre.

This update is provided for informational purposes only and reflects platform verification data. It does not prescribe how services are performed. Contractors retain full discretion over the manner and method of service delivery, subject to contractual and platform requirements.

✓ IR35 filter passed
Zero second-person · Zero imperatives · Spec-referenced

Closing note · from the desk

Let us read your next scorecard with you.

Thirty minutes with the founder, a screen share, and this week's live files. NEXUS·DSP processes them live. If we can't surface a root cause or pattern your scorecard missed, the call is over. No pitch. Just proof.

Book a 30-minute read Email the desk

Prefer a form? Submit your details →

— Trust · verify independently