What real implementations look like

Renaissance is one of the largest education SaaS companies in the world, with roughly $3 billion in annual sales. When they came to PlanFlamingo, their compensation process was largely manual — manageable in a spreadsheet world, but increasingly untenable at 350–400 North American sellers and growing.

We built their commission calculation engine in Anaplan for the North America team first, covering account executives, CS teams, and SDRs across the full range of plan structures — multi-tier logic, accelerators, overrides, and everything in between. Attainment tracking updates daily, so reps always have a current view of where they stand. We then extended the same infrastructure to their Global team, which added another 150–200 sellers across additional territories and plan structures.

On disputes: Full visibility into commissions surfaced disputes that had previously gone unresolved. Rather than treat this as a problem, we built a structured dispute management workflow directly into the model — so every dispute has an owner, a resolution path, and a closed-loop outcome. The process that used to happen over email now lives in the same place as the commission calculations themselves.

We also built their territory and quota modeling — account segmentation, territory mapping and balancing, and a quota-setting framework that connects capacity assumptions to achievable targets before plans go live. PlanFlamingo has been managing and evolving the Renaissance Anaplan environment for over four years.

Riverview LLP had been on Anaplan for seven years. In that time, the model had grown around their business rather than with it — logic layered on logic, workarounds built on workarounds. It worked, mostly. But finding data in it was hard, understanding it was harder, and making changes was something only a specialist could do. The team had stopped trying.

We migrated Riverview from Anaplan to Pigment — not just a platform swap, but a full rebuild of how their planning works. We started from first principles: what does this business actually need to model? The result is a unified Pigment environment covering cattle projection, P&L, feed production, labor, balance sheet and cash flow, CapEx and debt, and project management — all in one place, all connected.

The most significant change wasn't in the platform — it was in who can use it. On Anaplan, the model was effectively inaccessible to the people it was meant to serve. In Pigment, the Riverview team navigates it themselves. They know where their data is. They can make changes. They've connected the AI functionality to their planning workflows. The model went from something that existed for compliance to something people actually rely on.

This engagement is a good illustration of something we see often: the platform isn't always the problem, but the architecture is. Seven years of Anaplan wasn't wasted — it meant Riverview knew exactly what they needed. Starting clean, in the right place, made all of it work.