04 · Software & Systems
Custom software, interfaces and integrations for processes that standard tools do not solve properly. From the data model to operation, and only where building is genuinely the right path.
01 How you recognise it
Three starting points we see regularly. One of them is enough.
It lives in spreadsheets, email chains and workarounds that everyone in the team follows differently.
CRM, ERP and specialist applications do not know each other. Data gets copied instead of transferred.
Several tools together create more friction and cost than one suitable solution of your own.
02 What you get
Configure, integrate, automate or build, with cost and consequences for each option. Standard where standard is enough.
The data model first, then a first production version that runs in daily work and grows with the feedback.
Monitoring, handover and training are part of the project. Source code, data and access belong to you.
03 What it looks like
Schematic example with fictitious data
Before any synchronisation comes the question of which system wins in a contradiction.
| Object / field | Leading system | Direction | Trigger | Conflict rule |
|---|---|---|---|---|
| Company · name, address | ERP | ERP → CRM | Change in the ERP | ERP overwrites; the CRM change is logged |
| Company · industry, segment | CRM | CRM → ERP | Change in the CRM | CRM overwrites |
| Contact · email, phone | CRM | CRM → ERP | Change in the CRM | CRM overwrites; empty values never overwrite |
| Customer · payment terms, credit limit | ERP | ERP → CRM (read only) | Nightly synchronisation | Not editable in the CRM |
| Order · status | ERP | ERP → CRM | Status change in the ERP | ERP overwrites |
Empty values never overwrite filled ones. Without that rule the first incomplete synchronisation deletes maintained data.
When it fits
Your tools do not represent an important process, and workarounds have become the habit.
What a first step delivers
A basis for the decision: configure, integrate, automate or build, with effort and consequences for each path.
What we need from you
A description of the process, access to the systems involved and your requirements for operation and data protection.
We only need these accesses and documents once we start working together. For a first conversation, a short description of your situation is enough.
04 Decision
The right answer is rarely “everything from scratch”. We climb the ladder from the bottom and stop at the step that solves the problem.
Can an existing system represent the process?
Set up standard software properly: objects, fields, permissions, workflows. The cheapest path, as long as the process fits the standard.
Step 1 of 4Is only the connection between systems missing?
Synchronise data between CRM, ERP, marketing tools and specialist applications, through standard interfaces, APIs or a lean middleware.
Step 2 of 4Is the process clear but manual?
Automate flows with rules, triggers and AI steps, on automation platforms or as a service of our own.
Step 3 of 4Does no standard solve the core of the problem?
Custom software or a product of your own: when the process is your competitive advantage or no tool represents it cleanly.
Step 4 of 405 Definition
Custom software is worth it when a process is business critical and no standard product represents it without compromises, or when combining several tools creates more friction than one solution of your own.
The opposite holds just as much: nobody builds their own accounting, email or standard CRM. The craft lies in the boundary between the two. FIOXX draws it based on process, data model and operating cost, not on what is easier to sell.
System integration connects applications so that data flows between them automatically and by rules, with a defined leading system per data object, error handling and monitoring.
Typical cases: CRM and ERP, shop and inventory management, marketing tool and CRM, specialist application and document storage. The value appears when nobody retypes data and every department sees the same picture.
06 Services
Applications for processes standard tools do not represent, from the data model to the production interface.
Products for many users: multi-tenant, maintainable, with operation and evolution in mind.
Interfaces between systems that run stably, report errors and are documented.
Customer, order and master data in one picture, without double entry.
Bring data from several sources together, clean it and make it usable for reporting and AI.
Internal processes with owners, status and approvals, as an application of your own instead of an email chain.
Small, targeted tools for teams: dashboards, input forms, checking tools, quick and precisely fitted.
Operation, data storage and security where it suits the use case, including hosting in the EU.
07 How we work
Six principles that shape every software project at FIOXX.
Before we build interfaces we clarify which objects, relationships and states the process really has. A good data model outlives every UI.
We only build what makes a difference. For everything else we use proven components, platforms and services.
Every integration has a description, error handling and monitoring. Nothing runs “somehow in the background”.
Logging, backups, updates and access are part of the design, not an addition after go-live.
Source code, data and access belong to you. Documentation and handover are part of every project.
First usable versions early, feedback from daily work, then extension. No months of specification without software.
08 Software × products
Under the IYOS brand FIOXX works on LinkedIn marketing for B2B companies and develops its own software for it. Our own ventures keep us honest: they force us to build software that stays maintainable and works in daily use. The same standards we apply to customer projects.
09 FAQ
When the process is a competitive advantage, when no standard represents it without contortions, or when combining several tools becomes more expensive and more error-prone than one solution of your own. We check that honestly and recommend the standard when the standard is enough.
With modern, widely used web and cloud technologies that can be operated long term and taken over by other developers. The specific choice follows the requirements, the existing landscape and the operating model, not fashion. We justify every decision in writing.
You decide: FIOXX can take on operation and further development, or we hand over to your team or your IT provider, with documentation, access and training. The source code belongs to you in any case.
For us software is never an end in itself. It comes into being because a sales process, a revenue system or an AI application needs it. That way we know the context it is used in and build accordingly pragmatically.
Next step
We look at your process and your system landscape and say honestly whether configuring, integrating, automating or building is the right path.