Go-live is not the finish line for an EPM implementation. For finance leaders, pigment managed services provide the operating support that keeps a live planning environment reliable, governed, and useful as the business changes. The need usually becomes visible during the first forecast, budget cycle, or organizational change after launch.
What Is Pigment Managed Services Support After Go-Live?
Pigment managed services are an ongoing support model for a live planning environment. They can combine administration, issue resolution, model maintenance, user enablement, governance, and optimization so finance teams can adapt Pigment without treating every change as a new implementation project.
An implementation creates the initial planning architecture. It defines requirements, builds the model, connects source data, configures access, tests key workflows, and prepares users for launch. Post-go-live support addresses the work that follows: new entities, revised assumptions, additional users, changed reporting requirements, integration issues, and lessons from the first planning cycle.
Implementation establishes the foundation
A strong implementation gives the organization a functioning way to plan. It also creates the documentation, ownership model, and decision history that support future changes. Amvent Consulting uses a structured six-phase approach that moves from business needs through design, integrations, testing, go-live, and system administration.
That foundation matters because a support partner should not be learning the model from scratch during every request. A team that understands the original design can distinguish a safe configuration change from one that could affect data integrity, reporting logic, or user access.
Managed services operate and evolve the environment
After launch, the focus shifts from delivering a defined project to operating a live planning system. Support may include administration, bug fixes, performance optimization, configuration updates, access reviews, monitoring, documentation, and user training. The agreement should state what is included, how work is prioritized, and which requests require separate project scope.
The practical distinction is simple. Implementation asks what to build and how to launch it. Managed services ask how to keep the model reliable and aligned with the business as requirements change. That requires prioritization, change control, testing, documentation, and clear ownership.
For more context on the implementation-to-support handoff, review Amvent's Pigment implementation methodology.
What Does a Pigment Managed Services Retainer Typically Cover?
A managed services retainer should give finance teams a predictable operating layer after implementation. The exact scope depends on the model, integrations, internal capability, and planning calendar. A useful agreement combines reactive support with proactive maintenance instead of functioning as an undefined ticket queue.
Support area | Typical work | Finance outcome |
|---|---|---|
Administration | User access, roles, workflow settings, and routine configuration | Controlled day-to-day operation |
Issue resolution | Root-cause investigation, defect correction, and escalation | Less disruption during planning cycles |
Model maintenance | Dimensions, assumptions, formulas, and reporting updates | A model that reflects current business logic |
Enablement | User guidance, documentation, and targeted training | More self-sufficiency and adoption |
Optimization | Performance review, simplification, and roadmap recommendations | Better value from the platform over time |
Administration and user support
Administrative requests can appear small but still affect control. Adding a user, changing a role, or adjusting a workflow should follow an agreed process. Support teams may also answer questions about navigation, input workflows, reports, and planning calendars. Clear documentation prevents the same question from becoming a recurring dependency.
Defects, requests, and project work
Not every request belongs in the same queue. A calculation that stopped working, a failed data load, and a new planning module have different levels of urgency and effort. A mature support model classifies requests, records the impact, identifies the owner, and separates maintenance from work that needs a defined project plan.
Finance leaders should ask prospective partners how they distinguish incidents from enhancements. Without that distinction, a retainer can become difficult to forecast and the team can spend its capacity on urgent but low-value requests.
Documentation and knowledge transfer
Documentation should evolve with the model. Useful materials explain important assumptions, integrations, ownership, approval paths, recurring processes, and known limitations. The goal is not to create paperwork for its own sake. It is to make future decisions faster and reduce the risk that a single administrator becomes the only person who understands a critical process.
Why Does a 24-Hour SLA Matter to Finance Teams?
A 24-hour SLA gives finance teams a defined response expectation when a planning issue affects a close, forecast, budget, or executive report. It does not mean every issue is solved in one day. It creates a clear first-response, triage, communication, and escalation discipline.
Response time matters because planning systems are tied to business deadlines. A model issue discovered during a quiet period may be inconvenient. The same issue during forecast submission or board reporting can delay decisions and force manual workarounds.
Response time is not the same as resolution time
A useful SLA distinguishes acknowledgement, triage, workaround, resolution, and escalation. A first response within 24 hours can confirm that the issue is understood, identify its priority, and set the next checkpoint. Complex model changes may require more time, especially when they affect integrations or multiple planning processes.
This distinction keeps the promise credible. Finance users know whether a request is being investigated, whether a temporary workaround exists, and when they will receive the next update. They are not left guessing whether a ticket has been seen.
Priority should follow business impact
Support priorities should reflect the finance calendar and the scope of the disruption. An issue that blocks all users deserves different treatment from a question affecting one report. A failed load that threatens a forecast deadline should be visible to the right stakeholders, even if the technical fix is not immediate.
Before signing an agreement, ask how priorities are defined, who can escalate an issue, which channels are monitored, and how communication works outside a routine planning cycle. Amvent's service delivery model differentiates through personalized support and a 24-hour SLA guarantee.
How Does Ongoing Model Maintenance Protect Planning Quality?
Ongoing model maintenance protects planning quality by reviewing changes before they spread through formulas, dimensions, integrations, workflows, and reports. It combines controlled updates with testing and documentation, helping finance teams preserve trust in outputs while the business, structure, and planning assumptions evolve.
A planning model is not static. Companies add products, change territories, reorganize teams, revise cost centers, and introduce new scenarios. Each change can affect more than the screen where it first appears.
Control structural changes
Dimensions, hierarchies, assumptions, and ownership rules should be changed deliberately. A new entity may require updates to data mappings, reporting views, permissions, and workflow steps. A support partner can help identify those dependencies before a change reaches production.
Test integrations and calculations
Data quality depends on the full flow from source systems into the planning environment and then into reports. Maintenance should include checks for failed loads, unexpected values, timing changes, and formula behavior. Testing is especially important before a forecast or budget cycle, when a small issue can affect many users.
Testing does not need to mean a full implementation cycle for every request. It does mean matching the depth of validation to the risk. A display change may need a focused check. A change to revenue logic or workforce assumptions deserves a broader test across affected outputs.
Review access and performance
Access should reflect current roles and responsibilities. Joiners, movers, and leavers create a recurring administration need, while broader organizational changes may require a more formal review. Performance should also be monitored as the model grows. Simplifying unused structures and documenting design decisions can protect usability without reducing planning capability.
Amvent's guide to access management in Pigment provides a related control perspective for teams defining ownership after launch.
When Should You Use a Managed Services Partner Instead of Building In-House?
Use a managed services partner when the cost or risk of maintaining Pigment alone exceeds the value of internal capacity. The decision depends on model complexity, planning-cycle pressure, integration risk, available administrators, and the need for specialist support during periods of change or growth.
Internal ownership is valuable. Finance teams should retain business context, decision authority, and accountability for the planning process. The question is whether the organization also has enough technical depth and capacity to maintain the environment consistently.
Factors that favor internal ownership
The model is stable and relatively contained.
Internal administrators have protected time for maintenance.
Documentation and change-control practices are established.
The organization has backup coverage for key administrators.
Complex integrations and model changes can be tested internally.
Factors that favor external support
The model supports multiple connected planning processes.
Finance has limited technical administration capacity.
Planning cycles create concentrated periods of risk.
The organization is expanding the model to new teams or entities.
There is a need for specialist troubleshooting or optimization.
A hybrid model is often practical. Internal owners remain close to the business while a specialist partner provides a deeper bench for complex changes, troubleshooting, optimization, and roadmap decisions. This can also make knowledge transfer more intentional instead of leaving the team dependent on informal expertise.
How Do You Evaluate a Pigment Managed Services Partner?
Evaluate a Pigment managed services partner on platform depth, response commitments, maintenance discipline, communication, documentation, and understanding of finance processes. Ask for a clear scope, escalation path, ownership model, and examples of how the partner handles incidents, enhancements, testing, and knowledge transfer.
The right partner should be able to discuss both the platform and the planning work it supports. A generic support promise is not enough if the team cannot explain how it would protect model logic during a forecast, budget, close, or organizational change.
Questions to ask before selecting a partner
What is included in the recurring scope? Ask how administration, defects, model changes, training, documentation, and optimization are handled.
How is the SLA measured? Confirm the response definition, priority levels, escalation process, communication channel, and treatment of urgent planning-cycle issues.
Who will work on the model? Understand the team's Pigment experience, finance-process knowledge, backup coverage, and access controls.
How are changes tested? Look for a risk-based approach that protects integrations, calculations, workflows, and reporting outputs.
How does the relationship evolve? Confirm how recurring themes become roadmap recommendations, documentation updates, or training opportunities.
Amvent is a Toronto-based boutique EPM consulting firm and official Pigment Delivery Partner. Its practitioner-led approach is designed for finance leaders who want specialized support rather than a generalist service desk. Learn more about Amvent's Pigment planning and implementation services before defining the post-go-live operating model.
For a broader view of how planning environments connect across teams, see the path to connected planning.
Frequently Asked Questions
What does Pigment managed services support include?
It can include platform administration, issue resolution, model maintenance, access reviews, integration checks, performance optimization, documentation, user training, and roadmap guidance. The exact scope should be defined in the agreement, including what counts as routine support and what requires a separate project.
When should managed services begin after a Pigment implementation?
Support should be planned before go-live and begin when the environment enters operational use. An early handoff preserves implementation knowledge, gives users a clear escalation path, and lets the team capture lessons from the first forecast or budget cycle.
Does a 24-hour SLA mean every issue is fixed within 24 hours?
No. A 24-hour SLA generally sets a response or acknowledgement expectation. Resolution time depends on the issue's priority, complexity, dependencies, and required testing. The agreement should explain response, triage, communication, workaround, resolution, and escalation commitments.
Can an internal finance team manage Pigment without an external partner?
Yes, if the team has the required platform knowledge, protected maintenance capacity, documentation, backup coverage, and change-control discipline. External support becomes more valuable as the model, integrations, user base, and planning calendar become more complex.
How should finance leaders compare managed services proposals?
Compare scope, response commitments, partner experience, named ownership, testing practices, documentation, escalation, and knowledge-transfer plans. The lowest recurring fee is not necessarily the lowest-risk option if it leaves critical model decisions, planning deadlines, or access controls unclear.
Schema note: the FAQ below summarizes the article's reader questions.
Get Pigment Managed Services Support After Go-Live
The right post-go-live model protects more than system uptime. It helps finance teams preserve trust in planning outputs, respond to business change, and build a sustainable ownership model around Pigment. Start by defining the risks, responsibilities, planning-cycle requirements, and support outcomes that matter to your organization.
Get in touch with Amvent Consulting
Get in touch to discuss Pigment support
