Recently active topics

PurposeLaunch moves the solution into production and transitions the customer into ownership. Launch is where everything the agent captured along the way, every Design decision, every Build note, every test outcome, becomes the customer's to run without you in the room. This stage answers: Is the solution ready for production? Are open items, known limitations, and support needs documented? Who owns the solution after launch? What knowledge needs to transfer to the customer and CS team? What sustainment cadence is needed after implementation? Use the Stencil agentAsk the Stencil agent to prepare launch materials, summarize Project Memory, and organize sustainment hand-off. See the Stencil Agent Guide for an example prompt for this stage. Key activities, ownership, and customer actions Activity Owner Purpose Customer action Confirm go-live readiness Project Lead / Customer Project Owner Validate that launch criteria have been met

PurposeTest validates that the Pigment solution end-to-end supports the customer's business process and is ready for launch. This stage answers: Does the solution work as expected? Can users complete the required business processes? What issues need to be fixed, retested, or accepted? Is the customer ready to approve the launch? Are support, ownership, and hand-off needs understood? Use the Stencil agentAsk the Stencil agent to generate UAT scenarios, organize feedback, identify retest needs and summarize readiness. See the Stencil Agent Guide for an example prompt for this stage. Key activities, ownership, and customer actions Activity Owner Purpose Customer action Confirm UAT scope and plan Customer Project Owner/Lead Align testing scope, owners, timeline and process Confirm UAT owners and testers, and continue the end-user training and change management planning started in Build Prepare UAT scenarios Customer Bu

PurposeBuild is where the Spec becomes real:the agent breaks approved work into tasks evaluates output against the Spec and flags what needs a steering decision, so the team spends its time reviewing and directing instead of drafting from scratchThis stage answers: What needs to be built by workstream or use case? Does the build align with the approved Spec? What needs to be evaluated, corrected, or escalated? Which changes require scope review or change control? Is functionality ready for broader testing? Use the Stencil agentAsk the Stencil agent to turn the signed-off Design Doc, Architecture and Spec into a working Pigment solution. See the Stencil Agent Guide for an example prompt for this stage. The Build Loop (Spec -> Build -> Eval -> Steer)This is the core cycle inside Build. It is not a one-way sequence: each pass through Eval either confirms the build is ready or sends a steering decision into the next Spec, and the loop repeats until functionality is ready for sign-

PurposeDesign turns Discovery + Onboarding context into the source of truth for Build. Design is where the agent does its heaviest lifting: drafting requirements from workshop notes, flagging gaps before they become rework and translating approved decisions straight into build-ready instructions. This stage answers: What is the MVP scope? What business process is Pigment supporting? What requirements, assumptions, and open questions need to be documented? What architecture will support the solution? What validation criteria will confirm the solution works? What build-ready Spec is needed before Build begins? Use the Stencil agentAsk the Stencil agent to turn Discovery + Onboarding context into the Design Doc, Architecture and Spec that Build will run on. See the Stencil Agent Guide for an example prompt for this stage. Key activities, ownership, and customer actions Activity Owner Purpose Customer action Review Discovery + Onboarding outputs Sol

PurposeDiscovery starts at the first customer interaction and turns early project context into a clear starting point for Design. Discovery is what Pigment already knows before the ink is dry. Onboarding is what the customer prepares before Design should start. Together they answer: Why is the customer implementing Pigment? What was learned during Sales, Presales, scoping, and prototype work? What assumptions, risks, constraints, and open questions need to carry forward? Who owns business, data, technical, and decision-making responsibilities? What needs to be ready before Design? How will agent-assisted delivery be governed? Use the Stencil agentAsk the Stencil agent to turn everything Sales, Presales and PS scoping already know, plus what the customer may have provided already and still may need to prepare, into one clear starting point for Design. See the Stencil Agent Guide for an example prompt for this stage. Key activities, ownership, and customer actions Activity Owne

PurposeClear ownership is one of the biggest drivers of a successful Pigment implementation, agent or no agent. This article is where Pigment Stencil draws the line: who's involved, what each team owns, how decisions get made and how governance keeps the project aligned and moving. The agent accelerates the visibility work, status, RAID and gap-spotting, but every decision, approval and sign-off in this article belongs to a named human, not a prompt. Typical ownership modelDepending on the project structure, activities may be different  Area Customer owns Pigment / Partner supports Business process Defines current and future process needs Guides how to implement and optimize within Pigment Scope and priorities Confirms MVP priorities Assesses feasibility, effort and trade-offs Data readiness Provides clean, structured, usable data Helps load, connect and validate data Decisions Makes b

PurposeAsk the Stencil agent. If you remember nothing else from this article, remember that.Every phase of Pigment Stencil assumes you're already talking to the agent. This guide is what makes that real: the difference between an agent that has to guess what you need  versus one that gives you the plan, the draft or the answer tailored to this customer, this use case, this stageThat difference is the value case for Stencil itself: faster time-to-value because nobody starts from a blank page, more consistent delivery because the agent applies the same rigor every time and knowledge that compounds instead of resetting. What is the Stencil agent?What it is: a Pigment agent that guides a project through delivery. Ask it about any stage, Discovery through Launch, and it knows the deliverables, the gates and the approach to get there. What it isn't: a decision maker. It drafts, evaluates and recommends; every decision, approval and sign-off still belongs to a named human. How Stencil agents

PurposePigment Stencil is an agent-led delivery methodology. The agent doesn't sit alongside the process, it drives it: turning customer context into a Design Doc, a Design Doc into a build-ready Spec, a Spec into a working solution and every decision along the way into Project Memory that outlives the project team. For the customer, that means faster time-to-value, lower total cost of ownership because knowledge doesn't walk out the door with the last consultant and de-risked delivery because every gate is governed by an artifact, and builds on patterns proven across every prior Pigment delivery.Ask the Stencil agent. You can ask it about any project stage, Discovery through Sustain.  It's the first move in every phase of a Pigment implementation, and the whole point of Pigment Stencil. This isn't a traditional methodology with AI added on. The methodology runs on Prompt, Validate, Run: Prompt the agent to draft the heavy lifting Validate the result together Run your process as part o

Introduction:Hello Pigmenteers! I’m Axelle Cazalets (​@Axelle Cazalets in the community). I’m based in Toronto, Canada, and I work at Procore, a construction management software company. My role is focused on FP&A systems and program management, with my main responsibility being to maintain and continue developing our Pigment workspace to support financial planning across the organization.I also have FP&A responsibilities outside of Pigment, which I’ve been really happy to take on as I continue developing my understanding of what FP&A teams do every day. I would say my role today is around 60% Pigment and 40% broader FP&A responsibilities. You can see Axelle’s full interview here: Can you tell us a little about your career journey?I’ve been in the EPM industry for more than 10 years. I first entered the consulting world without really knowing what to expect, and over time I had the opportunity to work with many different businesses and understand the challenges FP&A