Enterprise DNA

Instead of Minitab

Stop renting Minitab for the weekly review. Own your process statistics desk.

We build your version around the measurements, specifications and review routines you use. We bring your Minitab worksheet data across and operate the agreed system through Omni by Enterprise DNA.

Minitab Solution Center Core lists US$2,394 per named user per year, before taxes. Local prices and volume terms can differ.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

A yearly licence for each named analyst

Minitab bundles a broad statistical product with other capabilities. Compare the procedures you actually use with the work your own version must perform. Prices below are the vendor’s published US list prices, checked 29 October 2026.

person

Core: US$2,394 annually

A single named-user subscription includes statistical software, experiment-design tools and Workspace.

insights

Analytics: US$2,593.50 annually

The Analytics bundle includes predictive analytics alongside the shared capabilities.

layers

Copilot: US$2,793 annually

The Copilot bundle includes Workspace and predictive analytics.

extension

Specialist modules: US$528 annually

The pricing page separately lists modules for areas including retail, supply chain and sample size.

devices

Desktop and online access

The named-user annual subscriptions include both access options. Your owned version is scoped around how your team reviews the work.

folder_open

A separate worksheet handover

Minitab supports exporting worksheets as CSV. Moving the measurements is one step; validating the calculations and reports is another.

What you own

The measurements, their meaning and the follow-through

Measure

Know exactly what entered the study

Each import retains the source rows and its mapping, so the next review starts with evidence.

  • check Bring a named measurement and collection times across
  • check Keep missing measurements visible
  • check Compare counts, means and variation by shift
  • check Trace an analysis back to its source fingerprint

Compare

Separate an unusual reading from a new baseline

Check later measurements against saved limits for the same process. Keep the assumptions with the answer.

  • check Save the baseline used for the study
  • check Find observations beyond individuals limits
  • check Find unusually large changes between adjacent observations
  • check Keep gaps from becoming invented measurements

Interpret

Keep specification history with the result

An overall performance number remains attached to the limits used when it was calculated.

  • check Record lower and upper specification revisions
  • check Calculate overall Pp and Ppk from sample variation
  • check Read sample counts and method warnings together
  • check Retain earlier results after specifications change

Investigate

Connect the excursion to the work it created

Find the measurement, named owner, due date and recorded resolution in the same review.

  • check Assign an investigation to an actual owner
  • check Find overdue work and stale source reviews together
  • check Draft analysis and investigation documents in your brand
  • check Export the measurement and decision history together

Make it yours

Design your own Minitab replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Minitab. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Minitab replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Minitab data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Process Statistics for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Process Statistics for Claude Code

Connected to your own database

Which investigations and reviews are overdue?

process review due

Id
10000000-0000-4000-8000-000000000001
Record
Bottle fill
Owner
Demo quality lead
Due
2026-10-26

data review due

Id
30000000-0000-4000-8000-000000000002
Record
Fill week
Owner
Demo quality lead
Due
2026-10-27

overdue investigation

Id
40000000-0000-4000-8000-000000000001
Record
Check fill excursion on Shift B
Owner
Demo quality lead
Due
2026-10-28

Ask it anything

Questions your own process records answer

Combine measurements, specification history and investigation ownership. These are real questions the free base answers, with the assumptions kept visible.

chat_bubble Which processes have overdue investigations and an overdue process review?
chat_bubble Which imported series have missing measurements?
chat_bubble Which later observations break the limits from our saved baseline?
chat_bubble Which shift contains the largest observed fill value?
chat_bubble How many valid observations support this capability number?
chat_bubble Which saved results still refer to the previous specification revision?
chat_bubble Which imports came from the same source and mapping fingerprints?
chat_bubble Who recorded a specification change and why?
chat_bubble Which source records are due for a retention review?
chat_bubble Which investigations are closed with recorded evidence?

Switching

How to switch from Minitab

