Move-in/move-out & account lifecycle PM · vacancy
Here's what AI can do for this role — and what still needs a human. Built straight from ENSEK's own job advert, running live on my_db.ensek_demo.accounts. Not a slide about AI. The job, getting done.
Every line on the left is lifted from ENSEK's actual job ad. If a card lacks a harvested JD line, it is omitted. On the right is the AI doing it — with eligible cards running live against the warehouse and offline inspection clearly labelled in the workspace.
“Own the strategy, vision and roadmap for Home and Business Moves across domestic and B2B journeys”
How long do customers stay — tenure distribution across the active book, with revenue and churn signal?
bar chart“Deliver an end-to-end move experience, from notification through to billing handoff”
What's the current state of the book — active, pending and closed accounts by fuel type?
table“Design scalable solutions to support international markets and regulatory frameworks”
Where does churn risk concentrate — established versus new customers, by tariff type?
bar chart“Partner across product and engineering to ensure robust integrations with industry systems”
What's the recent acquisition shape — new accounts (under 12 months tenure) by region and tariff?
table“Drive AI-led innovation, including intelligent exception handling and automated occupancy detection”
How does the active book split by fuel type — and does dual-fuel tenure and churn differ from single-fuel?
kpiThe honest other half. AI does the analysis; a person owns the decision — especially where regulation, fairness and accountability bite.
A plain-English question — the same one the job ad describes — is translated to SQL by the agentic backend.
Curated cards run server-side against MotherDuck when eligible. The workspace separately labels any local inspection path.
Runs against my_db.ensek_demo.accounts. No synthetic numbers.
Each figure carries a falsifier — recomputed from the result set, not a stored number, so it can't quietly drift.
It's the role getting done: curated questions run live server-side against the warehouse; local inspection is labelled inside the workspace.
Open the live workspace →Provenance. Representative ENSEK-style operational dataset (480 accounts · 424 active · 5,676 monthly consumption records). Schema mirrors my_db.ensek_demo.accounts. Seed 20260609 — reproducible. No real ENSEK or customer data.
It's Sorted — I took ENSEK's job ads and didn't write a report on what AI could do. I built it. Get the rest sorted →
I'm trained on this proof and the real ENSEK: the Ignition meter-to-cash platform (seven modules), the move under Centrica in 2024, 7M+ energy accounts migrated for suppliers like British Gas and Utility Warehouse, and the Ofgem framing. Ask me how the Data Analyst function changes shape, or which open roles map to which Ignition module.