Summary

  • Pigment announced Frames on September 10, with an open beta for all customers scheduled for September 28, rather than immediate universal availability.
  • Frames can read and write the live planning model. Creator permissions, per-user access rights and a private-to-published lifecycle remain distinct controls.

A planning screen is more consequential when typing into it changes the plan. That is the distinction behind Pigment Frames, announced on September 10 as a way to generate custom interfaces inside the company's business-planning applications. The proposed shortcut is not merely from a prompt to a presentable dashboard. It is from a description to a page that can participate in the operating model.

The company says customers will get the open beta on September 28. Examples shown at announcement are therefore evidence of preview use, not proof that every customer can already deploy the feature. Pigment describes data-entry forms, what-if planners and executive presentations, all connected to its unified planning model. September 10 announcement.

This connection changes what a polished interface means. According to the product explanation, an input entered through a Frame can flow into the live model and through its calculation logic. A custom form need not become a separate spreadsheet whose results are copied back later. The potential gain is less work maintaining that extra interface and reconciliation layer. It is not evidence that the underlying forecast assumptions have become correct.

Pigment puts several boundaries around creation and use. Its product FAQ says only users with the Configure Blocks permission can create or edit Frames. The resulting interface reads and writes within each user's existing access rights, so a shared page does not imply a shared entitlement to every field. The product also retains Boards for data-intensive exploration and high-performance analysis; Frames are an additional way to contribute, explore or present, not an announced replacement for that existing surface. Frames product details.

There is a separate release boundary. Pigment says a new or updated Frame remains private to its author until publication, and generated code undergoes an automated security and performance review first. Creating an attractive result and distributing it across an organisation are consequently different steps. The product blog describes this review as a technical control; it is not an independent audit of the feature or a guarantee that a planning rule expresses management's intended decision. Product launch explanation.

That distinction is important for live write-back. A form may successfully validate the presence of an input while leaving a business question unresolved: which assumption should change, who should confirm it and which version of a plan should receive it? These are analytical examples of what teams still need to settle, not reports of defects in Frames. A feature capable of supporting approval flows does not by itself specify an organisation's approval policy.

The September package also includes Agent Connectors and an AI-guided trial. Those announcements broaden the route into Pigment, but they do not supply a Frames-specific unit price or a measured return for every customer. Customer demonstrations and testimonials show intended uses; they do not establish a general build-time, error-rate or labour-saving guarantee.

The buying question is therefore about a governed contribution to a plan, not the number of interfaces a team can generate. A useful pilot would show that the right people can submit the right changes, that others cannot, and that publication is deliberate. Less effort spent drawing a screen is valuable only if the resulting screen is fit to touch the business model.