Loading...
Loading...
Digital publishing — one console for 180,000 subscribers' churn risk, instead of a weekly export.
Project details — company names, locations and other identifying specifics — have been anonymised. The brief, the discovery work and the interactive wireframe are the real output our build engine produced.
A digital news publisher has 180,000 digital subscribers, and retention work was stuck between a weekly reporting pull and a separate campaign tool. By the time a subscriber looked "at risk" in a report, the save window had often already closed.
Scores churn risk continuously from engagement recency and reading depth, not on a weekly cycle
Triggers save-offer journeys automatically into the team's existing campaign tool
Queues at-risk subscribers for a specialist's outbound call before they lapse, not after
VP Audience, accountable for the 12-month retention target
A retention console scoped to this newsroom's exact signals and workflow, not a general-purpose marketing suite retrofitted to fit.
Click around — this is the real output, not a screenshot.
Rust + Axum · PostgreSQL · Next.js + React
There's no self-serve sign-up yet — every build starts with the Founding Programme.
Wealth advisory — suitability reviews that run themselves before a recommendation goes out.
Commodities trading — a live hedge book instead of a spreadsheet reconciled once a week.
Primary care — replacing paper charts and phone bookings for a 3-clinic GP group.