Technology · Business Software
Custom business software.
The systems that carry daily operations: records, orders, approvals, planning and reporting.
When clients usually bring us in
- the existing system no longer keeps up
- the work happens in spreadsheets
- data is duplicated across systems
- you need a new application
- you want to modernise an old system
- you're building a new digital product
You don't always have to build from scratch
If the existing system can be properly modernised or connected to others, that's usually faster and cheaper than a new application. We start by looking at what's worth keeping.
What this means for you
- Fewer spreadsheets and manual status updates.
- Less duplicated data across systems.
- One view of the process for management and the team.
- A system that grows with the company.
- Less dependence on the one person who knows how it works.
Problem → solution
Typical modules
- CRM and sales process
- orders and quotes
- stock and inventory
- resource and shift planning
- approvals and internal requests
- records and registers
- reports and dashboards
When a company outgrows its tools
- the same data is entered into two or three systems
- the management report is assembled by hand every month
- nobody knows which document is the current one
- approvals run over email
- a new hire needs months to find their way
- data cannot be exported without the supplier
A rollout is an organisational project, not just a technical one
A system that works technically but nobody uses is not deployed. So the rollout also covers who owns the system, how people will be trained and what happens to the old way of working.
Current state
What is used today and where duplicate work arises.
Scope
Which part goes first and which waits.
Setup
Configuration, permissions, migration of existing data.
Trial
A small group of users doing real work.
Go-live
Switch-over with a firm date and support in the first days.
Maintenance
Fixes, additions and a review after a few months.
ERP or a custom system
This is the question we hear most often, and the honest answer is rarely “one or the other”. A standard ERP is good at what every company does the same way - accounting, purchasing, inventory, invoicing. A custom system makes sense for what sets your company apart, and for work that does not belong in the ERP.
| When | Solution |
|---|---|
| the process is standard for the sector | configure the existing ERP |
| the ERP covers it but people work around it | first find out why - often it is the rollout, not the system |
| the process is your competitive advantage | a custom system connected to the ERP |
| data is scattered across systems | integration, not a new system |
| work runs on email and spreadsheets | an application for that process, linked to the ERP |
So before quoting we look at what the ERP already does and what it does not. Anyone selling a new system before checking that is selling a system, not a solution.
Cloud or on-premise
Cloud
Faster rollout, no hardware of your own, access from several sites. Suitable when there are no special data-location requirements and connectivity is reliable.
On-premise
Data stays inside the company and the system keeps working when the internet fails. Suitable for production floors that cannot stop because of connectivity, and for strict security environments.
Hybrid
The part that must work on the line runs locally; reporting, management access and external integrations run in the cloud. The most common choice in larger companies.
HR processes: hiring, onboarding, planning
In larger companies HR processes often live in email: approving a new position, collecting documents at hiring, access rights, equipment, training, shift planning and leaving. Each step has its owner, but nobody sees the whole.
- approving a new position along a clear path
- an arrival checklist: access, equipment, training
- shift planning that respects absences and qualifications
- records of training and certificate validity
- an orderly exit: revoking access and returning equipment
Employee personal data requires role-based access and a record of who viewed what - this is part of the design, not an add-on.
What this page covers
Business software covers sales, finance, stock, documents, projects and reporting. We first check whether a standard ERP or product is enough. We propose custom development only for processes a standard tool cannot cover without expensive customisation.
How we build the system
Architecture
We define the data model, modules and system boundaries before development, so later growth doesn't require a rewrite.
UX/UI
You approve the user journeys and a prototype of the key screens before any feature is written.
Frontend and backend
The interface and the server side are built to one standard: readable code covered by automated tests.
Integrations
Connections to ERP, CRM, document systems and registries, with logging and retries.
Data
Migration, cleanup and data quality rules, so the new system doesn't inherit the old errors.
Security, quality, rollout
Security
Authentication and permissions, encryption in transit and at rest, an audit trail and a review before go-live.
Testing
Automated tests, regression and acceptance testing against your criteria, not ours.
Deployment
Separate environments, phased release and the ability to roll back within minutes.
Handover
Code, access, documentation and team training. The system stays yours.
Maintenance
An agreed response time, monitoring and a monthly allocation for enhancements.
Related work
FAQ
Can you extend our existing system instead of building a new one?
Yes. We first look at what is worth keeping; we propose new development only when modernisation isn't enough.
Who owns the code?
You do. At handover you receive the code, the access and the documentation.
What happens after go-live?
With an agreed response time, monitoring and a monthly allocation for enhancements.
Tell us what you need
A few sentences are enough: what you need, for which process or system and by when. We will reply by email.
Related solutions
Sounds like your project?
Send us the project description, your existing system, the tender documents or the event date.
Or email info@epix.si