ERP — ANALYSIS · BUILD · GO LIVE
ERP BUILT AROUND YOU
We don't resell licences for anyone else's system. We build ERP-class software around your processes — and say plainly when connecting what you already own would be cheaper.
WHAT WE DON'T DO, AND WHAT WE DO
We don't resell licences for anyone else's ERP, we are not a partner of any vendor and we have no boxed product to push. We build ERP-class systems tailored to a specific company's processes — for the cases where an off-the-shelf product would mean bending the company around somebody else's software.
A vendor of a packaged ERP earns on licences and on every module you add. We earn on the work on the system — so we have no reason to talk you into features you don't need. We do have a reason to build less rather than more: a smaller system is cheaper to maintain, for us as well.
The consequence goes further: the most common recommendation after an audit isn't „let us build you a system”. It is „stay with what you have and connect it to the rest” — because that is usually cheaper, faster and less risky.
CONNECT OR BUILD
This is the first decision and the most expensive one to get wrong. Below are the criteria we use in the audit — with no single universal recommendation, because the answer depends on what exactly hurts.
and connect WHEN THE PROBLEM IS AT THE SEAMS, NOT IN THE FEATURES
- The tools do what they should, they just don't talk to each other
- The biggest pain is re-typing data, not missing functionality
- People know the systems and work in them efficiently
- The vendors still develop and support them
- They can be connected over an API without acrobatics
your own WHEN THE COMPANY WOULD HAVE TO BEND AROUND THE SOFTWARE
- The process that is your advantage doesn't fit an off-the-shelf system
- Configuring a packaged product costs more than building your own
- You pay for dozens of modules and use three
- The vendor ended support or left the market
- Every change requires a ticket to the vendor and waits for months
Buying a packaged ERP from a vendor. Sometimes it is the best choice — particularly when the company's processes are standard and the industry has mature off-the-shelf options. We will say so plainly, even though we don't sell it and earn nothing from it.
Thirty minutes is usually enough to establish which side you are on — and whether the topic is worth opening at all this year.
HOW WE BUILD IT
We don't
build
everything
A tailored system doesn't mean writing from scratch everything the company has today. We start with the one area that hurts most and that off-the-shelf tools don't cover — the rest stays where it is and gets connected to it.
Accounting usually stays in a specialist package, and rightly so. There is no reason to write your own VAT handling when it is a solved problem governed by rules that change every year.
The code
and data
are yours
The repository, the documentation and access to the infrastructure belong to the client from day one, not at the end of the engagement. There is no licence we can withdraw and no data format you can't get out of.
We treat that as the condition for an honest conversation about custom software. If the only reason you stay with someone is that you can't leave, that isn't a partnership — it's a trap.
Data is harder
than the
system
The biggest surprise is never the software; it is the state of the data. The same customer in four versions, product codes assigned over the years by three different conventions, stock levels that don't match the shelf.
Migration is a separate stage with its own budget and deadline. Moving a mess into a new system produces the same mess, only more expensive.
In stages,
beside what
works
The first module goes live after a few months rather than a year, and starts saving time immediately. The old way of working runs in parallel until the new one proves it is better — there is no single day on which the whole company switches blind.
We use the same approach on every other project — described in more depth under digital transformation.
If you suspect the problem isn't a missing system but that your current tools don't talk to each other, look at system integration. And if you don't yet know which side of the fork you are on, the IT audit answers that.
FREQUENTLY ASKED
How does a tailored ERP-class system differ from a packaged ERP?
In the direction of the fit. A packaged ERP assumes a particular way of working and the company adapts its processes to it — an advantage when the processes are standard, an expensive drawback when doing something differently is your advantage.
A system built for the company goes the other way: it mirrors processes that already work and contains no modules you don't want to pay for. The price of that flexibility is a longer start and the need to maintain your own solution.
How long does building such a system take?
The first module in production usually 4 to 6 months after the decision, with process analysis and design taking the first 6–10 weeks. We don't build everything before going live — an area goes into use when it is ready and further ones follow.
The full scope typically spreads over a year or more, and that is normal. The single biggest risk to the schedule is the state of the data, not the programming.
Isn't building your own more expensive than buying?
At the start almost always, and we say so honestly. The difference shows up in later years: with a packaged system you pay licences for all users and all modules, including unused ones, and every non-standard change requires a ticket to the vendor.
So we cost both options over several years rather than over the first invoice. When the maths favours an off-the-shelf product, we say so — even though we earn nothing from it.
Would we become dependent on you as the only supplier?
The code repository, documentation and infrastructure access belong to the client from day one. We build on widely known technologies so another team can take it over — not only one that knows our habits.
That is a test worth running on any custom software supplier: ask what happens if you part ways in two years. If the answer is vague, you already know the risk.
When do you advise against building a custom system?
When the company's processes are standard and a mature packaged product exists for your industry. Building from scratch then means paying to recreate something somebody has already thought through, with no advantage gained.
We also advise against it when the real problem is a lack of data flow between existing tools. That is a job for integration — considerably cheaper and faster than a new system.
WE REPLY WITHIN 24 HOURS
LET'S START WITH A TALK
A free 30-minute consultation. No commitment and no sales rep — you talk to the person who will run your project.
JET LARK SP. Z O.O.
3 MAJA 22 / 2C
40-096 KATOWICE, POLAND
Thank you!
Your message has taken off. We'll get back to you within 24 hours — check your inbox (spam folder too, sometimes).