A move usually involves exporting the worksheet data you need, mapping its columns, checking the import, and validating the new process review before you stop using Minitab.

  1. 1

    Export your worksheets

    Start with the Minitab worksheets that hold the measurements you need. Minitab documents CSV worksheet exports. Export what your account allows, usually CSV or Excel, and check with Minitab if you are unsure how to get the worksheet data out. Decide which measurement history you need to keep. Project files, graphs, macros and advanced models need separate work and verification.

  2. 2

    Map and test the data

    Map each worksheet column to the fields used for the process record, including the measurement, collection time and any optional shift. Start with a test run or dry run so the importer checks every row without writing data. This gives you a chance to correct the mapping before the records are loaded. Use an empty database for actual records.

  3. 3

    Load and check the records

    After correcting any test-run issues, load the worksheet into the database. Review the import validation results and reconcile the number of source rows with the number loaded. Check which measurements are missing and confirm the collection times and shifts landed in the right fields. Resolve discrepancies before you rely on saved results or investigations.

  4. 4

    Run both workflows briefly

    Keep Minitab available and run both workflows side by side for a short period using the same incoming measurements. Compare the records and process findings you rely on, including descriptive statistics, control signals and Pp/Ppk where relevant. Check assumptions and discrepancies with the people who review the process. A statistical result does not approve production.

  5. 5

    Switch off Minitab

    Once you have reconciled the records and findings, stop using Minitab for the process review you migrated. Keep Minitab records or access according to your retention needs. Confirm the database has backups and the operational controls your setup requires before relying on it. Imported historical data and computed results do not establish regulated validation or approve a batch release.

construction

Where the real effort goes

Most of the effort is deciding how your worksheet columns map to your process records, which measurements and history to bring, and which rules and procedures your version must preserve. Worksheet data is the straightforward starting point. Project files, graphs, macros and advanced models need separate work and verification. If Enterprise DNA installs and runs your version, they scope and handle this migration work with you.

Not ready for a call?

Get your Minitab switch plan by email

We will send you the step-by-step plan for moving your business off Minitab, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free base or have your version built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm test and npm run demo on the fictional measurements
  3. 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
  4. 4 Trial your Minitab CSV export with an explicit mapping, then compare the results
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your measurement definitions and approved specifications
  • check Your Minitab worksheet data mapped and checked
  • check Your required calculations and reports built and validated
  • check A web front end or a different technology stack if you want one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your agreed collection connections and reporting routines
  • check Access, backups and operating responsibilities agreed from the start
  • check Your process review adapted as the business changes
Talk to Sam

Questions

Instead of Minitab, answered

Does this cover every Minitab calculation? expand_more

The free base covers descriptive statistics, individuals and moving-range signals, and overall Pp and Ppk. We scope and validate the other procedures your business needs as part of your version. A computed result does not approve production or establish statistical fitness. Review your sampling, stability and distribution assumptions.

Can we bring our existing worksheets with us? expand_more

Yes. Minitab documents CSV worksheet exports. Map the measurement, collection time and optional shift, do a test run and reconcile counts and missing values. Project files, graphs, macros and advanced models need separate work. We establish what your version must preserve before you switch.

Why pay for a custom version when free statistical tools exist? expand_more

jamovi is a real free statistical alternative. This offer is for an owner who wants their measurement history, specification decisions, investigations and operating routines built and run together. Choose the free base if you can install and operate it yourself.

Will this tell us that a batch is safe to release? expand_more

It reports measurements and statistical findings. Your authorised people still decide what those findings mean and which release rules apply. We agree the validation and operational controls for your custom version before it is used for those decisions.

What does Enterprise DNA charge? expand_more

One setup fee, then a monthly retainer. Sam scopes the data migration, calculations, reports, connections and ongoing operation around your actual process. There is no invented saving or fixed package price on this page.

Show Sam the review your team repeats every week

In a 30-minute call, walk through one worksheet, the limits you use and the investigation it creates. Sam will scope the version your business needs and the work to bring it across.

Book 30 minutes with Sam Get the free version

Process Statistics for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Minitab?

Get your version built