[Guide] Cobuilding EPM: A Typical Pigment Implementation

For new tools, especially those with business-wide impact like EPM platforms, implementation sets the tone for the rest of the lifecycle. It’s not just about configuration, either; a successful implementation means enablement, integration, and forward thinking. 

That’s the main reason EPM implementations can falter: they focus too narrowly on the time frame leading up to “go live” or “launch.” And when businesses want to make major changes, they have to re-engage with the team who completed the initial configuration and undergo a whole new project. This is both inefficient and frustrating, but it’s alarmingly common within the EPM industry, as it keeps customers reliant on their vendors.

At Pigment, do things differently. We use the implementation process to configure the tool successfully today, but also to lay the foundations for growth and evolution – equipping your team to own your use cases day-to-day, make changes to them, and even implement new ones themselves.

The cobuild approach

One of Pigment’s key benefits is its flexibility - plans change, and Pigment is built to reflect that, both within the platform and our implementation approach.

When we onboard a new customer, the implementation phase comes first – this is an opportunity for your team to work with our Solution Architect and Customer Success teams to build out your initial use cases. Again, this isn’t just about configuration; it’s about demonstrating a repeatable framework that you can use well beyond the initial implementation, enabling your team to own future iterations of that framework.

Our team takes the lead from the start, but your team is equally involved in not only the architecture of your use cases and applications, but even in the actual configuration and deployment within Pigment. Because Pigment has been designed for ease of use, our customers pick up the tool very quickly when spending time in it, and collaborating on the build means those modelers are able to own the Pigment instance confidently moving forward.

We find this method is far more cost-effective and convenient for our customers - it does require a more hands-on approach from the customer project team, but the payoff more than makes up for it.

Learn more

Interested to learn more? We've written a guide on the entire process, covering:

• An overview and timeline of a typical Pigment implementation
• Details of who is involved at each step, and the time commitments they’ll need to make
• Details of the ‘cobuild’ approach Pigment has adopted
• The ongoing support and frameworks we’ve put in place for post-implementation

Click here to download.