Sigma's App Templates are ready-to-use applications built on Sigma's native features and connected to sample data. Each one ships fully functional — you can explore it immediately, learn how it's built by switching to edit mode, and adapt it to your own data and workflows without starting from scratch.

The Pipeline Forecasting app gives sales reps and managers a single workspace to categorize open deals, submit forecast calls (Gut, Commit, Best Case), track quota coverage, and monitor how the forecast has moved week over week — all against live CRM data. An AI-generated summary surfaces the rep's current position and any deals that need attention, and a configurable staleness threshold flags deals that haven't been updated within the expected cadence.

This QuickStart walks through how the app works as a user, how it's designed under the hood, and how to connect it to your own data.

Target Audience

Sales representatives, frontline managers, and revenue operations teams evaluating or adopting Sigma for pipeline forecasting workflows. Solutions Engineers and technical stakeholders exploring the app as a reference design.

Prerequisites

What You'll Learn

Footer

Open and Save the Template

Navigate to Templates in the left sidebar. The Pipeline Forecasting app appears in the Made by Sigma collection:

Click the template card to open a preview. Before clicking Use template, confirm both requirements shown on the detail page are met:

Once both are in place, click Use template. Sigma creates a personal copy in your workspace that you can explore, edit, and connect to your own data without affecting the original template:

Click Save as and give the workbook a name:

Pipeline Forecasting

README Page

The app opens on its README page, which describes the purpose of each page and the four-step workflow at a glance. A short demo video walks through the core forecasting cycle. The README is worth reading before diving in — it describes what each page does and the order to follow:

The four steps are:

  1. Set your period and quota — pick the current planning cycle (e.g., Q2 FY26) and confirm your quota in the top bar. The quota line drives every coverage chart, gap calculation, and forecast verdict on the Home page.
  2. Categorize your deals — walk the Board and assign each open deal a forecast category — Commit, Best Case, Pipeline, or Omit. Uncategorized deals pin to the top until you call them.
  3. Add manager calls — submit your Gut, Commit, and Best Case values for each deal through the deal detail overlay.
  4. Execute on the board — keep deal categories current as the quarter progresses. Flag any changes to Commit, Gut, or Best Case as deals move through stages.

The Application Pages section at the bottom of the README summarizes each page in the workbook:

Footer

Home Page — Your Forecast at a Glance

Open to the Published version:

Before exploring the dashboard, set the two selectors at the top of the page:

The Home page (labeled Overview in the workbook nav) is the starting point for every forecasting session. It shows the full picture for the active quarter and rep in a single view.

At the top left, a COMMIT FORECAST card shows the rep's current Commit as a large number with quota percentage below it.

Three supporting KPIs sit alongside it — CLOSED WON, BEST CASE, and OPEN PIPELINE — each with a quota coverage line:

Below the KPIs, an AI-generated forecast summary (labeled "Generated using Sigma AI") reads the rep's forecast history and surfaces two sentences: the current trajectory and the deals most likely to affect the outcome. The summary updates as new forecast submissions are added.

A QUOTA COVERAGE bar on the right stacks Closed Won, Commit, and Best Case as normalized segments against the quota line, showing path-to-quota at a glance:

The NEXT Alert

A dark NEXT banner below the main KPIs counts deals that haven't had a forecast update within the configured cadence (default: 7 days). It shows the count and a short message prompting action. Clicking any deal in the list opens its detail overlay directly:

Pipeline Composition and Forecast Trend

Two panels at the bottom of the Home page give pipeline-level context:

At the bottom right, an ACV BY STAGE bar chart shows total pipeline value at each opportunity stage — useful for understanding where dollar risk is concentrated in the funnel:

All Deals Page — Work the Board

The All Deals page is where reps categorize deals and submit forecast calls. The header shows the current quarter and two filters — All (show every deal) and a toggle that filters to deals that need a call (those outside the cadence threshold).

Two counters in the header update live:

Deals are displayed in two groups. Committed deals appear below the header with deal name, stage, ACV, and the three forecast values (Commit, Gut, Best Case) displayed inline. A Closes date appears at the top right of each card:

