We use necessary cookies to make the site work. With your consent we also use optional cookies to understand how the site is used and to measure our marketing. You can accept, reject, or choose what to allow.
Read our Privacy Policy for the full list of cookies.
We turn the data your ERP already holds into reports and apps for everyday work.
The ERP itself usually works. The hours go on what people do around it by hand: reports, spreadsheets and retyping. We fix each of these on its own, without a big project.
Only one person knows how to pull that report. When they are on holiday, everyone waits.
Report unavailable: Only one person knows how to pull that report. When they are on holiday, everyone waits.
How we fix itThe report arrives by itself, every morning at 7:00
It is built from data your ERP already holds and sent to whoever needs it, so nobody waits for a colleague to come back.
The licence is only part of the cost. The rest is on no invoice: it is the hours your team spends working around the ERP.
68% of that cost is not on any invoice
Based on 46 working weeks a year.
Upheave pulls the data out of your ERP, builds apps for everyday work and helps you replace it when that pays off.
We combine reports and spreadsheets into one view you can trust: dashboards and reports that build themselves, with no manual work.
The right choice when the data exists, but getting to it takes manual work.
First version in 3 to 4 weeks
Field entry, approvals, production planning and links to your website and other systems. Your ERP stays as it is.
The right choice when people work around the ERP because it does not fit their job.
One process at a time
We define with you what the new ERP has to do, compare the offers and move the data over with a transition period.
The right choice when the vendor has stopped developing the system or licences grow faster than the value.
Estimate after analysis
One job, one simple tool, using data your ERP already has. Pick a job and see what it looks like.
Bills of materials and stock across all warehouses on one screen. For every product you see at once how many you can make and what will run out first.
Describe it and we will tell you whether an app for it is worth building.
Two companies on the same ERP. Capacity was calculated by hand in a spreadsheet; today the planner sees it on one screen.
Before: Capacity was worked out by hand, in a spreadsheet with formulas that broke easily.
After: For every product, how many they can make and what runs out first, in seconds.
Before: Someone retyped the two companies' data from one spreadsheet into another.
After: Both companies in one place, with their shared warehouses and suppliers.
Before: Three stock reports overlapped, so the same goods were counted twice.
After: One stock report instead of three, with no double counting.
Before: Nobody could see in advance what open work orders would use up.
After: Work orders visible in advance, and production simulated before it starts.
The ERP did not need replacing. The way people worked with it did.
Your whole business lives in the ERP, so we never touch it without agreement. We agree every step before we take it.
We build on any ERP that supports
We do not change it or work around it. The app reads from it, and writes to it only where we have explicitly agreed it should.
For every figure in the app you can see which report or record it came from, so you can trust the numbers.
If your ERP can save a CSV or Excel file, we can build on it, even without an API. Messy spreadsheets, old formats and local date formats are normal for us.
Data from your ERP is never sent to outside AI services. Where the app and the data live is agreed before the first line of code.
You tell us which question your ERP cannot answer and where your team loses time. The call is free.
We go through the reports and spreadsheets you use today and tell you what can be done with them.
We build a tool for one job and put it into use with your real data.
Once the first app pays off, we pick the next job or look at replacing the ERP.
What companies most often ask us before the first call.
Usually not. Replacing an ERP is expensive, risky and slow, and the problem is rarely the data itself. It is how people get to it. So we start by building a layer next to the ERP you already run. If we conclude on the call that replacing it really is the better choice, we will tell you and help you make the move.
The first call is free, and after it you get the scope and a cost estimate in writing. The price depends on what we build and what we connect to, so we do not make it up in advance. You can compare the estimate with what that work costs you today, for example in the calculator on this page.
A first app for one job is usually in use within 3 to 4 weeks, after a few days of looking at the data. Integrations that write into the ERP, and replacing the system, take longer; we estimate those after an analysis.
If your ERP can save a CSV or Excel file, or has an API, yes, whoever makes it. If there is no API, we work with the reports you already export, and can automate that later so nobody has to pull them by hand.
It should not. The app as a rule only reads data from the ERP and does not touch its settings. Where it needs to write data into the ERP, it uses the interfaces the ERP provides for that, which we agree with you in advance.
Power BI and similar tools show data. The app we build also does the maths: it tells you how much you can make and what runs out first, and takes entries, approvals and simulations. If all you need is a report, we will tell you.
Usually only the data mapping needs adjusting, not the whole app. The app reports an error when a report's format changes, instead of quietly writing the wrong data.
When the vendor no longer develops the system, when licences and maintenance grow faster than the value, or when the business needs something the old system cannot support even with add-ons. Then we define the requirements with you, compare the offers and plan the data migration so the business keeps running.
Write the question, or the job that takes most of your time today. We will come back with a proposal for what is worth fixing first.
Who you will talk to
Boris SeverCo-founder & Partner
Building software since 2019, from Zagreb, Croatia.
Prefer email? Write to us at office@upheave.tech.
