For ENSEK · Data & Reporting · the 'deliver, don't apply' proof

Here's your work.
Here's the AI that does most of it.

You're hiring a Senior Data Analyst. We took the job description apart, built an agentic system that genuinely does the automatable two-thirds of it — live, in your browser, not slides — and we'll show you exactly which third still needs a person, and why. Then we'll tell you the headcount you'd actually hire.


01 · The work

A Data Analyst's job, decomposed.

Straight from the ENSEK Senior Data Analyst JD (Nottingham) and the standard energy-retail data-team remit. Twelve tasks, graded honestly: what an AI does end-to-end, what it drafts for a human to own, and what stays human.

TaskVerdictWhy
Routine SQL pulls / ad-hoc data questionsautomateDeterministic, checkable. Demonstrated.
Dashboard drafting & refreshautomateSpec→query→chart is mechanical. Demonstrated.
Billing-discrepancy / reconciliation auditautomateRecompute the whole book each cycle. Demonstrated — 114 flagged live.
Estimated-read / data-quality monitoringautomateContinuous cohort detection. Demonstrated.
Debt-book & early-arrears detectionautomateBilled-vs-paid arithmetic. Demonstrated.
Decision-ready report draftingassistAI drafts; analyst owns the interpretation. Demonstrated.
Metric-definition governanceassistAI proposes & enforces one definition; human signs off. Demonstrated.
A/B test design & read-outassistAI computes; human owns validity & the ship call.
Stakeholder framing of ambiguous problemshuman-onlyNeeds org context, politics, judgement.
Coaching / raising analytical standardshuman-onlyMentorship is a human relationship.
Customer corrections, refunds, collectionshuman-onlyAccountable to customer + Ofgem. AI detects; a person decides.
Pricing / tariff decisionshuman-onlyRegulatory, fairness, commercial weight.

Five of the highest-volume tasks are demonstrated running live on the next page — over a synthetic ENSEK-shaped dataset, computed in your browser. Not a mock-up. Edit the SQL yourself.


02 · The system

An agentic backend pointed at the automatable work.

Ask in English

The agent translates the analyst's question into SQL — and exposes the SQL so it's auditable, not a black box.

Runs for real

Queries execute live against the data. Billing reconciliation re-derives every charge from tariff maths — across the whole book, every cycle.

Writes the read

Each result comes with a decision-ready narrative and a recommended action — drafted for a human to own.

Knows where to stop

Every output names its human control point. The system is built to hand off, not to overreach.

Open the live analyst →


03 · The headcount you'd actually hire

The function doesn't go to zero. It changes shape.

Fewer hands turning the SQL crank. The people who remain are accountable owners and judgement roles — not query-writers. Post-automation, this is the team we'd argue for:

RoleHeadsWhy it survives automation
Analytics lead / owner1Owns metric governance, signs off canonical definitions, accountable for what the AI ships.
Billing / assurance analyst1–2Adjudicates flagged discrepancies, owns customer-facing corrections & regulator-facing accuracy.
Data engineer1Owns the pipelines & tariff/reference data the AI depends on. Garbage in still means garbage out.
Senior / principal analyst1Problem framing, experiment validity, exec partnership, coaching — the human-only column.

The role that's absorbed: the 'write-the-SQL, refresh-the-dashboard' recurring-production headcount. You hire for accountability and judgement, not throughput. See the full human-core argument →


The provocation

You advertised one job.
Here's the system that does most of it — built before the interview.

This is what 'deliver, don't apply' looks like at org scale: real, sourced, dated, and running. The question isn't whether the work can be automated. It's which third you want a person accountable for.