Skip to main content
Sigma Computing

Sigma for finance teams

Close, explain, and reforecast in a spreadsheet your team already knows, on the numbers your data team already trusts.

  • Explain the variance

    Variance commentary sits next to the numbers it explains. An agent can draft it for the lines that moved, and owners review and sign off.

  • Reforecast with owners in the loop

    Business owners enter assumptions in the report, and they’re saved to the warehouse instead of emailed back.

  • Works like the spreadsheet you know

    Formulas your team already writes on the full ledger, with Sigma Assistant to draft the rest when you ask.

FY26 variance and reforecast

Variance Analyst

New chat

I draft variance commentary from the GL, CRM and event plans. Owners review every draft before it counts.

Ask anything

AI can make mistakes. Please double-check responses.

Approvals

9+3 forecast

ActionByWhen
Draft savedMaya LindqvistOct 20

Sep close · FY26

Variance and 9+3 reforecast

9 months actual (Jan to Sep) + 3 months forecast (Oct to Dec)

Scenario9+3 forecast
PeriodSep 2026
Submit 9+3 forecast

Revenue, YTD actual

$48.20M

+3.8%vs budget $46.44M

Operating income, YTD actual

$3.98M

+15.9%vs budget $3.44M

FY operating income (9+3)

$5.46M

+9.2%vs FY budget $5.00M

Commentary, lines over $500K

0 of 3

None drafted yet

P&L variance by line

Jan to Sep, $K. Variance is favorable / (unfavorable).

P&L lineActualBudgetVarianceVar %CommentaryStatus
Subscription revenue39,64037,900+1,740+4.6%Open
Services revenue8,5608,535+25+0.3%
Total revenue48,20046,435+1,765+3.8%
Cost of revenue13,98013,000(980)(7.5%)Open
Sales and marketing15,41014,600(810)(5.5%)Open
Research and development9,87010,350+480+4.6%
General and administrative4,9605,050+90+1.8%
Operating income3,9803,435+545+15.9%

Q4 drivers

Oct to Dec, $K · editable drivers

DriverBudgetForecastSource
Revenue16,56516,900Sep run rate × 3
Cost of revenue4,5004,82028.5% of revenue
Event spend1,2001,200FY26 plan
Other opex9,3009,400Headcount plan

Full-year outlook

$K

Full yearBudgetOutlook (9+3)Variance
Revenue63,00065,100+2,100
Costs58,00059,640(1,640)
Operating income5,0005,460+460

Trusted by finance teams

Yamaha Motor FinanceBlackstonePodiumRightRevClayBuiltGroup 1001Affirm
JP Morgan Chase
Verisk logo
Tradeweb logo
Cowen
MongoDB logo
Vista logo

Variances explained

The books close before the explanations do

Finance spends the days after close downloading reports, chasing commentary by email, and rebuilding the forecast in a file nobody else can audit.

TodayWith Sigma
Monday mornings spent downloading and stitching reportsActuals arrive live from the warehouse with nothing to download
Variance commentary collected by email and pasted into decksVariance commentary lives next to the numbers it explains
Assumptions buried in personal spreadsheet tabsOwners save assumptions and commentary to the warehouse from the app
Forecast models that slow to a crawl as the file growsSpreadsheet models that run on the full ledger
Forecast versions multiply with no record of who changed whatEach forecast submission recorded with who approved it
Business owners wait on finance for every numberOwners explore their own numbers on the same data finance uses

Finance work on the numbers your data team trusts

Your warehouse already holds the ledger. Finance can work on it directly in a spreadsheet without an extract.

  • Your data team already built it

    The warehouse already holds the ledger, the sub-ledgers, and the operational data. Finance works on it directly, and nobody makes an extract.

  • Start with the report everyone dreads

    Build the one report that eats the first week of close. There’s no migration to finish first, and the next workflow can wait until this one works.

  • Formulas your team already writes

    It works the way a spreadsheet does. Sigma Assistant drafts a formula, a pivot, or a whole workbook when you describe it.

Explain it, decide, submit

Explain the variance, decide whether it changes the outlook, and submit the revised forecast, all on the same live data.

Month-end review

Review results and collect explanations

