Pigment Implementation: What UK Finance Teams Need to Know
The honest version. Not the sales deck.
You've seen the Pigment demo. The interface looks slick, the scenario modelling looks impressive, and your CFO is now asking about timelines and costs. The question you're left with is whether it will make your life easier or just hand you a different set of problems.
We've implemented Pigment for insurance businesses, SaaS companies and professional services firms across the UK, and a few patterns come up on every project.
What Pigment Is (And Isn't)
Pigment is a cloud planning platform for budgeting, forecasting, scenario analysis and reporting. The interface is modern and well designed, and users tend to find it quick to pick up. After proper training, finance people can usually build simple models themselves.
What it isn't is a fix for broken processes. If your current planning approach is chaos, Pigment will give you faster, more collaborative chaos. You need to know what you're trying to achieve before the software can help.
Pigment is a newer entrant to the EPM market, and that shapes where it's strong. The interface benefits from modern design thinking, while some of the deeper enterprise features are still maturing. If you need complex multi-currency consolidation with minority-interest calculations across dozens of entities, Planful or IBM Planning Analytics may be a better fit for those specific requirements.
When Pigment Makes Sense
You're drowning in spreadsheets. The budget lives across dozens of Excel files, version control means bolting "_v3_FINAL" onto filenames, and one overwritten formula can cost you a day of rework. Pigment consolidates that into a single model with real-time updates and a proper audit trail.
Your team hates the current tool. You might have an EPM system already, but adoption is poor, and people export to Excel because the day-to-day experience is painful. This is where Pigment tends to win people over: teams find it easy enough that they stop routing around it. We've seen adoption climb sharply once the tool stops fighting them.
You need scenarios fast. A board member wants to know what a headcount cut does to next year's numbers, and they want it before tomorrow's meeting. In Excel that's most of a day. In Pigment, once the model exists, it's a few minutes' work.
You're a SaaS company. Pigment handles recurring-revenue models well: ARR tracking, cohort analysis and NRR calculations are built in rather than bolted on. Its subscription templates give you a real head start, where some competitors' "accelerators" still need heavy customisation before they're any use.
When Pigment Might Not Be Right
It's just as important to know when it isn't the right fit.
You need deep statutory reporting. If your main pain is IFRS 16 lease accounting or complex intercompany eliminations across many entities, Planful has more mature functionality here. Pigment is closing the gap, but closing the gap and having years of production track record behind you aren't the same thing.
Your current platform already works. If your existing EPM system is well adopted and doing its job, switching to Pigment means real cost and disruption in exchange for incremental gains. There's rarely a strong case for replacing something that already meets your needs.
You have very large data volumes. Pigment handles normal FP&A data sizes comfortably. If you're running transaction-level analysis across millions of rows with complex allocations, test it against your real workload before committing rather than taking performance on trust.
Your data is a mess. This is true of any EPM tool: if you can't get clean actuals out of your ERP today, Pigment won't solve that for you. A better front end on bad data is still bad data. Sort out the source systems first.
What Implementation Looks Like In Practice
A focused FP&A deployment typically runs 8-12 weeks from kickoff to go-live. That's the range we deliver in practice, not a best-case sales figure — though the word "focused" is carrying real weight in that sentence.
Weeks 1-2: Discovery. We map your current process, get to grips with your data sources and agree what success looks like. It feels slow when everyone's itching to build, but skipping it is what causes problems later. In our experience, the projects that go wrong almost always cut this phase short.
Weeks 3-6: Build. We configure the model, set up integrations and build the input templates and reports. This is the heart of the project, and your team needs to be part of it: involved in the design decisions, not just reviewing them at the end.
Weeks 7-9: Test. Run parallel cycles, so your next forecast happens in both the old system and the new one. That's how you find the gaps and build confidence before you rely on it. Don't skip it because you're impatient to go live.
Weeks 10-12: Train and go-live. Hands-on training built around real scenarios, using the tool your team will work in every day rather than a webinar or a recording. Then go live, with support on hand for the first cycles.
Cost depends on scope: implementation scales with the complexity of your requirements, and licensing scales with deployment size. Projects with multiple use cases naturally run higher.
Common Mistakes We See
Scope creep disguised as ambition. "While we're at it, let's also do workforce planning, revenue forecasting and operational KPIs." Now the 10-week project is a 30-week one and nobody remembers the original problem. Start narrow and expand once the first phase is live.
Underestimating data integration. Everyone assumes their ERP will simply "connect" to Pigment. Sometimes it does; often there's manual data prep happening in Excel that nobody mentioned upfront. Budget for integration properly.
Treating training as an afterthought. A two-hour session the week before go-live isn't training. Without hands-on practice on realistic scenarios, your team will drift back to Excel within a month.
Expecting the tool to fix process problems. "Our forecast is always wrong" usually isn't a technology failure; it's a process and incentive one. New software won't change the result unless you deal with the underlying causes first.
What to Ask a Pigment Consultant
If you're evaluating implementation consultants, these are the questions worth asking:
"Who will be building this?" Big consultancies send partners to the sales meeting and juniors to the delivery. Ask specifically who will build your model, and meet them before you sign.
"Can you show me a similar implementation?" Ask for a reference call with a client who's been through it, not just a case-study PDF. What went well, and what turned out harder than expected?
"What happens after go-live?" Your model will keep changing — new cost centres, revised driver logic, extra reports — so ask how ongoing support works and agree it upfront rather than discovering it on a later invoice.
"Do you work with other platforms?" A firm that only implements Pigment has little reason to tell you when something else fits better. One that also works with Anaplan and Planful can give you a more objective view of whether Pigment suits your situation.
The Honest Assessment
Pigment is a strong platform that's maturing quickly. For a lot of UK finance teams, particularly in SaaS, professional services and insurance, it's a strong choice: the interface is well received, implementations tend to move quickly, and teams generally take to it.
It isn't the right answer for everyone, though. If you need proven, heavy-duty statutory consolidation, or you already have a platform that's working well, other options will serve you better.
The best way to find out is a proof of concept on your own data — the messy, real-world version, not a tidy demo dataset. Watching how it copes with your actual requirements will tell you far more than any amount of reading.
We're independent consultants who work with Anaplan, Pigment, Planful, and IBM Planning Analytics. If you're evaluating platforms or planning an implementation, we're happy to talk through your specific situation, with no pressure and no obligation.