Services you can engage us for
Engage us for a new project, recovery of an existing model or support after go-live.
Anaplan & Pigment implementation
We design and build budgeting, financial forecasting, demand or capacity models with the required calculations and access rules.
Deliverables : Tested models, user views and documentation.
Model audits & optimisation
We diagnose slow performance, data discrepancies and maintenance difficulties, then implement the fixes agreed with you.
Deliverables : Prioritised diagnosis and verified fixes within the agreed scope.
Integration & ongoing support
We connect ERP or BI sources, improve data loads and train administrators. Support and improvements are scoped around your needs.
Deliverables : Validated data flows, operating procedures and knowledge transfer.
An approach tailored to your engagement
We agree the steps needed for your scope. An audit or assessment can be commissioned separately, without committing to implementation.
01. Observe a complete cycle
Map inputs, decisions and manual rework. Deliverable: a prioritised diagnosis separating verified causes from open questions.
02. Build a usable first cycle
Model a representative scope and reconcile it to source data. Deliverable: a testable cycle and explicit deferred scope.
03. Prepare operations
Have users run the cycle, test exceptions and prepare recovery. Deliverable: acceptance records, operating guidance and post-delivery ownership.
Illustrative example, not a client engagement
A sales forecast changes after approval
Illustrative example: a team changes a volume assumption after the forecast has been approved. The model must preserve the approved version, recalculate the working scenario and expose the margin and capacity impact. Acceptance checks reconciliation, traceability and publication permissions. The number of screens delivered does not establish success.
Before you start
Must we choose Anaplan or Pigment first?
Initial scoping lets you compare platforms against the same scenarios. If the choice is already made, we document the constraints and trade-offs within that environment.
Can you help without rebuilding?
Yes, subject to diagnosis. Targeted changes to loads, calculations or the process may suffice. A rebuild needs documented reasons and a transition plan.
How is success measured?
Through a real cycle: reconciled results, manual rework, approval times and the team's ability to operate independently. Thresholds are agreed during scoping.
What happens after delivery?
After the first cycle, support can cover defects, processing times and administrator autonomy. Changes enter a business-prioritised backlog; their impact on calculations, data and the planning calendar is assessed before release.
What determines the budget?
Processes, reference data diversity, integrations, historical data and contributor availability drive effort. Licences and recurring support should be separated from implementation costs.
Discuss your project
Starting a project or unblocking a model?
Tell us which cycle and tool are involved and where you are getting stuck. A few lines are enough to begin.