SigmaForge
Enterprise

Improvement work your leadership can audit

Projects, tollgates, validated savings, a portfolio view, and a record of who approved what.

32
analyses
28 deterministic
14
templates
8 draw a diagram
56
tools
across the loop
5
tollgates
one per phase
An enterprise project workspace in the Improve phase: DMAIC gates across the top, phase tools, the team task board, deliverables, the tollgate and an AI phase summary.
Product screen, demo dataOne project, every phase

The video · 3:27

Watch one project go from an idea to signed-off savings

An idea is scored and chartered. The team works in one project, the AI agents do the heavy lifting, and a tollgate decides. When it closes, an admin who did not lead it signs off the savings.

Every screen is the product, running on a demo company’s data.

SigmaForge for Enterprise3:27 · Captions

The journey

From a first cohort to a governed portfolio

The same six stages the platform runs on, and what each one means once more than one team is using it.
  1. 01 Learn

    Enroll a cohort on the courses they need

    /org/courses

  2. 02 Practice

    Practice exams graded on the server, not self-marked

    /certiai

  3. 03 Apply

    Run the project through five tollgates

    /projects

  4. 04 Track

    Analyze the data and watch the board

    /org/board

  5. 05 Optimize

    Savings validated by someone other than the owner

    /org/portfolio

  6. 06 Scale

    The same templates and gates on every project

    /org/training

Run the work

Every project visible. Every decision recorded.

Improvement work usually lives in one person’s spreadsheet. Here it lives in a workspace with a charter, 5 tollgates and a record of who approved what.

Project workspace

Charter to sign-off in one place

Charter, phase plan, task board, process steps, shared collection sheet, deliverables, comments and a dossier PDF.

  • The DMAIC gate strip across the top
  • Tasks assigned to people, by phase
  • An AI summary of the phase, written from the work
sigmaforge.ai/projects
An enterprise project workspace in the Improve phase: DMAIC gates across the top, phase tools, the team task board, deliverables, the tollgate and an AI phase summary.
  1. 1The gatesThree approved, Improve in review.
  2. 2Who is doing whatTasks by phase and lane, each with an owner.
  3. 3DeliverablesThe evidence the gate is decided on.
  4. 4The tollgateAwaiting review by an OE Manager.
Product screen, demo data

Improvement board

Every project by phase, and the gates waiting on someone

Every project by phase, the gates waiting on review, and the ones flagged at risk. A quiet project carries the reason it was flagged, scored from the work rather than guessed.

  • Gates awaiting review, never by the person who submitted
  • At-risk projects with the reason behind the flag
  • Time in phase against the median
How the gates are governed
sigmaforge.ai/org/board
Delivery board for a demo company: active, completed and at-risk counts, a tollgate awaiting review under segregation of duties, and every project placed in its DMAIC phase.
  1. 1The program at a glanceActive, completed, gates to review, at risk.
  2. 2Segregation of dutiesA gate is never approved by its submitter.
  3. 3A nudge, with a reasonNo activity for 22 days.
  4. 4Every project, by phaseWith time in phase.
Product screen, demo data

Idea hopper

Ideas scored, then chartered into projects

Ideas scored on impact and effort, then chartered into a project from a template. The person who raised an idea cannot be the one who charters it.

  • Impact, effort, confidence and fit, scored
  • Ranked by priority
  • Chartered from a template in one step
sigmaforge.ai/org/hopper
The idea hopper: counts by stage, open ideas ranked by priority score with impact, effort, confidence and fit, and a form to submit a new idea.
  1. 1Ideas by stageRaw, awaiting approval, ready, chartered.
  2. 2A priority scoreWorked out from the four ratings.
  3. 3Charter into a projectOnce an owner or admin approves it.
  4. 4Anyone can submitThe best programs are fed from the floor.
Product screen, demo data

ProjectSensei, inside the project

Every team gets told what is blocking the gate

Phase coaching reads the project and says how ready the phase is, the one thing blocking it, and which evidence is attached or missing. Its next steps go straight onto the task board. It advises; a person decides the gate.

  • Readiness against the gate date
  • The one blocker, with the reason
  • Next steps you add as tasks
