feliXart

Service

Enterprise Software Development

The core system your company’s daily operation runs on.

We argue for a system shaped around how the company works, not a company reshaped around a package. Operations, planning, fleet, documents, accounts, invoicing and reporting come together on one data model; desktop, web and mobile all read from the same source. The system runs on your servers and the source code is yours — any dependency on the outside becomes your choice rather than a consequence of the architecture.

What it covers04

Operations core

Job records, status flow, planning screens and document management — where the daily work happens.

Finance layer

Accounts, invoicing, receivables and payables, income and expense, per-job profitability.

Integrations

Your existing software, e-invoicing provider, vehicle tracking, payments and third-party services all meet in one connection layer.

Roles and permissions

Unit-level authorisation, audit trail and separation of personal data under GDPR/KVKK.

Process04
01

Technical assessment

We review the existing system and processes on site; scope, boundaries and budget come out of that work.

02

Architecture and data model

We define where data is born and where the connection to the outside world sits, from the start.

03

Wave rollout

Each wave brings training, parallel running and output comparison; the switch is decided together.

04

Operate and hand over

We keep the live part standing while your team is trained inside the process.

FAQ05
Why build our own instead of buying an ERP?
If your processes fit a standard package, off-the-shelf is cheaper and we will say so plainly. The maths changes if you are constantly paying for customisation, finishing the job in Excel, or losing negotiating power at every licence renewal. The technical assessment puts the multi-year cost of both routes side by side.
Do we switch off the old software in one go?
No. The system goes live in waves; in each wave old and new run in parallel, outputs are compared, and the switch is decided together once the gap closes. We do not do irreversible cutovers.
Who owns the source code?
You do, once payment obligations are complete. Code is delivered at every phase acceptance and sits on your own servers, with unlimited rights to develop it with your own staff.
Will we be dependent on you afterwards?
The aim is the opposite. The people who will take the system over join while development is still running; when documentation, training and a handover rehearsal are done, operation moves to your side.
How long does it take?
An operations core is typically measured in months, a full transfer of processes closer to a year. A firm phase-by-phase timeline follows the technical assessment.

Is your operation running on software you do not own?

Let us review where you are, and cost the way out together.