Clicking any deal card opens a deal detail overlay. The overlay shows the deal name, stage, ACV, and close date, along with editable Commit, Gut, and Best Case fields. Enter your forecast values and click Save to record the submission. The submission is timestamped and stored in the Forecasts input table, and the deal's "Days Since Last Forecast" counter resets immediately.

After submitting calls, return to the Home page. The Commit number, quota coverage gauge, and AI summary all reflect the updated submissions immediately.

Footer

This section walks through the end-to-end workflow using the sample data that ships with the app. Follow along to see how a rep starts their session, identifies what needs attention, submits forecast calls, and checks the updated dashboard — all without leaving the workbook.

Step 1: Select a Rep and Period

The REP and PERIOD selectors at the top of the Home page control whose forecast you're viewing. Select the following to match this walkthrough:

Orient to Winslet's current position before doing anything else:

The AI summary has already flagged the core risk: Xenox River Upsell is carrying the entire forecast (and growing), while Meganomics Renewal is sitting at zero across every forecast category:

The QUOTA COVERAGE panel on the right confirms the picture — the stacked segments barely register against the $2M quota line, with a Gap to Quota: -$1,983,800 label at the bottom.

Step 2: Check the NEXT Alert

The dark NEXT banner surfaces the deals the AI summary just flagged — the ones with no recent forecast updates. Meganomics Renewal should appear here, sitting at zero across every forecast category.

The NEXT banner surfaces it automatically so Winslet doesn't have to scan the full deal list to find what's stale:

Step 3: Go to All Deals

Navigate to the All Deals page. Enable the Requires Forecast Update toggle to filter to just the stale deals:

The board shows committed deals on the left and Needs your call deals on the right. The stale deal card aligns with what the AI summary and NEXT banner flagged — Meganomics Renewal with $0 across every forecast category:

Step 4: Submit a Forecast Call

Click Meganomics Renewal to open the forecast overlay. The overlay shows deal context — name, stage (1 - Suspect), ACV ($0), close date (June 21 2026) — so Winslet has what's needed to make a call without switching to the CRM.

Enter the following values to record a first forecast submission for this renewal:

Gut:

12000

Commit:

8000

Best Case:

15000

Notes:

Renewal at risk — no activity in 3 weeks. Following up this week to gauge timeline and decision maker availability.

Click Submit. The submission is written to the input table (on the Data page > Input tables tab) immediately.

Once submitted, the Needs your call count drops to zero.

Step 5: Return to the Home Page

Navigate back to the Home page. Every metric reflects the submissions just made:

The AI summary has regenerated and now reflects the activity. It tracks the trajectory of each deal since the quarter began, calling out which deals have moved and which still carry risk:

The HOW YOUR FORECAST HAS MOVED line chart adds a new data point for this week's submissions. Over the course of a quarter, this chart shows whether the forecast has been consistent, improving, or eroding — giving managers a trend to discuss on the weekly call rather than comparing numbers from memory.

Footer

The Data page contains every backend table that powers the app. Each table includes a description of its purpose. The page is organized into tabs: Warehouse Sources, Input Tables, Linked Input Tables, Transformations, and Helpers. Here's how the pieces fit together.

Place the workbook into Edit mode.

The Data Sources

The app draws from three warehouse tables, visible under the Warehouse Sources tab:

These three tables are the ones to replace when connecting to your own data. See the Connect Your Own Data section for details.

The Forecasts Input Table

[INPUT TABLE] Forecasts is the core writeback table. Reps submit a new row for each deal call, recording:

Column

Type

Purpose

Opportunity ID

Text

The deal being called — links to OPPORTUNITIES_ENRICHED

Date

Datetime

When the forecast was submitted

Gut

Number

Rep's gut-feel forecast for the deal

Commit

Number

Rep's committed forecast

Best Case

Number

Rep's upside forecast

Notes

Text

Free-text call notes

Three lookup columns are derived automatically: Opportunity Name, Opportunity Owner Guid, and Quarter — all resolved from the Opportunity ID without the rep entering them manually.

