One platform, three surfaces

Before Pantry, Hangry ran on a third party HRIS (Mekari Talenta) that fanned out across three separate surfaces and two very different audiences. Understanding its full shape came first, so the scope of what we would rebuild in house was clear.

Dozens of features across the stack

The platform spanned three layers of HR, from day to day core operations to strategic tooling. Rebuilding all of it in house was never realistic in the time we had, which made auditing the full surface area essential.

40+ features across 3 HR layers, 3 surfaces, and 2 audiences.

Where the subscription cost actually sat

The clearest signal for what to prioritize was the third party subscription bill. Operational accounts and the outlet portal dominated the annual cost, while HQ was a rounding error by comparison.

Operational cost ~8× more than HQ, and carried the heavier day to day reliance.

Operational first

With cost and reliance both pointing the same way, I made the call: build the operational surfaces and the admin back office first, and defer only the HQ user app to after launch.

From requirement to live, then improve

With scope set to operational first, this was the P0 plan to reach go live before April. Everything here shipped for launch. The HQ app and deferred features became P1 and P2 after live.

Every step above was P0, delivered before and around go live. The HQ app and the features we deferred became the P1 and P2 roadmap after launch.