Meet ProjectSensei
sigmaforge.ai/projects
Phase coaching for an enterprise project: readiness, the one thing blocking the phase, gate evidence attached and missing, and the numbers that decide it.
  1. 1ReadinessHow close the phase is to its gate.
  2. 2The one blockerNamed, with why it matters.
  3. 3Gate evidenceAttached and missing, against the gate.
Product screen, demo data

Governance

Nobody signs off their own work

6 rules the system applies rather than asks for. Each one is a refusal in code, not a line in a policy document.
  • Nobody approves their own gate

    The person who submits a tollgate cannot be the person who approves it. The system refuses, rather than trusting the org chart.

  • Savings in three numbers

    Estimated, actual and validated are separate fields. Only an owner or admin can validate, only after the project is complete, and never the person who ran it.

  • An approved document keeps serving until someone accepts the change

    A revision to an approved deliverable waits for an approver instead of quietly replacing what people are working from.

  • The idea and the project have different owners

    Converting an idea into a chartered project is separated from raising it, so the hopper cannot be used to self-authorize work.

  • Every decision is written down

    Gate approvals, benefit validations and accepted revisions land in an audit log the customer can read.

  • You grant and revoke our access

    Support access can be set to need a time-boxed grant the customer makes and can withdraw, and every access is logged like everything else.

sigmaforge.ai/projects
The Improve tollgate awaiting review with four of four artifacts attached, beside the phase deliverables and the DMAIC gate strip.
Product screen, demo dataA gate the submitter cannot approve

Lead the program

One view for the people funding it

Savings are three separate numbers: estimated, actual, and validated by someone other than the person who ran the project. Only the validated one reaches the board pack.

Executive portfolio

Phase funnel, projected against realized savings, belt coverage, and a branded PDF for the board pack.

/org/portfolio

Weekly digest

A written summary generated every Monday and shown on the portfolio page. It is not emailed.

/org/portfolio

Training view, by TeachPilot

See who is learning, and who has stalled

Cohort progress and who is falling behind, with a written summary for the manager. The member table is hidden here, so nobody on the demo is identifiable.

  • Enrolled, active, certified and at risk
  • A written insight for the manager
  • The sections people struggle with
Meet TeachPilot
sigmaforge.ai/org/training
TeachPilot team training view: enrolled, active this week, certified and at-risk counts, a written cohort insight, and the sections where learners struggle.
Product screen, demo data

The program, on video · 1:39

Whose idea gets funded? Not the loudest one.

Every idea is scored on impact, effort, confidence and fit, so ideas are ranked by arithmetic, not by who asked. The board shows every gate waiting and the projects at risk, a digest is written each week from your own records, and savings are validated by someone who did not lead the project.

More videos for leaders
Your improvement program1:39 · Captions

Standardize

The same method on every project

Standardizing improvement work is mostly a matter of everyone starting from the same documents and passing the same gates.
  • 14

    document templates

    Charter, SIPOC, A3, FMEA, control plan, OCAP and eight more.

  • 5

    DMAIC tollgates

    Define, Measure, Analyze, Improve, Control: the same five gates on every project, in every team.

  • 4

    belts

    White to Black, taught with the tools the team will actually use.

  • 32

    analyses

    28 of 32 computed by the engine, not written by a model.

DocuForge templates

Every team starts from the same documents

All 14 templates, arranged by the DMAIC phase they belong to and the belt they are taught at. Describe the project, sharpen the brief, export a branded PDF.

See the templates
sigmaforge.ai/docuforge
The DocuForge template board: fourteen templates arranged by DMAIC phase, each with its belt level, and the four steps from template to branded PDF.
Product screen, demo data

Your data stays yours

Isolated, and only reached with your say-so

  • Isolated at the database

    Each organization is walled off by the tables themselves and by row-level security, proven by tests against a live database.

  • Access you grant and revoke

    Our support access is a time-boxed grant your own admin makes and can withdraw.

  • Recorded like everything else

    Every reach by our staff lands in your audit log beside every gate decision.

Book a demo

See it on your own data

Thirty minutes. Bring a spreadsheet, and we will run one of your processes through the workspace while you watch.