WHY IT MATTERS:
The append-only submission model means every forecast call is preserved. The rep's trajectory across the quarter is a complete audit trail — not just the current state. That history powers the week-over-week trend chart and makes it possible to see whether a rep's Commit has been stable, climbing, or eroding.

Latest Forecasts — RowNumber for Current State

The Latest Forecasts table is a transformation (visible under the Transformations tab) that extracts just the most recent submission per deal. It uses RowNumber([Date], "desc") partitioned by Opportunity ID to rank submissions newest-first, then filters to Forecast Rank = 1:

The result is one row per deal — the rep's current call — which feeds into the Rep Summary aggregation table and the All Deals deal cards.

WHY IT MATTERS:
The RowNumber pattern is a lightweight alternative to a max-date subquery. It ranks within a partition, so the "most recent" logic is computed at the workbook level without a warehouse round-trip. Any new submission immediately becomes rank 1, and the dashboard reflects it without any additional refresh logic.

Rep × Quarter Cross Join for Quota Coverage

The Quota linked input table allows managers to set quota targets per rep per quarter. To ensure every rep has a row for every quarter — even before any deals exist or any quota is entered — a Reps x Quarter Cross Join table generates the full grid first.

The cross join is a Cartesian product of Reps [WAREHOUSE] and Fiscal Calendar [WAREHOUSE] — every combination of rep × fiscal quarter. It produces 560,640 rows across 3 columns (Opportunity Owner Guid, Opportunity Owner User Name, Quarter) and lives under the Transformations tab.

The Quota [LINKED INPUT TABLE] (visible under the Linked Input Tables tab) uses this cross join as its row source. The table is marked Editable in draft — managers open the workbook in draft mode to set or adjust quota targets per rep per quarter. The Quota column writes back to the warehouse; the rep and quarter columns are read-only, pulled from the cross join.

WHY IT MATTERS:
Without the cross join, the quota table would only have rows for rep × quarter combinations that already appear in the opportunities data. New reps or future quarters would be missing, and the coverage gauge would show no quota line. The cross join guarantees completeness: every rep has a quota slot for every quarter, whether or not they have any deals yet.

Rep Summary — Aggregating the Forecast

The Rep Summary table joins quota data with deal metrics to produce the per-rep aggregates used throughout the Home dashboard. For each rep, it calculates:

AI Summary as an Editable Prompt

The AI-generated forecast summary on the Home page is driven by a prompt stored in the Ai Summary control on the Helpers tab of the Data page. The prompt instructs the model to return a two-sentence plain-text summary in a conversational, direct tone. It includes an example output style so the model understands the expected register, and a fallback instruction: if no data is available, return Cannot generate AI Summary rather than fabricating output.

The prompt is stored as a workbook control — not hardcoded into the text element formula — so it can be tuned without touching the workbook structure:

The formula in the Home page text element calls CallText("ai_complete", "claude-sonnet-4-6", ...), passing the Ai Summary prompt value alongside a ListAgg of the rep's recent forecast submissions as context.

WHY IT MATTERS:
Storing the AI prompt as an editable control separates what the model is asked from how the result is displayed. Sales managers can adjust the summary's focus — emphasizing Commit risk, deal count, or cadence gaps — without modifying the underlying workbook formula. The prompt is visible and auditable in one place, which matters when AI output informs a manager's weekly call.

The Forecast Cadence Control

A number control labeled Forecast Cadence (days) on the Helpers tab (default: 7) sets the staleness threshold in days. Any deal where DateDiff("day", [UPDATED], Now()) > [forecast-cadence] is flagged as needing an update. The Requires Forecast Update column on the Deals table evaluates this condition and feeds both the NEXT banner count and the Needs your call filter on All Deals.

To change the cadence for your team, edit the default value of the Forecast Cadence (days) control on the Helpers tab:

Footer

The Pipeline Forecasting app is designed to work with any CRM opportunities dataset that tracks deal stages, amounts, and owners. The three source tables to replace are OPPORTUNITIES_ENRICHED, Reps, and Fiscal Calendar on the Data page.

What the App Needs

Opportunities table:

