Services Products Cases Contact Talk to us
Services  /  Connected planning
Services · Connected planning

Connected planning

Planning models on Anaplan where finance, demand, supply and sales feed each other, not a model per department. Built by people who ran planning in consumer goods.

One set of master data, one number at the review.

You are in the right place if

  • Planning still lives in spreadsheets: hundreds of files, one owner each, and a market signal that takes two months to reach the P&L.
  • Anaplan is in, but the model is slow: workspace is full, calculations take minutes, users went back to Excel.
  • The model works and nobody can change it: the builder left, and every change request waits for a consultant.
  • Finance, demand, supply and sales each plan in their own model, and the numbers meet once a quarter.
  • Twenty sources feed the forecast, and nobody can say which one moved it this week.
  • You want AI in planning — forecasting, agents, explanations — and the model is not ready for it.

What's included

Implementation and model design

A model designed around your process, not a template: discovery, design sprint, build in increments, user acceptance, go-live. Connected by design: the demand model feeds supply and finance, a price change in the sales plan shows up in the P&L the same day, one set of master data serves all of them. Fixed price for a defined scope.

Performance, workspace and model health

For models that grew faster than they were designed to. Performance and workspace optimisation, model re-architecture, a UX that users actually open. The entry point is a model health check: one to two weeks, a prioritised report, not fifty pages of screenshots.

Managed service and training

Named people, agreed response times, monthly releases: your model keeps evolving with the business without an internal team of model builders. Anaplan support fixes the platform; we fix and evolve your models. Training for model builders and end users; a centre of excellence coached until it stands on its own.

Data integration

Pipelines between Anaplan and your ERP, data warehouse, BI and external sources: Anaplan Connect, CloudWorks, APIs. The same master data in the model and in the systems around it.

AI in planning

PlanIQ forecasting, CoPlanner and CoModeler enablement, role-based agents in Anaplan; custom forecasting and uplift models feeding the planning model; an agent over the model that answers "why" with the drivers.

Models we have built before

  • Demand planning from sell-out. Forecast by customer warehouse, shipping warehouse, SKU and week, with 20+ signals and the forecast decomposed by driver.
  • Cost of goods and recipe modelling. Raw material cost from recipes, prices and volumes; what-if for procurement; recipe changes with quality thresholds and their financial effect.
  • Logistics cost forecasting and modelling. Transport and storage cost from volumes by customer and SKU; bridge reporting by driver; scenarios for pack size, supply chain and palletisation.
  • Production cost and prime cost consolidation. Factory costs, transfer pricing inside the model and hidden from those who must not see it, non-quality cost tracked separately, consolidation across markets and factories.
  • FP&A. Budget and rolling forecast, driver-based P&L, scenario planning, variance bridges.

Why connected planning

A model per department reproduces the spreadsheet problem on a better platform: finance plans revenue, supply plans volume, sales plans accounts, and the three numbers meet once a quarter. Connected planning means the demand model feeds supply and finance, a price change in the sales plan shows up in the P&L the same day, and one set of master data serves all of them. That is what we build, and the reason our models for cost of goods, logistics and demand are designed to talk to each other from the start.

How we start

  1. Discovery sessionOne hour, your process and systems; a written scope within a week.
  2. Design sprintTwo to three weeks: data model, user stories, prototype dashboards; a fixed price for the build.
  3. Build in incrementsReleases every two to four weeks with your users in the loop.
  4. RunManaged service or a hand-over to your centre of excellence.

Why us

  • Consumer goods is our domain.Sell-out, promo uplift, prime cost, transfer pricing, trade spend: we have modelled them before.
  • Senior people, small team.The architect who scopes the work builds it.
  • Fixed price for defined scope.Implementation phases and health checks at a fixed price; managed service on a monthly retainer.
  • Team extension.We also work as an extension of in-house teams and of larger integrators on multi-market programmes.

Bring us the model that hurts

The slow one, the one nobody can change, or the one that still lives in Excel. One discovery session and you get a written scope.