Pigment: Gen-3 xP&A Platform for Modern Finance & Operations
A Gen-3 xP&A platform with visual modeling, collaborative planning, and enterprise-grade capabilities for modern finance and operations teams.
Pigment is a Gen-3 integrated business planning platform built for organizations that need real-time, multi-scenario planning across Finance, Revenue, HR, and Operations — without inheriting the complexity and drag of legacy EPM. It combines an in-memory modeling engine, strong UX, and an emerging AI "agentic" layer to support xP&A at scale.
1. Snapshot
What Pigment is
- AI-powered integrated business planning / xP&A platform
- Designed to replace fragmented models across FP&A, RevOps, HR, and Supply Chain with a single connected planning layer
Company facts
- Founded: 2019 (Paris)
- HQ & presence: Paris + US (San Francisco) + UK; global enterprise focus
- Funding: ~$145M Series D in April 2024, led by ICONIQ Growth; total funding in the high-hundreds of millions from ICONIQ, IVP, Meritech, Greenoaks, Felix, and others
- Tech stack (inferred from job listings):
- Backend: C# on .NET Core (Linux), custom formula & query engine
- Data: PostgreSQL
- Infra: Google Cloud Platform, Kubernetes, Docker, Terraform, RabbitMQ, CircleCI
- Frontend: React, TypeScript
Who uses Pigment today (public stories & inferred logos)
Well-known scale-ups use Pigment for unified FP&A, including:
- The Coca-Cola Company
- Unilever
- ServiceNow
- Fivetran
- Evenflo
- Cobalt
- Frontify
- American Power & Gas
- Muck Rack
- SpotOn
2. Who Pigment Is Really For (ICP)
Best fit segments
Pigment is best suited for:
- Mid-market to large enterprises that:
- Have multiple entities, regions, or product lines
- Need integrated planning across Finance, Revenue, HR, and Operations
- Are outgrowing Adaptive/Planful/Vena or are blocked by Anaplan's cost/complexity
- Typical sweet spots:
- High-growth SaaS and tech
- Large consumer/CPG
- Global services / B2B platforms
- Organizations already using modern ERPs and CRMs (NetSuite, SAP S/4, Salesforce, etc.)
Less ideal for
- Very small teams that only need basic cash/runway modeling
- Organizations that insist on remaining 100% spreadsheet-native and are unwilling to move planning logic into a centralized model
- Purely consolidation-led projects (Pigment can do planning-adjacent consolidation, but it is not a pure consolidation engine like OneStream/Tagetik)
3. Product Overview & Key Use Cases
Pigment is an xP&A platform rather than a single-function FP&A tool. At a high level you can think in four domains:
1. Finance (FP&A)
- Budgeting & forecasting (P&L, BS, CF)
- Integrated financial statements
- Multi-scenario planning & sensitivity analysis
- Financial consolidation (lighter than full CPM, but often "good enough" for many mid-market cases)
- Board & management reporting
2. Revenue & Sales Planning
- Sales capacity and headcount planning
- Territory & quota planning
- Pipeline-to-revenue modeling
- Revenue forecasting tied to financial plans
3. HR & Workforce Planning
- Headcount, hiring plans, attrition, compensation modeling
- Workforce OPEX modeling linked to P&L and cash
- Scenario planning around org design and restructuring
4. Supply Chain & Operations
- Demand & inventory planning
- S&OP and integrated business planning
- Product profitability and cost-to-serve analysis
Pigment's pitch:
All these domains exist in one modeling engine, with shared dimensions and real-time updates, not separate, brittle Excel files.
4. Architecture & Tech Stack (Buyer-Relevant View)
From public engineering materials and job posts, Pigment's architecture looks like:
Custom calculation engine
- Proprietary formula and query engine optimized for multi-dimensional, high-volume models
- Real-time recalculation, dependency graph management, granular dimensions
Service & data layer
- Backend in C#/.NET Core on Linux
- PostgreSQL as a core data store
- Eventing/message bus via RabbitMQ
Cloud infrastructure
- Deployed on Google Cloud Platform
- Containerized via Docker, Kubernetes
- Infra as code with Terraform; CI/CD via CircleCI
Front-end
- Web app in React + TypeScript
- Rich grid, charting, workflow UI
Practically, this matters because:
- It's multi-tenant SaaS with modern tooling — you're not buying a legacy on-premise cube.
- The engine is explicitly designed for real-time, large-scale recalculation, not overnight batch jobs.
- Integrations and AI capabilities sit on top of a modern, API-driven foundation.
5. AI & "Agentic" Capabilities
Pigment is currently one of the more aggressive players in AI-powered planning, leaning into an "agentic AI" narrative:
What AI does today (publicly):
- AI Agents:
- Analyst-style agents that can analyze plans, highlight anomalies, and surface drivers
- Planner/Modeler agents that can propose changes to models or plans based on observed patterns
- Insights & variance analysis
- Automated contribution & variance analysis (e.g., what drove revenue growth/decline) with natural-language summaries and visual explanations
- Self-driving finance narrative
- In webinars and videos, Pigment talks about "AI agents for self-driving finance" — AI that not only describes what happened but proposes what to do next.
What this means for a buyer:
- AI is layered on top of structured, well-governed models, not on raw spreadsheets.
- It's more about augmenting FP&A (variance analysis, scenario recommendations) than firing off fully automated budgets.
- The value will scale with:
- How well your data is integrated
- How well-designed your Pigment models are
6. Integrations & Ecosystem
Pigment positions itself as an integrated planning platform that connects to your ERP, CRM, HRIS, and data stack:
Common integration patterns include:
- ERPs: NetSuite, SAP S/4HANA, Oracle, Microsoft Dynamics (via partners and ETL)
- CRMs & GTM tools: Salesforce, HubSpot
- HR / HCM: Workday, HiBob, BambooHR, etc.
- Data & ETL: Warehouse/ETL stacks (Snowflake, Fivetran, dbt, MuleSoft)
There's a growing ecosystem of implementation partners and SIs specializing in Pigment:
- Boutique and mid-sized partners (e.g., valantic, Alpha FMC, Bright Point, Polestar) publish case studies around Pigment-based FP&A/joint solutions.
Practically, this means:
- You're not limited to a single "big-4" partner ecosystem.
- There's a mix of specialist partners that can do fast, domain-specific implementations.
Pigment's integration strategy is:
connect to the systems modern SaaS companies actually use.
Notably absent today: deep SAP/S4, Oracle, Workday integrations — which is why this is not an enterprise-first platform.
7. Implementation & Time-to-Value
Implementation timelines vary by scope, but from partner case studies you see patterns like:
- Light FP&A footprint (data hub + P&L + basic workforce planning):
- Roughly 8–12 weeks from project kickoff to first live forecasting cycle (assuming you bring clean chart of accounts and initial data).
- Full FP&A suite (data hub + revenue + COGS + OpEx + workforce + full 3-statement + reporting):
- Often 3–6 months, with iterative releases
- Cross-functional xP&A (Finance + HR + Sales + Supply Chain):
- Multi-wave deployment and ongoing model build; think phased programs rather than a one-and-done go-live.
Typical implementation components:
- Data modeling and "Data Hub" design
- Core financial model (Revenue, COGS, OpEx, HC, P&L, BS, CF)
- Security model: access control by role, region, function
- Scenario templates (Base, Upside, Downside)
- Reporting/dashboarding and board pack templates
8. Pricing & Commercial Model (Directional)
Pigment does not publish pricing, but based on market data:
Commercial model:
- Annual subscription, typically tied to:
- Platform edition
- Number of model domains (Finance only vs Finance + HR + Sales, etc.)
- User tiers (modelers, planners, viewers)
Relative cost position:
- Generally more expensive than mid-market tools like Cube or Vena, but often 30–50% lower TCO than a comparable Anaplan deployment once you include services and ongoing maintenance.
Position on your page: "Pigment is a premium Gen-3 platform: more costly than spreadsheet-native tools, but materially cheaper and faster to deploy than legacy EPM in most mid-market/enterprise scenarios."
9. Case Studies & Outcomes (Synthesized From Public Information)
Pigment's own site and partner ecosystem highlight a growing library of case studies across industries:
Examples (you can name-drop a few on your page, then link out or summarize):
- Fivetran – uses Pigment for driver-based forecasting and scenario modeling; emphasizes the ability to apply assumptions and generate calendarized forecasts quickly.
- Cobalt – improved FP&A security and scenario analysis with Pigment, leveraging access controls and scenario modeling for more robust planning.
- Evenflo – uses Pigment to quickly analyze tariff impact on margins and model P&L implications in a fast-changing cost environment.
- Frontify (via valantic) – implemented a full FP&A solution including scenario planning and reporting, significantly reducing manual data gathering.
- Fintech "automated FP&A model" case (via Alpha FMC) – shows a full Pigment build with modules for Data Hub, Revenue, COGS, OpEx, Workforce Planning, P&L, BS, CF, and board reporting.
- American Power & Gas, Muck Rack, SpotOn (via Bright Point) – case studies highlight moving from Excel chaos to centralized Pigment models, real-time data feeds, and unified scenario planning.
Common themes from these stories:
- Reduction in manual Excel work and reconciliation
- Faster reforecast cycles (weekly/monthly vs quarterly)
- Better scenario agility (more "what ifs" in less time)
- Stronger alignment across finance, sales, and operations
10. Go-to-Market Strategy & Ecosystem
From a buyer's point of view, Pigment's GTM motion looks like:
- Enterprise & upper mid-market direct sales:
- Account-based GTM toward CFOs, FP&A leaders, and operational planning leaders
- Partner-assisted deals:
- SIs and boutiques (valantic, Alpha FMC, Bright Point, Polestar) co-selling and implementing Pigment in specific industries (SaaS, CPG, manufacturing, fintech).
- Education & thought leadership:
- Weekly live demos / tours
- Webinars on "AI Agents", "self-driving finance", and xP&A best practices
This matters because:
- You're buying into an ecosystem, not just software.
- There's a clear path to get specialized help (SIs) if internal bandwidth is limited.
11. Strengths & Limitations
Biggest strengths
- Powerful modeling engine with enterprise-grade dimensionality and real-time recalculation
- Strong cross-functional coverage (Finance, Revenue, HR, Supply Chain) in one platform
- Modern tech stack & UX — widely regarded as one of the better UIs in planning
- Rich and emerging AI/agentic capabilities for variance analysis and guided planning
- Growing ecosystem of partners and case studies across industries
Potential limitations / watch-outs
- Complexity: you still need real modeling discipline; if your team is not comfortable with structured models, you may recreate "Anaplan problems" in a nicer UI.
- Services dependency: most mid-large deployments will still require partner involvement to design a robust data hub and model architecture.
- Not a pure consolidation engine: if your top priority is statutory consolidation with deep legal ownership and complex GAAP/IFRS logic, a pure CPM/consolidation tool may still be required alongside Pigment.
- Cost vs spreadsheet-native tools: for smaller orgs or very narrow use cases, Pigment will be overkill compared to Cube, Causal, or Runway.
12. When Pigment Is a Great Fit vs When to Consider Alternatives
Pigment is a great fit if:
- You need enterprise-class modeling across multiple planning domains
- You want to escape Anaplan/legacy EPM without going back to spreadsheet chaos
- You care about UX and business-user adoption, not just a back-end engine
- You want to leverage AI agents for analysis and scenario guidance, not just static reports
- Your data stack is ready (or you're willing to invest in a data hub / integration project)
You might consider other tools if:
- You're a smaller org (less than $20–30M) with light planning needs → Causal, Runway, Cube may be better value.
- You are Microsoft-all-in and want to live in Power BI/Excel → Acterys is more native to your world.
- You need heavy statutory consolidation first, FP&A second → OneStream / Tagetik or similar CPM tools may still play a role.
13. Key Questions to Ask Pigment in a Demo
You can reuse this as a consistent section across all vendor pages.
Architecture & fit
- How would you model our entities, products, and regions in Pigment?
- What does a typical data hub look like for a company like ours?
- How do you handle slow-changing dimensions and historical restatement?
AI & intelligence
- Show us concrete examples of AI agents:
- How they surface variance drivers
- How they propose plan changes
- What guardrails exist so AI doesn't break models?
Implementation
- For a company like ours (size, industry, ERP), what's a realistic timeline to:
- Go live with base FP&A?
- Extend into Sales/HR/Supply Chain?
- Which partners would you recommend and why?
Integrations
- Which ERP/CRM/HR connectors do you have out-of-the-box for our stack?
- How often can data be refreshed (near real time vs nightly)?
Commercials
- Which edition would you recommend for our scope?
- What drives total cost the most (users, modules, entities)?
- What does a typical 3-year TCO look like for similar customers?
Need Help Evaluating Pigment?
Our analysts can help you evaluate Pigment against other Gen-3 xP&A platforms and determine if it's the right fit for your mid-market to enterprise finance and operations teams.
Book a 20-min Consultation