Sigma review

Sigma is a business intelligence platform for building analytics, apps, and AI agents on live warehouse data. Teams can ask questions in plain language or explore information through spreadsheet-style workbooks, dashboards, and reports. Sigma also lets teams build data apps with forms and workflows that write information back to the warehouse. Its agents can answer data questions, monitor changes, and take actions with approval. Embedded analytics and apps can be placed inside another product. Permissions are tied to warehouse access rules, including row-level controls, and admins can review audit logs, agent activity, and token usage. That makes Sigma more than a dashboard builder: it combines reporting, workflow and writeback, and AI features around warehouse data. But the key commercial detail is missing: pricing is custom-quoted, with no public monthly or annual rate.

Sigma’s main advantage is that analytics, apps, and agents work on live warehouse data, rather than being presented as separate tools with separate data access. That can make it a fit for teams that want to explore data, build operational workflows, and put analytics into a product without moving those jobs outside their warehouse environment.

The feature set also connects those jobs in useful ways:

• Spreadsheet-style exploration, dashboards, reports, and plain-language questions give users different ways to work with warehouse data.
• Forms and workflows can write data back to the warehouse, while agents can monitor changes and take approved actions.
• Warehouse permissions, including row-level access, apply to apps, answers, and agents.
• Admins can review audit logs, agent activity, and token usage.

For a switch evaluation, the permission model and writeback matter as much as the AI features. They suggest Sigma is aimed at governed workflows, not just generating answers. The tradeoff is that teams need to assess it against their own warehouse setup and requirements; the published material does not establish compatibility details or quantify implementation effort.

The biggest buying problem is price opacity. The pricing information available lists a custom-quote plan, but no monthly or annual price, billing unit, or included features. It also does not list a free plan or publish a free-trial offer. That leaves buyers unable to estimate cost or compare Sigma with a current BI contract from the public details alone; you will need to contact sales for a quote.

The published pricing details do not state seat limits, warehouse limits, agent limits, or usage caps. Sigma’s admin visibility into token usage is useful, but it does not tell buyers what usage is included or what extra usage costs. Those terms need to be confirmed before comparing total cost or planning a rollout.

There is also no relevant user feedback in the Reddit discussion we read: the discussions are about cameras, chemicals, and a movie, not Sigma’s analytics software. So we cannot use those threads to settle questions about reliability, support, or migration experience. The live-warehouse feature set is clear; the cost and independent evidence are not.

Sigma’s pricing page does not publish a starting price, monthly or annual rates, or a free-trial offer. The listed plan is Custom, with pricing available by contacting sales. That means there’s no public tier-to-tier price jump to compare—and no way to estimate the bill from the available pricing information.

Monthly and annual billing prices are both unpublished, so buyers should ask sales for the quote, billing term, and any minimum commitment before comparing Sigma with another BI platform. The published pricing details list no add-ons, but that is not confirmation that every feature is included in a quote.

The product’s live-warehouse analytics, AI agents, data apps, and embedded analytics may fit teams with warehouse-backed data, but the public information does not connect those features to specific plan limits. There’s no free public tier listed. For procurement, treat the cost as unknown until Sigma provides a written quote that spells out included features, usage limits, and any extra charges.

Sigma is built around live warehouse data, so a move to Sigma depends on having a warehouse-backed data environment. Its apps can write data back, and its agents can take actions with approval; teams considering a move should map those workflows and permissions before rebuilding them. The published materials do not document migration tools, supported import paths, or effort estimates.

Leaving may mean recreating Sigma-built dashboards, apps, embedded experiences, and agent behavior in another product. That can create dependence on Sigma’s application layer, even though the published material does not establish where app definitions or other configuration can be exported. Data export and portability terms are not published on the vendor's site; confirm them with Sigma rather than assume warehouse access covers everything.

We don’t have relevant Reddit feedback to identify common reasons customers leave or how difficult migrations have been. Ask for export details, migration support, and a clear inventory of what is portable before signing.