One engine.
Three audiences. Three views.
The same underlying finding renders three ways for three jobs-to-be-done. The detection logic is shared; the surfaces are not. Use this page to explain Relo's architecture in client conversations.
This single record — produced by the detection engine — is what each surface below transforms for its audience. Identical inputs. Three different outputs.
A short, ranked task.
Bilal opens Teams at 7:45 AM. He gets the top-3 priority transfers ranked by impact. One tap acts.
Surface character:in the workflow, in Teams, single-tap, ranked. No navigation, no exploration. The allocator does not need the why — they need the what.
A diagnostic with a prescription.
Faiza opens her Monday briefing. She sees the pattern, the SOP gap behind it, and what to act on.
Black school shoes (32–38) sitting on 6+ wks cover at Lahore Defence and Karachi Clifton. Faisalabad, Multan, Peshawar OOS for 4+ days. Eid peak in 14 days.
Prescription:Generate 14 transfers · 1,840 units. Freight Rs. 1.4 L. ROI in 5 days.
Surface character: diagnostic and prescriptive. Includes the why and the SOP gap. Faiza needs to defend the call to her CEO and brief her allocator team.
A narrative with implications.
Mr. Malik reads the monthly briefing. He sees the pattern as a story, the captured value, the strategic ask.
Stock is rarely missing from the company. It's usually missing from the right store.
Of the Rs. 1.84 Cr leak detected in April, Rs. 62 L (34%)was network rebalancing lag — situations where the company collectively had enough stock to meet demand, but it was sitting in the wrong stores.
The classic example, repeated four times across April: a surge in school-shoe demand in Punjab cluster coincided with overstocked Karachi Clifton and Lahore Defence stores carrying 6+ weeks of cover. Transfer cycle averaged 4.2 days against a benchmark of 1.8 days.
The fix is not technical, it's procedural. Our current SOP triggers transfers only when a store hits OOS. The recommended change is to trigger when a recipient drops below 1.5 weeks and a donor exceeds 5. Estimated annual upside: Rs. 1.4–1.8 Cr.
Surface character:editorial, narrative, framed as story. No tables, no widgets. The exec is making a strategic call — not approving a transfer.
The wedge that doesn't fit a single screen.
Most stock-intelligence products try to serve all three audiences with a single dashboard, then bolt on role-toggles. That's the messy hybrid. Relo is a clean hybrid: shared engine, distinct surfaces.
The detection catalogue is the compounding asset. Each new SOP gap discovered for one client benefits all clients. Builds a moat that competing dashboards cannot match.
The allocator, the manager, and the CEO need different things from the same finding. Forcing one screen to serve all three produces a screen that serves none of them well.
Each surface lives where the audience already works. Allocator gets Teams. Manager gets a briefing. Exec gets a PDF. Relo is non-invasive — no new tool to adopt.