
Digital engineering firm, Polaris migration
A model at its ceiling, rebuilt with room to grow.
THE CHALLENGE
Finance had a model close to 300GB and a growing list of things they had been told weren't possible. Not because the requirements were unreasonable, but because a Hyperblock model at that size has nowhere left to put them. Optimisation had been exhausted. The question was no longer how to make the model smaller, but whether the engine underneath it was still the right one.
.webp)
WHAT WE DID
A Polaris migration done as a lift-and-shift produces a Polaris-shaped Classic model, and the gains disappear. Sparsity behaves differently on the new engine, so the structures that made sense under Hyperblock are rarely the ones that make sense after. We redesigned for how Polaris actually stores and calculates, then rebuilt to that design. Ten weeks, one solution architect and two model builders, and a model that came out at 15GB.
Redesigned for Polaris
Structures rebuilt for how Polaris actually stores and calculates, not ported from Hyperblock.
Small Team, Ten Weeks
One solution architect and two model builders.
Room to Grow Again
A model at its ceiling now has headroom.
THE RESULT

For the first time in a while, I felt optimistic about what we could do with Anaplan. More importantly, we started seeing that potential become real.
MORE CASE STUDIES
Proof that the plan can actually work.
Rollout recoveries, platform migrations, and end-to-end builds — real outcomes from other Anaplan engagements.
Where do you want your planning to be next year?
Planning that's slower than business needs, forecasts nobody acts on, an Anaplan investment that isn't paying back. Describe it and we'll tell you honestly where we can help.






