Pricing
Commercial clarity for teams that want real deployment, not AI theatre.
CommandLoom pricing is built around one principle: get one governed workflow live, prove value quickly, then expand across users, systems, and automation depth with a model that stays legible.
Setup
No developer required
First milestone
Identity + 2 sources + 1 workflow
Commercial stance
Contact-led, use-case scoped
Commercial model
One runtime, four growth stages
Starter to Growth
Identity, key sources, one workflow, supervised rollout
Professional to Enterprise
Broader automation, deeper governance, stronger deployment options
Typical first milestone
Federate identity and access
Connect two meaningful sources
Launch one governed workflow
Why pricing is contact-based
The right plan depends on data surface, approval posture, user scope, and deployment model. The buying conversation stays grounded in operating reality instead of checkbox inflation.
Buying model
The commercial model stays simple because the product already has depth.
You do not need ten confusing plan toggles. The meaningful variables are workflow complexity, connector surface, user scope, governance posture, and deployment maturity.
Plans
Four tiers, one consistent operating model
Every plan includes role-aware access, approval-aware actions, and exportable audit trails. The step up between tiers is about breadth, automation depth, and deployment confidence.
Included in every tier
Governance, guided setup, and a serious operating model.
Growth stage
Growth stage
Recommended operating tier
Growth stage
Starter validates the first live use case
Growth expands across teams and supervised actions
Professional becomes the default operating tier for serious rollout
Enterprise adds deployment isolation and broader scale
Specialist plans
Education and government have their own commercial path
These environments do not fit a generic SaaS pricing table. Procurement, compliance, residency, and operational shape matter too much.
Every tier starts from the same product core
Setup guidance, policy-aware control, and the CommandLoom operating model stay consistent as you grow.
Pricing is scoped around your actual environment
The first proposal is shaped around systems, users, workflow depth, and governance requirements rather than generic seat math alone.
Deployment flexibility expands with maturity
SaaS-first is the default. Dedicated, hybrid, and private deployment paths open as operating and compliance requirements increase.
Get started
Bring the use case. Leave with a path to launch.
A useful first step is a conversation grounded in your systems, your users, and the first workflow you want live.