Ramp vs Pigment
Side-by-side trajectory, velocity, and editorial themes.
Ramp pushes deeper into vendor and license governance while widening international card coverage.
Ramp's recent cadence splits between accounting depth (QuickBooks Online custom fields and dimensions), vendor intelligence (license usage pulled from Okta, Entra, and Chrome), and geographic reach (USD cards for Canadian businesses, European per diem reimbursements). Around that, the Chrome extension picked up auto-receipt capture for Amazon and Uber. Each release is small, but the pattern shows three coordinated tracks.
Ramp is moving past pure card-and-expense to claim the full vendor-spend graph: who is paying for what, who is actually using it, and where it sits across geographies. Pulling identity-provider data into vendor management is the most strategically interesting move — it makes Ramp a candidate to replace Zylo, Productiv, or Vendr for mid-market SaaS spend.
Expect license intelligence to extend to more identity providers (Google Workspace, JumpCloud) and pair with an automated reclaim workflow, and international card programs to add EUR or GBP issuance to match the per-diem push.
Hardening change management for enterprise planning — granular and local Test and Deploy with deployable User Groups.
Pigment has spent the last month tightening the deployment story for its enterprise planning platform: granular deployment to push specific changes (not whole environments), local deployment to test inside a Workspace using temporary Application copies, and User Groups now flowing through Test and Deploy with their access assignments. Modeling-side tooling has caught up too — bulk Dimension substitution across Applications, frozen columns in the grid, and contextual BY-formula hover hints. Just outside the 6-entry window, the Modeler Agent and Claude Code/Cursor plugins set the directional tone.
Two parallel arcs are visible: AI-assisted model construction (Modeler Agent, scheduled Analyst Agent missions, IDE plugins) is widening the on-ramp for new model authors, while the Test and Deploy pipeline is maturing into something resembling proper software CI/CD — enterprise FP&A has historically been weak here, and Pigment is closing the gap. The cluster of releases on or around April 21–28 suggests a coordinated platform release, not just steady-state polish.
Expect the Modeler Agent to expand into Application-level scaffolding (full model from a brief, not just templates) and the deployment pipeline to gain CI integration and scheduled deploys. The Claude Code/Cursor plugin pattern will likely lead to a public Pigment SDK or programmable model API for IDE-driven workflows.
See more alternatives to Ramp →
See more alternatives to Pigment →