ENGAGEMENT
We show it on your data first, agree scope and price, then build.
A free one-week demo on your spreadsheets, a six-to-eight-week fixed-price build, then yearly maintenance and subscription. What you provide, what you get and how each step is judged.
HOW WE DELIVER
From the first workflow to what comes next.
One-week live-data demo
Your one or two spreadsheets on working screens, checked by the person who owns the numbers.
6–8 week fixed-price build
Scope and price agreed in writing, then permissions, alerts and connections built.
Maintenance and subscription
Updates and change requests, and the next workflow added the same way.
Instead of a paper assessment, your spreadsheets on screen within a week
Evaluation starts from a screen running your data, not a proposal. The one-week demo is free, and you decide whether to continue after seeing it. The build follows at a fixed price over six to eight weeks, and is then run under a yearly maintenance and subscription agreement.
Step 1. Free one-week demo on your data
| You provide | You get | How the next step is decided |
|---|---|---|
| One or two spreadsheets for the target workflow, one owner | The workflow on screen with your items and codes | Your owner checks the numbers against their spreadsheet |
| A 30-minute kickoff call | A code mapping table and a list of data issues found | Mismatches and their causes are reviewed together |
| One demo meeting | Proposed build scope and fixed price | You decide whether to proceed |
The demo usually takes one week, and up to two for larger data sets. The demo is free. If the data does not fit the workflow, we tell you what else is needed, or we do not propose a build.
Step 2. Six-to-eight-week fixed-price build
| You provide | You get | Acceptance |
|---|---|---|
| Full data for the workflow, a business owner | Screens, permissions and alerts for the agreed scope | Judged against acceptance criteria agreed at kickoff |
| Users and roles | Role-based accounts and approval settings | Real users process real cases from start to finish |
| How your systems export data | Intake from your ERP and MES, with reconciliation | Quantities, units and dates match the source records |
| Where it runs (Giz cloud or your servers) | Installation, administrator guide, handover | Your administrator runs it with the handed-over procedures |
Scope and price are fixed in writing before work starts. Anything outside scope is agreed separately; the price does not change without agreement. Capabilities marked as validated during the build are checked on your data in this step before they go live.
Step 3. Maintenance and subscription
| You provide | You get | How it runs |
|---|---|---|
| One operations contact | Updates, fixes and support | Support hours and response are set in the contract |
| A list of change requests | Small changes to rules and screens | Every change is recorded |
| The next workflow to move | Scope and fixed price for it | Each new workflow starts with its own one-week demo |
Workflows are added one at a time, each checked in a demo first and built as its own package.
What we need for the first week
- One or two spreadsheets for the target workflow. Masked names and suppliers are fine.
- One person who does that work every day
- A 30-minute call to walk through the data
Talk to us · Shortages and expediting · On-premises deployment
YOUR NEXT STEP
Bring us the workflow that needs to work.
Start with the files and systems you use today, and the work you want to change.