Column

Description

Opportunity Guid

Unique deal identifier

Opportunity Name

Display name shown in deal cards and the overlay

Opportunity Type

Deal type (e.g., New, Renewal, Expansion)

Opportunity Stage Name

Current pipeline stage — "Closed Won" is expected for closed deals

Opportunity ACV Amount

Annual contract value or deal amount

Opportunity Owner Guid

Unique rep identifier — used to join quotas and aggregate per-rep metrics

Opportunity Owner User Name

Rep display name

Opportunity Close Date

Expected close date — used to resolve fiscal quarter

Fiscal Calendar table:

Column

Description

Date

One row per calendar date

Fiscal Quarter

Quarter label (e.g., Q2)

Fiscal Year

Fiscal year (e.g., 2026)

Quarter (derived)

[Fiscal Quarter] & " " & Text([Fiscal Year]) — the combined label used throughout the app

The calendar table is used solely to resolve quarter labels from close dates. If your CRM data already carries a quarter field, you can simplify or bypass this lookup.

Reps table:

Column

Description

Opportunity Owner Guid

Unique rep identifier — must match the GUID in OPPORTUNITIES_ENRICHED

Opportunity Owner User Name

Rep display name shown in the REP selector and deal cards

This is typically a deduplicated list of reps pulled from the same CRM connection as the Opportunities table. It's used as one side of the cross join that generates the complete rep × quarter quota grid.

How to Swap the Sources

On the Data page, open OPPORTUNITIES_ENRICHED [WAREHOUSE] in edit mode. Use Change source to point the table at your own connection and opportunities table. Map your columns to the column names the app expects — especially Opportunity Guid, Opportunity Owner Guid, and Opportunity Stage Name, which appear as join keys and filter conditions throughout the workbook.

Open Reps [WAREHOUSE] and point it at a deduplicated list of rep IDs and display names from your CRM or HR system. The Opportunity Owner Guid must match the values in OPPORTUNITIES_ENRICHED for the cross join and quota grid to function correctly.

Then open Fiscal Calendar [WAREHOUSE] in edit mode and point it at your organization's fiscal calendar table, or replace it with a simpler quarter derivation if your opportunities table already carries a quarter column.

What Carries Over Automatically

Once sources are swapped and columns are mapped correctly:

The main manual step after swapping sources is entering initial quota values for each rep in the Quota [LINKED INPUT TABLE] — and populating the Forecasts input table with a seed round of deal submissions before the trend chart has data to plot.

Footer

This QuickStart walked through the Pipeline Forecasting app from end to end: exploring the Home dashboard, working the All Deals board, and examining the design decisions that make the app function.

The append-only forecast submission model is the operational pattern worth carrying forward. Every deal call is a new timestamped record — not an overwrite — which means the rep's trajectory across the quarter is preserved in full. That history powers the week-over-week trend chart and makes forecast accuracy analysis possible after the quarter closes. The same pattern applies to any domain where you want a complete submission history rather than just current state.

The RowNumber for latest-record resolution is a reusable technique for any time-series input table. By partitioning on a deal ID and ranking submissions by date descending, the app always surfaces the most recent call per deal without a max-date subquery or warehouse round-trip. Stack this on top of an append-only input table in any Sigma workbook where you need both history and current state.

The cross join for complete coverage grids solves a common problem: aggregations that should produce a row for every combination of two dimensions even when the fact table has gaps. The Reps × Quarter cross join guarantees every rep has a quota slot for every fiscal quarter, regardless of whether they have any deals. This pattern applies directly to headcount planning, capacity allocation, or any scenario where you need to enforce completeness before managers enter targets.

The AI prompt as an editable control shows how to make AI output configurable without exposing formulas. The forecast summary prompt lives on the Data page as a text-area control — managers can tune what the model focuses on, and the change takes effect immediately without touching the workbook structure. The same approach works for any AI-assisted app where the business context changes more often than the underlying data model.

Additional Resource Links

Blog
Community
Help Center
QuickStarts

Be sure to check out all the latest developments at Sigma's First Friday Feature page!

Footer