Review financial results as soon as the books close. Drill from the P&L to the transactions behind a number, and collect explanations from business owners in the same app.

  • Budget vs. actual by entity, department, and account
  • Exceptions flagged for owner review
  • Owner commentary saved to the warehouse

Scenario forecasts

Model scenarios and submit the forecast

Change a driver and watch revenue, margin, and cash update on live warehouse data. When the scenario holds up, submit the revised forecast for approval.

  • Driver-based scenarios for revenue, margin, and spend
  • Assumptions saved with who changed them
  • Forecast submissions routed for approval

Headcount plans

Plan headcount against the budget

Hiring managers submit requests against the plan, see the cost against the budget as they type, and finance reviews them in the same app.

  • Headcount modeled across growth scenarios
  • Approval workflows for compensation budget
  • Actual headcount tracked against plan

Spend control

Let an agent collect the expense forecast

An expense forecast agent collects parameters from budget owners, builds the forecast from operational drivers, and routes it for review.

  • Driver-based models that categorize and predict spend
  • Budget owners update monthly forecasts directly
  • One live view of total spend for finance

Collections

Prioritize collections and track follow-up

Work aging invoices and unapplied payments on live data. Collectors assign accounts, add notes, and log promises to pay next to the invoice, without waiting on an ERP export.

  • Live invoice aging by customer
  • Assignments and notes saved to the warehouse
  • Agents flag accounts sliding past terms
Collections

Assign Amberleigh Health to yourself.

AR aging · as of Oct 23

Collections

Past terms

$306.5K

+$48.2Kvs last week

Unassigned

$184.0K

1 account

Promised to pay

$41.9K

1 account

Accounts past terms

Customer61–9090+OwnerStatusAction
Amberleigh Health$184,000$0UnassignedOpen
Corlett Retail$62,400$18,200J. ParkIn review
Corwin Logistics$41,900$0J. ParkPromise to pay

Collection activity

CustomerActionAmountDue
1Corwin LogisticsPromise to pay$41,900Oct 31
2Corlett RetailCall logged$80,600
3Halden FoodsPaid in full$22,300
+

61–90 days by customer

Amberleigh Health$184,000Corlett Retail$62,400Corwin Logistics$41,900

Agents with a specific job

Agents draft the commentary for owners to approve

Gathering context and drafting explanations are jobs you can check. Agents handle them, and nothing is final until an owner approves it.

  1. 1Gather contextWhen a line moves, an agent pulls the drivers from the GL, the plan, and the operational data behind it.
  2. 2Draft the explanationIt drafts commentary for the owner to edit, linked to the rows it used.
  3. 3Approve and recordThe owner approves, and the explanation is saved to the warehouse with who signed off.

Explore finance apps built in Sigma

Working examples from the App Library. Open one to see how it works.

Browse the App Library

Controls finance can sign off on

Built for teams that need auditability, access control, and one set of numbers that updates when the source changes.

Visit the Trust Center
  • Assumptions saved to the warehouse

    Assumptions, commentary, and submissions entered in a report are saved to tables in your warehouse, with a full edit history.

  • Approval trails

    Forecast submissions and approvals are recorded with who approved them and when.

  • Per-user OAuth

    Connect with OAuth so queries run with each person’s own warehouse role.

  • Row- and column-level security

    Reads and writes both inherit your table policies.

  • Audit trail

    Audit logs record user activity, AI conversations, and edits to entered data, so you can see who changed what.

  • Your data stays put

    Sigma queries your warehouse in place and never copies the data out.

Finance FAQs

  • How does Sigma change the month-end close?

    Teams review results on live warehouse data as soon as the books close, investigate exceptions down to the transaction, and collect owner explanations in the same app instead of by email.

  • How long does it take to get started?

    Most teams start with one report, usually the one that eats the first week of close, and build it on data already in the warehouse. There’s no migration to finish first, and you add the next workflow once the first one is working.

  • Do we need to learn something new?

    If your team writes spreadsheet formulas, they can build in Sigma. The interface works like a spreadsheet, and Sigma Assistant can draft a formula, a pivot, or a whole workbook when you describe what you need.

Bring next month’s variance review

We’ll walk through it on your warehouse: explanations drafted, owners in the loop, and the forecast submitted.