Pigment review

The short answer

Buy Pigment if your planning cycle moves faster than your planning tool. The case is strongest for finance teams that recut the forecast monthly, model revenue across segments or cohorts, and want sales capacity, headcount and the P&L sharing one data model instead of three spreadsheets that get reconciled by hand. The second reason to buy is ownership: Pigment is built so that an experienced FP&A professional can add accounts, change driver assumptions and build report views without a certified specialist.

Skip it if your central requirement is statutory consolidation with intercompany eliminations and multi-GAAP reporting, or structured close management alongside planning. Pigment lists consolidation among its use cases and it is not positioned as a close platform, so verify that specific scope against your own checklist rather than against the demo. Skip it too if you need budget data written back into an ERP for commitment control, and treat the lack of any published price or free trial as a real cost of evaluation rather than a formality.

Where Pigment fits

Pigment pricing

Pigment publishes nothing, and it does not even have a pricing page. Checked on 25 September 2026, pigment.com/pricing returns a 404, so the route to a number is the contact form, and the quote depends on the planning use cases and the users you license. There is also no free trial listed on pigment.com, which means that unlike Workday Adaptive Planning you cannot touch the product before a sales conversation. No price and no trial is the real cost of evaluating Pigment, and the answer is a structured pilot on your own data rather than a scripted demo.

Three things move the quote, plus the services line that is not in it at all.

1. Which use cases you license. Pigment spans FP&A and consolidation, sales planning, supply chain and workforce planning, and the normal pattern is to start with one and add others later. That makes the second use case the most important number in the negotiation, and the one easiest to get before signature. If you intend to start with FP&A and add workforce or sales planning next year, put both in the first quote even if you only sign one.
2. How users are licensed. Ask whether the split is model builders, contributors and viewers, what each type can do, and whether a budget holder who submits numbers once a quarter needs a full licence. A rollout with two hundred occasional contributors and a handful of builders is a different contract from one with fifty heavy users, and the mix decides the number more than headcount does.
3. How AI is licensed. Pigment's Modeler, Analyst and Planner agents are part of the product line, so ask directly whether the agents you were shown in the demo sit in the base contract or carry a separate charge. Get the answer in the order form. A capability that appears in a demo and not in a contract is the usual gap between what a buyer thinks they bought and what they may use.
4. Implementation, which has no published fee. Ask whether Pigment delivers the build or a partner does, how the services are priced, and what counts as a change order. Pigment's partner network is smaller than Workday's or Anaplan's, so confirm partner availability in your geography and their FP&A depth before making partner choice part of the plan.

What to get confirmed as included

• The AI agents: Modeler, Analyst and Planner. They are part of the product line rather than a separately marketed bundle, which is exactly why the contract should name the ones you intend to use.
• Data connectors. Pigment integrates with NetSuite, Salesforce, HubSpot, SAP, Workday and HRIS platforms, with Salesforce and NetSuite the most mature. Ask which connectors are included, which need configuration work, and who pays for that work.
• Implementation and onboarding services, which carry no published fee and should arrive as a fixed scope next to the subscription rather than as a day rate.
• End-user training for the business unit contributors who will submit budget inputs. Adoption quality drives forecast reliability, and underinvesting here is a recognised implementation risk rather than a hypothetical one.

Implementation and commercial terms

The rows below record what is confirmed as of 25 September 2026 and, more usefully, what Pigment has not published. Everything in the second category is a first-call question.

Published price

None. pigment.com/pricing returns a 404.

Pricing model

Quote-based custom subscription, by use case and users.

Route to a quote

The Pigment contact form. There is no self-service path.

Free trial

None listed. Ask for a scoped pilot on your own data instead.

Implementation fee

Not published. Pigment or a partner delivers the build.

Deployment

Cloud only, SOC 2 Type II certified. Confirm your data region.

Renewal uplift

Not published. Negotiate a cap before signature.

Budget Pigment as a subscription plus a build, and get both in writing before the first number becomes an anchor. Define the single use case you will go live on, count your users by licence type, name the AI agents you expect to use, and ask for the second use case priced in the same document. Then ask for a pilot built on your chart of accounts and your own Salesforce or ERP data, because with no published price and no trial, the pilot is the only part of the evaluation you control. If a shortlisted vendor publishes anything at all, say so in the negotiation: it is a legitimate point of comparison, and Pigment is currently on the wrong side of it.

Source: the Pigment contact page, since there is no pricing page, checked 25 September 2026. Confirm current prices with the vendor before you budget.

What Pigment gives up

How Pigment compares

You cannot compare FP&A platforms on price, because not one of these five publishes a figure. Pigment is at the far end of that: no pricing page and no free trial. So compare on the things that do differ: whether your own team can change the model, where consolidation lives, and how high the modelling ceiling goes. Every cell below comes from that vendor's own site, checked on 25 September 2026, with nothing estimated.

What to test in a Pigment demo

There is no free trial listed on pigment.com, so what you can get is a demo and, if you ask firmly, a pilot scoped on your own data. Ask for the pilot. A demo shows you a model somebody else built, and the question you need answered is whether your team can build and change one. Five tests are worth the time.

1. Have the pilot built on your chart of accounts, your entity structure and one real month of actuals. Mapping the ERP chart of accounts to the planning hierarchy you want is the universal friction point in these implementations, and nothing in a demo environment tells you how much of it you are facing.
2. Make one of your own analysts change the model while the vendor watches. Add an account, change a driver assumption, add an entity, build a report view. Pigment's claim is that trained FP&A professionals can do this without a specialist, and that claim is the main commercial reason to prefer it over Anaplan. It is also the easiest claim in the whole evaluation to test directly.
3. Connect your real Salesforce or CRM instance if revenue planning is part of the case. The revenue model is only as good as the pipeline data behind it, and a pilot that surfaces dirty pipeline data has done you a favour. While you are there, confirm what the ERP connector does with your version and chart of accounts rather than with the vendor's reference setup.
4. Test the consolidation and close requirement explicitly, item by item. Write out your intercompany eliminations, minority interest treatments and any statutory reporting obligation, and have Pigment demonstrate each one or say plainly that it does not. This is the boundary where this product is most often oversold, and the list is the only reliable way to test it.
5. Price the second use case and name the AI agents. Ask for FP&A quoted now and for workforce or sales planning quoted alongside it, and get Modeler, Analyst and Planner either included in the order form or priced as a line. Both of these are far easier to obtain before signature than after, and both are the kind of thing that turns a good year-one number into a bad year-three one.

Frequently asked questions about Pigment