The tools that make your sustainability work repeatable
DEISO builds the calculators, data systems and models your team runs every cycle — life-cycle costing engines, product carbon footprint calculators, Scope 1–3 data collection systems, LCA inventory tools.
Designed by people who actually do the science, not generic developers.
Most sustainability work is rebuilt from zero every cycle
The method was right. The numbers were right. But it lived in one person's spreadsheet, and next year the whole thing starts again — new files, new assumptions, new questions from the reviewer. A tool fixes that permanently.
- Every product carbon footprint is a paid one-off study
- Emission factors sit in three spreadsheets, none of them agreeing
- Scope 1–3 data is chased by email, plant by plant, every year
- Nobody can reproduce last year's number when the reviewer asks
- The method leaves when the consultant's contract ends
- Your team produces the footprint in-house, as often as needed
- One governed factor set, with the source recorded against each entry
- Data comes in through a fixed workflow that flags gaps as they happen
- Every result traces back to its input, its factor and its assumption
- The method stays in your company, because it is built into the tool
The value is not the software. It is the sustainability method locked inside it, so the right answer comes out the same way every time.
The life-cycle costing and total-cost-of-ownership engine
Purchase price is the smallest part of what an asset costs. The engine takes a product, an asset or a process and builds its full cost picture across the life cycle — acquisition, operation, maintenance, energy, replacement, end of life — using the same system boundary logic your environmental assessment already uses.
A general software supplier cannot build this, because the difficulty is not the code. It is knowing what a life-cycle cost boundary is, where the standard puts each cost category, and which assumptions a reviewer will question.
What it does for your team
- Builds the cost model with the life-cycle stages already structured, so nobody has to decide the layout from scratch
- Compares options side by side — two designs, two suppliers, two maintenance strategies — on the same cost basis
- Shows where the cost actually sits, so the conversation moves from purchase price to lifetime cost
- Keeps every assumption visible and recorded next to the number it produced
- Runs on your desktop, with your data staying inside your organisation
Built in, not bolted on
The engine is in active development and is shown as a working demonstration rather than a shipped product. What you see in a demonstration is the real application running on real structure — we will tell you plainly which parts are complete and which are still being built.
Where a tool sits, and what changes because of it
A tool on its own is a screen. What makes it worth building is the method inside it and the system around it — that is the part your team keeps.
Stage one — what happens inside the tool
Your data goes in
- Plant and site activity data
- Supplier and procurement records
- Energy, materials, transport
- Cost and asset information
The method does the work
- System boundary already set the way the standard requires
- Emission factors governed, with source and version held against each one
- Weak or missing data flagged as it enters, not discovered at the end
- Every assumption recorded next to the number it produced
The result comes out
- Footprint, inventory or cost model
- Traceable back to every input
- In the structure a reviewer expects
- Repeatable next cycle, same way
Stage two — where it sits in the DEISO operating system
This is why the tools are not a separate service. They are layer three of the operating system we build — and the layer almost nobody else can build, because it needs the science and the software in the same hands.
The hard part is the method, not the screen
Designed by people who actually do the science, not generic developers.
- Asks you to specify the method, then builds exactly what you specified
- Cannot tell you that a system boundary is wrong, because it does not know what one is
- Treats an emission factor as a number in a field, not as something that needs a source and a version
- Has never sat opposite a verifier and been asked to defend a result
- Leaves you owning a tool that works and an output the reviewer rejects
- Brings the method with us — ISO 14040, 14044, 14067, GHG Protocol already understood
- Corrects the boundary and the assumptions before a line of the tool is designed
- Builds factor governance in, because we know what an unsourced factor costs you later
- Builds for the review, having sat on both sides of it
- Leaves you owning a tool whose output holds up when it is questioned
This is why the tools sit inside our sustainability work rather than beside it. An operating system needs something to run on — we build that part ourselves.
Compare the three build plans
Every tool is built to your scope, so each plan is quoted rather than priced from a list. The table below shows what is included at each level — the method inside the tool, what it does with your data, and what your team owns at the end.
Every capability in this section is the same across all three plans.
| Capability | Standard Quotation based 21 of 40 capabilities A working tool for one repeatable job — the spreadsheet your team rebuilds every cycle, turned into software your team owns. Request a quotation → | Professional Quotation based 27 of 40 capabilities For teams whose data arrives from several systems and whose results are read outside the team — wider import and export, assumption records, and fuller control. Request a quotation → | Enterprise Quotation based 39 of 40 capabilities For work that is reviewed, verified, or audited — standards alignment, full traceability, the method inside the tool, and the controls a data policy requires. Request a quotation → | Enterprise+ Quotation based 40 of 40 capabilities Everything in Enterprise, with the source code handed to your organisation — for teams that need to maintain, extend, or audit the tool with their own developers. Request a quotation → |
|---|---|---|---|---|
| Scope and standards | 1 of 3 | 1 of 3 | 3 of 3 | 3 of 3 |
| The tool is built for whichever sustainability work your team repeats — GHG accounting and Scope 1–3 data collection, product carbon footprint, LCA inventory, life-cycle costing, emission factor inventories, ESG evidence, or another domain you name. The method behind it changes with the domain; the way it is built does not. | Standard | Professional | Enterprise | Enterprise+ |
| The tool is built and documented against whichever standard your work has to satisfy — ISO 14040, 14044 and 14067, the GHG Protocol, EN 15804, PCRs, and sector or programme standards among them. Boundaries, categories, and calculation rules follow that standard rather than a general software convention, and the documentation is written so a reviewer or verifier can see which requirement each part answers. | Standard | Professional | Enterprise | Enterprise+ |
| Capability specific to your domain, industry, and scope — the advanced calculations, rules, and workflows the work actually needs, rather than a fixed feature list. What these are is decided during the method and scope step, because they differ between a carbon footprint tool, a life-cycle costing engine, and a supplier data system. | Standard | Professional | Enterprise | Enterprise+ |
| Method and traceability | 0 of 4 | 1 of 4 | 4 of 4 | 4 of 4 |
| Every assumption is recorded next to the number it produced, with the reasoning behind it. When a result is questioned months later, the answer is in the tool rather than in someone’s memory or a separate note. | Standard | Professional | Enterprise | Enterprise+ |
| Every result traces back to the input, the factor, and the assumption behind it. A reviewer can follow any number to its source without asking your team to reconstruct how it was produced. | Standard | Professional | Enterprise | Enterprise+ |
| The method sits alongside the calculation — what the standard requires, where each boundary falls, and why the tool does what it does. The team learns the method while using the tool rather than being trained on it separately. | Standard | Professional | Enterprise | Enterprise+ |
| A visual view of how the model fits together — the items, the flows between them, and what depends on what. It shows the structure behind the numbers rather than a decorative diagram, and changing a relationship changes the underlying record. Available where the tool has a structure worth showing; not every tool does. | Standard | Professional | Enterprise | Enterprise+ |
| Data in and out | 2 of 6 | 5 of 6 | 6 of 6 | 6 of 6 |
| Bring in the data your team already holds. The tool imports from Excel — activity data, supplier records, cost and asset registers, factor tables — so nobody re-types what already exists in a spreadsheet. Structure and column mapping are set during the build, against the files your team actually uses. | Standard | Professional | Enterprise | Enterprise+ |
| Import from CSV as well as Excel, for data coming out of an ERP, a plant system, a supplier portal, or any export that does not arrive as a workbook. | Standard | Professional | Enterprise | Enterprise+ |
| Take the results out as Excel. The output keeps the structure the tool produced — results, inputs, factors, and assumptions — so the numbers can be read, checked, or built on outside the tool without being re-typed. | Standard | Professional | Enterprise | Enterprise+ |
| Export to CSV as well as Excel, for feeding results into a reporting platform, a database, or another system that takes a plain data file rather than a workbook. | Standard | Professional | Enterprise | Enterprise+ |
| Produce the result as a PDF for reporting, review, or filing. The layout carries the same structure as the on-screen output, so what a reviewer receives matches what the team produced. | Standard | Professional | Enterprise | Enterprise+ |
| Search finds the right entry even when the spelling is not exact, and suggests matches as you type. Useful in tools holding long lists — process names, factor sets, suppliers, materials — where an exact match is slow to type and easy to get slightly wrong. | Standard | Professional | Enterprise | Enterprise+ |
| Storage, backup, and recovery | 4 of 6 | 4 of 6 | 6 of 6 | 6 of 6 |
| The tool runs on your desktops and writes to your own storage. Nothing is held on DEISO infrastructure, so your activity data, costs, supplier information, and results stay inside your organisation and under your own IT policy. | Standard | Professional | Enterprise | Enterprise+ |
| Work files sync through whichever cloud service your organisation already uses — Dropbox, OneDrive, Google Drive, or another. The tool writes to a folder on your machine and the service handles the rest, so nothing is stored on DEISO infrastructure and your data stays under your own IT policy. The service is installed and managed by you. | Standard | Professional | Enterprise | Enterprise+ |
| The tool keeps point-in-time snapshots of the work as it syncs, so a previous state can be recovered if a file is overwritten, a change needs to be undone, or a reviewer asks what the model looked like at an earlier date. Snapshots sit alongside the live file in your own cloud folder. | Standard | Professional | Enterprise | Enterprise+ |
| Backups run on a schedule you set — hourly, every few hours, daily, every few days, weekly, or monthly. Each backup is written to your own storage, so a working file can be recovered without depending on anyone remembering to save a copy. | Standard | Professional | Enterprise | Enterprise+ |
| Backups can be written to a second location outside the working folder — another drive, a network share, or a separate cloud folder — so a copy survives if the working folder is lost, overwritten, or synced badly. | Standard | Professional | Enterprise | Enterprise+ |
| Return the tool to a clean state, in one action. Studies, data, settings, backups, and synced copies are erased together, so nothing is left behind on the machine or in the sync folder. Built for cases where sensitive data has to be removed on demand — a device changing hands, a project closing, or a data-handling policy that requires it. | Standard | Professional | Enterprise | Enterprise+ |
| Working in a team | 1 of 3 | 1 of 3 | 3 of 3 | 3 of 3 |
| Move a complete study to another person or machine — data, structure, assumptions, and evidence together, not as loose files. One person can build a model and hand it to a colleague to continue, review, or check, with nothing lost in between. | Standard | Professional | Enterprise | Enterprise+ |
| The tool can be set to require a password on opening, so the data inside it is not available to anyone with access to the machine. Optional, and switched on at your request. | Standard | Professional | Enterprise | Enterprise+ |
| Training on the tool for the people who will run it — how it works, how the method behind it works, and how to keep it running each cycle. Included with Enterprise. Available on the other plans as a separate quoted item. | Optional, quoted | Optional, quoted | Included | Included |
| The application | 7 of 11 | 9 of 11 | 11 of 11 | 11 of 11 |
| The tool is built as a Windows desktop application. It runs on your machines, and your data stays inside your organisation rather than on DEISO infrastructure. | Windows | Windows | Windows | Windows |
| The tool ships as a proper installer, so it can be deployed by your IT team the way any other application is, and removed cleanly when needed. | Standard | Professional | Enterprise | Enterprise+ |
| The tool is named for your organisation and presented as your software throughout — in the installer, the window title, the application itself, and the outputs it produces. | Standard | Professional | Enterprise | Enterprise+ |
| The tool carries your branding — logo, colours, and naming — across the interface and the outputs it produces. It reads as your company’s own software, not as a DEISO product with your name on it. | Standard | Professional | Enterprise | Enterprise+ |
| A branded screen appears while the tool loads, carrying your logo and the application name. | Standard | Professional | Enterprise | Enterprise+ |
| The tool sits in the Windows system tray with your logo, and its menu gives quick access to the actions your team uses most without opening the full window. | Standard | Professional | Enterprise | Enterprise+ |
| Switch the interface between light and dark. Useful for long working sessions, low-light environments, and teams whose machines follow a system-wide appearance setting. | Standard | Professional | Enterprise | Enterprise+ |
| Standard covers the settings a user needs day to day — appearance, file locations, backup schedule, and defaults. Advanced adds control over how the tool behaves: calculation options, workflow rules, data handling, and the parameters an administrator sets once for the whole team. | Standard | Advanced | Advanced | Advanced |
| Help sits inside the tool rather than in a separate manual — what each screen does, what each field expects, and how the workflow runs. A new team member can find the answer where the question comes up. | Standard | Professional | Enterprise | Enterprise+ |
| Guidance sits next to the feature it explains — what this screen is for, what to do next, and what the field expects. It works alongside the help page rather than replacing it, so a new user learns the tool while using it rather than reading about it first. | Standard | Professional | Enterprise | Enterprise+ |
| A page inside the tool recording what it is — version, build, who it was made for, and the DEISO contact for support. It tells anyone opening the tool later exactly which build they are looking at. | Standard | Professional | Enterprise | Enterprise+ |
| Support and ownership | 6 of 7 | 6 of 7 | 6 of 7 | 7 of 7 |
| Updates are made on request rather than shipped on a schedule. When you need a change — a new factor set, a revised standard, a workflow adjustment, an added feature — it is quoted and built as a small piece of work. The tool you own keeps running as it is until you ask for a change. | On request | On request | On request | On request |
| New capability can be added to the tool after handover — another calculation, another data source, another output, another workflow. Each addition is scoped and quoted as its own piece of work, so the tool grows as your sustainability work does rather than being fixed at the day it shipped. | Quoted separately | Quoted separately | Quoted separately | Quoted separately |
| Support after handover is arranged as a separate agreement — response times, scope, and duration set to what your team needs. The tool is yours to run; support is there for when something needs DEISO rather than your own IT. | Quoted separately | Quoted separately | Quoted separately | Quoted separately |
| When something does not behave as expected, the tool records what happened so the cause can be found without guesswork. Basic covers error logging and a readable report you can send to DEISO. Advanced adds deeper diagnostics — the state of the model at the point of failure, and traces that let a problem be reproduced and fixed faster. | Basic | Advanced | Advanced | Advanced |
| If the tool stops unexpectedly, it records what it was doing at the time and produces a report you can send to DEISO. That report is what makes a fault reproducible, so it can be found and fixed rather than described. | Standard | Professional | Enterprise | Enterprise+ |
| Copyright in the software remains with DEISO LLC. Your organisation holds a licence to use the tool. | DEISO LLC | DEISO LLC | DEISO LLC | DEISO LLC |
| The full source code is handed to your organisation, so the tool can be maintained, extended, or audited by your own developers without depending on DEISO. What the licence permits is set in the agreement. | Standard | Professional | Enterprise | Enterprise+ |
Three steps, and you can stop after the first
No long procurement exercise to find out whether this is worth doing. The first step is a short working session that ends with something written down, and it commits you to nothing.
Tools session
We look at the work your team repeats every cycle — the spreadsheet everyone dreads, the study you keep re-commissioning, the data request that never arrives on time — and identify which part is worth building into a tool and which part is not.
Method and scope
We fix the method before the tool is designed — boundaries, factor sources, data structure, what the output has to satisfy and who will review it. This is the step a general supplier cannot do, and it is the step that decides whether the tool is trusted.
Build and hand over
We build the tool, test it against real data from your operation, and hand it over with your team trained to run it. The method stays in your company because it is inside the tool, not inside a consultant's head.
Scope varies too much for a list price to mean anything, so we do not publish one. What we can tell you at the end of step one is whether the tool is worth building at all — and we will say so if it is not.
Three steps, and you can stop after the first
No long procurement exercise to find out whether this is worth doing. The first step is a short working session that ends with something written down, and it commits you to nothing.
Tools session
We look at the work your team repeats every cycle — the spreadsheet everyone dreads, the study you keep re-commissioning, the data request that never arrives on time — and identify which part is worth building into a tool and which part is not.
Method and scope
We fix the method before the tool is designed — boundaries, factor sources, data structure, what the output has to satisfy and who will review it. This is the step a general supplier cannot do, and it is the step that decides whether the tool is trusted.
Build and hand over
We build the tool, test it against real data from your operation, and hand it over with your team trained to run it. The method stays in your company because it is inside the tool, not inside a consultant's head.
Scope varies too much for a list price to mean anything, so we do not publish one. What we can tell you at the end of step one is whether the tool is worth building at all — and we will say so if it is not.
Tell us the work your team repeats every cycle
That is all we need to begin. Name the spreadsheet, the study you keep re-commissioning, or the data request that never arrives on time, and we will tell you whether a tool solves it — including when it does not.
