Getting funded.

Run your own numbers in the ROI estimate, then take the total to whoever signs off.

01
Discover
A call that ends with one line picked.
02
Start on one line
Success measures agreed up front.
03
Scale line by line
Add lines, shifts and modules as results come in.
04
Supported after go-live
Hypercare, then Help Center tickets.

Book a 30-minute discovery call How pricing works

ROI estimate

Change the numbers below to match your plant.

01Time saved → headcount

Hours no longer spent on manual tallies, chasing updates, and building reports and meeting packs.

Hours saved per person (h a week)

People who use it

Working weeks a year

Hours in a full-time year

Fully loaded cost per FTE ($ a year)

Show the workingHide the working

Hours saved a week × people × weeks ÷ hours in a full-time year = FTE freed. FTE freed × cost per FTE = value a year.

3 h × 12 people × 48 weeks = 1,728 h a year

1,728 h ÷ 2,080 h = 0.8 FTE

1,728 h ÷ 2,080 h × $85,000 = $70,615

0.8 FTE freed$70,615 a year

02Productivity gain → recouped OEE losses

Good output won back from availability, performance and quality losses on the lines you run.

Lines

Planned production hours per line (h a year)

Value of one hour of good output ($ an hour)

OEE points recovered

Value of one hour, at full rate: your margin on it, not its sales price, gives a stricter number.

OEE points: Line 4 in our examples runs 6.6 points under its 78.0% goal. The default takes back under a third of a gap like that.

Show the workingHide the working

Lines × planned hours per line × OEE points recovered ÷ 100 = hours of good output won back. Those hours × the value of one hour = value a year.

2 lines × 6,000 h × 2.0 points ÷ 100 = 240 h

240 h × $1,500 = $360,000

240 h of good output$360,000 a year

Estimated value a year$430,615

Time saved $70,615 + productivity $360,000

Optional: your annual quote ($ a year)

Only if you already have one. It turns the estimate into a payback time.

An estimate from the numbers above, not a quote or a promise. Results depend on the plant: its lines, its people and its data. Plant Toolbox does not guarantee any saving.

A quote built around your business.

We look at what your business needs and the size of your organization, then build your quote from the parts below. It comes in writing before you add a line, a shift or a module.

PartHow it is counted

Plants

Each plant that runs Plant Toolbox. You start with one line at one plant.

Modules

The modules each plant turns on. We suggest starting with the Core 4: Operations, Autonomous Maintenance, Action Planning and Loss Elimination.

Users

The people who sign in, from operators to the plant manager.

Integrations

Links to an ERP or LIMS. Each one is scoped with you before work starts.

AI usage

Only if you switch AI on. Metered against credits you control.

Deployment

What happens once your quote is agreed, in order, with the timing planned around your modules, users and devices.

Before go-live

Step 1: Staging environment

We set up a staging site where Plant Toolbox is configured and tested before anything goes live.
2
Step 2: two steps at the same time
- 2a Training
  
  Key-user training
  
  Your key users learn to run and manage Plant Toolbox, so they can shape the configuration with us.
- 2b Data
  
  Data preparation
  
  Lines, products, standards and equipment lists are cleaned for loading. The spreadsheets you already keep are a fine start.
3
Step 3: two steps at the same time
- 3a Configuration
  
  Production environment configuration
  
  The live site is set up to match how your plant runs: lines, shifts, goals and boards.
- 3b Data
  
  Initial data load (staging)
  
  Prepared data goes into staging first, so it is checked before it reaches the live site.
4
Step 4: two steps at the same time
- 4a Training
  
  End-user training
  
  Operators, leads and support teams learn the screens they will use on their shift.
- 4b Data
  
  Additional data load (staging)
  
  The rest of the data goes into staging, with the fixes the first load showed.
Step 5: Data load (production)

Checked data moves from staging into the live site.

Go-live and after

Step 6: Go-live

Your team runs its shifts in Plant Toolbox. The last go-live task is a full shift your team runs on its own.
Step 7: Hypercare

Intensive support straight after go-live. Issues are picked up and fixed quickly while the first shifts run.
Step 8: Ongoing support

Support carries on in the Help Center: open a ticket from the screen you are on, and read release notes in the app.

Tell us which line you would start with.

Name the line, the shifts it runs and the number that keeps missing. We will show you what its next eight hours would look like in Plant Toolbox.

Propose your first line Schedule a demo

Write to us instead

Discover

Start on one line

Scale line by line

Supported after go-live

ROI estimate

Step 1: Staging environment

Key-user training

Data preparation

Production environment configuration

Initial data load (staging)

End-user training

Additional data load (staging)

Step 5: Data load (production)

Step 6: Go-live

Step 7: Hypercare

Step 8: Ongoing support

Tell us which line you would start with.