Sigma for planning

Own your plan in one place

Hundreds of planners submit at once, approvals lock the numbers, and finance stops going dark for 3 to 4 weeks.

Schedule demo

What today's cycle costs, and what changes

What the current cycle costs

Each number here comes from the planning cycle customers run today.

4-5 days0 days

4-5 days → 0 daysof manual work a quarter

3 to 4 weeks → 1 stepfrom submitted to approved

1 → 120planners submitting at once

How it works

3 steps from targets to approval

1
Seed every row
Input Tables pre-fill every row from live warehouse data. Planners override instead of retyping.
2
Submit at the same time
Hundreds of contributors edit their own rows at once. Row-level security holds each to their scope.
3
Approve and lock
Actions route each submission to its approver. Approved rows lock, and audit history logs the change.

Seed every row. Submit at the same time. Approve and lock

One plan, three scopes

The same plan, scoped to each role

One governed plan

Planner1 district

Cascade North$3,040,000

Accounts268

Var %-5.0%

StatusApproved

Regional approverown region

Cascade North$3,040,000

Pacific Northwest$3,100,000

Mid-Atlantic$4,692,000

Gulf Coast$3,966,000

Executivesummary

plans submitted104/120

Row-level security decides what each person opens, so nobody works from a separate copy of the plan.

Built for planning at scale

01Explore

Type a number, keep the trail

Planners type into the workbook the way they type into a spreadsheet. Input Tables write each edit back to the warehouse with the user, the timestamp, and the change type.

Enter targets in the spreadsheet interface planners know
Write back to Databricks and Snowflake, and others like BigQuery and Amazon Redshift
Keep production tables untouched with append-only inserts

02Act

Approvals that lock the numbers

Actions route each submission to the right approver and set its status in place. Approved rows lock, and a later change lands as a new tagged version rather than an overwrite.

Route submissions to approvers without leaving the workbook
Lock approved rows so nobody overwrites a signed-off number
Trace every entry to a user and a timestamp

03Govern

Governance the plan inherits

The planning spreadsheet moves back inside the perimeter. Every workbook inherits the warehouse roles and row-level security you already run, so hundreds of planners work at once, each seeing only their rows.

Inherit warehouse roles and row-level security by default
Scope each planner to the districts and rows they own
Retire a parallel planning system and its permissions

Connections

Always on the newest trusted data

Sigma queries your warehouse live, so a workbook reads what landed a moment ago.

Governance IT already approved

The plan moves back inside the perimeter, under the warehouse roles and row-level security you already run.

Change historyAppend only

DWPlanning lead set Target on Mid-Atlantic14:22

MEDistrict manager edited Commentary on Cascade North14:09

ROFinance director approved Status on Great Lakes East13:51

JTPlanning lead reassigned Owner on Mid-Atlantic11:04

Live query, no extracts

Sigma queries the warehouse directly, so no copy of the plan sits outside your controls.

Row-level security

Each planner sees the rows their warehouse role allows, and you maintain no second permission model.

Audit history on edits

Audit history records the user, timestamp, and change type on every edit. Approvals hold up at audit.

6 planning apps to start from

Every app here runs on live warehouse data, and headcount planning and territory management ship as App Templates.

Headcount planning

Build a headcount plan tied to your revenue goals, with AI hiring recommendations and approvals that update the roster live, instead of a spreadsheet that drifts from the plan.