Financial planning · Available

Pigment for Claude, ChatGPT and Copilot

Finance, revenue and people teams share one Pigment workspace, but they ask different questions of it. With Claude, ChatGPT or Copilot connected, each can ask about metrics across versions, what a board shows for a region, how a scenario differs from the base plan and which transaction list items drive a variance. Access follows applications and dimensions. Pigment is connected to your workspace through a guided pilot.

Status
Available
Setup
Guided pilot with your team
AI assistants
Claude, ChatGPT, Copilot Studio
Access
By role, view only or with approvals

Ask in a sentence

What can your team ask Pigment?

Questions from head of FP&A, revenue operations lead, people analytics lead and others, answered from live Pigment data and only for the people allowed to see them.

Records it works with

  • Applications
  • Metrics
  • Lists
  • Transaction lists
  • Boards
  • Scenarios
  • Snapshots
  • Head of FP&A

    “How does the ARR metric in the base scenario compare with the downside scenario for next year?”

  • Revenue operations lead

    “Which segments are furthest behind their bookings target on the sales capacity board this quarter?”

  • People analytics lead

    “How many hires per department does the workforce application include for Q1, and at what cost in euros?”

  • Finance business partner

    “Which transaction list entries drove the September variance in software spend?”

  • CFO

    “What did operating cash flow look like in last month’s snapshot against today’s forecast?”

  • Sales finance analyst

    “Which reps have quota in the plan but no ramp assumption set?”

Changes, governed

What the assistant can prepare in Pigment

The assistant never saves on its own. It prepares the change, the person checks the preview and confirms, and anything above your limits waits for an approver.

  1. 1 Prepare The assistant drafts the change from the request.
  2. 2 Preview and confirm The person sees exactly what will change.
  3. 3 Approve Above your limits, a second person decides.
  4. 4 Saved and logged Written to Pigment under a named person.
  • Update an input metric for one department and month

    Changes above €40,000 on the year need the head of FP&A to approve.

  • Create a scenario from the base plan for a pricing test

    A pricing test scenario is kept apart from the base plan; the planner confirms it, and FP&A decides whether to use it.

  • Change a future hire’s start date in the workforce application

    Moves across quarters need the department head and the people team.

Example rules. During the pilot you set the limits, the approvers and which roles may prepare each change.

Why it needs care

Governance built for Pigment

Pigment puts revenue, headcount and spend plans in one workspace, so access to the wrong board can expose salaries or pipeline. Access follows applications and dimension items. Large inputs need the head of FP&A, and a hire moved across quarters needs both the department head and the people team.

  • Sign-in by work email

    Only people you invite, with a one-time code. No shared logins.

  • Roles per tool

    Each role reaches only the Pigment records it needs.

  • View only, if you prefer

    Admins can keep a connection to lookups with one switch.

  • A preview first

    Every change is shown in full before anything is saved.

  • Approval rules

    Above your limits, a second person approves the change.

  • One audit log

    Every request tied to a named person, ready for review.

Setup

How Pigment gets connected

We connect Pigment for your team in a guided pilot, on the same gateway every app uses. No code on your side.

  1. 01

    Agree the questions

    We list the Pigment questions and changes your team needs, and who may use each.

  2. 02

    Connect with your admin

    Your Pigment administrator creates a dedicated integration user with only that access.

  3. 03

    Test with your people

    A small group tries it in Claude, ChatGPT or Copilot while we tune the tools.

  4. 04

    Roll out with rules

    Roles, approval limits and the audit log are in place before everyone joins.

Then people use it from the assistant they already have

Pigment questions

Can the assistant compare Pigment scenarios?

Yes. People can ask how a metric differs between scenarios or against a snapshot, and the answer names both sides of the comparison so nobody mixes the base plan with a what-if case.

Does it follow our access rights in Pigment?

We set mcpbizapps roles to match the access rights you already use for applications and dimension items. A sales manager then sees their own segment, while finance sees the whole plan.

Can it write to Pigment boards?

It can prepare input changes to metrics that you allow, shown as a preview first. Calculated metrics and boards update in Pigment once the change is confirmed and approved where needed.

Does mcpbizapps keep a copy of our Pigment data?

No. When someone asks a question, mcpbizapps reads the answer live from Pigment through a dedicated integration user and returns it without storing it. The audit log records who asked, which tool ran and the result, with personal fields and free text removed.

Pigment is a trademark of its owner. mcpbizapps is not affiliated with Pigment; the name describes the connection only.

Start

Bring Pigment into your AI assistant

Tell us how your team uses Pigment, and we will plan a guided pilot around your own questions.

  • We agree the tools and approval rules with you
  • Your admin creates the integration user; no code
  • Business data is read live and not stored

Start a Pigment pilot

Fields marked with a star are required.

We use these details only to reply to you. They are emailed to our team and not stored on this website. See website privacy.

Last updated